RE: [Xen-users] Re: FULL VIRTUALIZATION - missing /dev/fb0

["Artur Linhart - Linux communication" <AL.LINUX@xxxxxxxxxxx>]

Hello,

        I have the same problem like the one described below...

        Did somebody resolved the issue with the missing /dev/fd0 device?

        Mknod does not help. What does it mean "configure udev properly"? If
fb works OK without Xen, how should I configure udev for xen - what should
be modified in the xen configuration to get Dom0 working again, like if
running without Xen?

        Any help would be appreciated, 

        With best regards

                Archie

-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Andre Rein
Sent: Wednesday, February 28, 2007 4:09 PM
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Re: FULL VIRTUALIZATION

Petersson, Mats <Mats.Petersson <at> amd.com> writes:

> 
> 
> > -----Original Message-----
> > From: Carlo [mailto:carlo <at> granisso.it] 
> > Sent: 28 February 2007 10:54
> > To: Petersson, Mats; Carlo; xen-users <at> lists.xensource.com
> > Subject: RE: [Xen-users] FULL VIRTUALIZATION
> > 
> > I've solved the first problem: path of qemu-dm in the config file was
> > uncorrect...
> > 
> > Now, qemu-dm say:
> > 
> > domid: 6
> > qemu: the number of cpus is 1
> > shared page at pfn:1ffff, mfn: df18
> > buffered io page at pfn:1fffd, mfn: df1a
> > 
> >        ---------------------- DirectFB v0.9.25 ---------------------
> >              (c) 2000-2002  convergence integrated media GmbH
> >              (c) 2002-2004  convergence GmbH
> >         -----------------------------------------------------------
> > 
> > (*) DirectFB/Core: Single Application Core. (2006-12-04 07:00)
> > (*) Direct/Memcpy: Using MMXEXT optimized memcpy()
> > (!) Direct/Util: opening '/dev/fb0' and '/dev/fb/0' failed
> >     --> No such file or directory
> > (!) DirectFB/FBDev: Error opening framebuffer device!
> > (!) DirectFB/FBDev: Use 'fbdev' option or set FRAMEBUFFER environment
> > variable.
> > (!) DirectFB/Core: Could not initialize 'system' core!
> >     --> Initialization error!
> > Could not initialize SDL - exiting

got the same Problem here :)
You don´t have a Framebufferdevice /dev/fb0. Create one withe mknod or 
configure udev properly.

Second choice, use vnc (vnc=1) and connect with xvncviewer ip:0, so I do.

here my config:


kernel  = '/usr/lib/xen-3.0.3-1/boot/hvmloader'
builder = 'hvm'
memory  = '1024'
device_model='/usr/lib/xen-3.0.3-1/bin/qemu-dm'


disk    = [

'file:/home/xen/windoof/windisk.img,ioemu:hda,w',
'file:/home/ar/WXPVOL_DE.ISO,ioemu:hdc:cdrom,r'
]
#disk    = [ 'phy:/dev/hda,hda,r' ]


name    = 'windoof'


vif = ['type=ioemu, bridge=xenbr0']


boot='d'
vnc=1
vncpassword='xyz'
vncunused=1
vncviewer=0
#vnclisten="127.0.0.1"
serial='pty'
sdl=0



greetings


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

__________ Informace od NOD32 2082 (20070226) __________

Tato zprava byla proverena antivirovym systemem NOD32.
http://www.nod32.cz



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