[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] Cannot access to PV domU via VNC
Thank you for your reply. I turned on CONFIG_FB_VIRTUAL in kernel compile option but it didn't work. I solved this issue by installing Ubuntu Desktop on the disk image file using HVM domU firstly, and then creating PV domU with that disk image. I used pygrub without specifying kernel and ramdisk images in the configuration file. It works well. I really appreciate your help. Thank you so much! On Mon, Mar 3, 2014 at 6:45 PM, Wei Liu <wei.liu2@xxxxxxxxxx> wrote: > On Sat, Mar 01, 2014 at 05:47:27PM +0900, Jeongseok Son wrote: >> Thank you so much. I did a stupid mistake. Now I set the vnclisten >> option as 0.0.0.0 then I can connect to it. >> >> However, I could only see a black screen on VNC client so I tried to >> install x window system. >> >> apt-get install x-window-system >> >> And then I ran "startx" command but I got this error message. >> >> (EE) open /dev/fb0: No such file or directory >> (EE) No devices detected. >> >> Fatal server error: >> no screens found >> >> Why frame buffer device is not enabled in PV domU? Ho can solve this issue? >> > > I've never used that feature so I cannot help with this. But I would > suggest you check your kernel if it has Xen PV framebuffer enabled. > > Wei > >> On Thu, Feb 27, 2014 at 11:44 PM, Wei Liu <wei.liu2@xxxxxxxxxx> wrote: >> > On Wed, Feb 26, 2014 at 11:47:39PM +0900, Jeongseok Son wrote: >> >> Hello, I have to use graphical interface in PV domU so I tried to >> >> connect to domU via VNC. >> >> >> >> I'm currently using Xen Hypervisor 4.3.1. I installed Ubuntu Lucid >> >> (10.04) PV domU with xen-create-image. I can use hvc0 console of domU >> >> (with xl console command) but cannot connect to VNC console. >> >> >> >> The following is my xen configuration for PV domU. >> >> >> >> # Kernel + memory size >> >> kernel = '/boot/vmlinuz-3.9.4+' >> >> ramdisk = '/boot/initrd.img-3.9.4+' >> >> >> >> vcpus = '2' >> >> memory = '2048' >> >> >> >> # Disk device(s) >> >> root = '/dev/xvda2 ro' >> >> disk = [ >> >> 'file:/path/to/disk.img,xvda2,w', >> >> 'file:/path/to/swap.img,xvda1,w', >> >> ] >> >> >> >> # Hostname >> >> name = 'pv-ubuntu' >> >> >> >> # vfb >> >> vfb = [ "vnc=1, vncpasswd='', vncdisplay=1" ] >> >> >> >> # Behaviour >> >> on_poweroff = 'destroy' >> >> on_reboot = 'restart' >> >> on_crash = 'restart' >> >> >> >> With netstat -a command, the following line is printed so I think Xen >> >> listens the connections. >> >> >> >> Proto Recv-Q Send-Q Local Address Foreign Address State >> >> tcp 0 0 localhost:5901 *:* >> >> LISTEN >> >> >> > >> > That's because your vnc is listening on 127.0.0.1 only. >> > >> > Please have a look at xl manpage for the "vnclisten" option. >> > >> > Wei. >> > >> >> But when I attempt to connect to it using VNC client, I got >> >> "Connection to host xxx.xxx.xxx.xxx::5901 was closed." message. >> >> >> >> I successfully worked with GUI Interface via VNC in HVM domU (Both >> >> Ubuntu 12.04 Desktop and Server). >> >> Why it doesn't work in PV domU? Are there anything to set up in PV >> >> domU to make it work? >> >> I really appreciate any help you can provide. >> >> >> >> _______________________________________________ >> >> Xen-users mailing list >> >> Xen-users@xxxxxxxxxxxxx >> >> http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxx http://lists.xen.org/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |