http://bugzilla.opensuse.org/show_bug.cgi?id=909547
--- Comment #19 from Wilson Hein
Ok, we've verified you can connect to libvirtd. Are you now seeing the same problem as noted in the original description? Are you unable to create new VMs through virt-manager? Can you successfully create new VMs with xl, by-passing virt-manager and libvirt?
With the recently rebuilt libvirt I do not see the errors. Currently I have 2 guests running, 1 pvm using opensus13.2 and 1 hvm running Win7. However if I reboot the host, I can easily recreate the errors, because the guests fail after a reboot. Example If I cleanly rebuild libvirt, and not create any guest VMs, and reboot the host, VM creation fails with errors. Untested recently, I believe that in this condition xl create, or vm-install with the usexl switch would likely fail as well. I first came across this issue when I was using opensuse12.3 with working guest VMs, and upgraded to version 13.1. At that point the system would have been still using xend to handle libvirt instructions. As I investigated I found out about the depreciation of xend, and started re-configuring my system too work with libxl. about this time opensuse13.2 was released, and I upgraded again in hopes that it would resolve the problem, which it did not. Through a lot of trial and error, I developed the process I'm currently using to cleanly rebuild libvirt which is documented in the opensuse forums links I provided, where I've been documenting my progress, and or mostly my lack there of. As long as I don't reboot the host the guest VMs function correctly in virt-manager. What remains my question is what happens after a host reboot with xen/libxl/libvirt/etc. that breaks the system.
For the reporter jean-paul: Is the original issue you reported fixed by the libvirt and xen packages in Virtualization:openSUSE13.2 project?
http://download.opensuse.org/repositories/Virtualization:/openSUSE13.2/ openSUSE_13.2/
-- You are receiving this mail because: You are on the CC list for the bug.