Re: [KVM_AUTOTEST] unattended installs take 2

On 6/19/2009 12:50 AM, David Huff wrote: Second pass at the unattended install test. Both Linux and Windows guests are working however currently it just uses the existing boot test and extends timeouts. We still need a good way of determining if an unattended install completed without error. Fo

Re: [PATCH] Added two sample unattended config files, Fedora and Windows

On 6/19/2009 12:50 AM, David Huff wrote: You must add your own product key to the windows config file. --- client/tests/kvm/unattended/Fedora-11-i386.ks | 24 +++ client/tests/kvm/unattended/WinXP-32.sif | 52 + 2 files changed, 76 insertions(+), 0 del

[PATCH/RFC] virtio_test: A module for testing virtio via userspace

Hello Rusty, this is a result of a two month internship about virtio testing. From: Adrian Schneider From: Tim Hofmann From: Christian Ehrhardt From: Christian Borntraeger This patch introduces a prototype for a virtio_test module. This module can be bound to any virtio device via sysfs bind

Re: [PATCH] kvm: device-assignment: Add PCI option ROM support

On Friday 19 June 2009 00:28:41 Alex Williamson wrote: > On Thu, 2009-06-18 at 13:30 +0800, Yang, Sheng wrote: > > On Tuesday 16 June 2009 00:29:17 Alex Williamson wrote: > > > The PCI code already knows about option ROMs, so we just need to > > > mmap some space for it, load it with a copy of the

Re: ESX on KVM requirements

On 19.06.2009, at 03:19, Ben Sanders wrote: I needed nested paging to have things work, so phenom was mandatory. Also, because I was running things on a Phenom, I figured the safest bet is to be truthful in telling the guest what it's running on. Also ESX checked for specific cpuid revisi

[PATCH] KVM: SVM: Pass through the host kernel's IO delay port

From: Paolo Bonzini KVM's optimization of guest port 80 accesses was removed last May 11 in commit 99f85a. However, this probably has speed penalties. I don't have a machine to test but the equivalent VMX patch (fdef3ad) reported a speedup of 3-5%, and on the Xen mailing list it was mentioned t

Re: [KVM-AUTOTEST PATCH] stress_boot - Boot VMs until one of them becomes unresponsive - Version2

On Thu, 2009-06-18 at 17:16 +0800, Yolkfull Chow wrote: > Hi Lucas, I also found the number counting problem later after sending > the patch. I haven't been able to re-send the updated one since I got > some other things to deal with in these days. Sorry for that... > > Please see attachment

[PATCH 3/8] kvm/mmu: rename is_largepage_backed to mapping_level

With the new name and the corresponding backend changes this function can now support multiple hugepage sizes. Signed-off-by: Joerg Roedel --- arch/x86/kvm/mmu.c | 100 +-- arch/x86/kvm/paging_tmpl.h |4 +- 2 files changed, 69 insertions(+), 3

[PATCH 7/8] kvm/mmu: enable gbpages by increasing nr of pagesizes

Signed-off-by: Joerg Roedel --- arch/x86/include/asm/kvm_host.h |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/arch/x86/include/asm/kvm_host.h b/arch/x86/include/asm/kvm_host.h index 397f992..26ea9b8 100644 --- a/arch/x86/include/asm/kvm_host.h +++ b/arch/x86/include/as

[PATCH 2/8] kvm: change memslot data structures for multiple hugepage sizes

Signed-off-by: Joerg Roedel --- arch/ia64/include/asm/kvm_host.h|3 +- arch/powerpc/include/asm/kvm_host.h |3 +- arch/x86/include/asm/kvm_host.h | 12 arch/x86/kvm/mmu.c | 30 ++- arch/x86/kvm/paging_tmpl.h |3 +- include

[PATCH 1/8] hugetlbfs: export vma_kernel_pagsize to modules

This function is required by KVM. Signed-off-by: Joerg Roedel --- mm/hugetlb.c |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/mm/hugetlb.c b/mm/hugetlb.c index e83ad2c..e2016ef 100644 --- a/mm/hugetlb.c +++ b/mm/hugetlb.c @@ -234,6 +234,7 @@ unsigned long vma_kernel_pag

[PATCH 6/8] kvm/mmu: add support for another level to page walker

The page walker may be used with nested paging too when accessing mmio areas. Make it support the additional page-level too. Signed-off-by: Joerg Roedel --- arch/x86/kvm/mmu.c |6 ++ arch/x86/kvm/paging_tmpl.h | 16 2 files changed, 22 insertions(+), 0 deletion

[PATCH 5/8] kvm/mmu: make direct mapping paths aware of mapping levels

Signed-off-by: Joerg Roedel --- arch/x86/include/asm/kvm_host.h |2 +- arch/x86/kvm/mmu.c | 60 ++- arch/x86/kvm/paging_tmpl.h |6 ++-- 3 files changed, 38 insertions(+), 30 deletions(-) diff --git a/arch/x86/include/asm/kvm_host.h

[PATCH 4/8] kvm/mmu: make rmap code aware of mapping levels

This patch removes the largepage parameter from the rmap_add function. Together with rmap_remove this function now uses the role.level field to find determine if the page is a huge page. Signed-off-by: Joerg Roedel --- arch/x86/kvm/mmu.c | 53 +++

[PATCH 8/8] kvm x86: report 1GB page support to userspace

If userspace knows that the kernel part supports 1GB pages it can enable the corresponding cpuid bit so that guests actually use GB pages. Signed-off-by: Joerg Roedel --- arch/x86/include/asm/kvm_host.h |1 + arch/x86/kvm/svm.c |6 ++ arch/x86/kvm/vmx.c |

[PATCH 0/8 v3] KVM support for 1GB pages

Hi, this is the third version of the patches for KVM to support 1GB pages. Changes to the last version include: - changed reporting of 1GB page support to userspace to use SUPPORTED_CPUID ioctl - added support for 1GB pages to the software page walker code too This code

Re: [PATCH] kvm: device-assignment: Add PCI option ROM support

On Fri, 2009-06-19 at 15:27 +0800, Yang, Sheng wrote: > On Friday 19 June 2009 00:28:41 Alex Williamson wrote: > > The one oddity I noticed is that even when the enable bit is clear, the > > guest can read the ROM. I don't know that this is actually illegal, vs > > returning zeros or ones though.

Re: [PATCH 2/2][RFC] Kernel changes for HPET legacy mode (v7)

Jan Kiszka wrote: Beth Kon wrote: When kvm is in hpet_legacy_mode, the hpet is providing the timer interrupt and the pit should not be. So in legacy mode, the pit timer is destroyed, but the *state* of the pit is maintained. So if kvm or the guest tries to modify the state of the pit, this m

[patch] qemu-kvm introduce -maxcpus argument

Hi, This one introduces a -maxcpus setting, allowing the user to specify the maximum number of vCPUs the system can have, as discussed with Gleb earlier in the week. Cheers, Jes Introduce -maxcpus flag to QEMU and pass the value to the BIOS through FW_CFG. Follow on patch will use it to determ

[patch] qemu-kvm, use max_cpus to size MADT table

Hi, This one goes on top of the -maxcpus patch. It changes the bios to use max_cpus to determine the size of the MADT table. When no -maxcpus argument is given, we still fall back to the old default of 16. Cheers, Jes Build madt table based on max_cpus count. Signed-off-by: Jes Sorensen

Re: [patch] qemu-kvm introduce -maxcpus argument

On Fri, Jun 19, 2009 at 03:59:57PM +0200, Jes Sorensen wrote: > Hi, > > This one introduces a -maxcpus setting, allowing the user to specify > the maximum number of vCPUs the system can have, as discussed with Gleb > earlier in the week. What is the maximum value for the 'maxcpus' setting for KVM

Re: [patch] qemu-kvm introduce -maxcpus argument

On 06/19/2009 04:15 PM, Daniel P. Berrange wrote: On Fri, Jun 19, 2009 at 03:59:57PM +0200, Jes Sorensen wrote: Hi, This one introduces a -maxcpus setting, allowing the user to specify the maximum number of vCPUs the system can have, as discussed with Gleb earlier in the week. What is the max

-no-kvm broken since merge a5b526135d

JFYI: qemu-kvm commit de408d70d8 works fine with -no-kvm, a5b526135d produces qemu: fatal: Trying to execute code outside RAM or ROM at 0x0001000d5f4f EAX=0001 EBX=0070 ECX=005f EDX=0001 ESI= EDI= EBP= ESP= EIP=000e5f4f EFL=0002 [---] CP

Re: [patch] qemu-kvm introduce -maxcpus argument

On (Fri) Jun 19 2009 [15:59:57], Jes Sorensen wrote: > Hi, > > This one introduces a -maxcpus setting, allowing the user to specify > the maximum number of vCPUs the system can have, as discussed with Gleb > earlier in the week. ACK, but please fix this: +DEF("maxcpus", HAS_ARG, QEMU_OPTION_maxcp

Re: [KVM PATCH v2 2/2] kvm: use POLLHUP to close an irqfd instead of an explicit ioctl

On Thu, Jun 18, 2009 at 12:29:31PM -0400, Gregory Haskins wrote: > Michael S. Tsirkin wrote: > > On Thu, Jun 18, 2009 at 10:03:36AM -0400, Gregory Haskins wrote: > > > >> Michael S. Tsirkin wrote: > >> > >>> On Thu, Jun 18, 2009 at 08:00:39AM -0400, Gregory Haskins wrote: > >>> > >>>

Re: [KVM PATCH v2 2/2] kvm: use POLLHUP to close an irqfd instead of an explicit ioctl

Michael S. Tsirkin wrote: > On Thu, Jun 18, 2009 at 12:29:31PM -0400, Gregory Haskins wrote: > >> Michael S. Tsirkin wrote: >> >>> On Thu, Jun 18, 2009 at 10:03:36AM -0400, Gregory Haskins wrote: >>> >>> Michael S. Tsirkin wrote: > On Thu, Jun 18,

[PATCH] qemu-kvm: x86: Fix CPU initialization

Fix regression in CPU initialization caused by merge a5b526135d and try to avoid this in the future by dropping qemu-kvm specific pc_new_cpu. If such refactoring is desired, it should go through upstream first. Signed-off-by: Jan Kiszka --- hw/pc.c | 44 ++-

[PATCH v2] qemu-kvm: x86: Fix CPU initialization

Jan Kiszka wrote: > Fix regression in CPU initialization caused by merge a5b526135d and try > to avoid this in the future by dropping qemu-kvm specific pc_new_cpu. If > such refactoring is desired, it should go through upstream first. F...ine. I'll write a hundred times: "Don't post while still co

Checking guest memory pages changes from host userspace

Hi list, I need to monitor some guest memory pages. I need to know if the information in these pages was changed. For this, I was thinking to mark the guest memory pages in some way (like write protecting them) so a page fault is generated. Then manage this fault inside qemu. Is there so

[PATCH] virtio_blk: don't bounce highmem requests

By default a block driver bounces highmem requests, but virtio-blk is perfectly fine with any request that fit into it's 64 bit addressing scheme, mapped in the kernel virtual space or not. Besides improving performance on highmem systems this also makes the reproducible oops in __bounce_end_io g

[PATCH 1/3] eventfd: Allow waiters to be notified about the eventfd file* going away

From: Davide Libenzi And give them a change to unregister from the wait queue. This is turn allows eventfd users to use the eventfd file* w/out holding a live reference to it. After the eventfd user callbacks returns, any usage of the eventfd file* should be dropped. The eventfd user callback

Re: [KVM-RFC PATCH 1/2] eventfd: add an explicit srcu based notifier interface

Davide Libenzi wrote: > On Thu, 18 Jun 2009, Gregory Haskins wrote: > >> >> But the fact is: I do not see any way to actually use your referenceless >> POLLHUP release code in a race free way without doing something like I >> propose in 3/4, 4/4. Lets keep the discussion focused on that for now,

[PATCH 3/3] eventfd: add internal reference counting to fix notifier race conditions

eventfd currently emits a POLLHUP wakeup on f_ops->release() to generate a notifier->release() callback. This lets notification clients know if the eventfd is about to go away and is very useful particularly for in-kernel clients. However, as it stands today it is not possible to use the notifica

[PATCH 2/3] eventfd: add generalized notifier interface

Users that want to register for signal notifications with eventfd have several choices today: They can do a standard sleep+wakeup against a ->read(), or they can provide their own wakeup handling using the wait-queue callback mechanism coupled with the the eventfd->poll() interface. In fact, Davi

Re: [PATCH 3/3] eventfd: add internal reference counting to fix notifier race conditions

On Fri, 19 Jun 2009, Gregory Haskins wrote: > eventfd currently emits a POLLHUP wakeup on f_ops->release() to generate a > notifier->release() callback. This lets notification clients know if > the eventfd is about to go away and is very useful particularly for > in-kernel clients. However, as i

kvm: emulation failure

I see this problem with a x86 sles10 guest running on x86_64 intel host. If the guest is reset abruptly and rebooted, some where before grub sequence it hangs and the following message is seen in the logs emulation failed (pagetable) rip 7ed5 66 60 ac 20. I located this instruction sequence in i

Re: [PATCH 3/3] eventfd: add internal reference counting to fix notifier race conditions

Davide Libenzi wrote: > On Fri, 19 Jun 2009, Gregory Haskins wrote: > > >> eventfd currently emits a POLLHUP wakeup on f_ops->release() to generate a >> notifier->release() callback. This lets notification clients know if >> the eventfd is about to go away and is very useful particularly for >>

Re: [PATCH 3/3] eventfd: add internal reference counting to fix notifier race conditions

On Fri, 19 Jun 2009, Gregory Haskins wrote: > Davide Libenzi wrote: > > On Fri, 19 Jun 2009, Gregory Haskins wrote: > > > > > >> eventfd currently emits a POLLHUP wakeup on f_ops->release() to generate a > >> notifier->release() callback. This lets notification clients know if > >> the eventfd

Re: [PATCH 3/3] eventfd: add internal reference counting to fix notifier race conditions

Davide Libenzi wrote: > On Fri, 19 Jun 2009, Gregory Haskins wrote: > > >> Davide Libenzi wrote: >> >>> On Fri, 19 Jun 2009, Gregory Haskins wrote: >>> >>> >>> eventfd currently emits a POLLHUP wakeup on f_ops->release() to generate a notifier->release() callback. This

Re: [PATCH 3/3] eventfd: add internal reference counting to fix notifier race conditions

On Fri, 19 Jun 2009, Gregory Haskins wrote: > I am fairly confident it is not that simple after having thought about > this issue over the last few days. But I've been wrong in the past. > Propose a patch and I will review it for races/correctness, if you > like. Perhaps a combination of that p

Re: [PATCH 3/3] eventfd: add internal reference counting to fix notifier race conditions

On Fri, 19 Jun 2009, Davide Libenzi wrote: > On Fri, 19 Jun 2009, Gregory Haskins wrote: > > > I am fairly confident it is not that simple after having thought about > > this issue over the last few days. But I've been wrong in the past. > > Propose a patch and I will review it for races/correc

Re: [PATCH 3/3] eventfd: add internal reference counting to fix notifier race conditions

Davide Libenzi wrote: > On Fri, 19 Jun 2009, Davide Libenzi wrote: > > >> On Fri, 19 Jun 2009, Gregory Haskins wrote: >> >> >>> I am fairly confident it is not that simple after having thought about >>> this issue over the last few days. But I've been wrong in the past. >>> Propose a patc

Luvalley-3 has been released, this release is for AMD CPU only

Hi, all, This Luvalley release is for machines with AMD CPUs only. It cannot work on Intel CPUs. Also, this release is for Linux dom0 only. Please refer to Luvalley-2 if you have a machine with Intel CPUs. Due to the limitations of AMD CPUs, this Luvalley release has a new architecture different

kernel backtrace pointing at KVM

Hello KVM team, I am using KVM for maintaining mixture of Windows and Linux VMs. recently I reinstalled the system with latest kernel 2.6.30 and qemu-kvm-0.86. I kept using the KVM module from the 2.6.30 kernel not from the pack with the qemu-kvm. Last night one of the Windows XP SP3 system reboot

Re: Checking guest memory pages changes from host userspace

On (Fri) Jun 19 2009 [12:09:10], Passera, Pablo R wrote: > Hi list, > I need to monitor some guest memory pages. I need to know if the > information in these pages was changed. For this, I was thinking to mark the > guest memory pages in some way (like write protecting them) so a page fau