https://bugzilla.novell.com/show_bug.cgi?id=859361 https://bugzilla.novell.com/show_bug.cgi?id=859361#c13 Olaf Hering <ohering@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|ohering@suse.com | --- Comment #13 from Olaf Hering <ohering@suse.com> 2014-02-20 10:21:35 CET --- I think its possible to have a single disk image for several VM types, for testing purpose. But nothing in our code actually takes care of such setup. So the code should take care of the following: native (includes KVM and Hyper-V guest) native dom0 xen PV dom0 xen PV domU xen HVM xen HVM is like native, expect that it has /proc/xen. Look at /lib/mkinitrd/scripts/setup-fv_guest.sh. One possible method of detection is to see if /sys/class/dmi/id exists. If it does exist and product_name == "HVM domU" and sys_vendor == "Xen", then its HVM and just kernel-default has to be considered. Maybe one day HVM can do nested virt and maybe it would be possible to run dom0 inside a HVM guest. If thats ever possible, I'm sure there will be other attributes to check for that. For the time being the check above is good. xen PV domU or dom0 can be found by /proc/xen/capabilities, if it contains "control_d" its a dom0. Otherwise its a domU. and native dom0 can be found by checking if the kernel can actually act as a dom0, by looking at its .config. There are probably ways to poke around in the binary and look for certain capabilities, but that requires additional tools to extract that info. Does that answer the question? -- 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.