Hello everyone, I feel like I am very close with this so I'll recap quickly what I've tried and where I'm at, thanks for taking a look:
I started with the obvious Âline in the configuration file:
vfb = [ 'type=vnc' ]
And then the domU did not start. After checking out the logs, I found out that xen wanted to use qemu to open up a VNC server. I performed an 'apt-get install qemu-system' which seemed to put all the qemu stuff in the right places.
Then it got a little further: the VM started to boot but hung. After inspecting theÂqemu-dm-vm.log file, it was complaining like so:
xen be core: xen be core: can't open gnttab device
can't open gnttab device
After more googling it turned out that the xen-gntdev module was not loaded by default in ubuntu, but at least it was present. I performed a modprobe xen-gntdev and I got past that error.
So now the domU boots successfully just like it did before I added the vfb setting. I can see the VNC server created by qemu-dm running on port 5900 after performing an 'lsof -i'. I SSH tunneled port 5900 to my localhost and tried to connect with the realvnc client, but all I see is a black (blank) screen. I have confirmed that the VM is running, I can SSH into it and can perform an 'xm console'ÂsuccessfullyÂas well.
I'm able to press ctrl-alt-2 and see the qemu monitor screen in my vnc client, but after switching back to ctrl-alt-1 it goes black. Here is the entirety of theÂqemu-dm-vm.log file:
domid: 130
Warning: vlan 0 is not connected to host network
char device redirected to /dev/pts/3
xs_read(): target get error. /local/domain/130/target.
xs_read(): vncpasswd get error. /vm/e4549f7c-05cc-b752-feb8-5cf15f2d51f5/vncpasswd.
char device redirected to /dev/pts/5
Just for good measure I performed an 'echo test > /dev/pts/5' while the VM was running then did an 'xm console' into the VM. Sure enough the text 'test' appeared inside the domU's console, so it seems like it's linking up to the right device.
I also notice if I connect to the VNC server quickly as the domU is booting, I can see it change resolutions midway through the boot process even though everything is black, so it seems like I'm close.
Anyone have any thoughts on how I figure the rest of this out?
Thanks,
Chris
