search for: pvfb

Samuel Thibault, le Tue 04 Mar 2008 16:12:20 +0000, a écrit : > Markus Armbruster, le Tue 04 Mar 2008 16:48:20 +0100, a écrit : > > I imagine (perhaps naively): > > > > * The domU writes to a framebuffer provided by the frontend. > > > > * The framebuffer (not a copy of it) can be shared with the backend, > > which only reads. > > Well,

...age----- >From: xen-ia64-devel-bounces@lists.xensource.com [mailto:xen-ia64-devel-bounces@lists.xensource.com] On Behalf Of Atsushi >SAKAI >Sent: 2006年12月4日 12:22 >To: xen-devel@lists.xensource.com; xen-ia64-devel@lists.xensource.com >Subject: [Xen-ia64-devel] [PATCH] buildconfigsfor pvfb > >Hi, > >This is a patch for Kconfig (PVFB related) changes. >Without this fixes, >user should reply at following phase (for example) >scripts/kconfig/conf -o arch/i386/Kconfig > >the following question raised >Framebuffer-device frontend driver (XEN_FRAMEBUFFER) >...

This makes the Xen console just work. Before, you had to ask for it on the kernel command line with console=hvc0 Signed-off-by: Markus Armbruster <armbru at redhat.com> --- diff --git a/arch/x86/xen/enlighten.c b/arch/x86/xen/enlighten.c index 49e5358..df63185 100644 --- a/arch/x86/xen/enlighten.c +++ b/arch/x86/xen/enlighten.c @@ -25,6 +25,7 @@ #include <linux/mm.h> #include

...'re not doing any CPU emulation merely using the event loop/display state. So to workaround this assumption I create a single CPUState * instance, and permanently disable it by setting ''cpu->hflags = HF_HALTED_MASK''. Seems to do the job. Next, up we attach to the guest PVFB frontend - just using the existing code for this - qemu/hw/xenfb.c (formerly xen-unstable/tools/xenfb/xenfb.c). Now we register a QEMU graphical console, a mouse event receiver, a keyboard event receiver, and register the xenstored and event channel file handles with QEMU''s event loop. F...

...e resolution support is enabled the guests frame buffer size jumps from 2MB to 5MB. Maximum scanline length is 1280 pixels. Code can support any resolution thats fits within the 5MB and does not exceed a width of 1280. New xenstore virtual machine specific VNC attributes: vncresizable-pvfb: For those that don''t need higher resolutions in their guest. Default: 0. vnc-fixevdev-abs: Older versions of evdev do not have an option to disable scaling. This attribute adjust the abs mouse position to counter evdevs scaling. Default: 0 Attribute usage:...

This is an update to the Linux part of the Xen PVFB. Linux Xen PVFB 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. Their backends run in dom0 user space. Parts in this patch series: 1. Enable Xen console by default in domU 2. P...

This is an update to the Linux part of the Xen PVFB. Linux Xen PVFB 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. Their backends run in dom0 user space. Parts in this patch series: 1. Enable Xen console by default in domU 2. P...

This is an update to the Linux part of the Xen PVFB. Linux Xen PVFB 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. Their backends run in dom0 user space. Parts in this patch series: 1. Enable Xen console by default in domU 2. P...

...a dummy. In that case, we want the preferred console to be the Xen console hvc0, and we want it without having to fiddle with the kernel command line. Even with PV framebuffer enabled, we still want to enable the Xen console as well. Problem: when tty registers, we can't yet know whether the PVFB is enabled. By the time we can know (xenstore is up), the console setup game is over. Enable the Xen console hvc by default, and make it the preferred console. Change the preferred to tty when PVFB probes successfully. Signed-off-by: Markus Armbruster <armbru at redhat.com> --- This patch...

...a dummy. In that case, we want the preferred console to be the Xen console hvc0, and we want it without having to fiddle with the kernel command line. Even with PV framebuffer enabled, we still want to enable the Xen console as well. Problem: when tty registers, we can't yet know whether the PVFB is enabled. By the time we can know (xenstore is up), the console setup game is over. Enable the Xen console hvc by default, and make it the preferred console. Change the preferred to tty when PVFB probes successfully. Signed-off-by: Markus Armbruster <armbru at redhat.com> --- This patch...

...a dummy. In that case, we want the preferred console to be the Xen console hvc0, and we want it without having to fiddle with the kernel command line. Even with PV framebuffer enabled, we still want to enable the Xen console as well. Problem: when tty registers, we can't yet know whether the PVFB is enabled. By the time we can know (xenstore is up), the console setup game is over. Enable the Xen console hvc by default, and make it the preferred console. Change the preferred to tty when PVFB probes successfully. Signed-off-by: Markus Armbruster <armbru at redhat.com> --- This patch...

Hello, Sometimes the backend of PVFB knows that it doesn''t need permanent refresh, when the window is minimized for instance (no refresh at all), or the administration tools know that the window is thumnailed, and so a slow refresh rate is fine. Also, some users may want to tune the refresh rate according to the smoothness t...

...ecessary to complain to me about this bug report on IRC I'm replying to this bug now as well. > On Thu, Jun 19, 2008 at 04:56:54PM +0200, Thomas Bl?sing wrote: > > CVE-2008-1943[0]: > > | Buffer overflow in the backend of XenSource Xen Para Virtualized Frame > > | Buffer (PVFB) 3.0 through 3.1.2 allows local users to cause a denial > > | of service (crash) and possibly execute arbitrary code via a crafted > > | description of a shared framebuffer. > > 3.1.2 < 3.2 > > > CVE-2008-1944[1]: > > | Buffer overflow in the backend framebuffe...

...eded for some reason, are there any guidelines for >> non-root operation? >> > > In general qemu is used for the following purposes: > > - for certain domU disk backend types (image files), and/or if there's no blktap driver in dom0 kernel. > - domU graphical console (PVFB) VNC server, if it's enabled for the domU. > > >> -- >> Karel Hendrych > > > -- Pasi > > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > https://lists.centos.org/mailman/listinfo/centos-virt >

Source: xen-unstable Version: 3.3-unstable+hg17602-1 Severity: grave Tags: security, patch Hi, the following CVE (Common Vulnerabilities & Exposures) ids were published for xen-unstable. CVE-2008-1943[0]: | Buffer overflow in the backend of XenSource Xen Para Virtualized Frame | Buffer (PVFB) 3.0 through 3.1.2 allows local users to cause a denial | of service (crash) and possibly execute arbitrary code via a crafted | description of a shared framebuffer. CVE-2008-1944[1]: | Buffer overflow in the backend framebuffer of XenSource Xen | Para-Virtualized Framebuffer (PVFB) Message 3.0 th...

Source: xen-3 Version: 3.2.1-1 Severity: grave Tags: security, patch Hi, the following CVE (Common Vulnerabilities & Exposures) ids were published for xen-3. CVE-2008-1943[0]: | Buffer overflow in the backend of XenSource Xen Para Virtualized Frame | Buffer (PVFB) 3.0 through 3.1.2 allows local users to cause a denial | of service (crash) and possibly execute arbitrary code via a crafted | description of a shared framebuffer. CVE-2008-1944[1]: | Buffer overflow in the backend framebuffer of XenSource Xen | Para-Virtualized Framebuffer (PVFB) Message 3.0 th...

...root operation? > >>> > >> > >>In general qemu is used for the following purposes: > >> > >>- for certain domU disk backend types (image files), and/or if there's > >>no blktap driver in dom0 kernel. > >>- domU graphical console (PVFB) VNC server, if it's enabled for the domU. > >> > >> > >>>-- > >>>Karel Hendrych > >> > >> > >>-- Pasi > >> > >>_______________________________________________ > >>CentOS-virt mailing list > >&...

Hi, after migrating to libvirt/libxl according to: https://wiki.centos.org/HowTos/Xen/Xen4QuickStart/Xen4Libvirt I've noticed that my Xen PV domains are being launched by qemu-system-i386 running under root privileges. I am wondering why is this? Previously no qemu process was used. If qemu is needed for some reason, are there any guidelines for non-root operation? Thanks -- Karel

...Could you please check, whether they affect any debian versions and how important they are? They are rather left over on our TODO list and I'd like to forward them to you for checking. CVE-2008-1944: Buffer overflow in the backend framebuffer of XenSource Xen Para-Virtualized Framebuffer (PVFB) Message 3.0 through 3.0.3 allows local users to cause a denial of service (SDL crash) and possibly execute arbitrary code via "bogus screen updates," related to missing validation of the "format of messages." CVE-2008-1943: Buffer overflow in the backend of XenSource Xen P...

Hi folks, I tried to find out what xen version upstream intends to use in 5.3, but did not find anything. So now I hope that there is some secret knowledge among the CentOS people you could share? :-) Any hint or link would be helpful. Thanks in advance, Dirk