Diferencia entre revisiones de «Xen»
De gacq wiki
(→Common problems) |
|||
| Línea 83: | Línea 83: | ||
mv /lib/tls /lib/tls.disabled | mv /lib/tls /lib/tls.disabled | ||
| + | ==Error: Device 0 (vif) could not be connected== | ||
| + | # If you get the following error when trying to create a domU: | ||
| + | |||
| + | Error: Device 0 (vif) could not be connected. Backend device not found. | ||
| + | |||
| + | and your /var/log/xen/xend-debug.log shows something complaining about brctl, like that: | ||
| + | |||
| + | /etc/xen/scripts/network-bridge: line 114: brctl: command not found | ||
| + | |||
| + | it seems that bridge-utils package is not installed in your host, so: | ||
| + | |||
| + | apt-get install bridge-utils | ||
| + | /etc/init.d/xend restart | ||
| + | |||
| + | should solve the problem. | ||
| + | |||
| + | Thanks to: http://www.dit.upm.es/vnumlwiki/index.php/Xen-test-debian | ||
=Tools= | =Tools= | ||
Revisión del 12:33 2 mar 2008
Installation
Debian Etch installation
Packages install
- INTEL
sudo apt-get install linux-image-2.6.18-6-xen-686 xen-hypervisor-3.0.3-1-i386-pae xen-linux-system-2.6.18-6-xen-686 libc6-xen
- AMD
sudo apt-get install linux-image-2.6-xen-amd64 xen-hypervisor-3.0.3-1-amd64 xen-linux-system-2.6.18-5-xen-amd64
Optional packages:
- xen-docs-3.0
- xen-shell
Network config
Before the reboot, a small change in /etc/xen/xend-config.sxp should be done.
Replace
(network-script network-dummy)
with
(network-script 'network-bridge netdev=eth0')
- reboot
xen-tools
- (optional) to install latests version from project repository add to sources.lists
# # Steve Kemp's repository: Etch # deb http://apt.steve.org.uk/etch etch main non-free contrib deb-src http://apt.steve.org.uk/etch etch main non-free contrib
sudo apt-get install xen-tools
- xen-tools config
in /etc/xen-tools/xen-tools.conf
lvm = vg0 debootstrap = 1 size = 10Gb # Disk image size. memory = 256Mb # Memory size swap = 256Mb # Swap size fs = ext3 # use the EXT3 filesystem for the disk image. dist = etch # Default distribution to install. image = sparse # Specify sparse vs. full disk images. dhcp = 1 kernel = /boot/vmlinuz-2.6.18-5-xen-amd64 initrd = /boot/initrd.img-2.6.18-5-xen-amd64 mirror = http://ftp.us.debian.org/debian/
Administration
Create image
xen-create-image --hostname vserver1.mydomain
- or use with options
xen-create-image --hostname=vm1.domain.com --size=5Gb --swap=256Mb --ide \ --ip=192.168.0.101 --netmask=255.255.255.0 --gateway=192.168.0.1 --force \ --dir=/vserver --memory=32Mb --arch=i386 --kernel=/boot/vmlinuz-2.6.18-xenU \ --debootstrap --dist=etch --mirror=http://ftp2.de.debian.org/debian/ --passwd
Boot
xm create /etc/xen/vserver1.mydomain.cfg
Console connect
xm console vserver1.mydomain
Other common commands
xm shutdown <name> - Stop a virtual machine. xm destroy <name> - Stop a virtual machine immediately without shutting it down. It's as if you switch off the power button. xm list - List all running systems. xm help - List of all commands.
Common problems
To fix up "4gb seg fixup" errors on sarge and olds domU's
mv /lib/tls /lib/tls.disabled
Error: Device 0 (vif) could not be connected
- If you get the following error when trying to create a domU:
Error: Device 0 (vif) could not be connected. Backend device not found.
and your /var/log/xen/xend-debug.log shows something complaining about brctl, like that:
/etc/xen/scripts/network-bridge: line 114: brctl: command not found
it seems that bridge-utils package is not installed in your host, so:
apt-get install bridge-utils /etc/init.d/xend restart
should solve the problem.
Thanks to: http://www.dit.upm.es/vnumlwiki/index.php/Xen-test-debian
