- bnc#897614 - Virtualization/xen: Bug xen-tools uninstallable;
grub2-x86_64-xen dependency not available xen.spec - More cleanup of README.SUSE - Update xen patch with upstream patch so that latest libvirt patch can work. (bnc#896044) + 53fcebab-xen-pass-kernel-initrd-to-qemu.patch - xen-pass-kernel-initrd-to-qemu.patch - bnc#895804 - VUL-0: CVE-2014-6268: xen: XSA-107: Mishandling of uninitialised FIFO-based event channel control blocks xsa107.patch - bnc#895802 - VUL-0: xen: XSA-106: Missing privilege level checks in x86 emulation of software interrupts xsa106.patch - bnc#895799 - VUL-0: xen: XSA-105: Missing privilege level checks in x86 HLT, LGDT, LIDT, and LMSW emulation xsa105.patch - bnc#895798 - VUL-0: xen: XSA-104: Race condition in HVMOP_track_dirty_vram xsa104.patch OBS-URL: https://build.opensuse.org/package/show/Virtualization/xen?expand=0&rev=331
This commit is contained in:
Charles Arnold
committed by
Git OBS Bridge
Git OBS Bridge
parent
5c685a813a
commit
4cdbb395f2
63
README.SUSE
63
README.SUSE
@@ -8,9 +8,8 @@ virtualization chapter in the SLES or SUSE Linux manual, or read up-to-date
|
||||
virtualization information, at
|
||||
https://www.suse.com/documentation/sles11/singlehtml/book_xen/book_xen.html
|
||||
|
||||
For more complete documentation on Xen itself, please install one of the
|
||||
xen-doc-* packages and read the documentation installed into
|
||||
/usr/share/doc/packages/xen/.
|
||||
For more complete documentation on Xen itself, please install the xen-doc-html
|
||||
package and read the documentation installed into /usr/share/doc/packages/xen/.
|
||||
|
||||
|
||||
About
|
||||
@@ -18,7 +17,7 @@ About
|
||||
Xen allows you to run multiple virtual machines on a single physical machine.
|
||||
|
||||
See the Xen homepage for more information:
|
||||
http://www.cl.cam.ac.uk/research/srg/netos/xen/
|
||||
http://www.xenproject.org/
|
||||
|
||||
If you want to use Xen, you need to install the Xen hypervisor and a number of
|
||||
supporting packages. During the initial SUSE installation (or when installing
|
||||
@@ -129,7 +128,7 @@ For more information on how to add options to the hypervisor, see the sections
|
||||
below called; "Dom0 Memory Ballooning" and "Troubleshooting".
|
||||
|
||||
For a more complete discussion of possible parameters, see the user
|
||||
documentation in the xen-doc-* packages.
|
||||
documentation in the xen-doc-html package.
|
||||
|
||||
|
||||
Creating a VM with virt-install
|
||||
@@ -137,14 +136,14 @@ Creating a VM with virt-install
|
||||
The virt-install program (part of the virt-install package, and accessible
|
||||
through YaST's Control Center) is the recommended method to create VMs. This
|
||||
program handles creating both the VM's libvirt XML definition and disk(s).
|
||||
It can help install any operating system, not just SUSE. Virt-install has both
|
||||
It can help install any operating system, not just SUSE. virt-install has both
|
||||
a command line only mode and a graphical wizard mode that may be used to define
|
||||
and start VM installations.
|
||||
|
||||
Virt-install may be launched from the virt-manager VM management tool. After
|
||||
starting virt-manager either from the YaST Control Center or by starting
|
||||
it from the command line. The installation icon from the main virt-manager
|
||||
screen may be selected to begin the virt-install installation wizard.
|
||||
virt-install may be launched from the virt-manager VM management tool. Start
|
||||
virt-manager either from the YaST Control Center or from the command line.
|
||||
The installation icon from the main virt-manager screen may be selected to
|
||||
begin the virt-install installation wizard.
|
||||
|
||||
The use of virt-install or virt-manager requires the installation of the
|
||||
libvirt packages and the libvirt daemon must be running on the host unless
|
||||
@@ -161,9 +160,10 @@ NFS or other networked or cluster filesystems.
|
||||
|
||||
When defining the virtual network adapter(s), we recommend using a static MAC
|
||||
for the VM rather than allowing Xen to randomly select one each time the VM
|
||||
boots. (See "Network Troubleshooting" below.) XenSource has been allocated a
|
||||
range of MAC addresses with the OUI of 00-16-3E. By using MACs from this
|
||||
range you can be sure they will not conflict with any physical adapters.
|
||||
boots. (See "Network Troubleshooting" below.) The Xen Project has been
|
||||
allocated a range of MAC addresses with the OUI of 00-16-3E. By using MACs
|
||||
from this range you can be sure they will not conflict with any physical
|
||||
adapters.
|
||||
|
||||
When the VM shuts down (because the installation -- or at least the first
|
||||
stage of it -- is done), the wizard finalizes the VM's configuration and
|
||||
@@ -177,7 +177,7 @@ supports it.
|
||||
Creating a VM with vm-install
|
||||
-----------------------------
|
||||
The vm-install program is also provided to create VMs. Like virt-install,
|
||||
this optional program handles creating both the VM's Libvirt XML definition
|
||||
this optional program handles creating both the VM's libvirt XML definition
|
||||
and disk(s). It also creates a legacy configuration file for use with 'xl'.
|
||||
It can help install any operating system, not just SUSE.
|
||||
|
||||
@@ -210,16 +210,17 @@ recommended way), you will need to create a disk (or reuse an existing one)
|
||||
and a configuration file.
|
||||
|
||||
If you are using a disk or disk image that is already installed with an
|
||||
operating system, you'll probably need to replace its kernel with a
|
||||
Xen-enabled kernel.
|
||||
operating system and you want the VM to run in paravirtual mode, you'll
|
||||
probably need to replace its kernel with a Xen-enabled kernel.
|
||||
|
||||
The kernel and ramdisk used to bootstrap the VM must match any kernel modules
|
||||
that might be present in the VM's disk. It is possible to manually copy the
|
||||
kernel and ramdisk from the VM's disk (for example, after updating the kernel
|
||||
within that VM) to the VM server's filesystem. However, an easier (and less
|
||||
error-prone) method is to use something called the "pygrub". Before a new
|
||||
VM is started, this loader automatically copies the kernel and ramdisk into
|
||||
the VM server's filesystem, so that it can be used to bootstrap the new VM.
|
||||
error-prone) method is to use /usr/lib/grub2/x86_64-xen/grub.xen as the VM
|
||||
kernel. When the new VM is started, it runs grub.xen to read the grub
|
||||
configuration from the VM disk, selecting the configured kernel and ramdisk
|
||||
so that it can be used to bootstrap the new VM.
|
||||
|
||||
Next, make a copy of one of the /etc/xen/examples/* files, and modify it to
|
||||
suit your needs. You'll need to change (at very least) the "name" and "disk"
|
||||
@@ -243,9 +244,8 @@ Now to start the VM:
|
||||
virsh start my-vm
|
||||
or start it from virt-manager's graphical menu.
|
||||
|
||||
Have a look at running sessions with "virsh list". Note the ID of the newly
|
||||
created VM. Attach to the VM's text console with "virsh console <ID>"
|
||||
(replacing ID with the VM's ID). Attaching to multiple VM consoles is most
|
||||
Have a look at running VMs with "virsh list". Attach to the VM's text console
|
||||
with "virsh console <vm-name>". Attaching to multiple VM consoles is most
|
||||
conveniently done with the terminal multiplexer "screen".
|
||||
|
||||
Have a look at the other virsh commands by typing "virsh help". Note that most
|
||||
@@ -478,7 +478,7 @@ before you can begin using libvirt on VMs that were previously managed by
|
||||
xm/xend, you must run a conversion tool called /usr/sbin/xen2libvirt for all
|
||||
VMs.
|
||||
|
||||
For example, to convert all managed xend domains:
|
||||
For example, to convert all domains previously managed by xend:
|
||||
xen2libvirt -r /var/lib/xend/domains/
|
||||
|
||||
Now typing 'virsh list --all' will show your previously xend managed domains
|
||||
@@ -623,33 +623,20 @@ Xen hypervisor will write any error messages to the log file (viewable with
|
||||
the "xl dmesg" command).
|
||||
|
||||
If problems persist, check if a newer version is available. Well-tested
|
||||
versions will be shipped with SUSE and via YaST Online Update. More frequent
|
||||
(but less supported) updates are available on Novell's Forge site:
|
||||
http://forge.novell.com/modules/xfmod/project/?xenpreview
|
||||
versions will be shipped with SUSE and via YaST Online Update.
|
||||
|
||||
|
||||
Resources
|
||||
---------
|
||||
https://www.suse.com/documentation/sles11/singlehtml/book_xen/book_xen.html
|
||||
http://doc.opensuse.org/products/draft/SLES/SLES-xen_sd_draft/cha.xen.basics.html
|
||||
http://www.novell.com/documentation/vmserver/.
|
||||
|
||||
|
||||
Disclaimer
|
||||
----------
|
||||
Xen performed amazingly well in our tests and proved very stable. Still, you
|
||||
should be careful when using it, just like you'd be careful if you boot an
|
||||
experimental kernel. Expect that it may not boot and be prepared to have a
|
||||
fall-back solution for that scenario. Be prepared that it may not support all
|
||||
of your hardware. And for the worst of all cases, have your most valuable
|
||||
data backed up. (This is always a good idea, of course.)
|
||||
|
||||
|
||||
Feedback
|
||||
--------
|
||||
In case you have remarks about, problems with, ideas for, or praise for Xen,
|
||||
please report it back to the xen-devel list:
|
||||
xen-devel@lists.xensource.com
|
||||
xen-devel@lists.xen.org
|
||||
If you find issues with the packaging or setup done by SUSE, please report
|
||||
it through bugzilla:
|
||||
https://bugzilla.novell.com
|
||||
|
||||
Reference in New Issue
Block a user