Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm using this HVM File to create a new guest

kernel = "/usr/lib/xen-3.2-1/boot/hvmloader"
memory = 4096

# Should be at least 2KB per MB of domain memory, plus a few MB per vcpu.
shadow_memory = 64
name = "hessel-windows2008"
vif = [ 'ip=188.40.xx.xx,mac=00:16:3E:C1:8F:CE' ]

acpi = 1
apic = 1
disk = [ 'file:/home/xen/disks/hessel/win2008/win2008.img,hda,w', 'file:/home/xen/isopool/win2008_32.iso,hdc:cdrom,r' ]

device_model = '/usr/lib/xen/bin/qemu-dm'

# boot on floppy (a), hard disk (c) or CD-ROM (d) 
# default: hard disk, cd-rom, floppy




The guest is created without an error. But no vnc display is created. Any ideas, how to fix that?

prometheus:~# netstat -ant

Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0      0 *               LISTEN
tcp        0      0   *               LISTEN
tcp        0      0  *               LISTEN
tcp        0      0    *               LISTEN
tcp        0      0    *               LISTEN
tcp        0      0*               LISTEN
tcp        0    232 188.40.xx.xx:8080      ESTABLISHED
tcp        0      0 188.40.xx.xx:8080      ESTABLISHED
tcp6       0      0 :::8080                 :::*                    LISTEN
tcp6       0      0 :::53                   :::*                    LISTEN
tcp6       0      0 :::22                   :::*                    LISTEN
tcp6       0      0 ::1:6010                :::*                    LISTEN
share|improve this question
up vote 1 down vote accepted

The line I'm using for mine looks like this:


Which causes the port to listen. But then, I'm using a slightly older version of Xen than you are.

share|improve this answer
Already tried that, but it seems vnc doesn't start because it's trying to bind to the xen bridge witch doesn't exist, because I have to use a routed network configuration. – Henrik P. Hessel Aug 12 '09 at 20:33

You're missing vncunused = 0 in your config. That's the only real difference between your setup and the one we're running here.

share|improve this answer
do you use a bridged xen setup? – Henrik P. Hessel Aug 12 '09 at 21:44
That's not relevant to the problem at hand. – womble Aug 12 '09 at 23:47

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.