similar to: no xenfb in Fedora 8 Xen kernel?

include/xen/xenbus.h nicely declares struct xenbus_driver''s ''ids'' member as pointer to const... As usual, written and tested on 2.6.25-rc3 and made apply to the 2.6.18 tree without further testing. Signed-off-by: Jan Beulich <jbeulich@novell.com> Index: head-2008-02-26/drivers/xen/blkback/xenbus.c

After some changes resulting in the irq (since used as an array index) to be converted to unsigned int, we''re observing oopses resulting from xenfb calling notify_remote_via_irq() with -1 as the irq argument. Clearly, the two possible simple work-arounds would be to either make the event channel code always tolerate and ignore invalid irq inputs or to prevent the call to

Unfortunately we managed to not catch in our automatic testing this oversight during the porting of the corresponding pv-ops patch (info->irq now getting set later, which doesn''t matter for pv-ops as that has the event channel at hand). Signed-off-by: Jan Beulich <jbeulich@novell.com> --- a/drivers/xen/fbfront/xenfb.c +++ b/drivers/xen/fbfront/xenfb.c @@ -757,7 +757,7 @@ static

Hi, Is vfb working well lately? I thought I''d test it out on ia64 and it works great, but only once per boot. If I stop the domain and restart it, I get the following: Error: Device 0 (vkbd) is already connected. To make sure this isn''t an ia64 anomaly, I tried it on an x86_64 system. Same thing, works the first time, reboot the domain and it''s broken. I see

ioemu: fix xenfb slow case update Signed-off-by: Samuel Thibault <samuel.thibault@eu.citrix.com> diff -r 067d8f19e78a tools/ioemu/hw/xenfb.c --- a/tools/ioemu/hw/xenfb.c Thu Feb 28 13:55:37 2008 +0000 +++ b/tools/ioemu/hw/xenfb.c Fri Feb 29 15:25:17 2008 +0000 @@ -1072,7 +1072,7 @@ /* A convenient function for munging pixels between different depths */ #define

Hi folks There are two components, which are currently not included in the main utils package: ioemu, xenfb. ioemu is currently shipped in its own package, xenfb is not shipped at all. Should we fold them into the main utils package for simplicity? ioemu adds 300k to the package and 4300k in one dependency (libsdl1.2debian). xenfb adds another 200k to the package and 200k in one dependency

The following series of 10 patches is a merge of the xenfb and xenconsoled functionality into the qemu-dm code. The general approach taken is to have qemu-dm provide two machine types - one for xen paravirt, the other for fullyvirt. For compatability the later is the default. The goals overall are to kill LibVNCServer, remove alot of code duplication and/or parallel impls of the same concepts, and

Patches 1of2 and 2of2 adds multiple frame buffer resolution support to the PV xenfb frame buffer driver and the PV xenfb VNC server. API Changelog entry is included here as I did not see doc/ChangeLog when I did a tip clone this morning. --------------------------------------------------------------- API Changelog entry: PV framebuffer multiple resolution facility: Guest may send

Hi, When I tested pvfb, I got the following warnings. It seems to be caused by checking/setting info->dirty without dirty_lock. We need to check/set info->dirty safely. xenfb_update_screen bogus rect 2147483647 0 2147483647 0 BUG: warning at /root/linux-2.6.18-xen.hg/drivers/xen/fbfront/xenfb.c:240/xenfb_update_screen() Call Trace: [<ffffffff8036920e>] xenfb_thread+0x19b/0x2be

Hi all, I''m trying to expand the screen resolution of my guest when using vnc. It appears I need to use the extra variable in my guest config file and xenfb. I pass it in like this: extra = ''xenfb.video=8,1024,768'' I can see this being passed to the kernel when it boots but it doesn''t change the vnc screen resolution. I also see this when I type ps -ef |

Goodmorning, I''m currently playing with XEN/arm on my Allwinner A20 (cubieboard2) I would like to get the XENFB driver working on domU. But currently in xen/arm there''s no support for VFB, atleast qemu is not supported. But this video http://www.youtube.com/watch?v=po1IeElg8tg and this one http://www.youtube.com/watch?v=Km6gBnIqaWo is showing a working framebuffer. So there are

Hi all, I recently installed Squeeze, followed but Xen 4.0. A few notes of things I've run into while installing. The network script part of the xend-config.sxp does not appear to work. Everything would boot find until I uncommented that line and tried to set it up per the Debian Xen wiki. I managed to get bridging to work using the debian network bridge tools, brctl. Xen does not

Attached patch includes dz in the mouse event packet sent to the frontend. Needed for mouse wheel support in a PV guest. Please apply to xen- unstable. Signed- off- by: Pat Campbell <plc@novell.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. Differences since last post: * Required patch fixing 32-on-64 xen-blkfront included. * Cleanup when xenkbd_probe() fails fixed. * Don't store event channel in device info. I started

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. Differences since last post: * Required patch fixing 32-on-64 xen-blkfront included. * Cleanup when xenkbd_probe() fails fixed. * Don't store event channel in device info. I started

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. Differences since last post: * Required patch fixing 32-on-64 xen-blkfront included. * Cleanup when xenkbd_probe() fails fixed. * Don't store event channel in device info. I started

When I try to create a PV domU, the VM starts up and I can access it through "xm console <id>", but when I try to connect to it through VNC, the port just hangs. I''ve tried using RealVNC and TightVNC, and also tried on Linux and Windows. All that happens on the client is that it says that the connection has established, and hangs there. I''ve tried running

As many of us are all too painfully aware we have completely different VNC server implementations for paravirt vs fullyvirt Xen guests. The former based on libvncserver, the latter integrated into QEMU. There are many new and interesting ideas being tried out in the VNC server space in particular wrt to virtualization and having to implement them all twice is not very desirable. Also

Hello, The following two patches add an additional offset part in the FB resize event. Samuel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi All, The following is my domU''s cfg file. # ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ kernel = ''/usr/local/src/xen/vmlinuz'' ramdisk = ''/usr/local/src/xen/initrd.img'' memory = ''256'' name = ''centos5.2'' vif0 = [ ''bridge=xenbr1'' ] disk = [ ''phy:/dev/server/cbox,xvda,w'' ] on_reboot =