https://bugzilla.novell.com/show_bug.cgi?id=852473 https://bugzilla.novell.com/show_bug.cgi?id=852473#c1 --- Comment #1 from Romain Pelissier 2013-11-27 14:46:35 UTC --- Created an attachment (id=569340) --> (http://bugzilla.novell.com/attachment.cgi?id=569340) Some logs Here a some logs generated by xen, libvirt and an extract of messages (journalctl in fact) with some errors in there. -- 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=852473 https://bugzilla.novell.com/show_bug.cgi?id=852473#c3 Romain Pelissier changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High --- Comment #3 from Romain Pelissier 2013-11-28 22:26:26 UTC --- I have install a new server to test again Xen. So here are the steps I use. * Install minimal server * Configure ip, update server * use lvm system At this point, server is ready and accessible and can download updates. * In yast search xen pattern and install what is recommended by yast * quit yast, run yast * Now, the visualization option is there * Select install Xen * Accept for dowloading additional rpm * Yast asks about using command line versus graphical components for Xen, let say no (keep it simple) * yast complain about a conflict with python lib and opensuse minimal pattern * I let yast remove the opensuse minimal pattern and let it install whatever it wants * Yast want to configure the bridge interface. Seem to working to much so I quit and re enter yast and the configuration for the network seems to be good * Reboot * I have the xen kernel * try vm-install and got the same issue: I can't create any vm. -- 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=852473 https://bugzilla.novell.com/show_bug.cgi?id=852473#c5 Charles Arnold changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |FIXED --- Comment #5 from Charles Arnold 2013-12-02 14:32:30 UTC --- (In reply to comment #4)

I have done the following:

zypper ar -f │http://download.opensuse.org/repositories/Virtualization/openSUSE_13.1/ XEN and then zypper dup --from XEN

Now it seems to work. But I rather having it work using the official repositories

This is the devel repo from which we submit to the official os13.1 repo. Pulling from here isn't necessarily bad and what you have are the fixes that will eventually make it out to the update channel. These changes have been submitted. There were some specific fixes in libvirt interacting with libxl (xen) that resolved some problems (note that vm-install uses libvirt when starting the VM). If apparmor is enabled, there were also some libvirt permission problems fixed. -- 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=852473 https://bugzilla.novell.com/show_bug.cgi?id=852473#c7 --- Comment #7 from Charles Arnold 2013-12-02 15:27:27 UTC --- (In reply to comment #6)

Thanks for those information, I am happy to heard that I am not stuck with a repo that even if it fixes some of the issue I have, is not the production one. So do you suggest that I remove the XEN repo I have just added so all future updates will be available in production repo?

You should keep the production repo. Keeping the XEN repo is optional but should be ok if you want to get (slightly) earlier access to fixes. This repo is just a staging area for submitting a maintenance request to the production repo. -- 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.