similar to: [PATCH] ioemu: fix xenfb slow case update

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

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

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

Hi, I''m trying to start Xorg on a PV Fedora8 guest running 2.6.21.7 fedora stock xen kernel, however, it seems that there''s no xenfb.ko driver included in the .rpm package. The only included drivers I see in /lib/modules are: emre@xenroot:/lib/modules/2.6.21.7-3.fc8xen/kernel/drivers/xen$ ls blkback blkfront blktap netback netfront pciback however, if I look at the

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

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

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

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, 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 |

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

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 they would like, balanced with the CPU time that requires.

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

Hi, I have installed Asterisk 1.4 with mISDN with the install-asterisk.tar.gz script from beronet.com. On my system I have two cards, one a AVM Frit!Card Pci 2.0 and one HFC-S chip. I know both to work well with mISDN on my system from a previous installation. Now however, the AVM card works well at first glance, i.e. it "registers" incoming calls and works through the asterisk

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

2011/7/19 Stefano Stabellini <stefano.stabellini@eu.citrix.com>: > CC''ing Tim and xen-devel > > On Mon, 18 Jul 2011, Jiageng Yu wrote: >> 2011/7/16 Stefano Stabellini <stefano.stabellini@eu.citrix.com>: >> > On Fri, 15 Jul 2011, Jiageng Yu wrote: >> >> 2011/7/15 Jiageng Yu <yujiageng734@gmail.com>: >> >> > 2011/7/15

Import "DisplayState interface change" from qemu mainstream: the patch has been adapted to qemu-xen and merged with several following fixes. The original qemu svn commit is the following: git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@6336 c046a42c-6fe2-441c-8c8c-71466251a162 Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> --- diff --git a/console.c

Hi, I'm trying to write up my little m68k backend things have been going smoothly. I've been working with the x86 backend as a template, fixing things as I go. Now I've run into branches and I have a crash I don't really understand. Here's the sample IR I'm running llc on to generate assembly: define i32 @ilog2(i32 %x) { entry: %tmp718 = icmp eq i32 %x, 0

Replying to my self here. It seems I was missing an isTerminator = 1 on the branch instruction in question, so LLVM didn't know that the instruction terminated a basic block. Does that make sense, or is just masking some other problem? Thanks, Andreas On 9/28/07, Andreas Fredriksson <deplinenoise at gmail.com> wrote: > Hi, > I'm trying to write up my little m68k backend

Hello all, I am looking at the assembly code of a loop body which is created by applying O3 optimization. Here it is: .LBB4_19: @ %for.body.91 @ =>This Inner Loop Header: Depth=1 ldr r0, [r5] mov r1, r8 add r0, r0, r7 vldr s0, [r0] mov r0, r6 vcvt.f64.f32 d0, s0 vmov