Difference between revisions of "Virtualization"
(→Configure) |
(→Configure) |
||
Line 133: | Line 133: | ||
vif = ['mac=00:00:00:00:00:00,bridge=xenbr0] | vif = ['mac=00:00:00:00:00:00,bridge=xenbr0] | ||
+ | {{File| /etc/xen-tools/xen-tools.conf | content= | ||
+ | bridge = xenbr0 | ||
+ | }} | ||
===Notes=== | ===Notes=== | ||
*http://wiki.xen.org/wiki/Host_Configuration/Networking | *http://wiki.xen.org/wiki/Host_Configuration/Networking |
Revision as of 18:15, 22 July 2012
- HVM is hardware and faster
- PV is Paravirtualization and usually slower
The networking scripts that come with xen are going to be phased out because they do not work all the time. You should setup bridge manually.
Contents
Debian
Xen Config File: /etc/xen/xend-config.sxp
Install
apt-get install xen-linux-system apt-get install xen-qemu-dm-4.0 dpkg-divert --divert /etc/grub.d/08_linux_xen --rename /etc/grub.d/20_linux_xen update-grub
May want to do this eventually to limit dom0 ram:
/etc/default/grub # Xen boot parameters for all Xen boots GRUB_CMDLINE_XEN="dom0_mem=1024M"
then
update-grub
then edit
/etc/xen/xend-config.sxp (dom0-min-mem 1024) (enable-dom0-ballooning no)
You would then need to reboot.
Network Scripts
They do not want you to use these anymore and instead setup the bridging up manually. You want to comment out anything with
(network-script
in front of it and do it right.
I did not even use the vif-script
/etc/xen/scripts/network-bridge /etc/xen/scripts/vif-bridge
Notes
Configure
Debian wiki states that the network control scripts that come with Xen are going to be phased out eventually. Goes on to say that you should setup networking yourself.
Something like:
ifconfig eth0 0.0.0.0
You cannot have and address assigned to eth0 and have it bridged at the same time. It will not work. I do not know if an alias would work. Like eth0:0 or whatever.
aptitude install bridge-utils brctl addbr br0
- br0 could be anything like: whatever0
ip addr show
- Just to see interfaces
You now need to add interfaces to the bridge
brctl addif br0 eth0 eth1
To make the bridge perm you need to edit /etc/network/interfaces
/etc/network/interfaces
or something using ethernet aliases:
/etc/network/interfaces
You then could edit /etc/xen/xend-config.sxp but since the networking scripts included with xen may be phased out at any moment you should just configure the domu's to use the bridge. xen-tools will do this if you configure it to. You will need a vif line in the domU config to use the bridge:
vif = ['mac=00:00:00:00:00:00,bridge=xenbr0]
/etc/xen-tools/xen-tools.conf
Notes
- http://wiki.xen.org/wiki/Host_Configuration/Networking
- Has some recommendations:
bridge_stp off # disable Spanning Tree Protocol bridge_waitport 0 # no delay before a port becomes available bridge_fd 0 # no forwarding delay
- http://william.shallum.net/random-notes/debian-squeeze-xen-bridge-configuration-using-etc-network-interfaces
- http://www.debian-administration.org/articles/360
- http://www.cyberciti.biz/tips/ubuntu-linux-creating-ethernet-alias-for-eth0-network-device.html
- http://paste.debian.net/180252/
Install DomU xen-tools
To configure xen-tools, you can edit /etc/xen-tools/xen-tools.conf which contains default values that the xen-create-image script will use. The xen-create-image(8) manual page contains information on the available options.
xen-create-image --hostname <hostname> --ip <ip> --vcpus 2 --pygrub --dist <lenny|squeeze|maverick|whatever>
Install DomU Debian Installer
Fuck
- cloudstack.org/
- xcp
- http://www.xvpsource.org/
- openstack
Notes
HyperVM | Free and looks like a great product. Does not work with CentOS 6 because CentOS dropped Xen? |
- Xen XCP
- OpenVZ
- Virtuzzo
- ProxMox
- SolusVM
- vePortal
Most of these can integrate with a billing platform.
- lxcenter.org
kloxo