Re: [PATCH 5/5] Nested VMX patch 5 implements vmlaunch and vmresume

Gleb Natapov g...@redhat.com wrote on 29/10/2009 19:31:05: [image removed] Re: [PATCH 5/5] Nested VMX patch 5 implements vmlaunch and vmresume Gleb Natapov to: Orit Wasserman 29/10/2009 19:31 Cc: Abel Gordon, aliguori, Ben-Ami Yassour1, kvm, mdday, Muli Ben-Yehuda On Wed, Oct

Re: [PATCHv8 3/3] vhost_net: a kernel-level virtio server

On Mon, Nov 09, 2009 at 04:47:29PM +1030, Rusty Russell wrote: Actually, this looks wrong to me: + case VHOST_SET_VRING_BASE: ... + vq-avail_idx = vq-last_avail_idx = s.num; The last_avail_idx is part of the state of the driver. It needs to be saved and restored over

Serial Port Driver does not handle interrupt

Hi all, I've tested two kvm versions 77 and 88, both with the same behaviour: I add a serial device with -serial /dev/ttyS0 to my guest and launched HyperTerm on my Windows Guest. Additionally I plugged in a loopback plug on the serial connector that just routes back the data send back to the

Re: xp guest, blue screen c0000221 on boot

qemu-img convert -O raw xp.qcow2 xp.img using the same command on the raw image gives a blue screen on startup (same error as before) So converting from raw to qcow2 fixes the error, and converting back to raw reintroduces the error I'm not set up to use LVM volumes Avi Kivity wrote: On

Re: [PATCH] qemu-kvm: clear only essential parts of VirtIOBlockReq on object allocation

On Sun, Nov 8, 2009 at 3:07 PM, Avi Kivity a...@redhat.com wrote: [snip] Thanks for the comments. I'll soon resubmit the corrected patch. I don't understand what the comment below means. Submit to qemu-de...@nongnu.org since this came from upstream. Thanks, Saul -- To unsubscribe from this

[PATCHv9 0/3] vhost: a kernel-level virtio server

Ok, I think I've addressed all comments so far here, and it still seems to work :). Please take a look. I basically ended up accepting all Rusty's suggestions, except I did not get rid of avail_idx field in vq: I don't (yet?) understand what's wrong with it, if any, and it seems required for

[PATCHv9 1/3] tun: export underlying socket

Tun device looks similar to a packet socket in that both pass complete frames from/to userspace. This patch fills in enough fields in the socket underlying tun driver to support sendmsg/recvmsg operations, and message flags MSG_TRUNC and MSG_DONTWAIT, and exports access to this socket to modules.

[PATCHv9 2/3] mm: export use_mm/unuse_mm to modules

vhost net module wants to do copy to/from user from a kernel thread, which needs use_mm. Export it to modules. Acked-by: Andrea Arcangeli aarca...@redhat.com Acked-by: Andrew Morton a...@linux-foundation.org Signed-off-by: Michael S. Tsirkin m...@redhat.com --- mm/mmu_context.c |3 +++ 1

[PATCHv9 3/3] vhost_net: a kernel-level virtio server

What it is: vhost net is a character device that can be used to reduce the number of system calls involved in virtio networking. Existing virtio net code is used in the guest without modification. There's similarity with vringfd, with some differences and reduced scope - uses eventfd for

[PATCH] qemu-kvm: clear only essential parts of VirtIOBlockReq on object allocation - RESUBMIT

This patch reduces the size of memory being cleared on every virtio-blk IO. Improve number of IOPS when using avirtio-blk device. On every virtio-blk IO command passed to QEMU, virtio_blk_alloc_request() allocates and clears (with qemu_mallocz()) a VirtIOBlockReq object. The

Re: [PATCHv8 3/3] vhost_net: a kernel-level virtio server

On Mon, 9 Nov 2009 05:40:32 pm Michael S. Tsirkin wrote: On Mon, Nov 9, 2009 at 8:17 AM, Rusty Russell ru...@rustcorp.com.au wrote: There's something about the 'acked' which rubs me the wrong way. enabled_features is perhaps a better term than acked_features; acked seems more a user

PCI passthrough of TV-tuners with VT-d

Hi While considering upgrading my MythTV backend to a VT-d capable system, I'm trying to figure out if it would be possible to utilize PCI passthrough with KVM. As far as I understand the wiki page on How to assign devices with VT-d [1] and various posts on mailing lists, then all conventional

RE: PCI passthrough of TV-tuners with VT-d

Kenni Lund wrote: Hi While considering upgrading my MythTV backend to a VT-d capable system, I'm trying to figure out if it would be possible to utilize PCI passthrough with KVM. As far as I understand the wiki page on How to assign devices with VT-d [1] and various posts on mailing

Re: [PATCHv9 3/3] vhost_net: a kernel-level virtio server

On Tue, 10 Nov 2009 03:52:30 am Michael S. Tsirkin wrote: What it is: vhost net is a character device that can be used to reduce the number of system calls involved in virtio networking. Existing virtio net code is used in the guest without modification. Thanks, applied. Will be in tomorrow's

Re: [PATCHv9 3/3] vhost_net: a kernel-level virtio server

One fix: vhost: fix TUN=m VHOST_NET=y drivers/built-in.o: In function `get_tun_socket': net.c:(.text+0x15436e): undefined reference to `tun_get_socket' Signed-off-by: Rusty Russell ru...@rustcorp.com.au --- drivers/vhost/Kconfig |2 +- 1 file changed, 1 insertion(+), 1

kvm book3s issues

Hi Alex ! After a bit of digging as to why the karmic installer dies, I found out that you don't set the right SRR1 bits when forwarding a program check exception to the guest. I also did a couple of minor fixups (though the s/mtmsr/mtmsrd may not be necessary, I think the clearing of HID5 is).