Alexander Graf ag...@suse.de writes:
On 05.03.2010, at 17:52, Chris Webb wrote:
Of course, if the screen width or height is 1, it doesn't really matter what
the value of the mouse position for the click is, so something as simple as
diff --git a/vnc.c b/vnc.c
--- a/vnc.c
+++
Bugs item #2933400, was opened at 2010-01-16 15:35
Message generated for change (Comment added) made by masc82
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2933400group_id=180599
Please note that this message will contain a full copy of the comment
Bugs item #2933400, was opened at 2010-01-16 15:35
Message generated for change (Settings changed) made by masc82
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2933400group_id=180599
Please note that this message will contain a full copy of the comment
The idea is simple, just to pin the guest VM user space and then
let host NIC driver has the chance to directly DMA to it.
The patches are based on vhost-net backend driver. We add a device
which provides proto_ops as sendmsg/recvmsg to vhost-net to
send/recv directly to/from the NIC driver. KVM
From: Xin Xiaohui xiaohui@intel.com
Add a device to utilize the vhost-net backend driver for
copy-less data transfer between guest FE and host NIC.
It pins the guest user space to the host memory and
provides proto_ops as sendmsg/recvmsg to vhost-net.
Signed-off-by: Xin Xiaohui
From: Xin Xiaohui xiaohui@intel.com
The vhost-net backend now only supports synchronous send/recv
operations. The patch provides multiple submits and asynchronous
notifications. This is needed for zero-copy case.
Signed-off-by: Xin Xiaohui xiaohui@intel.com
---
drivers/vhost/net.c |
From: Xin Xiaohui xiaohui@intel.com
The patch let host NIC driver to receive user space skb,
then the driver has chance to directly DMA to guest user
space buffers thru single ethX interface.
Signed-off-by: Xin Xiaohui xiaohui@intel.com
Signed-off-by: Zhao Yu yzha...@gmail.com
Bugs item #2933400, was opened at 2010-01-16 17:35
Message generated for change (Comment added) made by mjtsf
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2933400group_id=180599
Please note that this message will contain a full copy of the comment
Bugs item #2933400, was opened at 2010-01-16 15:35
Message generated for change (Comment added) made by masc82
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2933400group_id=180599
Please note that this message will contain a full copy of the comment
Bugs item #2933400, was opened at 2010-01-16 15:35
Message generated for change (Comment added) made by masc82
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2933400group_id=180599
Please note that this message will contain a full copy of the comment
Hello,
I want to remind every intersted KVM developer/user/enthusiast that at
this years Chennitzer Linux-Tage[1] we will have a dedicated track for
KVM and virtualization topics :-) The conference exits since 1999 and
has evolved to an established open source community get-together in
Germany
i Avi,
we currently try to integrate this patch for an update into a 2.6.32 based
system (amongst other kvm updates). But as soon as this patch gets added kvm
will die on startup in kvm_leave_lazy_mmu. This has been documented here:
On Sat, 6 Mar 2010 17:38:38 +0800
xiaohui@intel.com wrote:
From: Xin Xiaohui xiaohui@intel.com
The patch let host NIC driver to receive user space skb,
then the driver has chance to directly DMA to guest user
space buffers thru single ethX interface.
Signed-off-by: Xin Xiaohui
Dear kvm developers
firstly thank you for doing such a great job on KVM.
Following this list I see great ongoing progresses on virtio-net, now
even more with the vhost
but I see virtio-blk very rarely mentioned.
We have an old kvm installation (host kernel is also old at 2.6.24) and
I don't
Hi,
With qemu-kvm-0.12.3:
./qemu-system-x86_64 [..] -drive file=/dev/sdc9,if=virtio,cache=none [..]
[1.882843] vdc:
[2.365154] udev: starting version 146
[2.693768] end_request: I/O error, dev vdc, sector 126
[2.693772] Buffer I/O error on device vdc, logical block 126
[
Antoine Martin wrote:
Hi,
With qemu-kvm-0.12.3:
./qemu-system-x86_64 [..] -drive file=/dev/sdc9,if=virtio,cache=none [..]
[1.882843] vdc:
[2.365154] udev: starting version 146
[2.693768] end_request: I/O error, dev vdc, sector 126
[2.693772] Buffer I/O error on device
On Thu, Mar 04, 2010 at 03:34:34PM -0600, Ryan Harper wrote:
* Aurelien Jarno aurel...@aurel32.net [2010-03-04 15:27]:
On Tue, Feb 23, 2010 at 06:02:15PM +0100, Aurelien Jarno wrote:
Ryan Harper a écrit :
Currently, x86_64-softmmu qemu segfaults when trying to use 4095M
memsize.
I have an HP Server with an OEM copy of Windows Server 2008. When I
try to install 2008 as a guest in KVM the HP OEM check pops up and
tells me I am not using supported hardware. It seems the OEM check is
looking for information in the BIOS of the server, but KVM is
presenting the installer with
On 03/07/2010 04:28 AM, Michael Tokarev wrote:
Antoine Martin wrote:
Hi,
With qemu-kvm-0.12.3:
./qemu-system-x86_64 [..] -drive file=/dev/sdc9,if=virtio,cache=none [..]
[1.882843] vdc:
[2.365154] udev: starting version 146
[2.693768] end_request: I/O error, dev vdc, sector 126
On Sat, Mar 06, 2010 at 04:43:10PM -0700, Phil Borlin wrote:
I have an HP Server with an OEM copy of Windows Server 2008. When I
try to install 2008 as a guest in KVM the HP OEM check pops up and
tells me I am not using supported hardware. It seems the OEM check is
looking for information in
On Thu, Mar 04, 2010 at 02:03:54PM +0200, Gleb Natapov wrote:
BTW, do real systems allow to hot plug BSP as well? Or how is the case
handled when you unplug the BSP and then reboot the box?
Did you mean hot unplug BSP? OS determines what CPU is BSP by checking
BSP bit in APIC base
21 matches
Mail list logo
