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

To: "jim burns" <jim_burn@xxxxxxxxxxxxx>
Subject: Re: [Xen-users] VNC console access in paravirtualized domUs
From: "Ray Barnes" <tical.net@xxxxxxxxx>
Date: Sat, 7 Jun 2008 14:35:42 -0400
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sat, 07 Jun 2008 11:36:14 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=Ze1/femicnmOakQNB0N95qwMDM2wrXGl8fLS3AVivzE=; b=nYlXSUo/YADtUYvXxTuAyVW76arXMhH7zObOUaHpSOO8yQ5tR/VA4+/ni+qHimBO0m HvwIqL4GhzSZtc+s5IV+rbFAHRGhrTw5/igyLaEqdFOBbchZ2Sv3ucfvHhHRSdOxt9p8 8KnuK88fbkbBJvNnMZBMlH3IUsCdM27logdeU=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=jD3X/IewvJtQtB7rpY4eGzEXGQ4t63d+Uei799dWJUN6eXVZ9Au889bW2nV1bEirHf tt1F9Jn41+/3raWtJaQeJZTV8JBNtKsgwvbaX3TFDz7wBY2MmkQgsFnsshpRSFerSm1J G9QhaAw/ne3P0lTKf0zCPC4Qfs/nFCCEWjtIk=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <200806070914.25710.jim_burn@xxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <afa5bb590806050138g4615f91ge3e9b6a5bdcde3c@xxxxxxxxxxxxxx> <200806061813.37786.jim_burn@xxxxxxxxxxxxx> <afa5bb590806070254u2e9cfe42o2ff3c7f2835fff3c@xxxxxxxxxxxxxx> <200806070914.25710.jim_burn@xxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Sat, Jun 7, 2008 at 9:14 AM, jim burns <jim_burn@xxxxxxxxxxxxx> wrote:
> I believe I mentioned that the fbdev frame buffer is what is used by xen 3.1.2
> and up. CentOS 5[.1] uses a xen 3.0.3 with 3.1 forward ports. I would doubt
> it changed over to fbdev, since that change was introduced in F8 after CentOS
> 5.1 had been out for awhile.

Got it.  Please bear with me as I'm relatively noobish on this
subject.  First off, I did replace my xorg.conf with yours - no
change, but I've got a pretty good idea why it doesn't work (below).
At the risk of generating more (potentially useless) list traffic,
here's what I've done as of late:

I found http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=398056 which
purports that the framebuffer simply doesn't work under kernel
versions prior to 2.6.25-1 under Debian (granted the platform is k7
not 686, but I assumed that to be true on 686 for the moment since I
have no desire to weed through endless changelogs).  So I upgraded
Lenny to Sid which has 2.6.25-2, figuring it wouldn't hurt (hopefully)
to have the newer kernel.  What I found is there's still no generation
of /dev/fb0.  If I 'insmod vfb.ko' (not sure if that's appropriate or
not), I get "-1 No such device or address" returned.  All of vfb.ko's
module dependencies are loading fine.  I can also 'insmod vga16fb.ko'
which works and outputs:

vga16fb: mapped to 0xc00a0000
Console: switching to colour frame buffer device 80x30
fb0: VGA16 VGA frame buffer device

as seen by dmesg.  So now I have a /dev/fb0 which goes nowhere as Xen
won't attach it.  I tried sticking the vga16fb module in the initrd;
it loads right after I get the "XENBUS: Device with no driver:
device/vfb/0" message on the console.  It never connects up
subsequently either, as I see "xenbus_dev_shutdown: device/vfb/0:
Initialising != Connected, skipping" - not sure if xen would make any
attempt to connect up if the driver were subsequently exposed, so
forgive me if that sounds dumb.  I've also read about a new driver
called "pvfb" which was introduced into the kernel earlier this year -
not sure what bearing that has on things, or if it makes fbdev
obsolete in some way.

-Ray

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

<Prev in Thread] Current Thread [Next in Thread>