[PATCH] kvm: libkvm: change full memory logging to use the per-slot refcounting api

From: Avi Kivity [EMAIL PROTECTED] this allows full memory logging (for migration) and partial memory logging (for vga tracking) to coexist. Signed-off-by: Avi Kivity [EMAIL PROTECTED] diff --git a/libkvm/libkvm.c b/libkvm/libkvm.c index a7cb2a9..444b97f 100644 --- a/libkvm/libkvm.c +++

[PATCH] kvm: libkvm: add memory registration debugging traces

From: Avi Kivity [EMAIL PROTECTED] Signed-off-by: Avi Kivity [EMAIL PROTECTED] diff --git a/libkvm/libkvm.c b/libkvm/libkvm.c index 4f23eae..c387522 100644 --- a/libkvm/libkvm.c +++ b/libkvm/libkvm.c @@ -180,7 +180,11 @@ static int kvm_dirty_pages_log_change(kvm_context_t kvm, unsigned long

[PATCH] kvm: add api to enable or disable dirty logging on a per-slot basis

From: Avi Kivity [EMAIL PROTECTED] the api counts the number of requests to log a slot, so that multiple simultaneous users can be supported. when the last user disappears, dirty logging is disabled. Signed-off-by: Avi Kivity [EMAIL PROTECTED] diff --git a/libkvm/libkvm.c b/libkvm/libkvm.c

[PATCH] kvm: libkvm: change the logging functions to be able to reset the log bit

From: Avi Kivity [EMAIL PROTECTED] currently, the memory logging functions aren't able to clear flags, and they don't maintain the slot flags field correctly. Fix by passing a mask which indicates which bits are to be set or reset. Signed-off-by: Avi Kivity [EMAIL PROTECTED] diff --git

[PATCH] kvm: qemu: add api to change memory logging status of a slot

From: Avi Kivity [EMAIL PROTECTED] Signed-off-by: Avi Kivity [EMAIL PROTECTED] diff --git a/qemu/qemu-kvm.c b/qemu/qemu-kvm.c index 3e47c81..aca3358 100644 --- a/qemu/qemu-kvm.c +++ b/qemu/qemu-kvm.c @@ -961,6 +961,15 @@ int kvm_update_dirty_pages_log(void) return r; } +void

[PATCH] kvm: qemu: fix migrate_close() returning random error

From: Avi Kivity [EMAIL PROTECTED] A recent merge changed the file close callback signature, resulting in migrate_close() returning garbage and failing migrations. Signed-off-by: Avi Kivity [EMAIL PROTECTED] diff --git a/qemu/migration.c b/qemu/migration.c index 20e4c54..44cb9eb 100644 ---

[PATCH] kvm: qemu: use qemu-allocated memory for vga

From: Avi Kivity [EMAIL PROTECTED] Instead of juggling with vga-allocated memory when logging memory, use the regular memory allocated by qemu from phys_ram_base, and use the slot management api to map it into kvm and turn on logging if the current mode allows this. Fixes the std-vga regression.

Re: [PATCH] [RESEND] VT-d: Support multiple device assignment to one guest

Han, Weidong wrote: It's hard to move kvm_vtd_domain inside current iommu API. It's kvm specific. It's not elegant to include kvm_vtd_domain stuffs in native VT-d code. It's cleaner than adding knowledge of how the iommu works to kvm. I think leave it in kvm side is more clean at this

Re: [PATCH 0/6] MTRR/PAT support for EPT (v3)

Sheng Yang wrote: Yeah, I think the condition I mentioned is a example of yours. But in fact it's difficult to get a optimize value... I think it's possible that qemu may access all memory it owned, if so, no guest mtrr would affect. But how can we tell qemu would access which region of

Re: [PATCH 0/6] MTRR/PAT support for EPT (v3)

On Friday 10 October 2008 14:49:13 Avi Kivity wrote: Sheng Yang wrote: Yeah, I think the condition I mentioned is a example of yours. But in fact it's difficult to get a optimize value... I think it's possible that qemu may access all memory it owned, if so, no guest mtrr would affect.

RE: [PATCH] [RESEND] VT-d: Support multiple device assignment to one guest

Avi Kivity wrote: Han, Weidong wrote: It's hard to move kvm_vtd_domain inside current iommu API. It's kvm specific. It's not elegant to include kvm_vtd_domain stuffs in native VT-d code. It's cleaner than adding knowledge of how the iommu works to kvm. I will try to move kvm_vtd_domain

Re: [PATCH 4/6 v3] PCI: support SR-IOV capability

Alex Chiang wrote: Do you want to emit a kobject_uevent here after success? Alternatively, have you investigated making these virtual functions into real struct device's? You get a lot of sysfs stuff for free if you do so, including correct place in sysfs hierarchy and uevents, etc. The

Re: [PATCH] [RESEND] VT-d: Support multiple device assignment to one guest

Han, Weidong wrote: 2.6.27 is out, so anything we do will be for 2.6.29. Do you mean the VT-d patches which haven't been checked in won't be pushed into 2.6.28? Yes. The only exception is the guest interrupt sharing patch, which is awaiting testing. -- I have a truly marvellous

RE: [PATCH] [RESEND] VT-d: Support multiple device assignment to one guest

Avi Kivity wrote: Han, Weidong wrote: 2.6.27 is out, so anything we do will be for 2.6.29. Do you mean the VT-d patches which haven't been checked in won't be pushed into 2.6.28? Yes. The only exception is the guest interrupt sharing patch, which is awaiting testing. Ok, I

[ kvm-Bugs-2138166 ] Vista guest fails to start on kvm-76

Bugs item #2138166, was opened at 2008-09-30 14:39 Message generated for change (Comment added) made by markit You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2138166group_id=180599 Please note that this message will contain a full copy of the comment

Re: [ Re: unhandled vm exit: 0x80000021 vcpu_id 0]

Messaggio originale Da: [EMAIL PROTECTED] Data: 09/10/2008 16.58 A: [EMAIL PROTECTED][EMAIL PROTECTED] Cc: kvmkvm@vger.kernel.org Ogg: Re: [ Re: unhandled vm exit: 0x8021 vcpu_id 0] On Wed, Oct 8, 2008 at 7:16 AM, [EMAIL PROTECTED] [EMAIL PROTECTED] it wrote: Hi Yang, I often

how to determine that the VM is running

Hi, I'm currently configuring two hosts that will run KVM virtual machines. They are attached to a shared storage device on which the vm's will be stored. I start the VM on one of the hosts and then connect to the monitor interface. To migrate, I enter the migrate ssh://other-host command

[ kvm-Bugs-2149609 ] Booting IA32e Windows guest meets BSOD

Bugs item #2149609, was opened at 2008-10-06 07:25 Message generated for change (Comment added) made by jiajun You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2149609group_id=180599 Please note that this message will contain a full copy of the comment

Re: Call for help: moving the kvm wiki

As you may have noticed, the kvm wiki is overrun by spammers. It the past I've regularly cleaned up the spam, but some time ago I've given up. So I'm looking for a volunteer to locate a spam-free public wiki host (candidates include wiki.kernel.org and fedorahosted.org) and transfer the

Re: [RFC][PATCH 0/2] Fix guest shared interrupt with in-kernel irqchip

* On Friday 03 Oct 2008 16:07:54 Sheng Yang wrote: @@ -319,15 +319,23 @@ static int kvm_vm_ioctl_assign_device(struct kvm *kvm, list_add(match-list, kvm-arch.assigned_dev_head); + r = kvm_request_irq_source_id(kvm); This should be done in the kvm_vm_ioctl_assign_irq call, just

Weekly KVM Test report, kernel fc803bfe ... userspace 812aed96 ... -- Two new issues

Hi All, This is our Weekly KVM Testing Report against lastest kvm.git fc803bfea824a49d1eb1b30f704cff0443d51069 and kvm-userspace.git 812aed967c6d140ccb0a38bba87b59f3185bab23. There are two new issues found this week. New issues: 1. Fail to do Live

Start KVM guest headless

I am wondering to how to start a KVM guest OS headless, ie, no monitoring window? And I can attach to the guest's console if I want to. Simon -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to [EMAIL PROTECTED] More majordomo info at

Re: Start KVM guest headless

On Fri, Oct 10, 2008 at 10:24 AM, Simon Gao [EMAIL PROTECTED] wrote: I am wondering to how to start a KVM guest OS headless, ie, no monitoring window? And I can attach to the guest's console if I want to. -vnc displaynum -- Javier -- To unsubscribe from this list: send the line unsubscribe

Re: Start KVM guest headless

On Fri, Oct 10, 2008 at 08:24:54AM -0700, Simon Gao wrote: I am wondering to how to start a KVM guest OS headless, ie, no monitoring window? And I can attach to the guest's console if I want to. http://bellard.org/qemu/qemu-doc.html#SEC10 Read about the '-vnc' option to start it headless,

Re: Start KVM guest headless

On Fri, Oct 10, 2008 at 11:24 AM, Simon Gao [EMAIL PROTECTED] wrote: I am wondering to how to start a KVM guest OS headless, ie, no monitoring window? And I can attach to the guest's console if I want to. Start the guest with -vnc :NUM -daemonize Connect to the guest later with vncviewer :NUM

with kerenl 2.6.27, CONFIG_KVM_GUEST does not work

Kernel 2.6.27 + kvm-76 on the host really gives some performance boost here. but: When running 2.6.27 compiled with CONFIG_KVM_GUEST=y in the guest, the guest won't start, lot's of segfaults (in the guest) especially udev initializations. unset CONFIG_KVM_GUEST=y, then the guest runs fine -- To

[PATCH] Expand cache= option and use write-through caching by default

This patch changes the cache= option to accept none, writeback, or writethough to control the host page cache behavior. By default, writethrough caching is now used which internally is implemented by using O_DSYNC to open the disk images. When using -snapshot, writeback is used by default since

Re: ACPI

On Fri, 10 Oct 2008 13:32:48 -0700, jd wrote: Hi -- For Windows guests No ACPI. XP and newer use an ACPI register, that according to the wiki, incurs a large virtualization penalty. -- For Linix guests Go ACPI afaik, so you get PM support and guess sleeping IIRC. Thanks /Jd

Re: exit timing analysis v1 - commentsdiscussions welcome

Hollis Blanchard wrote: Also, it looks like we use the generic find_first_bit(). That may be more expensive than we'd like. However, since vcpu-arch.pending_exceptions is a single long (not an arbitrary sized bitfield), we should be able to use ffs() instead, which has an optimized PowerPC