http://bugzilla.novell.com/show_bug.cgi?id=612006 http://bugzilla.novell.com/show_bug.cgi?id=612006#c2 --- Comment #2 from M Cook 2010-06-06 19:22:08 UTC --- Removing vif from the config file has resulted in another complaint... this is similar to other threads I've read circa 2006 on xen configuration on opensuse. Eg: Error: Device 768 (vbd) could not be connected. Hotplug scripts not working. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=612006 http://bugzilla.novell.com/show_bug.cgi?id=612006#c4 --- Comment #4 from M Cook 2010-06-07 17:43:50 UTC --- Additional info/debugging here: http://lists.xensource.com/archives/html/xen-users/2010-06/msg00240.html Also found this thread which may be similar but not sure: http://lists.xensource.com/archives/html/xen-users/2010-06/msg00000.html -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=612006 http://bugzilla.novell.com/show_bug.cgi?id=612006#c6 --- Comment #6 from M Cook 2010-06-08 13:32:26 UTC --- I've noticed there is an Oops everytime I start the VM. XEN starts up and xend-debug has: linux-oit2:/var/log/xen # tail -f /var/log/xen/xend-debug.log Xend started at Tue Jun 8 09:18:39 2010. /usr/lib64/python2.6/site-packages/xen/xend/XendAPI.py:551: DeprecationWarning: object.__new__() takes no parameters return object.__new__(cls, *args, **kwds) Then when I issue xm create <VM name> I see: linux-oit2:/etc/xen/vm # xm create WinXP_sp3.hvm Using config file "./WinXP_sp3.hvm". Message from syslogd@linux-oit2 at Jun 8 09:27:16 ... kernel:[ 693.223052] Oops: 0000 [#1] SMP Message from syslogd@linux-oit2 at Jun 8 09:27:16 ... kernel:[ 693.223061] last sysfs file: /sys/devices/xen-backend/vif-1-0/uevent Message from syslogd@linux-oit2 at Jun 8 09:27:16 ... kernel:[ 693.223413] Stack: Message from syslogd@linux-oit2 at Jun 8 09:27:16 ... kernel:[ 693.223454] Call Trace: Message from syslogd@linux-oit2 at Jun 8 09:27:16 ... kernel:[ 693.223620] Code: 48 3d 00 f0 ff ff 49 89 c5 0f 87 87 00 00 00 48 89 c2 48 c7 c6 e5 cf 88 a0 48 89 ef 31 c0 e8 45 41 99 df 4c 89 ef e8 4d c4 87 df <49> 8b 94 24 50 01 00 00 48 89 ef 48 c7 c6 ef cf 88 a0 31 c0 31 Message from syslogd@linux-oit2 at Jun 8 09:27:16 ... kernel:[ 693.223758] CR2: 0000000000000150 Started domain WinXP-SP3 (id=1) Attached is the dmesg output with the OOPs. [ 693.222999] BUG: unable to handle kernel NULL pointer dereference at 0000000000000150 [ 693.223015] IP: [<ffffffffa0889a63>] netback_uevent+0x73/0x100 [netbk] [ 693.223038] PGD 189cef067 PUD 189d30067 PMD 0 [ 693.223052] Oops: 0000 [#1] SMP [ 693.223061] last sysfs file: /sys/devices/xen-backend/vif-1-0/uevent [ 693.223068] CPU 2 .. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=612006 http://bugzilla.novell.com/show_bug.cgi?id=612006#c8 --- Comment #8 from M Cook 2010-06-08 14:22:12 UTC --- NULL ptr work in progress: http://lists.xensource.com/archives/html/xen-devel/2010-05/msg01590.html -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=612006 http://bugzilla.novell.com/show_bug.cgi?id=612006#c10 Thomas Richard changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |thomas9999@gmail.com --- Comment #10 from Thomas Richard 2010-06-12 22:37:12 UTC --- I have the very same problem. Running opensuse 11.3m7 as well. Everything you describe is exactly the same for me. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=612006 http://bugzilla.novell.com/show_bug.cgi?id=612006#c12 --- Comment #12 from M Cook 2010-06-18 14:49:31 UTC --- 11.3 RC1 - dom0 launching a domU has exactly the same behaviour with fresh install (hotplugin scripts not working). - xm create still has a crash wrt vif configuration - general networking manager seems more stable and automatic Giving up. Moving to some other virtualisation technology on Ubuntu. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=612006 http://bugzilla.novell.com/show_bug.cgi?id=612006#c14 --- Comment #14 from M Cook 2010-06-20 19:16:38 UTC --- (In reply to comment #13)

I have this issue too on openSUSE factory with xen-4.0.0_21091_05-4.1

I can start network-enabled VM only once after reboot host system, next tryies to launch vm gives me "Error: Device 0 (vif) could not be connected. Hotplug scripts not working."

The vif hotplug scripts not working is the first error I encountered. If you remove the VIF statement, which isn't very useful I agree, you end up with another hotplug not working error on the disk missing. I may have the disk wrongly specified or options missing? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=612006 http://bugzilla.novell.com/show_bug.cgi?id=612006#c16 Vittorio Manfredini changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vittorio@vitsoft.bz --- Comment #16 from Vittorio Manfredini 2010-07-22 10:48:03 UTC --- The problem it's related to kernel version 2.6.34-12.3 (same problem on sles11sp1 there is a ptf now). Try the latest kernel from kotd (kernel of the day) could help. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=612006 http://bugzilla.novell.com/show_bug.cgi?id=612006#c18 --- Comment #18 from M Cook 2010-07-29 17:38:41 UTC --- I found this x-ref http://lists.xensource.com/archives/html/xen-users/2010-07/msg00547.html to this bug report via my xen-users post http://lists.xensource.com/archives/html/xen-users/2010-06/msg00307.html. I am not sure what relevance RHEL vs Ubuntu has in Fajar & Boris' conversation (perhaps Ubuntu == OpenSUSE) but it seems/implies the kernel should have statically linked in "backend Dom0 drivers" instead of loadable kernel modules. Vittorio: do you know if the released version of opensuse 11.3 is any better. I'm guessing not as I believe its using 2.6.34-x. I can't downgrade to 11.2 without loosing driver/kernel support for W510 laptop. I would really appreciate this working. I have made some progress in getting XEN4.0 dom0 running in ubuntu environment. I couldn't get the xend or xenfs to come up though. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=612006 http://bugzilla.novell.com/show_bug.cgi?id=612006#c20 Boris Derzhavets changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bderzhavets@yahoo.com --- Comment #20 from Boris Derzhavets 2010-07-29 20:20:17 UTC --- I am not a Suse's expert, but Jan Beulich will be out of office until 08/05/2010. Looks like kernel at "kotd" page, i mentioned above ( ftp://ftp.suse.com/pub/projects/kernel/kotd/openSUSE-11.3/x86_64/ ) , has Jan's patch already applied and works with udev 157 on 11.3. This page seems to be updated on daily basis. I just downloaded current xen-kernel. Installed Xen host from DVD and installed new kernel :- # rpm -ivh kernel-xen-2.6.34.1-0.0.17.fdda44d.x86_64.rpm Grub entry would be created automatically. Reloaded system works fine:- 1. virt-install to create PV or HVM DomU 2. virt-manager to manage PV or HVM DomU My limited experience is absolutly positive. No problems with HVM domus as i got after udev downgrade 157->151. However, I cannot issue any warranty until Jan will confirm , that kernel is OK with udev 157. In meantime i would test it in QA or testing environment. Boris. 07/29/10 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=612006 http://bugzilla.novell.com/show_bug.cgi?id=612006#c22 --- Comment #22 from M Cook 2010-07-30 21:33:54 UTC --- I have opensuse 11.3 with kotd kernel now installed on my W510 laptop. I am trying to recompile the xen4-testing.hg source to try out 4.0.1rc5. I've added the c/c++ patterns and dev86 packages. Then "make xen" works. Calling "make tools" bombs out in two places: a) can't find: stub-32.h header file at /usr/src/gnu/ b) can't find: /usr/include/bits/predef.h Can anyone point me to a set of instructions for opensuse 11.3 build of XEN source? The XEN 4.0 source wiki instructions worked fine with Ubuntu. Not the case with opensuse. ;o( -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=612006 http://bugzilla.novell.com/show_bug.cgi?id=612006#c24 --- Comment #24 from M Cook 2010-08-04 14:09:13 UTC --- Forgot to add, I also see this when I attempt to start xend (manually): mcook@linux-z7hf:/etc/xen> sudo /etc/init.d/xend start Traceback (most recent call last): File "/usr/sbin/xend", line 36, in <module> from xen.xend.server import SrvDaemon File "/usr/lib64/python2.6/site-packages/xen/xend/server/SrvDaemon.py", line 20, in <module> import xen.lowlevel.xc ImportError: libbz2.so.1.0: cannot open shared object file: No such file or directory .. .. This is repeated several times for 20-30secs then stops displaying on cmd line. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=612006 http://bugzilla.novell.com/show_bug.cgi?id=612006#c26 --- Comment #26 from Boris Derzhavets 2010-08-04 14:50:27 UTC --- (In reply to comment #23)

Continuing with XEN 4.0 in OpenSUSE 11.3 and kotd (Linux linux-z7hf.site 2.6.34.1-0.0.18.cbab77c-xen #1 SMP 2010-07-29 14:00:26 +0200 x86_64 x86_64 x86_64 GNU/Linux) I have found the following error when I attempt to connect to the system using the XEN VirtManager:

Unable to open connection to hypervisor URI 'xen:///': unable to connect to 'localhost:8000': Connection refused Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/connection.py", line 971, in _try_open None], flags) File "/usr/lib64/python2.6/site-packages/libvirt.py", line 111, in openAuth if ret is None:raise libvirtError('virConnectOpenAuth() failed') libvirtError: unable to connect to 'localhost:8000': Connection refused

The above message repeats many times on the console, then a box pops up.

When I attempt to create a VM I get a pop-up-box wiht "Error: None" in it and nothing more.

Comment out (xend-unix-server yes) in /etc/xen/xend-config.sxp and export variable export VIRSH_DEFAULT_CONNECT_URI="xen:///" in root’s .bashrc. Then reboot Xen Host. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=612006 http://bugzilla.novell.com/show_bug.cgi?id=612006#c28 --- Comment #28 from Boris Derzhavets 2010-08-05 10:05:45 UTC ---

I dont see their defn's in VirtualManager panel until they are running. I can successfully connect using the console/vnc session.

Perform guest install via virt-install. What's wrong with default bridge "br0" installed along with Xen package ? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=612006 http://bugzilla.novell.com/show_bug.cgi?id=612006#c30 --- Comment #30 from M Cook 2010-08-05 14:29:21 UTC --- So I uninstalled all xen-related packages booted into a non-dom0 opensuse kernel and reinstalled XEN hypervisor from YAST. Then followed your blog steps stepping around the domU tools package problems. I also found that smpppd package doesn't like hte xen kernel and haven't managed to install it (with deps still intact). I found the hypervisor bridge-configuration step this time seems to have mapped eth0 to br1. On starting my ubuntu HVM it presents eth4 which now has bridged access to the LAN. Yay! I am assuming br1 was chosen because the network configuration in hypervisor found several potential network interfaces. It created a br2, although this is presumably for the wifi link. I have not touched YAST Network configuration tool since but it seemed easily confused or just broken. Perhaps XEN based nw configuration is required to link up guests with host interfaces. A remaining puzzle is why the guest screen is 400x320 and where I may be able to configure this to something larger? Or should I just run a vncserver within guest? I will also continue to work wiht multiple nw interfaces as one of the guests needs two NIC interfaces. Thanks for your suggestions and help though Boris! -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=612006 http://bugzilla.novell.com/show_bug.cgi?id=612006#c32 --- Comment #32 from M Cook 2010-08-05 18:02:00 UTC --- I noticed that the networking in YAST Network manager panel now says br0 is mapped to wlan0, br1 to eth0 and br2 to eth1 (DLINK adapter). I think this is 'as expected' and I have all HVM and PV guests up with network connectivity. Will continue to monitor stability but this finally seems to be functional. Screen updates & networking is rather slow but hey, you'd think I'd be happy! ;o) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=612006 https://bugzilla.novell.com/show_bug.cgi?id=612006#c34 --- Comment #34 from M Cook 2010-08-21 12:46:29 UTC --- Related KOTD thread: https://bugzilla.novell.com/show_bug.cgi?id=623286#c12 And http://lists.xensource.com/archives/html/xen-users/2010-08/msg00478.html -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=612006 https://bugzilla.novell.com/show_bug.cgi?id=612006#c39 Michal Zugec changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |mzugec@novell.com InfoProvider| |michaelcook_mjc@yahoo.com --- Comment #39 from Michal Zugec 2010-10-18 12:32:35 UTC --- First of all, please attach yast logs from bridge setup -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=612006 https://bugzilla.novell.com/show_bug.cgi?id=612006#c42 wei wang changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |CLOSED InfoProvider|michaelcook_mjc@yahoo.com | Resolution| |NORESPONSE --- Comment #42 from wei wang 2011-01-26 06:02:00 UTC --- I close it because no response ,please reopen it if you can provide more information about this issue,thank you . -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.