[opensuse-virtual] XEN on a 13.1 system
Hi all, Are there any known issues with 13.1 as a DOM0 ? @work, i installed+updated a new system, added XEN-tools + XEN-kernel, enabled bridging, verified with "xm list" that all was up-and-running. But when trying to create a domU (with the yast2-module) no show. First issue was that an ubuntu-client needed hw-virtualisation (which was disabled in the bios), but after tweaking that, still no show. Next i tried sles11sp3 (thus using paravirt.) but same problem. Disabled graphic-emulation, still fails. (sorry for the briefness, no access to those systems here athome) Is there anything i should tweak on 13.1? On 12.1 and 12.2 it worked out-of-the-box... Hans -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
Hans Witvliet wrote:
Hi all,
Are there any known issues with 13.1 as a DOM0 ?
@work, i installed+updated a new system, added XEN-tools + XEN-kernel, enabled bridging, verified with "xm list" that all was up-and-running.
xm/xend is on the way out. xl/libxl (aka libxenlight) is on the way in, and the default Xen toolstack in 13.1 See the following bug for some details, in particular comment#11 https://bugzilla.novell.com/show_bug.cgi?id=857271 I also recently wrote a blog post about libvirt's use of the old and new Xen toolstacks http://jfehlig.wordpress.com/2014/01/05/libvirt-support-for-xens-new-libxenl... Regards, Jim
But when trying to create a domU (with the yast2-module) no show. First issue was that an ubuntu-client needed hw-virtualisation (which was disabled in the bios), but after tweaking that, still no show.
Next i tried sles11sp3 (thus using paravirt.) but same problem. Disabled graphic-emulation, still fails. (sorry for the briefness, no access to those systems here athome)
Is there anything i should tweak on 13.1? On 12.1 and 12.2 it worked out-of-the-box...
Hans
-- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
Also, make sure there no appamor config install for Xen, I have seen appmor cause a lot of issues. Chuck On Thu, Jan 16, 2014 at 11:20 AM, Jim Fehlig <jfehlig@suse.com> wrote:
Hans Witvliet wrote:
Hi all,
Are there any known issues with 13.1 as a DOM0 ?
@work, i installed+updated a new system, added XEN-tools + XEN-kernel, enabled bridging, verified with "xm list" that all was up-and-running.
xm/xend is on the way out. xl/libxl (aka libxenlight) is on the way in, and the default Xen toolstack in 13.1
See the following bug for some details, in particular comment#11
https://bugzilla.novell.com/show_bug.cgi?id=857271
I also recently wrote a blog post about libvirt's use of the old and new Xen toolstacks
http://jfehlig.wordpress.com/2014/01/05/libvirt-support-for-xens-new-libxenl...
Regards, Jim
But when trying to create a domU (with the yast2-module) no show. First issue was that an ubuntu-client needed hw-virtualisation (which was disabled in the bios), but after tweaking that, still no show.
Next i tried sles11sp3 (thus using paravirt.) but same problem. Disabled graphic-emulation, still fails. (sorry for the briefness, no access to those systems here athome)
Is there anything i should tweak on 13.1? On 12.1 and 12.2 it worked out-of-the-box...
Hans
-- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
-- Terror PUP a.k.a Chuck "PUP" Payne (678) 636-9678 ----------------------------------------- Discover it! Enjoy it! Share it! openSUSE Linux. ----------------------------------------- openSUSE -- en.opensuse.org/User:Terrorpup openSUSE Ambassador/openSUSE Member Community Manager -- Southeast Linux Foundation (SELF) skype,twiiter,identica,friendfeed -- terrorpup freenode(irc) --terrorpup/lupinstein Register Linux Userid: 155363 Have you tried SUSE Studio? Need to create a Live CD, an app you want to package and distribute , or create your own linux distro. Give SUSE Studio a try. www.susestudio.com. See you at Southeast Linux Fest, June 7-9, 2013 in Charlotte, NC. www.southeastlinuxfest.org -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
On Thu, 2014-01-16 at 09:20 -0700, Jim Fehlig wrote:
Hans Witvliet wrote:
Hi all,
Are there any known issues with 13.1 as a DOM0 ?
@work, i installed+updated a new system, added XEN-tools + XEN-kernel, enabled bridging, verified with "xm list" that all was up-and-running.
xm/xend is on the way out. xl/libxl (aka libxenlight) is on the way in, and the default Xen toolstack in 13.1
See the following bug for some details, in particular comment#11
https://bugzilla.novell.com/show_bug.cgi?id=857271
I also recently wrote a blog post about libvirt's use of the old and new Xen toolstacks
http://jfehlig.wordpress.com/2014/01/05/libvirt-support-for-xens-new-libxenl...
Regards, Jim
But when trying to create a domU (with the yast2-module) no show. First issue was that an ubuntu-client needed hw-virtualisation (which was disabled in the bios), but after tweaking that, still no show.
Next i tried sles11sp3 (thus using paravirt.) but same problem. Disabled graphic-emulation, still fails. (sorry for the briefness, no access to those systems here athome)
Is there anything i should tweak on 13.1? On 12.1 and 12.2 it worked out-of-the-box...
Hans
Hi Jim, Nice reading, both of them.. Yes, i forgotten that xm/xend is depreceated. Heard that a couple of times at several fosdems from Ian, and when you mention "xm" at the xen-lists you are considered a relic from a distant past.... How ever: When you do a fresh instalation of the xen-stuff in 13.1, and you try to create a VM like one is used to do in previous versions, i still got a warning that i had to check because "xend was not running" btw the message i got when trying to build it from yast was: "Error Failed to start the vm, Details: Error, device0 (VIF) could not be connected. Hotplug scripts are not working" The vif-thing, i wonder if that might have something todo with the admin-unfriendly names, the network devices got since 13.1. having said that, bridge br0 is up-and-working and eth en!@#$%^ device is attached to it...
Hans Witvliet wrote:
Yes, i forgotten that xm/xend is depreceated. Heard that a couple of times at several fosdems from Ian, and when you mention "xm" at the xen-lists you are considered a relic from a distant past....
How ever: When you do a fresh instalation of the xen-stuff in 13.1, and you try to create a VM like one is used to do in previous versions, i still got a warning that i had to check because "xend was not running"
Charles, is there a check in {vm,virt}-install for xend running? I vaguely recall something along those lines, but suppose it was fixed long ago. WRT libvirt, If xend is disabled and libvirtd is restarted, it will use the libxl driver, and never fail or warn due to "xend not running".
btw the message i got when trying to build it from yast was: "Error Failed to start the vm, Details: Error, device0 (VIF) could not be connected. Hotplug scripts are not working"
I think this is due to a mis-configured toolstack. We've also fixed a number of bugs since 13.1 was released. I assume you have all the latest updates? You can also check for relevant fixes that are queued for the next update in our 13.1 maintenance project https://build.opensuse.org/project/show/Virtualization:openSUSE13.1 Regards, Jim -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
On Mon, 2014-01-20 at 19:29 -0700, Jim Fehlig wrote:
Hans Witvliet wrote:
Yes, i forgotten that xm/xend is depreceated. Heard that a couple of times at several fosdems from Ian, and when you mention "xm" at the xen-lists you are considered a relic from a distant past....
How ever: When you do a fresh instalation of the xen-stuff in 13.1, and you try to create a VM like one is used to do in previous versions, i still got a warning that i had to check because "xend was not running"
Charles, is there a check in {vm,virt}-install for xend running? I vaguely recall something along those lines, but suppose it was fixed long ago.
WRT libvirt, If xend is disabled and libvirtd is restarted, it will use the libxl driver, and never fail or warn due to "xend not running".
btw the message i got when trying to build it from yast was: "Error Failed to start the vm, Details: Error, device0 (VIF) could not be connected. Hotplug scripts are not working"
I think this is due to a mis-configured toolstack. We've also fixed a number of bugs since 13.1 was released. I assume you have all the latest updates? You can also check for relevant fixes that are queued for the next update in our 13.1 maintenance project
https://build.opensuse.org/project/show/Virtualization:openSUSE13.1
Regards, Jim
Hi Jim, yes lastest patches were included (during installation). Is it worthwhile trying to add the stuff in: repositories/Virtualization:/openSUSE13.1/openSUSE_13.1/x86_64/ the libvirt rpm's are from 21-ste of januari ? hw -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
Hans Witvliet wrote:
On Mon, 2014-01-20 at 19:29 -0700, Jim Fehlig wrote:
Hans Witvliet wrote:
Yes, i forgotten that xm/xend is depreceated. Heard that a couple of times at several fosdems from Ian, and when you mention "xm" at the xen-lists you are considered a relic from a distant past....
How ever: When you do a fresh instalation of the xen-stuff in 13.1, and you try to create a VM like one is used to do in previous versions, i still got a warning that i had to check because "xend was not running"
Charles, is there a check in {vm,virt}-install for xend running? I vaguely recall something along those lines, but suppose it was fixed long ago.
WRT libvirt, If xend is disabled and libvirtd is restarted, it will use the libxl driver, and never fail or warn due to "xend not running".
btw the message i got when trying to build it from yast was: "Error Failed to start the vm, Details: Error, device0 (VIF) could not be connected. Hotplug scripts are not working"
I think this is due to a mis-configured toolstack. We've also fixed a number of bugs since 13.1 was released. I assume you have all the latest updates? You can also check for relevant fixes that are queued for the next update in our 13.1 maintenance project
https://build.opensuse.org/project/show/Virtualization:openSUSE13.1
Regards, Jim
Hi Jim,
yes lastest patches were included (during installation).
Is it worthwhile trying to add the stuff in: repositories/Virtualization:/openSUSE13.1/openSUSE_13.1/x86_64/ the libvirt rpm's are from 21-ste of januari ?
Yes, there are a few fixes for the libxl driver queued in that repo for the *next* 13.1 update. I.e., fixes that have yet to hit the 13.1 update repos. Regards, Jim -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
On 1/20/2014 at 07:29 PM, in message <52DDDBA2.5000908@suse.com>, Jim Fehlig <jfehlig@suse.com> wrote: Hans Witvliet wrote: Yes, i forgotten that xm/xend is depreceated. Heard that a couple of times at several fosdems from Ian, and when you mention "xm" at the xen-lists you are considered a relic from a distant past....
How ever: When you do a fresh instalation of the xen-stuff in 13.1, and you try to create a VM like one is used to do in previous versions, i still got a warning that i had to check because "xend was not running"
Charles, is there a check in {vm,virt}-install for xend running? I vaguely recall something along those lines, but suppose it was fixed long ago.
Yes. vm-install does check for a running xend. This is how it knows whether to use 'xm' to start VMs or if xend is not running it uses a libvirt connection to start VMs. The only time vm-install uses 'xl' for starting VMs is if xend is not running and it fails to connect to libvirt. Failure to connect could mean libvirtd was not running or some other error occurred when connecting to libvirtd. For virt-install, it only uses libvirt for starting VMs. It will try to default to a xen connection if '/var/lib/xend' and '/proc/xen' exist otherwise it looks to see if qemu/kvm is present and connects to that. With virt-manager, and the command line virt-install you can specify the connection you want and that is what virt-install will use assuming the appropriate libvirt driver was loaded. - Charles -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
participants (4)
-
Charles Arnold -
Chuck Payne -
Hans Witvliet -
Jim Fehlig