Changes between Version 3 and Version 4 of Paravirtualization


Ignore:
Timestamp:
May 12, 2008, 4:05:52 AM (17 years ago)
Author:
andersk
Comment:

sipb-xen -> xvm

Legend:

Unmodified
Added
Removed
Modified

  • Paravirtualization

    v3 v4  
    11Xen supports two different types of virtualization: Hardware-supported virtualization (HVM) and paravirtualization (ParaVM).
    22
    3 Most sipb-xen VMs are initially created as HVMs. HVMs virtualize a full machine, down to the metal. They use special processor capabilities to do this. This allows you to run an unmodified operating system. For example, this is the only way to run Windows under Xen. However, I/O performance suffers as a result of this virtualization approach.
     3Most xvm VMs are initially created as HVMs. HVMs virtualize a full machine, down to the metal. They use special processor capabilities to do this. This allows you to run an unmodified operating system. For example, this is the only way to run Windows under Xen. However, I/O performance suffers as a result of this virtualization approach.
    44
    55ParaVMs on the other hand, modify the guest operating system to remove privileged operations, replacing them with calls to the Xen hypervisor. ParaVMs have significantly better performance, but require a modified kernel. Only a few operating systems have support for running as a paravirtualized Xen guest: Linux, NetBSD, OpenBSD, FreeBSD, and !OpenSolaris being the most well known.
    66
    7 The sipb-xen maintainers recommend that servers be converted to ParaVM when possible. Currently, we can offer instructions for upgrading 64-bit installs of Debian or Ubuntu.
     7The xvm maintainers recommend that servers be converted to ParaVM when possible. Currently, we can offer instructions for upgrading 64-bit installs of Debian or Ubuntu.
    88
    99== Converting a Linux Guest to ParaVM ==
    … …  
    1212
    1313* 64-bit install
    14   It is currently not possible to boot a 32-bit ParaVM kernel on sipb-xen (see #64). This should be possible, but for now, it is only possible to boot 64-bit kernels.
     14  It is currently not possible to boot a 32-bit ParaVM kernel on xvm (see #64). This should be possible, but for now, it is only possible to boot 64-bit kernels.
    1515* DHCP does not work
    16   The sipb-xen DHCP server currently does not communicate correctly with a paravirtualized guest, so the IP address will have to be set manually. To do this, edit /etc/network/interfaces and change the line that reads
     16  The xvm DHCP server currently does not communicate correctly with a paravirtualized guest, so the IP address will have to be set manually. To do this, edit /etc/network/interfaces and change the line that reads
    1717{{{
    1818iface eth0 inet dhcp
    … …  
    7171=== Change the Database Setting ===
    7272
    73 Once you've completed all of these steps, you should be able to shutdown your VM, change the radio button on the VM's info page at sipb-xen-dev.mit.edu, and then reboot the machine.
     73Once you've completed all of these steps, you should be able to shutdown your VM, change the radio button on the VM's info page at xvm.mit.edu, and then reboot the machine.