https://bugzilla.novell.com/show_bug.cgi?id=857271 https://bugzilla.novell.com/show_bug.cgi?id=857271#c2 James Fehlig changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |carnold@suse.com, | |cyliu@suse.com, | |jfehlig@suse.com --- Comment #2 from James Fehlig 2014-01-07 01:52:27 UTC --- (In reply to comment #0)

Steps to Reproduce: Prerequisites: Run virt-manager over a TCP connection.

You can run it over an ssh connection too.

Box A (the xen host) has to have xend/libvirtd running on a xen-aware kernel. Networking has to be taken away from xend so that it doesn't interfere with libvirtd, then set the network type to routed.

Why must xend be running? In openSUSE13.1, we've moved to the new libxl toolstack. The old xm/xend toolstack is deprecated upstream and slated for removal. I recommend disabling/removing xend and restarting libvirtd so that it loads and uses the new libxl driver.

Register the hd of the system as a storage pool (physical drive) - this requires that a free partition exists on that device!

Do you mean a libvirt disk storage pool (http://libvirt.org/storage.html#StorageBackendDisk) ? Yes, that requires a phyiscal disk.

Register the CD or DVD ROM as a storage pool (pre-formatted fs).

This isn't really necessary. You should be able to select an ISO or physical cdrom in the install tool (vm-install or virt-install).

Box B (without any virtualization) only has virt-manager running as a remote control for xend/libvirtd on box A (connection type xen).

1. Fire up the VM installation wizard and follow all steps. 2. Choose the physical optical drive as installation media. 3. Select one of the empty hd partitions for the VM's mass storage

FYI, as an option you can have vm-install (or virt-install) create an image file to serve as a disk for your virtual machines. If you do need to use libvirt storage pools, the directory or filesystem pool may be a better choice, since you won't consume hard drive partitions with each VM.

Error message returned (from virt-manager): Installation konnte nicht fertiggestellt werden: «POST-Operation schlug fehl: xend_post: Fehler von xen-Daemon: (xend.err 'Error creating domain: Block device type "qemu" is invalid.')»

Can you disable xend, restart libvirtd, and try another installation? -- 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=857271 https://bugzilla.novell.com/show_bug.cgi?id=857271#c4 Olaf Martens changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|olafmartens@web.de | --- Comment #4 from Olaf Martens 2014-01-07 15:13:49 UTC --- (In reply to comment #2)

[...] Why must xend be running? In openSUSE13.1, we've moved to the new libxl toolstack. The old xm/xend toolstack is deprecated upstream and slated for removal. I recommend disabling/removing xend and restarting libvirtd so that it loads and uses the new libxl driver. That somehow breaks libvirtd. See below for reasons...

[...]

Can you disable xend, restart libvirtd, and try another installation? Yes - but the entire process fails when I do.

Unfortunately I cannot do anything when I take away xend - libvirtd may be starting, but it seems as if it still requires xend to be running (whenever I attempt to establish a connection to libvirtd with xend disabled, virt-manager, although it connects to the remote machine, doesn't display anything for Domain-0, and when I attempt to create a machine, this is met with two errors: Error I: Installation konnte nicht fertiggestellt werden: «Ende der Datei beim Lesen von Daten: Eingabe-/Ausgabefehler» Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 96, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/create.py", line 2022, in do_install guest.start_install(False, meter=meter) File "/usr/lib/python2.7/site-packages/virtinst/Guest.py", line 1251, in start_install noboot) File "/usr/lib/python2.7/site-packages/virtinst/Guest.py", line 1319, in _create_guest dom = self.conn.createLinux(start_xml or final_xml, 0) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2886, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: Ende der Datei beim Lesen von Daten: Eingabe-/Ausgabefehler *** Error II (following a moment later): Fehler beim Abfragen der Verbindung «xen+tcp://thorin@192.168.1.1/»: Interner Fehler: Client Socket ist geschlossen None - Attempting to install from an unregistered optical drive causes libvirtd to complain about unknown media. - The use of a physical partition for storage is intended. However, switching to a partition image (I have tried that for verification) would be met with success. - Taking xend out of the equation and starting libvirtd on its own causes some things to break (looks as if that still relies on xen to work, although I have taken away libvirt's xen plugin - also uninstalling the xen driver for libvirt would cause a degradation from x86_64 to i586). Switching to SSH yields the exact same results as TCP/SASL (when xend runs, Domain-0 is displayed, when not, Domain-0 is not to be seen and any installation attempt fails). The other drawback of SSH: When pubkey authentication is used, the mechanism fails. Unfortunately all this does not solve the problem caused by virt-manager (i e. qemu: is prepended to the path to the installation media)... -- 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=857271 https://bugzilla.novell.com/show_bug.cgi?id=857271#c6 --- Comment #6 from Olaf Martens 2014-01-07 18:42:00 UTC --- libvirt-daemon-driver-xen-1.1.2-2.14.2.x86_64 libvirt-daemon-driver-libxl-1.1.2-2.14.2.x86_64 libvirt-daemon-xen-1.1.2-2.14.2.x86_64 xen-libs-4.3.1_02-4.4.x86_64 xen-xend-tools-4.3.1_02-4.4.x86_64 ipset-kmp-xen-6.19_k3.11.6_4-2.1.9.x86_64 libvirt-daemon-driver-nwfilter-1.1.2-2.14.2.x86_64 xen-doc-html-4.3.1_02-4.4.x86_64 xen-tools-4.3.1_02-4.4.x86_64 xen-kmp-default-4.3.0_14_k3.11.6_4-1.3.x86_64 kernel-xen-3.11.6-4.1.x86_64 libvirt-client-1.1.2-2.14.2.x86_64 libvirt-daemon-1.1.2-2.14.2.x86_64 libvirt-daemon-driver-uml-1.1.2-2.14.2.x86_64 libvirt-daemon-driver-nodedev-1.1.2-2.14.2.x86_64 libvirt-daemon-config-nwfilter-1.1.2-2.14.2.x86_64 libvirt-daemon-qemu-1.1.2-2.14.2.x86_64 xen-kmp-default-4.3.1_02_k3.11.6_4-4.4.x86_64 libvirt-doc-1.1.2-2.14.2.x86_64 libvirt-python-1.1.2-2.14.2.x86_64 libvirt-daemon-driver-storage-1.1.2-2.14.2.x86_64 libvirt-1.1.2-2.14.2.x86_64 libvirt-daemon-driver-network-1.1.2-2.14.2.x86_64 libvirt-daemon-driver-qemu-1.1.2-2.14.2.x86_64 cloop-kmp-xen-2.639_k3.11.6_4-11.1.9.x86_64 libvirt-daemon-driver-secret-1.1.2-2.14.2.x86_64 libvirt-daemon-driver-lxc-1.1.2-2.14.2.x86_64 xen-4.3.1_02-4.4.x86_64 libvirt-daemon-driver-vbox-1.1.2-2.14.2.x86_64 libvirt-daemon-driver-interface-1.1.2-2.14.2.x86_64 -- 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=857271 https://bugzilla.novell.com/show_bug.cgi?id=857271#c7 --- Comment #7 from Olaf Martens 2014-01-08 00:00:24 UTC --- Created an attachment (id=573620) --> (http://bugzilla.novell.com/attachment.cgi?id=573620) XML dump fom virt-install (generated with option --print-step all) I finally managed to generate an XML dump of the desired VM configuration, and it looks as if the definition in line 27 isn't interpreted correctly (I have tried to generate the VM by use of virsh, but it complained the same way virt-manager did). I have tried to change the type to xen, but it got rejected with an error as well (invalid block device type "xen"). -- 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=857271 https://bugzilla.novell.com/show_bug.cgi?id=857271#c9 James Fehlig changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |olafmartens@web.de --- Comment #9 from James Fehlig 2014-01-08 02:18:32 UTC --- I'd still like to know why your setup doesn't work without xend. What do you mean by "Taking xend out of the equation and starting libvirtd on its own causes some things to break"? Does libvirtd fail to start if xend is not running? Again, xend is on the way out and probably won't even be included in 13.2, so I'm loath to debug problems with the latest virt-manager, virt-install, libvirt, etc. on top of an old xen toolstack. We need to get to the bottom of any unknown problems in the new toolstack. Thanks! -- 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=857271 https://bugzilla.novell.com/show_bug.cgi?id=857271#c11 James Fehlig changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |olafmartens@web.de --- Comment #11 from James Fehlig 2014-01-08 04:22:23 UTC --- (In reply to comment #10)

When I shut down xend, I am still able to fire up libvirtd (or keep an already running libvirtd up), but for some reason I am unable to deal with anything concerning virtualization (libvirtd simply refuses to create virtual machines, nor does it display any stats on existing VMs, not even dom0).

Does virsh work? E.g. 'virsh version'? Some background which might help: When you start libvirtd, it will attempt load any of the installed libvirt-daemon-driver-<hypervisor> modules. In the case of Xen, it will try libvirt-daemon-driver-xen first, which will only load if xend is running. It then attempts to load libvirt-daemon-driver-libxl, which will only load if xend is not running. So in theory, when libvirtd is started, only one of the Xen drivers will be loaded - all based on whether or not xend is running. One difference between the xend and libxl toolstacks is that the former supports the notion of managed or persistent domains, i.e. xend is stateful. On the other hand, libxl is stateless. By necessity, this difference is propogated to libvirt, where libvirt-daemon-driver-xen is stateless (xend maintains the state) and libvirt-daemon-driver-libxl is stateful. This might shed some light on why e.g. you would no longer see any of your non-running domains when moving from xend to libxl. The libvirt libxl driver must now do the job of xend and maintain domain state. But it must know about the domains first. One way to do that is export the domain XML using the old xend stack (xend+libvirt-daemon-driver-xen) and then import the domains into libvirt after moving to the libxl stack. E.g. with xend running for each dom virsh dumpxml > dom-name.xml stop xend restart libvirtd for each dom virsh define dom-name.xml I am concerned about your comment of not being able to create VMs, so we'll need to get to the bottom of that. Not seeing existing domains should be explained above. As for dom0, it is (currently) viewed as the host from libvirt's perspective, so not shown in the domain list. This behavior is similar to the qemu/kvm driver, along with some of the other hypervisor drivers like vmware and hyper-v. -- 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=857271 https://bugzilla.novell.com/show_bug.cgi?id=857271#c13 James Fehlig changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |olafmartens@web.de --- Comment #13 from James Fehlig 2014-01-08 16:13:17 UTC --- Can you install the libvirt-*-debuginfo packages, run libvirtd in gdb, and then get a backtrace when the segfault occurs? E.g. # gdb /usr/sbin/libvirtd <gdb> run -l .. segfault occurs .. <gdb> thread apply all bt If you don't feel comfortable with this, I can try to reproduce locally. Does the segfault occur when trying to create a domain with configuration like you posted in #7? -- 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=857271 https://bugzilla.novell.com/show_bug.cgi?id=857271#c Olaf Martens changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #573740|application/octet-stream |text/plain mime type| | -- 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=857271 https://bugzilla.novell.com/show_bug.cgi?id=857271#c16 James Fehlig changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |olafmartens@web.de --- Comment #16 from James Fehlig 2014-01-09 04:48:25 UTC --- Thanks for the backtrace. It appears domain create failed, which upon cleanup triggered the segfault. The segfault has already been fixed upstream and I've backported the patch to the 13.1 libvirt package and have it queued in our 13.1 maintenance project https://build.opensuse.org/package/show/Virtualization:openSUSE13.1/libvirt You can install the updated packages from the following repo? http://download.opensuse.org/repositories/Virtualization:/openSUSE13.1/openS... That should get you around the segfault so we can start looking into the failed VM creation. Perhaps you can try using vm-install and virt-install directly instead of launching them through virt-manager. By default, virt-manager uses virt-install. I'd be interested in knowing if vm-install works for 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.

https://bugzilla.novell.com/show_bug.cgi?id=857271 https://bugzilla.novell.com/show_bug.cgi?id=857271#c18 --- Comment #18 from James Fehlig 2014-01-09 16:12:54 UTC --- The updated packages are in http://download.opensuse.org/repositories/Virtualization:/openSUSE13.1/openS... but the version is lower (1.1.2-10.1.x86_64.rpm) even though they contain everything in 1.1.2-2.14.2.x86_64 + the segfault fix. You can compare the changelogs to verify that. AFAIK, I don't have much control over the release part of the version, i.e. the 10.1 or 2.14.2 parts in these examples. But when I submit those packages to the openSUSE maintenance process, the version will be set correctly before the updates are released in the official update repo. You should be able to install the packages by explicitly stating the version you want, e.g. 'zypper in libvirt-daemon-driver-libxl-1.1.2-10.1.x86_64'. BTW, once you get beyond the segfault, it would be really helpful to identify the XML configuration which causes VM creation to fail. Thanks. -- 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=857271 https://bugzilla.novell.com/show_bug.cgi?id=857271#c20 Olaf Martens changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|olafmartens@web.de | --- Comment #20 from Olaf Martens 2014-01-09 18:54:40 UTC --- Created an attachment (id=573887) --> (http://bugzilla.novell.com/attachment.cgi?id=573887) Log of failed VM installation attempt (w/o NIC installation) This is what happened from an install via virt-manager after I have removed the virtual NIC from the list of devices. -- 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=857271 https://bugzilla.novell.com/show_bug.cgi?id=857271#c22 Olaf Martens changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|olafmartens@web.de | --- Comment #22 from Olaf Martens 2014-01-10 07:28:15 UTC --- Created an attachment (id=573951) --> (http://bugzilla.novell.com/attachment.cgi?id=573951) XML dump of virt-manager (domain spec only) As far as the network definition is concerned, I used libvirt's default network config and edited it. I set the network from bridged to routed and also tossed out the <dhcp> ... </dhcp> section, because I already have a stand-alone DHCP daemon running on dom0 and dnsmasq therefore would complain (on top of that I want all DHCP activity to be handled by one entity alone). Here's what the network definition looks like (it is intended that the data traffic can be routed to any of the physical NICs present in the box): <network> <name>default</name> <uuid>8d9d9625-f7a8-4228-a403-629aa49595ea</uuid> <forward mode='route'/> <bridge name='veth0' stp='on' delay='0'/> <mac address='52:54:00:f2:98:68'/> <ip address='192.168.127.1' netmask='255.255.255.0'> </ip> </network> As far as the XML is concerned, I have attached it. -- 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=857271 https://bugzilla.novell.com/show_bug.cgi?id=857271#c23 Swamp Workflow Management changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| |maint:running:56039:moderat | |e --- Comment #23 from Swamp Workflow Management 2014-01-28 08:26:13 UTC --- The SWAMPID for this issue is 56039. This issue was rated as moderate. Please submit fixed packages until 2014-02-11. When done, please reassign the bug to security-team@suse.de. Patchinfo will be handled by security team. -- 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=857271 https://bugzilla.novell.com/show_bug.cgi?id=857271#c27 --- Comment #27 from Olaf Martens 2014-01-28 23:58:27 UTC --- UPDATE II: Added a missing <driver> tag to the domain's hd definition - and all the sudden the domain was generated! -- 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=857271 https://bugzilla.novell.com/show_bug.cgi?id=857271#c Swamp Workflow Management changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:running:56039:moderat |maint:running:56039:moderat |e obs:running:2560:moderate |e -- 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=857271 https://bugzilla.novell.com/show_bug.cgi?id=857271#c29 James Fehlig changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |olafmartens@web.de --- Comment #29 from James Fehlig 2014-02-25 03:23:33 UTC --- (In reply to comment #27)

Added a missing <driver> tag to the domain's hd definition - and all the sudden the domain was generated!

Did you add any name or type attributes on the <driver> element? E.g. <driver name='qemu' type='raw'/> -- 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=857271 https://bugzilla.novell.com/show_bug.cgi?id=857271#c31 James Fehlig changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |olafmartens@web.de --- Comment #31 from James Fehlig 2014-05-06 02:22:52 UTC --- I must admit, I'm confused about the status of this bug. Are things working well for you with latest openSUSE13.1 updates? -- 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=857271 https://bugzilla.novell.com/show_bug.cgi?id=857271#c Olaf Martens changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|olafmartens@web.de | -- 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.