[COMMIT master] KVM: Trivial format fix in setup_routing_entry()

From: Chris Wright chr...@sous-sol.org Remove extra tab. Signed-off-by: Chris Wright chr...@redhat.com Signed-off-by: Avi Kivity a...@redhat.com diff --git a/virt/kvm/irq_comm.c b/virt/kvm/irq_comm.c index 4fa1f60..a8bd466 100644 --- a/virt/kvm/irq_comm.c +++ b/virt/kvm/irq_comm.c @@ -271,7

[COMMIT master] KVM: Fix NX support reporting

From: Avi Kivity a...@redhat.com NX support is bit 20, not bit 1. Signed-off-by: Avi Kivity a...@redhat.com diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c index 5fcde2c..8b0d777 100644 --- a/arch/x86/kvm/x86.c +++ b/arch/x86/kvm/x86.c @@ -1266,7 +1266,7 @@ static void do_cpuid_ent(struct

[COMMIT master] KVM: Make EFER reads safe when EFER does not exist

From: Avi Kivity a...@redhat.com Some processors don't have EFER; don't oops if userspace wants us to read EFER when we check NX. Cc: sta...@kernel.org Signed-off-by: Avi Kivity a...@redhat.com diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c index 8b0d777..2d7082c 100644 ---

[COMMIT master] Increment virtio-net savevm version to avoid conflict with upstream QEMU.

From: Anthony Liguori aligu...@us.ibm.com When TAP_VNET_HDR eventually merges into upstream QEMU, it cannot change the format of the version 6 savevm data. This means that we're going to have to bump the version up to 7. I'm happy to reserve version 7 as having TAP_VNET_HDR support to allow

[COMMIT master] Remove -cpu-vendor-string

From: Anthony Liguori aligu...@us.ibm.com Superceded by qemu '-cpu vendor=...' option. Signed-off-by: Anthony Liguori aligu...@us.ibm.com Signed-off-by: Avi Kivity a...@redhat.com diff --git a/linux-user/main.c b/linux-user/main.c index 5967fa3..dc39b05 100644 --- a/linux-user/main.c +++

[COMMIT master] Don't clean *.dtb

From: Anthony Liguori aligu...@us.ibm.com *.dtb is under source control, so it shouldn't be deleted. Signed-off-by: Anthony Liguori aligu...@us.ibm.com Acked-by: Hollis Blanchard holl...@us.ibm.com Signed-off-by: Avi Kivity a...@redhat.com diff --git a/pc-bios/Makefile b/pc-bios/Makefile index

[COMMIT master] Increment version id for CPU save state

From: Anthony Liguori aligu...@us.ibm.com 9 is reserved for KVM. KVM cannot support migration from any other version. Signed-off-by: Anthony Liguori aligu...@us.ibm.com Signed-off-by: Avi Kivity a...@redhat.com diff --git a/target-i386/cpu.h b/target-i386/cpu.h index f054af1..af0ee18 100644

[COMMIT master] Fix build when objdir != srcdir

From: Anthony Liguori aligu...@us.ibm.com This requires adding the necessary bits to configure to create the directories and symlinks for libkvm. It also requires sticking KVM_CFLAGS in config-host.mak to ensure that it gets the right set of includes for the kernel headers. Signed-off-by:

[COMMIT master] Rename config-powerpc to config-ppc

From: Hollis Blanchard holl...@us.ibm.com Apparently $(ARCH) now holds the qemu meaning, rather than the KVM meaning. Signed-off-by: Hollis Blanchard holl...@us.ibm.com Signed-off-by: Avi Kivity a...@redhat.com diff --git a/kvm/libkvm/config-powerpc.mak b/kvm/libkvm/config-ppc.mak similarity

[COMMIT master] Fix format of package version for KVM

From: Anthony Liguori aligu...@us.ibm.com We currently show 0.10.50kvm-devel whereas pkgversion normally would show 0.10.50 (kvm-devel). This is due to some weirdness in how pkgversion is constructed in configure. This corrects the version display. Signed-off-by: Anthony Liguori

[COMMIT master] Fix missing prototype warning.

From: Hollis Blanchard holl...@us.ibm.com As far as I can see, kvm_destroy_memory_region_works() has nothing to do with KVM_CAP_DEVICE_ASSIGNMENT, so move the prototype outside that ifdef block. Signed-off-by: Hollis Blanchard holl...@us.ibm.com Signed-off-by: Avi Kivity a...@redhat.com diff

[COMMIT master] Fix warning when__ia64__ is not defined.

From: Hollis Blanchard holl...@us.ibm.com Signed-off-by: Hollis Blanchard holl...@us.ibm.com Signed-off-by: Avi Kivity a...@redhat.com diff --git a/kvm/libkvm/kvm-common.h b/kvm/libkvm/kvm-common.h index 96361e8..591fb53 100644 --- a/kvm/libkvm/kvm-common.h +++ b/kvm/libkvm/kvm-common.h @@ -22,7

[COMMIT stable-0.10] Read kvm version from KVM_VERSION file

From: Avi Kivity a...@redhat.com This allows the packager to add a KVM_VERSION file to the tarball instead of modifying the source. Signed-off-by: Avi Kivity a...@redhat.com diff --git a/configure b/configure index 0cfdf7b..04e072b 100755 --- a/configure +++ b/configure @@ -152,6 +152,17 @@

[COMMIT master] patch add_powerpc_kvm_headers.diff

From: Hollis Blanchard holl...@us.ibm.com Signed-off-by: Avi Kivity a...@redhat.com diff --git a/kvm/kernel/arch/powerpc/include/asm/kvm.h b/kvm/kernel/arch/powerpc/include/asm/kvm.h new file mode 100644 index 000..c4f1ed1 --- /dev/null +++ b/kvm/kernel/arch/powerpc/include/asm/kvm.h @@

[COMMIT stable-0.10] Merge commit 'v0.10.3' into stable-0.10

From: Avi Kivity a...@redhat.com * commit 'v0.10.3': Update version for 0.10.3 release Implement cancellation method for dma async I/O (Avi Kivity) Convert vectored aio emulation to use a dedicated pool (Avi Kivity) Refactor aio callback allocation to use an aiocb pool (Avi Kivity) Fix

[COMMIT stable-0.10] kvm: Add release script

From: Avi Kivity a...@redhat.com Signed-off-by: Avi Kivity a...@redhat.com diff --git a/kvm/scripts/make-release b/kvm/scripts/make-release new file mode 100755 index 000..3b1dccf --- /dev/null +++ b/kvm/scripts/make-release @@ -0,0 +1,60 @@ +#!/bin/bash -e + +usage() { +echo usage: $0

[COMMIT stable-0.10] kvm: disable kqemu

From: Avi Kivity a...@redhat.com Signed-off-by: Avi Kivity a...@redhat.com diff --git a/configure b/configure index 913bcb8..0cfdf7b 100755 --- a/configure +++ b/configure @@ -314,6 +314,7 @@ if [ $cpu = i386 -o $cpu = x86_64 ] ; then kqemu=yes

[COMMIT master] Revert Sync idcache after emualted DMA operations for ia64

From: Hollis Blanchard holl...@us.ibm.com This reverts commit 9dc99a28236161a5a1b4c58f1e9c4ec6179cb976. Aside from the other issues discussed on kvm-devel, this commit breaks the PowerPC build. Signed-off-by: Hollis Blanchard holl...@us.ibm.com Signed-off-by: Avi Kivity a...@redhat.com diff

[COMMIT stable-0.10] Fix warning when__ia64__ is not defined.

From: Hollis Blanchard holl...@us.ibm.com Signed-off-by: Hollis Blanchard holl...@us.ibm.com Signed-off-by: Avi Kivity a...@redhat.com diff --git a/kvm/libkvm/kvm-common.h b/kvm/libkvm/kvm-common.h index de1ada2..9060820 100644 --- a/kvm/libkvm/kvm-common.h +++ b/kvm/libkvm/kvm-common.h @@ -22,7

[COMMIT master] kvm: Add release script

From: Avi Kivity a...@redhat.com Signed-off-by: Avi Kivity a...@redhat.com diff --git a/kvm/scripts/make-release b/kvm/scripts/make-release new file mode 100755 index 000..3b1dccf --- /dev/null +++ b/kvm/scripts/make-release @@ -0,0 +1,60 @@ +#!/bin/bash -e + +usage() { +echo usage: $0

Re: [KVM PATCH v3 2/2] kvm: add support for irqfd via eventfd-notification interface

On Mon, Apr 27, 2009 at 02:33:34PM -0400, Gregory Haskins wrote: + /* We re-use eventfd for irqfd */ + fd = sys_eventfd2(0, 0); + if (fd 0) { + ret = fd; + goto fail; + } + + /* We maintain a reference to eventfd for the irqfd lifetime */ +

Re: [PATCH] qemu-kvm: build system Add link to qemu

Jan Kiszka wrote: I'm getting closer to a working qemu-kvm, but there are still a few messy parts. The magic dance goes like this: cd qemu-kvm/kvm ln -s .. qemu (or apply patch below) ./configure -whatever make Still, this is unintuitive. As both top-level configure and Makefile

Re: PPC support for qemu-kvm

Hollis Blanchard wrote: These patches fix a number of issues with PowerPC builds of qemu-kvm.git. However, even after applying these patches it still doesn't build, due to confusion with KVM_UPSTREAM and CONFIG_KVM. Applied all, thanks. -- error compiling committee.c: too many arguments to

Re: [PATCH] kvm: trivial format fix in setup_routing_entry()

Chris Wright wrote: Remove extra tab. Applied, thanks. -- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at

Re: Unable to boot guest on kernel 2.6.29.1 with kvm-84 or kvm-85

Avi Kivity wrote: Kenni Lund wrote: Avi Kivity a...@redhat.com wrote: Kenni Lund wrote: Ok, but as I write in my message, I'm using the KVM modules from the latest upstream kernel, not the kvm-85 modules. According to the KVM download page,

Re: Implement generic double fault generation mechanism

On Thu, Apr 30, 2009 at 03:24:07PM +0800, Dong, Eddie wrote: Move Double-Fault generation logic out of page fault exception generating function to cover more generic case. Signed-off-by: Eddie Dong eddie.d...@intel.com diff --git a/arch/x86/kvm/x86.c

[PATCH] kvm: Add helpers for checking and requiring kvm extensions

Instead of open-coding the check extension sequence, provide helpers for checking whether an extension exists, and for aborting if an extension is missing. Signed-off-by: Avi Kivity a...@redhat.com --- kvm-all.c | 63 +++-- kvm.h

Re: Unable to boot guest on kernel 2.6.29.1 with kvm-84 or kvm-85

Avi Kivity wrote: Kenni Lund wrote: Avi Kivity a...@redhat.com wrote: Kenni Lund wrote: Ok, but as I write in my message, I'm using the

Re: Unable to boot guest on kernel 2.6.29.1 with kvm-84 or kvm-85

Kenni Lund wrote: It won't help - I reproduced the issue. Instead, try passing the parameter '-cpu qemu32' (or '-cpu qemu64,-nx'). Adding the parameter '-cpu qemu32' (32bit host + 32 bit guest) makes the WinXP guest boot. ...but is this parameter equal to '-no-kvm'? Eg. with emulated

[PATCH 0/4] Fix kvm cpuid reporting

kvm supports an interface for reporting which cpuid features are supported. Use it for trimming the cpu feature set reported to the guest. This prevents, for example, reporting NX to a guest when in fact we do not support it. Avi Kivity (4): kvm: Add support for querying supported cpu features

[PATCH 2/4] Make x86 cpuid feature names available in file scope

To be used later. Signed-off-by: Avi Kivity a...@redhat.com --- target-i386/helper.c | 55 + 1 files changed, 28 insertions(+), 27 deletions(-) diff --git a/target-i386/helper.c b/target-i386/helper.c index a070e08..88585b8 100644 ---

[PATCH 3/4] Fix x86 feature modifications for features that set multiple bits

QEMU allows adding or removing cpu features by using the syntax '-cpu +feature' or '-cpu -feature'. Some cpuid features cause more than one bit to be set or cleared; but QEMU stops after just one bit has been modified, causing the feature bits to be inconsistent. Fix by allowing all feature bits

[PATCH 4/4] kvm: Trim cpu features not supported by kvm

Remove cpu features that are not supported by kvm from the cpuid features reported to the guest. Signed-off-by: Avi Kivity a...@redhat.com --- target-i386/helper.c | 30 ++ 1 files changed, 30 insertions(+), 0 deletions(-) diff --git a/target-i386/helper.c

[PATCH 1/4] kvm: Add support for querying supported cpu features

kvm does not support all cpu features; add support for dunamically querying the supported feature set. Signed-off-by: Avi Kivity a...@redhat.com --- kvm.h |3 ++ target-i386/kvm.c | 80 + 2 files changed, 83 insertions(+), 0

Re: [PATCH] Revert Sync idcache after emualted DMA operations for ia64

Hollis Blanchard wrote: This reverts commit 9dc99a28236161a5a1b4c58f1e9c4ec6179cb976. Aside from the other issues discussed on kvm-devel, this commit breaks the PowerPC build. Applied, thanks. -- error compiling committee.c: too many arguments to function -- To unsubscribe from this

Re: [PATCH 03/04] qemu-kvm: Remove the dependency for phys_ram_base for ipf.c

Jes Sorensen wrote: Zhang, Xiantao wrote: Jes Sorensen wrote: I still can't see the difference with the patch in Avi's tree except nvram stuff. And I believe the global variable you mentioned should be only used for nvram. So I propose an incremental patch for that. :) Hi, Here is an

Re: [PATCH 03/21] Remove use of signalfd in block-raw-posix.c

Avi Kivity wrote: Anthony Liguori wrote: Oh okay. But signal delivery is slow; for example the FPU needs to be reset. Is it really justified to add all of this extra code (including signalfd emulation) for something that probably isn't even measurable? We don't have to add signalfd

Re: [KVM PATCH v3 2/2] kvm: add support for irqfd via eventfd-notification interface

Michael S. Tsirkin wrote: On Mon, Apr 27, 2009 at 02:33:34PM -0400, Gregory Haskins wrote: This allows an eventfd to be registered as an irq source with a guest. Any signaling operation on the eventfd (via userspace or kernel) will inject the registered GSI at the next available window.

qemu-kvm: unapplied patches in my queue

Hi, The following patches have been posted a week ago: [PATCH] qemu-kvm: make clean should propagate into libkvm dire [PATCH] qemu-kvm: fix compiler warning [PATCH] qemu-kvm: make kvm_create_pit static No comments have been made since then - does this mean they can be applied? Thanks, -- MST --

Re: qemu-kvm: unapplied patches in my queue

Michael S. Tsirkin wrote: Hi, The following patches have been posted a week ago: [PATCH] qemu-kvm: make clean should propagate into libkvm dire [PATCH] qemu-kvm: fix compiler warning [PATCH] qemu-kvm: make kvm_create_pit static No comments have been made since then - does this mean they can be

Re: [KVM PATCH v3 2/2] kvm: add support for irqfd via eventfd-notification interface

On Sun, 3 May 2009, Al Viro wrote: On Mon, Apr 27, 2009 at 02:33:34PM -0400, Gregory Haskins wrote: + /* We re-use eventfd for irqfd */ + fd = sys_eventfd2(0, 0); + if (fd 0) { + ret = fd; + goto fail; + } + + /* We maintain a reference to eventfd

Linux x86 guest panics in skb_copy_bits

Hi all, I have a pretty straightforward setup. Hypervisor: dual xeon e5205 running Gentoo Linux kernel 2.6.27 with virtio devices enabled kvm 84 libvirt 0.5.1 Guest: 32-bit, virtio for nic and disk, qcow2. Linux 2.6.28. Network is bridged using tap and brctl. I'm running Apache on the guest. 

Re: [KVM PATCH v3 2/2] kvm: add support for irqfd via eventfd-notification interface

On Sun, May 03, 2009 at 11:07:26AM -0700, Davide Libenzi wrote: On Sun, 3 May 2009, Al Viro wrote: On Mon, Apr 27, 2009 at 02:33:34PM -0400, Gregory Haskins wrote: + /* We re-use eventfd for irqfd */ + fd = sys_eventfd2(0, 0); + if (fd 0) { + ret = fd; + goto

Re: [KVM PATCH v3 2/2] kvm: add support for irqfd via eventfd-notification interface

On Sun, May 03, 2009 at 07:59:40PM +0300, Avi Kivity wrote: Michael S. Tsirkin wrote: On Mon, Apr 27, 2009 at 02:33:34PM -0400, Gregory Haskins wrote: This allows an eventfd to be registered as an irq source with a guest. Any signaling operation on the eventfd (via userspace or kernel)

Re: [KVM PATCH v3 2/2] kvm: add support for irqfd via eventfd-notification interface

Michael S. Tsirkin wrote: On Sun, May 03, 2009 at 07:59:40PM +0300, Avi Kivity wrote: Michael S. Tsirkin wrote: On Mon, Apr 27, 2009 at 02:33:34PM -0400, Gregory Haskins wrote: This allows an eventfd to be registered as an irq source with a guest. Any signaling operation on

file descriptor abuses

On Sun, May 03, 2009 at 08:01:36PM +0100, Al Viro wrote: General rules: * descriptor you've generated is fit only for return to userland; * descriptor you've got from userland is fit only for *single* fget() or equivalent, unless you are one of the core syscalls manipulating the

Re: [KVM PATCH v3 2/2] kvm: add support for irqfd via eventfd-notification interface

On Sun, May 03, 2009 at 10:17:16PM +0300, Avi Kivity wrote: Actually there's a third option: add KVM_MASK_IRQ, KVM_UNMASK_IRQ ioctls which will block/unblock guest from getting interrupt on this irq, whatever the source. Interrupts are queued in kernel while masked. A third ioctl

Re: [KVM PATCH v3 2/2] kvm: add support for irqfd via eventfd-notification interface

On Sun, 3 May 2009, Al Viro wrote: IOW, the sane solution would be to export something that returns your struct file *. And stop playing with fd completely. This builds but it's not tested at all. - Make all the work of the old anon_inode_getfd(), done by a new anon_inode_getfile(), with

Custom BIOS supported size

Hello, Which is the maximum size supported for a custom BIOS image(eg. coreboot-based)? I tried some 256K coreboot BIOS images and seemed to work fine, but it blowed up with a 3MB image (which by the way works on qemu just fine). Qemu also seems to fail with images greater than 4MB, and I'd

[RFC] Bring in all the Linux headers we depend on in QEMU

Sorry this explanation is long winded, but this is a messy situation. In Linux, there isn't a very consistent policy about userspace kernel header inclusion. On a typical Linux system, you're likely to find kernel headers in three places. glibc headers (/usr/include/{linux,asm}) These

Re: kvm-userspace broken?

Avi Kivity wrote: Oliver Rath wrote: Hi List, maybe i missed some announcements, but git clone git://git.kernel.org/pub/scm/virt/kvm/kvm-userspace.git givs no response: kvm-userspace # git clone git://git.kernel.org/pub/scm/virt/kvm/kvm-userspace.git Initialized empty Git repository in

Re: KVM x86_64 with SR-IOV..?

On Sat, 2009-05-02 at 18:22 +0800, Sheng Yang wrote: On Thu, Apr 30, 2009 at 01:22:54PM -0700, Nicholas A. Bellinger wrote: Greetings KVM folks, I wondering if any information exists for doing SR-IOV on the new VT-d capable chipsets with KVM..? From what I understand the patches for

RE: [PATCH] kvm-kmod: fix build on kernels with kvm trace set

Avi Kivity wrote: Michael S. Tsirkin wrote: CONFIG_KVM_TRACE in kernel conflicts with the definition in external module. external-module-compat-comm.h tried to work around this, but this didn't work as some code still does #include linux/autoconf.h directly. Solve this differently by

RE: [PATCH] Revert Sync idcache after emualted DMA operations for ia64

Avi Kivity wrote: Hollis Blanchard wrote: This reverts commit 9dc99a28236161a5a1b4c58f1e9c4ec6179cb976. Aside from the other issues discussed on kvm-devel, this commit breaks the PowerPC build. Applied, thanks. Hollis, Could you explain why this patch breaks the powerpc build?

RE: [PATCH 03/04] qemu-kvm: Remove the dependency for phys_ram_base for ipf.c

Avi Kivity wrote: Jes Sorensen wrote: Zhang, Xiantao wrote: Jes Sorensen wrote: I still can't see the difference with the patch in Avi's tree except nvram stuff. And I believe the global variable you mentioned should be only used for nvram. So I propose an incremental patch for that. :)

Re: [PATCH] Assign the correct pci id range to virtio_pci

On Mon, 27 Apr 2009 12:53:25 pm Pantelis Koukousoulas wrote: On Mon, Apr 27, 2009 at 3:44 AM, Anthony Liguori anth...@codemonkey.ws wrote: Would be good to at least include the experiment range in case people are making third-party virtio modules and want to play around without replacing

Re: KVM x86_64 with SR-IOV..?

On Monday 04 May 2009 08:53:07 Nicholas A. Bellinger wrote: On Sat, 2009-05-02 at 18:22 +0800, Sheng Yang wrote: On Thu, Apr 30, 2009 at 01:22:54PM -0700, Nicholas A. Bellinger wrote: Greetings KVM folks, I wondering if any information exists for doing SR-IOV on the new VT-d capable

Re: [PATCH] Assign the correct pci id range to virtio_pci

I 'd be happy with a simple comment explaining the 0x103f (e.g., /* Not yet using the full 0x1000 - 0x10ef to hedge our bets in case we broke the ABI.*/ as explained above) Thanks, I like your patch. Where did this idea of experimental range come from, BTW? In the qemu sources, there is a

Re: [RFC 1/2] Add MCE simulation support to qemu/tcg

I found there is a qemu-kvm.git on git.kernel.org. I will re-base my patches for that. And I found that the kvm support in qemu (target-i386/kvm.c) is quite different from that in qemu-kvm (kvm/). Where should MCE support goes? To target-i386/kvm.c or kvm/ or both? Best Regards, Huang Ying On

Re: KVM x86_64 with SR-IOV..?

On Mon, 2009-05-04 at 10:09 +0800, Sheng Yang wrote: On Monday 04 May 2009 08:53:07 Nicholas A. Bellinger wrote: On Sat, 2009-05-02 at 18:22 +0800, Sheng Yang wrote: On Thu, Apr 30, 2009 at 01:22:54PM -0700, Nicholas A. Bellinger wrote: Greetings KVM folks, I wondering if any

Re: [PATCH 03/04] qemu-kvm: Remove the dependency for phys_ram_base for ipf.c

Zhang, Xiantao wrote: Avi Kivity wrote: Looks good to me. Xiantao? Hi, Jes Have you tested nvram support with this patch? I Xiantao No, But it is behaving exactly like the old code, so it is no more broken than the old code was. Lets apply this and then look at the nvram issues

RE: [PATCH 03/04] qemu-kvm: Remove the dependency for phys_ram_base for ipf.c

Jes Sorensen wrote: Zhang, Xiantao wrote: Avi Kivity wrote: Looks good to me. Xiantao? Hi, Jes Have you tested nvram support with this patch? I Xiantao No, But it is behaving exactly like the old code, so it is no more broken than the old code was. Lets apply this and then

Re: KVM x86_64 with SR-IOV..?

On Sun, 2009-05-03 at 21:36 -0700, Nicholas A. Bellinger wrote: On Mon, 2009-05-04 at 10:09 +0800, Sheng Yang wrote: On Monday 04 May 2009 08:53:07 Nicholas A. Bellinger wrote: On Sat, 2009-05-02 at 18:22 +0800, Sheng Yang wrote: On Thu, Apr 30, 2009 at 01:22:54PM -0700, Nicholas A.

Re: KVM x86_64 with SR-IOV..?

On Sun, 2009-05-03 at 22:28 -0700, Nicholas A. Bellinger wrote: On Sun, 2009-05-03 at 21:36 -0700, Nicholas A. Bellinger wrote: On Mon, 2009-05-04 at 10:09 +0800, Sheng Yang wrote: On Monday 04 May 2009 08:53:07 Nicholas A. Bellinger wrote: On Sat, 2009-05-02 at 18:22 +0800, Sheng Yang