I spoke too soon... I just tried krdc and the same thing happened before I could even try to connect to anything with it (or even determine if it supports vnc, I don't remember). This is a quad core, and I have, in all instances, confirmed that each of the four vcpus in dom0 is tied to a different core. Additionally, I have never had more than one DomU per core on top of Dom0 using each core. Finally, in this latest instance, only one DomU was doing anything, and it could not have been using but 100% of one core, so the other three were, for lack of a better word, bored.

-----Original Message----- From: fedora-xen-bounces@redhat.com [mailto:fedora-xen-bounces@redhat.com] On Behalf Of Dustin Henning Sent: Friday, May 30, 2008 16:48 To: fedora-xen@redhat.com Subject: [Fedora-xen] Strange mouse issue (F7 & F8 xen kernel with vncviewer running)

I have been experiencing this (rather strange) issue for as long as I have been a member of this group, and I am curious as to whether anyone else has experienced it. The mouse will continue on in the direction I am moving it after I stop, change direction, or even suddenly reverse direction. Once this happens, the mouse inevitably ends up in one of the four corners of the screen, and will eventually stop trying to travel in that direction, at which point I can control it again. It seems like hitting some keys may cause this to happen sooner. The keys I most often go for are Esc, Alt, Ctrl, Super, Alt+F1, Arrows. Which keys usually depends on what is up in the vncviewer window, where I don't want to issue the wrong command to whatever client I may be working with. I have made the following observations regarding this behavior, though I can't say with absolute certainty that they are all 100% accurate and/or consistent: -keyboard and mouse are PS/2 -in all instances, hvm guests were running, consuming as much as 5 out of 8 GiB of memory on this machine -never experienced in standard kernel on F7 or F8 (even with multiple kvm guests and vncviewers running, though not to consume 5 of 8 GiB) -originally, in F7, vncviewer may not have been running every time it happened -now, in F8, vncviewer has definitely been running every time it happened, but not necessarily connected to anything -same issue was previously experienced on another machine with less memory (and less guests) on F7 Is this a known issue of any sort? It has recently occurred to me that I should try a different client, and I will do that at some point, but I figured it wouldn't hurt to see if there have been any other similar experiences out there in the meantime. Thanks, Dustin

-- Fedora-xen mailing list Fedora-xen@redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen