search for: xen_fbdev_frontend

Hi I just upgraded my domU kernel from 2.6.29-gentoo-r5 to 2.6.30-gentoo-r4 and was not able to boot successful. Only after disabling the xen frame buffer I was able to boot my domU kernel. Did I mis configure something or has the xen framebuffer fallen into the hands of the bitrot monster? No obvious hinds or messages on the (text) console or on xm dmesg. The output stops just before the

Hello, I wants to make a self compiled kernel for my domUs on a debian etch server with Xen 3.1.4 and 2.6.18.8 dom0 kernel. So, I download sources for linux-2.6.26.8, and I enabled all the Xen features : Symbol: HVC_XEN [=y] Symbol: XEN_BALLOON [=y] Symbol: XEN_FBDEV_FRONTEND [=y] Symbol: XEN_SCRUB_PAGES [=y] Symbol: XEN_KBDDEV_FRONTEND [=y] Symbol: XEN_BLKDEV_FRONTEND [=y] Symbol: XEN_NETDEV_FRONTEND [=y] Symbol: XEN [=y] my domu configuration file is : kernel = ''/boot/vmlinuz-2.6.26.8'' ramdisk = ''/boot/...

...by: Andrew Jones <drjones@redhat.com> --- drivers/video/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/video/Kconfig b/drivers/video/Kconfig index e7068c5..1969ea1 100644 --- a/drivers/video/Kconfig +++ b/drivers/video/Kconfig @@ -2245,7 +2245,7 @@ config XEN_FBDEV_FRONTEND select FB_SYS_IMAGEBLIT select FB_SYS_FOPS select FB_DEFERRED_IO - select INPUT_XEN_KBDDEV_FRONTEND + select INPUT_XEN_KBDDEV_FRONTEND if INPUT_MISC select XEN_XENBUS_FRONTEND default y help -- 1.7.11.7

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. I started with the Xen version at http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/ca05cf1a9bdc Differences to that Xen version, for those who care: * Rewritten on top of fb deferred

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. I started with the Xen version at http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/ca05cf1a9bdc Differences to that Xen version, for those who care: * Rewritten on top of fb deferred

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. I started with the Xen version at http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/ca05cf1a9bdc Differences to that Xen version, for those who care: * Rewritten on top of fb deferred

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

...changed, 816 insertions(+), 0 deletions(-) > create mode 100644 drivers/video/virtio-fb.c > > diff --git a/drivers/video/Kconfig b/drivers/video/Kconfig > index 9bbb285..f9be4c2 100644 > --- a/drivers/video/Kconfig > +++ b/drivers/video/Kconfig > @@ -2069,6 +2069,21 @@ config XEN_FBDEV_FRONTEND > frame buffer driver. It communicates with a back-end > in another domain. > > +config FB_VIRTIO > + tristate "Virtio virtual frame buffer support" > + depends on FB && VIRTIO > + select FB_SYS_FILLRECT > + select FB_SYS_COPYAREA > + select F...

...changed, 816 insertions(+), 0 deletions(-) > create mode 100644 drivers/video/virtio-fb.c > > diff --git a/drivers/video/Kconfig b/drivers/video/Kconfig > index 9bbb285..f9be4c2 100644 > --- a/drivers/video/Kconfig > +++ b/drivers/video/Kconfig > @@ -2069,6 +2069,21 @@ config XEN_FBDEV_FRONTEND > frame buffer driver. It communicates with a back-end > in another domain. > > +config FB_VIRTIO > + tristate "Virtio virtual frame buffer support" > + depends on FB && VIRTIO > + select FB_SYS_FILLRECT > + select FB_SYS_COPYAREA > + select F...

Hello, I''ve recently installed a hvm domU opensuse 11 guest and I cannot set the screen resolution higher then 640x480. This seems very strange to me, because I don''t have any problem to set higher resolution on a windows 7 domU, using the following parameters in the configuration file: stdvga=1 videoram=16 What could the problem be? Is some video driver missing? -- Flavio

Hello, I''ve recently installed a hvm domU opensuse 11 guest and I cannot set the screen resolution higher then 640x480. This seems very strange to me, because I don''t have any problem to set higher resolution on a windows 7 domU, using the following parameters in the configuration file: stdvga=1 videoram=16 What could the problem be? Is some video driver missing? -- Flavio

Hello, I''ve previously been successful with Xen4 and VT-d on other systems. I am having trouble getting VT-d passthrough working to a WinXP domain with DX58SO (Q45) motherboard and i7 930 CPU. VT-d is enabled in bios, xm info shows hvm_directio capability, I have iommu=1 set, I have the devices bound to pciback on dom0 cmdline, xm pci-list-assignable-devices shows the devices as

Hello, I''ve previously been successful with Xen4 and VT-d on other systems. I am having trouble getting VT-d passthrough working to a WinXP domain with DX58SO (Q45) motherboard and i7 930 CPU. VT-d is enabled in bios, xm info shows hvm_directio capability, I have iommu=1 set, I have the devices bound to pciback on dom0 cmdline, xm pci-list-assignable-devices shows the devices as