WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] VNC console access in paravirtualized domUs

On Friday June 06 2008 07:30:44 am you wrote:
> The tip about hvc0/xvc0 was helpful in getting Debian Lenny going; for
> grins I decided to spin an image of Lenny to assist in
> troubleshooting.  Regarding the framebuffer (using Lenny for
> reference), I've got the xorg fbdev package installed.  I've added a
> section to xorg.conf like:
>
> Section "Device"
>          Identifier "vnctest"
>          Driver "fbdev"
> EndSection

Here's my F9 pv xorg.conf:

# Xorg configuration created by system-config-display

Section "ServerLayout"
        Identifier     "single head configuration"
        Screen      0  "Screen0" 0 0
        InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "InputDevice"
        Identifier  "Keyboard0"
        Driver      "kbd"
        Option      "XkbModel" "pc105"
        Option      "XkbLayout" "us+inet"
EndSection

Section "Device"
        Identifier  "Videocard0"
        Driver      "fbdev"
EndSection

Section "Screen"
        Identifier "Screen0"
        Device     "Videocard0"
        DefaultDepth     24
        SubSection "Display"
                Viewport   0 0
                Depth     24
        EndSubSection
EndSection

In particular, note how the last two sections relate to each other - The 
identifier you associate with the fbdev driver has to be specified in the 
Screen section.

> But as far as I can tell, the issue is that the domU does not expose
> the framebuffer to the dom0:
>
> XENBUS: Device with no driver: device/vkbd/0
> XENBUS: Device with no driver: device/vfb/0
> XENBUS: Device with no driver: device/console/0

I've seen this many times on this list, and on my own pv domus, and I think 
they are just pre-initialization messages - an indication that xen is about 
to look for drivers. Anybody know any differently?

> I believe that's why I see "parallel0 console" in VNC.  There is no
> /dev/fb0 on the domU (docs make reference to this; I've got to believe
> udev would throw it up if it were configured properly).  Any ideas
> there?

With no more than the above xorg.conf, the output of 'ls -alF /dev/fb*' for me 
is:

lrwxrwxrwx 1 root root     3 2008-05-26 17:21 /dev/fb -> fb0
crw------- 1 jimb root 29, 0 2008-06-06 18:05 /dev/fb0

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users