Xen: Console not yet active for host

[joseph]

CentOS 5.4 xen from disks.. windows 2003 server image up and running on network.
when to /etc/xen and copied and edited the configuration to match the image.
I can try to start #2 and it gives "Console not yet active for host"
funny thing I cant stop this guest , I can pause but that is it.. requires reboot to get rid of it.

I have had success with cent54 guest images doing exact same thing.
note: guest #2 is pingable but can not get remote desktop to answer.

[joseph]

Two possible solutions here:
1.
Here might the problem. "vnc = 1" sets the vnc port to 5901, and "vncunused = 0" says NOT to look for an unused port if the specified port is taken. The settings are the same for both doms

vnc = 1
vncunused = 0

Your first machine starts successfully, grabbing 5901, but the second is blocked, so the boot does not proceed. You can either assign different vnc ports to each machine - "vnc = 1" binds to 5901, "vnc = 2" to 5902 etc, or set "vncunused = 1" and let the booting vm find its own unused port.

2,
Check the logfile here, just check the latest one. file path is /var/log/xen/qemu-dm.*.log, it's usually the place to look for errors.

[root@domain ~]# tail -n 10 /var/log/xen/qemu-dm.8282.log
domid: 7
qemu: the number of cpus is 1
Watching /local/domain/7/logdirty/next-active
Watching /local/domain/0/device-model/7/command
warning: could not open /dev/net/tun: no virtual network emulation
Could not initialize device 'tap'

As it's mentioned here, we need to make sure either tap or tun is available.
Generally you need to...

[root@domain ~]# insmod /lib/modules/2.6.18-164.6.1.el5xen/kernel/drivers/net/tun.ko

Then, all would work smoothly ..

[Faride]

Thanks a lot, that's the point:

# insmod /lib/modules/2.6.18-164.6.1.el5xen/kernel/drivers/net/tun.ko

Which works well at my side!