Re: [Xen-devel] paravirtualized guest OS

[Mark Williamson <mark.williamson@xxxxxxxxxxxx>]

> 1) When we install guest linux inside Xen using paravirtualization, how
> actually guest linux code is modified. Whats the actual process.

The guest isn't modified during installation.  Paravirtualised guests are 
adapted by developers in order to take advantage of Xen features.  In the 
case of Linux, folks at Cambridge University and XenSource wrote most of the 
code to do this.  Linux distributions leverage this code in order to make 
their own products Xen-aware.

When you install a guest using Yast, the Yast Xen module ensures that a 
Xen-aware kernel is installed into the virtual machine.

> 2) I am using suse 10.2. After installing xen package which comes with it,
> the new boot menu "SUSE (XEN)" gets added up. What are the difference
> between the kernel which runs this SUSE-XEN & original kernel.

The new boot menu option starts the Xen hypervisor (which is the first code to 
run at boot time), which in turn starts the Linux kernel for "domain 0".  
Domain 0 uses a paravirtualised Linux kernel which is responsible for 
controlling Xen, managing other domains, providing virtual devices, etc.

> I am new to Xen. So curious about knowing this.

Hope that helps!

Cheers,
Mark

-- 
Dave: Just a question. What use is a unicyle with no seat?  And no pedals!
Mark: To answer a question with a question: What use is a skateboard?
Dave: Skateboards have wheels.
Mark: My wheel has a wheel!

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel