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

[Paul Schulze <avlex@xxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Jim,

For a 2.6.25 kernel that is be true, but he said he is using Hardy  
and I think he is using the same kernel for his Hardy DomU as me.  
That being said, the standard Hardy Dom0/U kernel is version 2.6.24  
with the Xen components ported from RedHat/Fedora kernel 2.6.22 or 23  
(as far as I remember), so it is still the old XEN_FRAMEBUFFER=y he  
has to look out for. It would be interesting to see what happens with  
a 2.6.25+ kernel though, but at the moment I have more pressing  
issues to deal with, so I can't do any testing.
However, I can say this much, as long as Xorg is not running, it  
won't have any effect on the framebuffer. The problem here is simply  
to tell the kernel to use XenFB for its output, though there is the  
possibility that the same problem occurs with the kernel output  
module as does with Xorg and therefor the kernel refuses to use the  
framebuffer. In that case, the sollution is not that simple, it would  
need some kernel debugging since there doesn't seem to be a patch  
yet. And thats rather complicated (not sure if I could do it, maybe  
Ray can, depending on his level of experience). "/var/log/syslog" or  
"/var/log/kern.log" might have some information on this.
Even though I think VNC for console output isn't all that useful, I  
will do some testing on it once I finish up my current Xen project,  
but don't expect too much.
Cheers,


Paul.


- --
Paul Schulze
avlex@xxxxxxx
Public Key: http://solaris-net.dyndns.org/keys/key_avlex.asc

"Making mistakes is human,
but to really fuck things up you need Computers"


Am 20.06.2008 um 01:25 schrieb jim burns:

> On Thursday June 19 2008 10:03:27 am Paul Schulze wrote:
> > The vfb.ko module has nothing to do with Xen as far as I know. That
> > is only a dummy module, used for development and testing. What you
> > need is the Xen framebuffer, you can check which Xen components are
> > in your DomU's kernel by simply using: "grep 'XEN' /boot/config-$
> > (uname -r)". You'll want to look for XEN_FRAMEBUFFER in this
> > particular case (I think that was it).
> This would be true for, say, 2.6.21. For a pvops kernel such as  
> 2.6.25, the
> config setting is XEN_FBDEV_FRONTEND (for the domu), which  
> typically is
> builtin, not a module (as is also XEN_FRAMEBUFFER). Also note that  
> in Xorg
> 7.3, with xorg-x11-drv-fbdev installed, and 'fbdev' as your video  
> device in
> your xorg.conf, it is actually /usr/bin/Xorg that opens the /dev/ 
> fb0 device,
> which can be confirmed with 'lsof|grep /dev/fb'.
>
> > For your Hardy DomU, the only thing I can tell you is that this has
> > nothing to do with Xorg, since it isn't even installed.
> At one point, Ray did an 'apt-get -y install xorg', but that may  
> have just
> been experimentation.
>
> I'm glad that you and Ray are putting your heads together on this.  
> I was very
> impressed how you researched that Xorg bug in your thread 'PV DomU  
> VNC screen
> black and Xorg error'.
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFIW4/bYDWOGtiChoARAkj7AJwPKApzxDioe2rqQeFSQPJbgKq7PQCff8f2
u3ysKGSB0i0Z1uzDnP+4xvU=
=o7bm
-----END PGP SIGNATURE-----

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