Hi,
I am running Xen on Debian Lenny. I am having a very strange issue
regarding VNC.
I am able to connect to VNC just fine -- but as the paravirtualized
machine boots, it stops at "lo: Disabled Privacy Extensions", and
appears to hang there. The console will accept no keyboard input.
However...
The strange part is that "xm console" still works for this domu...
when I log in, I see that the domu has booted just fine! Everything
works, including networking. I need vnc to work on this this domu.
(btw- vnc works flawlessly with an hvm openbsd domu on the same
machine).
Here is a screenshot of what I see:
http://sciotech.com/xen_vnc_problem.png
Below is my cfg for this domu, and the output from my log file.
Please note that the commented lines in my cfg are things I have to
toggled to try and fix this -- none worked.
Thank you for your help.
---------------------------------------------------------------------------
cfg:
kernel = ''/boot/vmlinuz-2.6.26-1-xen-amd64''
ramdisk = ''/boot/initrd.img-2.6.26-1-xen-amd64''
memory = ''1536''
root = ''/dev/xvda2 ro''
disk = [
''phy:/dev/vg/mylenny_swap,xvda1,w'',
''phy:/dev/vg/mylenny_slash,xvda2,w'',
''phy:/dev/vg/mylenny_home,xvda3,w'',
]
name = ''mylennydomu''
dhcp = ''dhcp''
vif = [ ''mac=00:17:3F:2F:F7:34'' ]
on_poweroff = ''destroy''
on_reboot = ''restart''
on_crash = ''restart''
vfb = [ ''type=vnc,vncdisplay=2'' ]
#sdl=0
#vnc=1
#vnclisten=''0.0.0.0''
#vncconsole=1
#vncdisplay=0
#vncpasswd=''''
#stdvga=0
#serial=''pty''
#usbdevice=''tablet''
##localtime=1
#audio=0
#ne2000=1
----------------------------------------------------
qemu-dm-52.log:
Change xvda to look like hda
Change xvda to look like hda
Change xvda to look like hda
Watching /local/domain/0/device-model/52/logdirty/next-active
Watching /local/domain/0/device-model/52/command
shift keysym 003e keycode 86
shift keysym 00a6 keycode 86
keypad keysym ffae keycode 83
keypad keysym ffac keycode 83
keypad keysym ffb0 keycode 82
keypad keysym ffb1 keycode 79
keypad keysym ffb2 keycode 80
keypad keysym ffb3 keycode 81
keypad keysym ffb4 keycode 75
keypad keysym ffb5 keycode 76
keypad keysym ffb6 keycode 77
keypad keysym ffb7 keycode 71
keypad keysym ffb8 keycode 72
keypad keysym ffb9 keycode 73
shift keysym 0021 keycode 2
shift keysym 0040 keycode 3
shift keysym 0023 keycode 4
shift keysym 0024 keycode 5
shift keysym 0025 keycode 6
shift keysym 005e keycode 7
shift keysym 0026 keycode 8
shift keysym 002a keycode 9
shift keysym 0028 keycode 10
shift keysym 0029 keycode 11
shift keysym 005f keycode 12
shift keysym 002b keycode 13
shift keysym 007b keycode 26
shift keysym 007d keycode 27
shift keysym 003a keycode 39
shift keysym 0022 keycode 40
shift keysym 007e keycode 41
shift keysym 007c keycode 43
shift keysym 003c keycode 51
shift keysym 003e keycode 52
shift keysym 003f keycode 53
xs_read(): vncpasswd get error.
/vm/82b1f664-096e-56fe-fea0-a1b625600960/vncpasswd.
char device redirected to /dev/pts/1
Console: prepared domain, waiting for ringref at
/local/domain/52/console or /local/domain/52/serial/0
FB: Waiting for KBD backend creation
Doing backend watch on /local/domain/0/backend/vkbd/52/0
FB: Waiting for FB backend creation
Doing backend watch on /local/domain/0/backend/vfb/52/0
Console: got watch
Console: failed to find ring-ref/port yet
FB: Waiting for KBD frontend initialization
Doing frontend watch on /local/domain/52/device/vkbd/0
Console: got watch
Console: failed to find ring-ref/port yet
FB: Carry on waiting
Console: got watch
Console: got ring-ref 1078749 port 2
Console: connected to guest frontend
FB: Carry on waiting
FB: Waiting for FB frontend initialization
Doing frontend watch on /local/domain/52/device/vfb/0
Framebuffer 800x600x32 stride 3200
Framebuffer depth 32 width 800 height 600 line 3200
FB: Waiting for KBD frontend connection
Doing frontend watch on /local/domain/52/device/vkbd/0
FB: Carry on waiting
FB: Carry on waiting
FB: Carry on waiting
Xen Framebuffer registered
-----------------------------------------------------------
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Nicolas, Thanks for the reply, but that isn''t working. It gives me a big black screen with a flashing cursor in the upper left. The screen is likewise not responsive to keyboard input. I did notice the /dev/xvc* does not exist on either the domu or the dom0. I tried using xenconsole (/dev/xenconsole does exist in the domu)... but I get the same thing. Any other Ideas? Thanks. Quoting "Munoz, Nicolas" <nicolas.munoz@hp.com>:> Hi, > > Try to add the > > extra=''console=xvc0'' > > to your cfg file > > -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Chris > Sent: 13 August 2009 14:53 > To: xen-users@lists.xensource.com > Subject: [Xen-users] VNC Console Hangs > > Hi, > > I am running Xen on Debian Lenny. I am having a very strange issue > regarding VNC. > > I am able to connect to VNC just fine -- but as the paravirtualized > machine boots, it stops at "lo: Disabled Privacy Extensions", and > appears to hang there. The console will accept no keyboard input. > > However... > > The strange part is that "xm console" still works for this domu... > when I log in, I see that the domu has booted just fine! Everything > works, including networking. I need vnc to work on this this domu. > (btw- vnc works flawlessly with an hvm openbsd domu on the same > machine). > > Here is a screenshot of what I see: > http://sciotech.com/xen_vnc_problem.png > > Below is my cfg for this domu, and the output from my log file. > Please note that the commented lines in my cfg are things I have to > toggled to try and fix this -- none worked. > > Thank you for your help. > > > --------------------------------------------------------------------------- > cfg: > kernel = ''/boot/vmlinuz-2.6.26-1-xen-amd64'' > ramdisk = ''/boot/initrd.img-2.6.26-1-xen-amd64'' > memory = ''1536'' > root = ''/dev/xvda2 ro'' > disk = [ > ''phy:/dev/vg/mylenny_swap,xvda1,w'', > ''phy:/dev/vg/mylenny_slash,xvda2,w'', > ''phy:/dev/vg/mylenny_home,xvda3,w'', > ] > name = ''mylennydomu'' > dhcp = ''dhcp'' > vif = [ ''mac=00:17:3F:2F:F7:34'' ] > > on_poweroff = ''destroy'' > on_reboot = ''restart'' > on_crash = ''restart'' > > vfb = [ ''type=vnc,vncdisplay=2'' ] > #sdl=0 > #vnc=1 > #vnclisten=''0.0.0.0'' > #vncconsole=1 > #vncdisplay=0 > #vncpasswd='''' > #stdvga=0 > #serial=''pty'' > #usbdevice=''tablet'' > ##localtime=1 > #audio=0 > #ne2000=1 > > ---------------------------------------------------- > qemu-dm-52.log: > Change xvda to look like hda > Change xvda to look like hda > Change xvda to look like hda > Watching /local/domain/0/device-model/52/logdirty/next-active > Watching /local/domain/0/device-model/52/command > shift keysym 003e keycode 86 > shift keysym 00a6 keycode 86 > keypad keysym ffae keycode 83 > keypad keysym ffac keycode 83 > keypad keysym ffb0 keycode 82 > keypad keysym ffb1 keycode 79 > keypad keysym ffb2 keycode 80 > keypad keysym ffb3 keycode 81 > keypad keysym ffb4 keycode 75 > keypad keysym ffb5 keycode 76 > keypad keysym ffb6 keycode 77 > keypad keysym ffb7 keycode 71 > keypad keysym ffb8 keycode 72 > keypad keysym ffb9 keycode 73 > shift keysym 0021 keycode 2 > shift keysym 0040 keycode 3 > shift keysym 0023 keycode 4 > shift keysym 0024 keycode 5 > shift keysym 0025 keycode 6 > shift keysym 005e keycode 7 > shift keysym 0026 keycode 8 > shift keysym 002a keycode 9 > shift keysym 0028 keycode 10 > shift keysym 0029 keycode 11 > shift keysym 005f keycode 12 > shift keysym 002b keycode 13 > shift keysym 007b keycode 26 > shift keysym 007d keycode 27 > shift keysym 003a keycode 39 > shift keysym 0022 keycode 40 > shift keysym 007e keycode 41 > shift keysym 007c keycode 43 > shift keysym 003c keycode 51 > shift keysym 003e keycode 52 > shift keysym 003f keycode 53 > xs_read(): vncpasswd get error. > /vm/82b1f664-096e-56fe-fea0-a1b625600960/vncpasswd. > char device redirected to /dev/pts/1 > Console: prepared domain, waiting for ringref at > /local/domain/52/console or /local/domain/52/serial/0 > FB: Waiting for KBD backend creation > Doing backend watch on /local/domain/0/backend/vkbd/52/0 > FB: Waiting for FB backend creation > Doing backend watch on /local/domain/0/backend/vfb/52/0 > Console: got watch > Console: failed to find ring-ref/port yet > FB: Waiting for KBD frontend initialization > Doing frontend watch on /local/domain/52/device/vkbd/0 > Console: got watch > Console: failed to find ring-ref/port yet > FB: Carry on waiting > Console: got watch > Console: got ring-ref 1078749 port 2 > Console: connected to guest frontend > FB: Carry on waiting > FB: Waiting for FB frontend initialization > Doing frontend watch on /local/domain/52/device/vfb/0 > Framebuffer 800x600x32 stride 3200 > Framebuffer depth 32 width 800 height 600 line 3200 > FB: Waiting for KBD frontend connection > Doing frontend watch on /local/domain/52/device/vkbd/0 > FB: Carry on waiting > FB: Carry on waiting > FB: Carry on waiting > Xen Framebuffer registered > ----------------------------------------------------------- > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
vnc=1 only seems to work on my hvm domUs -- not my linux native domUs. I think this is because the linux machines use the framebuffer, and the others do not. so, the line: vfb = [ ''type=vnc,vncdisplay=2'' ] is supposed to take care of this. Without this line, the vncserver never starts Changing vnc=X doesn''t seem to make any difference with the paravirtualized linux boxes. So... it seems to me this is an fb thing... Booting to non-virutalized linux boxes, you can see that this is where the monitor makes the switch from a non-fb to a fb console. I cannot find any documentation on this anywhere on this... I''ve been trying to pass kernel params regarding fb to the the domu using the "extra=" directive, like "extra=''vga=791''" or "extra=''nofb''"... they just seem ignored... Help? Quoting "Munoz, Nicolas" <nicolas.munoz@hp.com>:> Wait a minute, I just noticed one strange thing... > > Why is your > > vnc=1 > > Line commented? You need to uncomment it > > -----Original Message----- > From: Chris [mailto:cjdl01@brokensolstice.com] > Sent: 13 August 2009 16:12 > To: Munoz, Nicolas > Cc: xen-users@lists.xensource.com > Subject: RE: [Xen-users] VNC Console Hangs > > Nicolas, > > Thanks for the reply, but that isn''t working. It gives me a big black > screen with a flashing cursor in the upper left. The screen is > likewise not responsive to keyboard input. > > I did notice the /dev/xvc* does not exist on either the domu or the > dom0. I tried using xenconsole (/dev/xenconsole does exist in the > domu)... but I get the same thing. > > Any other Ideas? > > Thanks. > > > Quoting "Munoz, Nicolas" <nicolas.munoz@hp.com>: > >> Hi, >> >> Try to add the >> >> extra=''console=xvc0'' >> >> to your cfg file >> >> -----Original Message----- >> From: xen-users-bounces@lists.xensource.com >> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Chris >> Sent: 13 August 2009 14:53 >> To: xen-users@lists.xensource.com >> Subject: [Xen-users] VNC Console Hangs >> >> Hi, >> >> I am running Xen on Debian Lenny. I am having a very strange issue >> regarding VNC. >> >> I am able to connect to VNC just fine -- but as the paravirtualized >> machine boots, it stops at "lo: Disabled Privacy Extensions", and >> appears to hang there. The console will accept no keyboard input. >> >> However... >> >> The strange part is that "xm console" still works for this domu... >> when I log in, I see that the domu has booted just fine! Everything >> works, including networking. I need vnc to work on this this domu. >> (btw- vnc works flawlessly with an hvm openbsd domu on the same >> machine). >> >> Here is a screenshot of what I see: >> http://sciotech.com/xen_vnc_problem.png >> >> Below is my cfg for this domu, and the output from my log file. >> Please note that the commented lines in my cfg are things I have to >> toggled to try and fix this -- none worked. >> >> Thank you for your help. >> >> >> --------------------------------------------------------------------------- >> cfg: >> kernel = ''/boot/vmlinuz-2.6.26-1-xen-amd64'' >> ramdisk = ''/boot/initrd.img-2.6.26-1-xen-amd64'' >> memory = ''1536'' >> root = ''/dev/xvda2 ro'' >> disk = [ >> ''phy:/dev/vg/mylenny_swap,xvda1,w'', >> ''phy:/dev/vg/mylenny_slash,xvda2,w'', >> ''phy:/dev/vg/mylenny_home,xvda3,w'', >> ] >> name = ''mylennydomu'' >> dhcp = ''dhcp'' >> vif = [ ''mac=00:17:3F:2F:F7:34'' ] >> >> on_poweroff = ''destroy'' >> on_reboot = ''restart'' >> on_crash = ''restart'' >> >> vfb = [ ''type=vnc,vncdisplay=2'' ] >> #sdl=0 >> #vnc=1 >> #vnclisten=''0.0.0.0'' >> #vncconsole=1 >> #vncdisplay=0 >> #vncpasswd='''' >> #stdvga=0 >> #serial=''pty'' >> #usbdevice=''tablet'' >> ##localtime=1 >> #audio=0 >> #ne2000=1 >> >> ---------------------------------------------------- >> qemu-dm-52.log: >> Change xvda to look like hda >> Change xvda to look like hda >> Change xvda to look like hda >> Watching /local/domain/0/device-model/52/logdirty/next-active >> Watching /local/domain/0/device-model/52/command >> shift keysym 003e keycode 86 >> shift keysym 00a6 keycode 86 >> keypad keysym ffae keycode 83 >> keypad keysym ffac keycode 83 >> keypad keysym ffb0 keycode 82 >> keypad keysym ffb1 keycode 79 >> keypad keysym ffb2 keycode 80 >> keypad keysym ffb3 keycode 81 >> keypad keysym ffb4 keycode 75 >> keypad keysym ffb5 keycode 76 >> keypad keysym ffb6 keycode 77 >> keypad keysym ffb7 keycode 71 >> keypad keysym ffb8 keycode 72 >> keypad keysym ffb9 keycode 73 >> shift keysym 0021 keycode 2 >> shift keysym 0040 keycode 3 >> shift keysym 0023 keycode 4 >> shift keysym 0024 keycode 5 >> shift keysym 0025 keycode 6 >> shift keysym 005e keycode 7 >> shift keysym 0026 keycode 8 >> shift keysym 002a keycode 9 >> shift keysym 0028 keycode 10 >> shift keysym 0029 keycode 11 >> shift keysym 005f keycode 12 >> shift keysym 002b keycode 13 >> shift keysym 007b keycode 26 >> shift keysym 007d keycode 27 >> shift keysym 003a keycode 39 >> shift keysym 0022 keycode 40 >> shift keysym 007e keycode 41 >> shift keysym 007c keycode 43 >> shift keysym 003c keycode 51 >> shift keysym 003e keycode 52 >> shift keysym 003f keycode 53 >> xs_read(): vncpasswd get error. >> /vm/82b1f664-096e-56fe-fea0-a1b625600960/vncpasswd. >> char device redirected to /dev/pts/1 >> Console: prepared domain, waiting for ringref at >> /local/domain/52/console or /local/domain/52/serial/0 >> FB: Waiting for KBD backend creation >> Doing backend watch on /local/domain/0/backend/vkbd/52/0 >> FB: Waiting for FB backend creation >> Doing backend watch on /local/domain/0/backend/vfb/52/0 >> Console: got watch >> Console: failed to find ring-ref/port yet >> FB: Waiting for KBD frontend initialization >> Doing frontend watch on /local/domain/52/device/vkbd/0 >> Console: got watch >> Console: failed to find ring-ref/port yet >> FB: Carry on waiting >> Console: got watch >> Console: got ring-ref 1078749 port 2 >> Console: connected to guest frontend >> FB: Carry on waiting >> FB: Waiting for FB frontend initialization >> Doing frontend watch on /local/domain/52/device/vfb/0 >> Framebuffer 800x600x32 stride 3200 >> Framebuffer depth 32 width 800 height 600 line 3200 >> FB: Waiting for KBD frontend connection >> Doing frontend watch on /local/domain/52/device/vkbd/0 >> FB: Carry on waiting >> FB: Carry on waiting >> FB: Carry on waiting >> Xen Framebuffer registered >> ----------------------------------------------------------- >> >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
How about your /etc/X11/xorg.conf file ? What''s in it ? -----Original Message----- From: Chris [mailto:cjdl01@brokensolstice.com] Sent: 13 August 2009 16:47 To: Munoz, Nicolas Cc: xen-users@lists.xensource.com Subject: RE: [Xen-users] VNC Console Hangs vnc=1 only seems to work on my hvm domUs -- not my linux native domUs. I think this is because the linux machines use the framebuffer, and the others do not. so, the line: vfb = [ ''type=vnc,vncdisplay=2'' ] is supposed to take care of this. Without this line, the vncserver never starts Changing vnc=X doesn''t seem to make any difference with the paravirtualized linux boxes. So... it seems to me this is an fb thing... Booting to non-virutalized linux boxes, you can see that this is where the monitor makes the switch from a non-fb to a fb console. I cannot find any documentation on this anywhere on this... I''ve been trying to pass kernel params regarding fb to the the domu using the "extra=" directive, like "extra=''vga=791''" or "extra=''nofb''"... they just seem ignored... Help? Quoting "Munoz, Nicolas" <nicolas.munoz@hp.com>:> Wait a minute, I just noticed one strange thing... > > Why is your > > vnc=1 > > Line commented? You need to uncomment it > > -----Original Message----- > From: Chris [mailto:cjdl01@brokensolstice.com] > Sent: 13 August 2009 16:12 > To: Munoz, Nicolas > Cc: xen-users@lists.xensource.com > Subject: RE: [Xen-users] VNC Console Hangs > > Nicolas, > > Thanks for the reply, but that isn''t working. It gives me a big black > screen with a flashing cursor in the upper left. The screen is > likewise not responsive to keyboard input. > > I did notice the /dev/xvc* does not exist on either the domu or the > dom0. I tried using xenconsole (/dev/xenconsole does exist in the > domu)... but I get the same thing. > > Any other Ideas? > > Thanks. > > > Quoting "Munoz, Nicolas" <nicolas.munoz@hp.com>: > >> Hi, >> >> Try to add the >> >> extra=''console=xvc0'' >> >> to your cfg file >> >> -----Original Message----- >> From: xen-users-bounces@lists.xensource.com >> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Chris >> Sent: 13 August 2009 14:53 >> To: xen-users@lists.xensource.com >> Subject: [Xen-users] VNC Console Hangs >> >> Hi, >> >> I am running Xen on Debian Lenny. I am having a very strange issue >> regarding VNC. >> >> I am able to connect to VNC just fine -- but as the paravirtualized >> machine boots, it stops at "lo: Disabled Privacy Extensions", and >> appears to hang there. The console will accept no keyboard input. >> >> However... >> >> The strange part is that "xm console" still works for this domu... >> when I log in, I see that the domu has booted just fine! Everything >> works, including networking. I need vnc to work on this this domu. >> (btw- vnc works flawlessly with an hvm openbsd domu on the same >> machine). >> >> Here is a screenshot of what I see: >> http://sciotech.com/xen_vnc_problem.png >> >> Below is my cfg for this domu, and the output from my log file. >> Please note that the commented lines in my cfg are things I have to >> toggled to try and fix this -- none worked. >> >> Thank you for your help. >> >> >> --------------------------------------------------------------------------- >> cfg: >> kernel = ''/boot/vmlinuz-2.6.26-1-xen-amd64'' >> ramdisk = ''/boot/initrd.img-2.6.26-1-xen-amd64'' >> memory = ''1536'' >> root = ''/dev/xvda2 ro'' >> disk = [ >> ''phy:/dev/vg/mylenny_swap,xvda1,w'', >> ''phy:/dev/vg/mylenny_slash,xvda2,w'', >> ''phy:/dev/vg/mylenny_home,xvda3,w'', >> ] >> name = ''mylennydomu'' >> dhcp = ''dhcp'' >> vif = [ ''mac=00:17:3F:2F:F7:34'' ] >> >> on_poweroff = ''destroy'' >> on_reboot = ''restart'' >> on_crash = ''restart'' >> >> vfb = [ ''type=vnc,vncdisplay=2'' ] >> #sdl=0 >> #vnc=1 >> #vnclisten=''0.0.0.0'' >> #vncconsole=1 >> #vncdisplay=0 >> #vncpasswd='''' >> #stdvga=0 >> #serial=''pty'' >> #usbdevice=''tablet'' >> ##localtime=1 >> #audio=0 >> #ne2000=1 >> >> ---------------------------------------------------- >> qemu-dm-52.log: >> Change xvda to look like hda >> Change xvda to look like hda >> Change xvda to look like hda >> Watching /local/domain/0/device-model/52/logdirty/next-active >> Watching /local/domain/0/device-model/52/command >> shift keysym 003e keycode 86 >> shift keysym 00a6 keycode 86 >> keypad keysym ffae keycode 83 >> keypad keysym ffac keycode 83 >> keypad keysym ffb0 keycode 82 >> keypad keysym ffb1 keycode 79 >> keypad keysym ffb2 keycode 80 >> keypad keysym ffb3 keycode 81 >> keypad keysym ffb4 keycode 75 >> keypad keysym ffb5 keycode 76 >> keypad keysym ffb6 keycode 77 >> keypad keysym ffb7 keycode 71 >> keypad keysym ffb8 keycode 72 >> keypad keysym ffb9 keycode 73 >> shift keysym 0021 keycode 2 >> shift keysym 0040 keycode 3 >> shift keysym 0023 keycode 4 >> shift keysym 0024 keycode 5 >> shift keysym 0025 keycode 6 >> shift keysym 005e keycode 7 >> shift keysym 0026 keycode 8 >> shift keysym 002a keycode 9 >> shift keysym 0028 keycode 10 >> shift keysym 0029 keycode 11 >> shift keysym 005f keycode 12 >> shift keysym 002b keycode 13 >> shift keysym 007b keycode 26 >> shift keysym 007d keycode 27 >> shift keysym 003a keycode 39 >> shift keysym 0022 keycode 40 >> shift keysym 007e keycode 41 >> shift keysym 007c keycode 43 >> shift keysym 003c keycode 51 >> shift keysym 003e keycode 52 >> shift keysym 003f keycode 53 >> xs_read(): vncpasswd get error. >> /vm/82b1f664-096e-56fe-fea0-a1b625600960/vncpasswd. >> char device redirected to /dev/pts/1 >> Console: prepared domain, waiting for ringref at >> /local/domain/52/console or /local/domain/52/serial/0 >> FB: Waiting for KBD backend creation >> Doing backend watch on /local/domain/0/backend/vkbd/52/0 >> FB: Waiting for FB backend creation >> Doing backend watch on /local/domain/0/backend/vfb/52/0 >> Console: got watch >> Console: failed to find ring-ref/port yet >> FB: Waiting for KBD frontend initialization >> Doing frontend watch on /local/domain/52/device/vkbd/0 >> Console: got watch >> Console: failed to find ring-ref/port yet >> FB: Carry on waiting >> Console: got watch >> Console: got ring-ref 1078749 port 2 >> Console: connected to guest frontend >> FB: Carry on waiting >> FB: Waiting for FB frontend initialization >> Doing frontend watch on /local/domain/52/device/vfb/0 >> Framebuffer 800x600x32 stride 3200 >> Framebuffer depth 32 width 800 height 600 line 3200 >> FB: Waiting for KBD frontend connection >> Doing frontend watch on /local/domain/52/device/vkbd/0 >> FB: Carry on waiting >> FB: Carry on waiting >> FB: Carry on waiting >> Xen Framebuffer registered >> ----------------------------------------------------------- >> >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ok. Looked at both systems, and xorg.conf is an empty file. But, like I said, since I''m not running X on either system (though xorg is installed) I''m not sure we are barking up the right tree here... Quoting "Munoz, Nicolas" <nicolas.munoz@hp.com>:> How about your /etc/X11/xorg.conf file ? > What''s in it ? > > > -----Original Message----- > From: Chris [mailto:cjdl01@brokensolstice.com] > Sent: 13 August 2009 16:47 > To: Munoz, Nicolas > Cc: xen-users@lists.xensource.com > Subject: RE: [Xen-users] VNC Console Hangs > > vnc=1 only seems to work on my hvm domUs -- not my linux native domUs. > > I think this is because the linux machines use the framebuffer, and > the others do not. > > so, the line: > vfb = [ ''type=vnc,vncdisplay=2'' ] > is supposed to take care of this. Without this line, the vncserver > never starts > > Changing vnc=X doesn''t seem to make any difference with the > paravirtualized linux boxes. > > So... it seems to me this is an fb thing... Booting to > non-virutalized linux boxes, you can see that this is where the > monitor makes the switch from a non-fb to a fb console. I cannot find > any documentation on this anywhere on this... > > I''ve been trying to pass kernel params regarding fb to the the domu > using the "extra=" directive, like "extra=''vga=791''" or > "extra=''nofb''"... they just seem ignored... > > Help? > > > Quoting "Munoz, Nicolas" <nicolas.munoz@hp.com>: > >> Wait a minute, I just noticed one strange thing... >> >> Why is your >> >> vnc=1 >> >> Line commented? You need to uncomment it >> >> -----Original Message----- >> From: Chris [mailto:cjdl01@brokensolstice.com] >> Sent: 13 August 2009 16:12 >> To: Munoz, Nicolas >> Cc: xen-users@lists.xensource.com >> Subject: RE: [Xen-users] VNC Console Hangs >> >> Nicolas, >> >> Thanks for the reply, but that isn''t working. It gives me a big black >> screen with a flashing cursor in the upper left. The screen is >> likewise not responsive to keyboard input. >> >> I did notice the /dev/xvc* does not exist on either the domu or the >> dom0. I tried using xenconsole (/dev/xenconsole does exist in the >> domu)... but I get the same thing. >> >> Any other Ideas? >> >> Thanks. >> >> >> Quoting "Munoz, Nicolas" <nicolas.munoz@hp.com>: >> >>> Hi, >>> >>> Try to add the >>> >>> extra=''console=xvc0'' >>> >>> to your cfg file >>> >>> -----Original Message----- >>> From: xen-users-bounces@lists.xensource.com >>> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Chris >>> Sent: 13 August 2009 14:53 >>> To: xen-users@lists.xensource.com >>> Subject: [Xen-users] VNC Console Hangs >>> >>> Hi, >>> >>> I am running Xen on Debian Lenny. I am having a very strange issue >>> regarding VNC. >>> >>> I am able to connect to VNC just fine -- but as the paravirtualized >>> machine boots, it stops at "lo: Disabled Privacy Extensions", and >>> appears to hang there. The console will accept no keyboard input. >>> >>> However... >>> >>> The strange part is that "xm console" still works for this domu... >>> when I log in, I see that the domu has booted just fine! Everything >>> works, including networking. I need vnc to work on this this domu. >>> (btw- vnc works flawlessly with an hvm openbsd domu on the same >>> machine). >>> >>> Here is a screenshot of what I see: >>> http://sciotech.com/xen_vnc_problem.png >>> >>> Below is my cfg for this domu, and the output from my log file. >>> Please note that the commented lines in my cfg are things I have to >>> toggled to try and fix this -- none worked. >>> >>> Thank you for your help. >>> >>> >>> --------------------------------------------------------------------------- >>> cfg: >>> kernel = ''/boot/vmlinuz-2.6.26-1-xen-amd64'' >>> ramdisk = ''/boot/initrd.img-2.6.26-1-xen-amd64'' >>> memory = ''1536'' >>> root = ''/dev/xvda2 ro'' >>> disk = [ >>> ''phy:/dev/vg/mylenny_swap,xvda1,w'', >>> ''phy:/dev/vg/mylenny_slash,xvda2,w'', >>> ''phy:/dev/vg/mylenny_home,xvda3,w'', >>> ] >>> name = ''mylennydomu'' >>> dhcp = ''dhcp'' >>> vif = [ ''mac=00:17:3F:2F:F7:34'' ] >>> >>> on_poweroff = ''destroy'' >>> on_reboot = ''restart'' >>> on_crash = ''restart'' >>> >>> vfb = [ ''type=vnc,vncdisplay=2'' ] >>> #sdl=0 >>> #vnc=1 >>> #vnclisten=''0.0.0.0'' >>> #vncconsole=1 >>> #vncdisplay=0 >>> #vncpasswd='''' >>> #stdvga=0 >>> #serial=''pty'' >>> #usbdevice=''tablet'' >>> ##localtime=1 >>> #audio=0 >>> #ne2000=1 >>> >>> ---------------------------------------------------- >>> qemu-dm-52.log: >>> Change xvda to look like hda >>> Change xvda to look like hda >>> Change xvda to look like hda >>> Watching /local/domain/0/device-model/52/logdirty/next-active >>> Watching /local/domain/0/device-model/52/command >>> shift keysym 003e keycode 86 >>> shift keysym 00a6 keycode 86 >>> keypad keysym ffae keycode 83 >>> keypad keysym ffac keycode 83 >>> keypad keysym ffb0 keycode 82 >>> keypad keysym ffb1 keycode 79 >>> keypad keysym ffb2 keycode 80 >>> keypad keysym ffb3 keycode 81 >>> keypad keysym ffb4 keycode 75 >>> keypad keysym ffb5 keycode 76 >>> keypad keysym ffb6 keycode 77 >>> keypad keysym ffb7 keycode 71 >>> keypad keysym ffb8 keycode 72 >>> keypad keysym ffb9 keycode 73 >>> shift keysym 0021 keycode 2 >>> shift keysym 0040 keycode 3 >>> shift keysym 0023 keycode 4 >>> shift keysym 0024 keycode 5 >>> shift keysym 0025 keycode 6 >>> shift keysym 005e keycode 7 >>> shift keysym 0026 keycode 8 >>> shift keysym 002a keycode 9 >>> shift keysym 0028 keycode 10 >>> shift keysym 0029 keycode 11 >>> shift keysym 005f keycode 12 >>> shift keysym 002b keycode 13 >>> shift keysym 007b keycode 26 >>> shift keysym 007d keycode 27 >>> shift keysym 003a keycode 39 >>> shift keysym 0022 keycode 40 >>> shift keysym 007e keycode 41 >>> shift keysym 007c keycode 43 >>> shift keysym 003c keycode 51 >>> shift keysym 003e keycode 52 >>> shift keysym 003f keycode 53 >>> xs_read(): vncpasswd get error. >>> /vm/82b1f664-096e-56fe-fea0-a1b625600960/vncpasswd. >>> char device redirected to /dev/pts/1 >>> Console: prepared domain, waiting for ringref at >>> /local/domain/52/console or /local/domain/52/serial/0 >>> FB: Waiting for KBD backend creation >>> Doing backend watch on /local/domain/0/backend/vkbd/52/0 >>> FB: Waiting for FB backend creation >>> Doing backend watch on /local/domain/0/backend/vfb/52/0 >>> Console: got watch >>> Console: failed to find ring-ref/port yet >>> FB: Waiting for KBD frontend initialization >>> Doing frontend watch on /local/domain/52/device/vkbd/0 >>> Console: got watch >>> Console: failed to find ring-ref/port yet >>> FB: Carry on waiting >>> Console: got watch >>> Console: got ring-ref 1078749 port 2 >>> Console: connected to guest frontend >>> FB: Carry on waiting >>> FB: Waiting for FB frontend initialization >>> Doing frontend watch on /local/domain/52/device/vfb/0 >>> Framebuffer 800x600x32 stride 3200 >>> Framebuffer depth 32 width 800 height 600 line 3200 >>> FB: Waiting for KBD frontend connection >>> Doing frontend watch on /local/domain/52/device/vkbd/0 >>> FB: Carry on waiting >>> FB: Carry on waiting >>> FB: Carry on waiting >>> Xen Framebuffer registered >>> ----------------------------------------------------------- >>> >>> >>> >>> _______________________________________________ >>> Xen-users mailing list >>> Xen-users@lists.xensource.com >>> http://lists.xensource.com/xen-users >>> >> >> >> > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ok! Not fixed yet, but some progress. Nicolas, you were very close. instead of doing: extra=''console=xvc0'' I did: xencons=''xvc0'' And it ALMOST boots. It stops at: "Starting periodic command scheduler: crond" If I wait a few minutes, the following appears, then it is hangs indefinitely: INIT: Id "1" respawning too fast: disabled for 5 minutes INIT: no more processes left in this runlevel I am soo close here... I have tried passing everything I can think of to the "console=" dirctive, like this: extra=''xencons=xvc0, console=xvc0'' (blank screen) or extra=''xencons=xvc0, console=tty'' (hangs as stated above) or extra=''xencons=xvc0, console=pty'' (blank screen) and so on... Any help, please? Thanks. Quoting Chris <cjdl01@brokensolstice.com>:> Ok. > > Looked at both systems, and xorg.conf is an empty file. But, like I > said, since I''m not running X on either system (though xorg is > installed) I''m not sure we are barking up the right tree here... > > > > > > Quoting "Munoz, Nicolas" <nicolas.munoz@hp.com>: > >> How about your /etc/X11/xorg.conf file ? >> What''s in it ? >> >> >> -----Original Message----- >> From: Chris [mailto:cjdl01@brokensolstice.com] >> Sent: 13 August 2009 16:47 >> To: Munoz, Nicolas >> Cc: xen-users@lists.xensource.com >> Subject: RE: [Xen-users] VNC Console Hangs >> >> vnc=1 only seems to work on my hvm domUs -- not my linux native domUs. >> >> I think this is because the linux machines use the framebuffer, and >> the others do not. >> >> so, the line: >> vfb = [ ''type=vnc,vncdisplay=2'' ] >> is supposed to take care of this. Without this line, the vncserver >> never starts >> >> Changing vnc=X doesn''t seem to make any difference with the >> paravirtualized linux boxes. >> >> So... it seems to me this is an fb thing... Booting to >> non-virutalized linux boxes, you can see that this is where the >> monitor makes the switch from a non-fb to a fb console. I cannot find >> any documentation on this anywhere on this... >> >> I''ve been trying to pass kernel params regarding fb to the the domu >> using the "extra=" directive, like "extra=''vga=791''" or >> "extra=''nofb''"... they just seem ignored... >> >> Help? >> >> >> Quoting "Munoz, Nicolas" <nicolas.munoz@hp.com>: >> >>> Wait a minute, I just noticed one strange thing... >>> >>> Why is your >>> >>> vnc=1 >>> >>> Line commented? You need to uncomment it >>> >>> -----Original Message----- >>> From: Chris [mailto:cjdl01@brokensolstice.com] >>> Sent: 13 August 2009 16:12 >>> To: Munoz, Nicolas >>> Cc: xen-users@lists.xensource.com >>> Subject: RE: [Xen-users] VNC Console Hangs >>> >>> Nicolas, >>> >>> Thanks for the reply, but that isn''t working. It gives me a big black >>> screen with a flashing cursor in the upper left. The screen is >>> likewise not responsive to keyboard input. >>> >>> I did notice the /dev/xvc* does not exist on either the domu or the >>> dom0. I tried using xenconsole (/dev/xenconsole does exist in the >>> domu)... but I get the same thing. >>> >>> Any other Ideas? >>> >>> Thanks. >>> >>> >>> Quoting "Munoz, Nicolas" <nicolas.munoz@hp.com>: >>> >>>> Hi, >>>> >>>> Try to add the >>>> >>>> extra=''console=xvc0'' >>>> >>>> to your cfg file >>>> >>>> -----Original Message----- >>>> From: xen-users-bounces@lists.xensource.com >>>> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Chris >>>> Sent: 13 August 2009 14:53 >>>> To: xen-users@lists.xensource.com >>>> Subject: [Xen-users] VNC Console Hangs >>>> >>>> Hi, >>>> >>>> I am running Xen on Debian Lenny. I am having a very strange issue >>>> regarding VNC. >>>> >>>> I am able to connect to VNC just fine -- but as the paravirtualized >>>> machine boots, it stops at "lo: Disabled Privacy Extensions", and >>>> appears to hang there. The console will accept no keyboard input. >>>> >>>> However... >>>> >>>> The strange part is that "xm console" still works for this domu... >>>> when I log in, I see that the domu has booted just fine! Everything >>>> works, including networking. I need vnc to work on this this domu. >>>> (btw- vnc works flawlessly with an hvm openbsd domu on the same >>>> machine). >>>> >>>> Here is a screenshot of what I see: >>>> http://sciotech.com/xen_vnc_problem.png >>>> >>>> Below is my cfg for this domu, and the output from my log file. >>>> Please note that the commented lines in my cfg are things I have to >>>> toggled to try and fix this -- none worked. >>>> >>>> Thank you for your help. >>>> >>>> >>>> --------------------------------------------------------------------------- >>>> cfg: >>>> kernel = ''/boot/vmlinuz-2.6.26-1-xen-amd64'' >>>> ramdisk = ''/boot/initrd.img-2.6.26-1-xen-amd64'' >>>> memory = ''1536'' >>>> root = ''/dev/xvda2 ro'' >>>> disk = [ >>>> ''phy:/dev/vg/mylenny_swap,xvda1,w'', >>>> ''phy:/dev/vg/mylenny_slash,xvda2,w'', >>>> ''phy:/dev/vg/mylenny_home,xvda3,w'', >>>> ] >>>> name = ''mylennydomu'' >>>> dhcp = ''dhcp'' >>>> vif = [ ''mac=00:17:3F:2F:F7:34'' ] >>>> >>>> on_poweroff = ''destroy'' >>>> on_reboot = ''restart'' >>>> on_crash = ''restart'' >>>> >>>> vfb = [ ''type=vnc,vncdisplay=2'' ] >>>> #sdl=0 >>>> #vnc=1 >>>> #vnclisten=''0.0.0.0'' >>>> #vncconsole=1 >>>> #vncdisplay=0 >>>> #vncpasswd='''' >>>> #stdvga=0 >>>> #serial=''pty'' >>>> #usbdevice=''tablet'' >>>> ##localtime=1 >>>> #audio=0 >>>> #ne2000=1 >>>> >>>> ---------------------------------------------------- >>>> qemu-dm-52.log: >>>> Change xvda to look like hda >>>> Change xvda to look like hda >>>> Change xvda to look like hda >>>> Watching /local/domain/0/device-model/52/logdirty/next-active >>>> Watching /local/domain/0/device-model/52/command >>>> shift keysym 003e keycode 86 >>>> shift keysym 00a6 keycode 86 >>>> keypad keysym ffae keycode 83 >>>> keypad keysym ffac keycode 83 >>>> keypad keysym ffb0 keycode 82 >>>> keypad keysym ffb1 keycode 79 >>>> keypad keysym ffb2 keycode 80 >>>> keypad keysym ffb3 keycode 81 >>>> keypad keysym ffb4 keycode 75 >>>> keypad keysym ffb5 keycode 76 >>>> keypad keysym ffb6 keycode 77 >>>> keypad keysym ffb7 keycode 71 >>>> keypad keysym ffb8 keycode 72 >>>> keypad keysym ffb9 keycode 73 >>>> shift keysym 0021 keycode 2 >>>> shift keysym 0040 keycode 3 >>>> shift keysym 0023 keycode 4 >>>> shift keysym 0024 keycode 5 >>>> shift keysym 0025 keycode 6 >>>> shift keysym 005e keycode 7 >>>> shift keysym 0026 keycode 8 >>>> shift keysym 002a keycode 9 >>>> shift keysym 0028 keycode 10 >>>> shift keysym 0029 keycode 11 >>>> shift keysym 005f keycode 12 >>>> shift keysym 002b keycode 13 >>>> shift keysym 007b keycode 26 >>>> shift keysym 007d keycode 27 >>>> shift keysym 003a keycode 39 >>>> shift keysym 0022 keycode 40 >>>> shift keysym 007e keycode 41 >>>> shift keysym 007c keycode 43 >>>> shift keysym 003c keycode 51 >>>> shift keysym 003e keycode 52 >>>> shift keysym 003f keycode 53 >>>> xs_read(): vncpasswd get error. >>>> /vm/82b1f664-096e-56fe-fea0-a1b625600960/vncpasswd. >>>> char device redirected to /dev/pts/1 >>>> Console: prepared domain, waiting for ringref at >>>> /local/domain/52/console or /local/domain/52/serial/0 >>>> FB: Waiting for KBD backend creation >>>> Doing backend watch on /local/domain/0/backend/vkbd/52/0 >>>> FB: Waiting for FB backend creation >>>> Doing backend watch on /local/domain/0/backend/vfb/52/0 >>>> Console: got watch >>>> Console: failed to find ring-ref/port yet >>>> FB: Waiting for KBD frontend initialization >>>> Doing frontend watch on /local/domain/52/device/vkbd/0 >>>> Console: got watch >>>> Console: failed to find ring-ref/port yet >>>> FB: Carry on waiting >>>> Console: got watch >>>> Console: got ring-ref 1078749 port 2 >>>> Console: connected to guest frontend >>>> FB: Carry on waiting >>>> FB: Waiting for FB frontend initialization >>>> Doing frontend watch on /local/domain/52/device/vfb/0 >>>> Framebuffer 800x600x32 stride 3200 >>>> Framebuffer depth 32 width 800 height 600 line 3200 >>>> FB: Waiting for KBD frontend connection >>>> Doing frontend watch on /local/domain/52/device/vkbd/0 >>>> FB: Carry on waiting >>>> FB: Carry on waiting >>>> FB: Carry on waiting >>>> Xen Framebuffer registered >>>> ----------------------------------------------------------- >>>> >>>> >>>> >>>> _______________________________________________ >>>> Xen-users mailing list >>>> Xen-users@lists.xensource.com >>>> http://lists.xensource.com/xen-users >>>> >>> >>> >>> >> >> >> > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
FINALLY.... I found the problem. I had to edit the inittab on the domu. I changed this line: 1:2345:respawn:/sbin/getty 38400 hvc0 to this line: 1:2345:respawn:/sbin/getty 38400 tty0 And editied the securetty file and changed hvc0 to tty0 I find this very ironic, as it is the exact OPPOSITE of what is stated here: http://www.ducea.com/2009/03/18/lenny-domu-xencons/ and yes, I did have serial_device set to hvc0 in my xen-tools.conf... but it wanted to use tty for some reason. Using hvc0 in my cfg file ALWAYS gave a a blank, black screen with a flashing cursor on my vnc console. Problem solved. Thanks for your input Nicholas, it got me moving in the right direction. Chris Quoting Chris <cjdl01@brokensolstice.com>:> Ok! > > Not fixed yet, but some progress. > > Nicolas, you were very close. > > instead of doing: > extra=''console=xvc0'' > I did: > xencons=''xvc0'' > > And it ALMOST boots. > > It stops at: > "Starting periodic command scheduler: crond" > > If I wait a few minutes, the following appears, then it is hangs > indefinitely: > INIT: Id "1" respawning too fast: disabled for 5 minutes > INIT: no more processes left in this runlevel > > I am soo close here... > > I have tried passing everything I can think of to the "console=" > dirctive, like this: > extra=''xencons=xvc0, console=xvc0'' (blank screen) > or > extra=''xencons=xvc0, console=tty'' (hangs as stated above) > or > extra=''xencons=xvc0, console=pty'' (blank screen) > and so on... > > Any help, please? > > Thanks. > > Quoting Chris <cjdl01@brokensolstice.com>: > >> Ok. >> >> Looked at both systems, and xorg.conf is an empty file. But, like I >> said, since I''m not running X on either system (though xorg is >> installed) I''m not sure we are barking up the right tree here... >> >> >> >> >> >> Quoting "Munoz, Nicolas" <nicolas.munoz@hp.com>: >> >>> How about your /etc/X11/xorg.conf file ? >>> What''s in it ? >>> >>> >>> -----Original Message----- >>> From: Chris [mailto:cjdl01@brokensolstice.com] >>> Sent: 13 August 2009 16:47 >>> To: Munoz, Nicolas >>> Cc: xen-users@lists.xensource.com >>> Subject: RE: [Xen-users] VNC Console Hangs >>> >>> vnc=1 only seems to work on my hvm domUs -- not my linux native domUs. >>> >>> I think this is because the linux machines use the framebuffer, and >>> the others do not. >>> >>> so, the line: >>> vfb = [ ''type=vnc,vncdisplay=2'' ] >>> is supposed to take care of this. Without this line, the vncserver >>> never starts >>> >>> Changing vnc=X doesn''t seem to make any difference with the >>> paravirtualized linux boxes. >>> >>> So... it seems to me this is an fb thing... Booting to >>> non-virutalized linux boxes, you can see that this is where the >>> monitor makes the switch from a non-fb to a fb console. I cannot find >>> any documentation on this anywhere on this... >>> >>> I''ve been trying to pass kernel params regarding fb to the the domu >>> using the "extra=" directive, like "extra=''vga=791''" or >>> "extra=''nofb''"... they just seem ignored... >>> >>> Help? >>> >>> >>> Quoting "Munoz, Nicolas" <nicolas.munoz@hp.com>: >>> >>>> Wait a minute, I just noticed one strange thing... >>>> >>>> Why is your >>>> >>>> vnc=1 >>>> >>>> Line commented? You need to uncomment it >>>> >>>> -----Original Message----- >>>> From: Chris [mailto:cjdl01@brokensolstice.com] >>>> Sent: 13 August 2009 16:12 >>>> To: Munoz, Nicolas >>>> Cc: xen-users@lists.xensource.com >>>> Subject: RE: [Xen-users] VNC Console Hangs >>>> >>>> Nicolas, >>>> >>>> Thanks for the reply, but that isn''t working. It gives me a big black >>>> screen with a flashing cursor in the upper left. The screen is >>>> likewise not responsive to keyboard input. >>>> >>>> I did notice the /dev/xvc* does not exist on either the domu or the >>>> dom0. I tried using xenconsole (/dev/xenconsole does exist in the >>>> domu)... but I get the same thing. >>>> >>>> Any other Ideas? >>>> >>>> Thanks. >>>> >>>> >>>> Quoting "Munoz, Nicolas" <nicolas.munoz@hp.com>: >>>> >>>>> Hi, >>>>> >>>>> Try to add the >>>>> >>>>> extra=''console=xvc0'' >>>>> >>>>> to your cfg file >>>>> >>>>> -----Original Message----- >>>>> From: xen-users-bounces@lists.xensource.com >>>>> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Chris >>>>> Sent: 13 August 2009 14:53 >>>>> To: xen-users@lists.xensource.com >>>>> Subject: [Xen-users] VNC Console Hangs >>>>> >>>>> Hi, >>>>> >>>>> I am running Xen on Debian Lenny. I am having a very strange issue >>>>> regarding VNC. >>>>> >>>>> I am able to connect to VNC just fine -- but as the paravirtualized >>>>> machine boots, it stops at "lo: Disabled Privacy Extensions", and >>>>> appears to hang there. The console will accept no keyboard input. >>>>> >>>>> However... >>>>> >>>>> The strange part is that "xm console" still works for this domu... >>>>> when I log in, I see that the domu has booted just fine! Everything >>>>> works, including networking. I need vnc to work on this this domu. >>>>> (btw- vnc works flawlessly with an hvm openbsd domu on the same >>>>> machine). >>>>> >>>>> Here is a screenshot of what I see: >>>>> http://sciotech.com/xen_vnc_problem.png >>>>> >>>>> Below is my cfg for this domu, and the output from my log file. >>>>> Please note that the commented lines in my cfg are things I have to >>>>> toggled to try and fix this -- none worked. >>>>> >>>>> Thank you for your help. >>>>> >>>>> >>>>> --------------------------------------------------------------------------- >>>>> cfg: >>>>> kernel = ''/boot/vmlinuz-2.6.26-1-xen-amd64'' >>>>> ramdisk = ''/boot/initrd.img-2.6.26-1-xen-amd64'' >>>>> memory = ''1536'' >>>>> root = ''/dev/xvda2 ro'' >>>>> disk = [ >>>>> ''phy:/dev/vg/mylenny_swap,xvda1,w'', >>>>> ''phy:/dev/vg/mylenny_slash,xvda2,w'', >>>>> ''phy:/dev/vg/mylenny_home,xvda3,w'', >>>>> ] >>>>> name = ''mylennydomu'' >>>>> dhcp = ''dhcp'' >>>>> vif = [ ''mac=00:17:3F:2F:F7:34'' ] >>>>> >>>>> on_poweroff = ''destroy'' >>>>> on_reboot = ''restart'' >>>>> on_crash = ''restart'' >>>>> >>>>> vfb = [ ''type=vnc,vncdisplay=2'' ] >>>>> #sdl=0 >>>>> #vnc=1 >>>>> #vnclisten=''0.0.0.0'' >>>>> #vncconsole=1 >>>>> #vncdisplay=0 >>>>> #vncpasswd='''' >>>>> #stdvga=0 >>>>> #serial=''pty'' >>>>> #usbdevice=''tablet'' >>>>> ##localtime=1 >>>>> #audio=0 >>>>> #ne2000=1 >>>>> >>>>> ---------------------------------------------------- >>>>> qemu-dm-52.log: >>>>> Change xvda to look like hda >>>>> Change xvda to look like hda >>>>> Change xvda to look like hda >>>>> Watching /local/domain/0/device-model/52/logdirty/next-active >>>>> Watching /local/domain/0/device-model/52/command >>>>> shift keysym 003e keycode 86 >>>>> shift keysym 00a6 keycode 86 >>>>> keypad keysym ffae keycode 83 >>>>> keypad keysym ffac keycode 83 >>>>> keypad keysym ffb0 keycode 82 >>>>> keypad keysym ffb1 keycode 79 >>>>> keypad keysym ffb2 keycode 80 >>>>> keypad keysym ffb3 keycode 81 >>>>> keypad keysym ffb4 keycode 75 >>>>> keypad keysym ffb5 keycode 76 >>>>> keypad keysym ffb6 keycode 77 >>>>> keypad keysym ffb7 keycode 71 >>>>> keypad keysym ffb8 keycode 72 >>>>> keypad keysym ffb9 keycode 73 >>>>> shift keysym 0021 keycode 2 >>>>> shift keysym 0040 keycode 3 >>>>> shift keysym 0023 keycode 4 >>>>> shift keysym 0024 keycode 5 >>>>> shift keysym 0025 keycode 6 >>>>> shift keysym 005e keycode 7 >>>>> shift keysym 0026 keycode 8 >>>>> shift keysym 002a keycode 9 >>>>> shift keysym 0028 keycode 10 >>>>> shift keysym 0029 keycode 11 >>>>> shift keysym 005f keycode 12 >>>>> shift keysym 002b keycode 13 >>>>> shift keysym 007b keycode 26 >>>>> shift keysym 007d keycode 27 >>>>> shift keysym 003a keycode 39 >>>>> shift keysym 0022 keycode 40 >>>>> shift keysym 007e keycode 41 >>>>> shift keysym 007c keycode 43 >>>>> shift keysym 003c keycode 51 >>>>> shift keysym 003e keycode 52 >>>>> shift keysym 003f keycode 53 >>>>> xs_read(): vncpasswd get error. >>>>> /vm/82b1f664-096e-56fe-fea0-a1b625600960/vncpasswd. >>>>> char device redirected to /dev/pts/1 >>>>> Console: prepared domain, waiting for ringref at >>>>> /local/domain/52/console or /local/domain/52/serial/0 >>>>> FB: Waiting for KBD backend creation >>>>> Doing backend watch on /local/domain/0/backend/vkbd/52/0 >>>>> FB: Waiting for FB backend creation >>>>> Doing backend watch on /local/domain/0/backend/vfb/52/0 >>>>> Console: got watch >>>>> Console: failed to find ring-ref/port yet >>>>> FB: Waiting for KBD frontend initialization >>>>> Doing frontend watch on /local/domain/52/device/vkbd/0 >>>>> Console: got watch >>>>> Console: failed to find ring-ref/port yet >>>>> FB: Carry on waiting >>>>> Console: got watch >>>>> Console: got ring-ref 1078749 port 2 >>>>> Console: connected to guest frontend >>>>> FB: Carry on waiting >>>>> FB: Waiting for FB frontend initialization >>>>> Doing frontend watch on /local/domain/52/device/vfb/0 >>>>> Framebuffer 800x600x32 stride 3200 >>>>> Framebuffer depth 32 width 800 height 600 line 3200 >>>>> FB: Waiting for KBD frontend connection >>>>> Doing frontend watch on /local/domain/52/device/vkbd/0 >>>>> FB: Carry on waiting >>>>> FB: Carry on waiting >>>>> FB: Carry on waiting >>>>> Xen Framebuffer registered >>>>> ----------------------------------------------------------- >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Xen-users mailing list >>>>> Xen-users@lists.xensource.com >>>>> http://lists.xensource.com/xen-users >>>>> >>>> >>>> >>>> >>> >>> >>> >> >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users > > > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users