User Tools

Site Tools



Dom0 Setting

vi /etc/xen/xend-config.sxp (vnc-listen '') #the above allows any computer connect to view with VNC. #change to to restrict viewing with VNC to dom0

VM disk based image setup: mkdir -p /xens/vm02 dd if=/dev/zero of=/xens/vm02/disk-vm02.img bs=1024k count=20000

VM Config

vi /etc/xen/vm02 kernel = '/usr/lib/xen-default/boot/hvmloader' builder = 'hvm' memory = '512' device_model='/usr/lib/xen-default/bin/qemu-dm'

# Disks disk = 'file:/xens/vm02/disk-vm02.img,ioemu:hda,w','file:/xens/vm02/windows7.iso,ioemu:hdc:cdrom,r'

# Hostname name = 'vm02'

# Networking vif = ip=, bridge=eth0'

# Behaviour boot='dc' vnc=1 vncviewer=1 serial='pty' shadow_memory = 8 vcpus=1 pae=0 acpi=1 apic=1 ne2000=0 usb=1 usbdevice='tablet'

Start VM

xm create /etc/xen/vm02 #you should see: Using config file “/etc/xen/vm02”. VNC= 1 Started domain vm02 #check: Debian-50-lenny-32-minimal:~# netstat -a | grep 5900 tcp 0 0 *:5900 *:* LISTEN Then open up your VNC viewer and connect. No password is required.


The above shows very basic settings to get Windows running on Xen with a CPU with virtualisation support. There are many, many configs and other setups out there for Windows on Xen. I used Windows7 as the domU guest. Three-four years ago on Xen3.0 I tried to get XP to run as domU. I did manage it, however I had to use kvm to get XP installed on a disk image, and then xen would run it as a domU. I had no such issues with Xen3.2 and Windows 7.


setup_of_windows_domu_on_debian_lenny_dom0.txt · Last modified: 2022/07/19 21:13 by