[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] how to create a full-virtualization xen VM with autoyast

  • To: xen-users@xxxxxxxxxxxxx
  • From: Alexandre Kouznetsov <alk@xxxxxxxxxx>
  • Date: Tue, 19 Mar 2013 19:41:49 -0600
  • Delivery-date: Wed, 20 Mar 2013 01:42:59 +0000
  • List-id: Xen user discussion <xen-users.lists.xen.org>


El 19/03/13 19:00, Jing Chen escribió:
Can you help to clarify what is difference between vmlinuz-xenpae.sles11.sp2
and hvmloader? can full-virtualization VM be create using
vmlinuz-xenpae.sles11.sp2  and initrd like Para-virtualization VM.

A fully virtualized DomU does not care about guest system's kernel or initrd. It does not even provide a boot loader for it. It attempts to emulate a whole computer, and the guest system is booted as if it where on a normal host. So, a fully virtualized DomU can not be created using a kernel and initrd files, as PV DomU.

In case of a PV DomU, the guest kernel interacts directly with Xen's low level hypervisor.

In case of HVM DomU, there is an additional layer between guest kernel and the hypervisor: qemu. Hvmloader's job is "to load all the necessary information that qemu will use to build the necessary environment that will "fool" an unmodified guest that he is in fact on a physical machine is needed by qemu".


As you may see, PV and HVM guests works in a quite different manner. If, by chance, they are configured and run in a similar way, that is because there is wrapper for that.
(If I'm wrong, please somebody correct me.)


Alexandre Kouznetsov

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.