[PATCH] extboot should update number of HDs reported by BIOS

This fixes Vista boot from virtio-blk issue. Signed-off-by: Gleb Natapov g...@redhat.com diff --git a/extboot/extboot.S b/extboot/extboot.S index e3d1adf..1e60f68 100644 --- a/extboot/extboot.S +++ b/extboot/extboot.S @@ -32,6 +32,9 @@ _start: xor %ax, %ax mov %ax, %ds +

Re: kvm: external module: do not hardcode tsc_khz

Marcelo Tosatti wrote: external module compat hard codes tsc_khz as 200 if KERNEL_VERSION (2,6,23). This breaks kvmclock on hosts with different frequency. While tsc_khz was only exported on 2.6.23, the majority of relevant older v2.6 based distros seem to have it exported. Applied,

Re: cr3 OOS optimisation breaks 32-bit GNU/kFreeBSD guest

Marcelo Tosatti wrote: Maybe it's best to resync when relinking a global page? How about this. It will shorten the unsync period of global pages, unfortunately. diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c index 2a36f7f..bccdcc7 100644 --- a/arch/x86/kvm/mmu.c +++

Re: [PATCH] extboot should update number of HDs reported by BIOS

Gleb Natapov schrieb: This fixes Vista boot from virtio-blk issue. Did I miss Windows virtio block drivers? ;) -- Tomasz Chmielewski http://wpkg.org -- 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: [PATCH] extboot should update number of HDs reported by BIOS

On Tue, Mar 24, 2009 at 11:03:12AM +0100, Tomasz Chmielewski wrote: Gleb Natapov schrieb: This fixes Vista boot from virtio-blk issue. Did I miss Windows virtio block drivers? ;) With this patch you'll get better experience with virtio block drivers when they will be released! :) --

Re: [PATCH 2/2] Interrupt unhalts vcpu when it shouldn't

Gleb Natapov wrote: kvm_vcpu_block() unhalts vpu on an interrupt/timer without checking if interrupt window is actually opened. Applied both, thanks. -- Do not meddle in the internals of kernels, for they are subtle and quick to panic. -- To unsubscribe from this list: send the line

Re: cr3 OOS optimisation breaks 32-bit GNU/kFreeBSD guest

On Mon, Mar 23, 2009 at 02:27:25PM -0300, Marcelo Tosatti wrote: On Sun, Mar 22, 2009 at 11:35:00AM +0200, Avi Kivity wrote: Good catch, indeed. But is it sufficient? We could unlink a page through other means, for example by the guest zapping a page directory entry. Yep.

[ kvm-Bugs-2702210 ] -cpu core2duo still crashes linux guests under kvm-84

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

AMD-Intel guest migration and CPUs without NX

I have an older Intel CPU which doesn't support NX (/proc/cpuinfo - below). Is it safe to migrate guests running on newer CPUs to this older CPU? I made some simple tests and migration works, but I'm not sure if the guests will be stable after such migration. I'm also a bit confused a bit

Inter VM Communication

Just like how Xen has Xenbus, Emulated Platform-PCI device and Events for Inter VM communication, Does KVM has any mechanism for Inter VM communication? How to share a page between two virtual machines running on KVM? Thx, Venkat -- To unsubscribe from this list: send the line unsubscribe kvm

Re: cr3 OOS optimisation breaks 32-bit GNU/kFreeBSD guest

On Tue, Mar 24, 2009 at 11:47:33AM +0200, Avi Kivity wrote: Marcelo Tosatti wrote: Maybe it's best to resync when relinking a global page? How about this. It will shorten the unsync period of global pages, unfortunately. diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c index

Re: [PATCH] extboot should update number of HDs reported by BIOS

Gleb Natapov wrote: This fixes Vista boot from virtio-blk issue. Applied, thanks. -- Do not meddle in the internals of kernels, for they are subtle and quick to panic. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org

Re: AMD-Intel guest migration and CPUs without NX

Tomasz Chmielewski wrote: I have an older Intel CPU which doesn't support NX (/proc/cpuinfo - below). Is it safe to migrate guests running on newer CPUs to this older CPU? I made some simple tests and migration works, but I'm not sure if the guests will be stable after such migration. I'm

kvm-84 and guests with more than 3536 MB Ram?

Hi! This is my first post here so please bear with me; we have a Debian Lenny system with kernel 2.6.28 and kvm-84, and can't start a guest with more than 3536 MB Ram. With kvm-72 (the version lenny released with) we can use all 7GB that is intended for that guest. Is this a known bug? Someone

Re: Inter VM Communication

Kumar, Venkat wrote: Just like how Xen has Xenbus, Emulated Platform-PCI device and Events for Inter VM communication, Does KVM has any mechanism for Inter VM communication? How to share a page between two virtual machines running on KVM? If you just want to share a page (or a bunch of

Re: kvm-84 and guests with more than 3536 MB Ram?

Lukas Kolbe wrote: Hi! This is my first post here so please bear with me; we have a Debian Lenny system with kernel 2.6.28 and kvm-84, and can't start a guest with more than 3536 MB Ram. With kvm-72 (the version lenny released with) we can use all 7GB that is intended for that guest. Is this a

[PATCH kvm-autotest] commonize log_into_alive_vm code

Almost all tests that are and will be have the common need to log into the vm, and verify it is alive. It's currently duplicated across all tests, so rip it to a common location. Signed-off-by: Glauber Costa glom...@redhat.com --- client/tests/kvm_runtest_2/kvm_tests.py | 46

KVM84 crash during compilation

Hi, I'm using KVM 84 with Gentoo as host and guest. All hosts and guest running with kernel 2.6.28 and the servers are HP DL380 with Intel Xeon CPU L5420. From time to time it happens that the guest crashes during compilation of a new kernel or update the OS which in turn means under Gentoo that

Re: AMD-Intel guest migration and CPUs without NX

Avi Kivity schrieb: So the above says I may have some problems. Right, it's not safe in general. It may work if the guest doesn't use NX. It may also work if the guest does not rely on NX working properly. Although I think my guests don't use it, you never know. Is it possible to disable

Re: AMD-Intel guest migration and CPUs without NX

Tomasz Chmielewski wrote: Although I think my guests don't use it, you never know. Is it possible to disable NX for chosen guests? -cpu qemu64,-nx -- Do not meddle in the internals of kernels, for they are subtle and quick to panic. -- To unsubscribe from this list: send the line

Re: [PATCH kvm-autotest] commonize log_into_alive_vm code

On Tue, Mar 24, 2009 at 10:20 AM, Glauber Costa glom...@redhat.com wrote: Almost all tests that are and will be have the common need to log into the vm, and verify it is alive. It's currently duplicated across all tests, so rip it to a common location. screw this. I just realized I sent an

Re: AMD-Intel guest migration and CPUs without NX

Avi Kivity schrieb: Tomasz Chmielewski wrote: Although I think my guests don't use it, you never know. Is it possible to disable NX for chosen guests? -cpu qemu64,-nx Thanks. I updated the FAQ and migration pages to contain this information. -- Tomasz Chmielewski http://wpkg.org -- To

Re: kvm-84 and guests with more than 3536 MB Ram?

On Di, 2009-03-24 at 14:59 +0200, Avi Kivity wrote: Lukas Kolbe wrote: Hi! This is my first post here so please bear with me; we have a Debian Lenny system with kernel 2.6.28 and kvm-84, and can't start a guest with more than 3536 MB Ram. With kvm-72 (the version lenny released with) we

Re: kvm-84 and guests with more than 3536 MB Ram?

Lukas Kolbe wrote: On Di, 2009-03-24 at 14:59 +0200, Avi Kivity wrote: Lukas Kolbe wrote: Hi! This is my first post here so please bear with me; we have a Debian Lenny system with kernel 2.6.28 and kvm-84, and can't start a guest with more than 3536 MB Ram. With kvm-72 (the version

Re: kvm-84 and guests with more than 3536 MB Ram?

Anthony Liguori schrieb: Lukas Kolbe wrote: On Di, 2009-03-24 at 14:59 +0200, Avi Kivity wrote: Lukas Kolbe wrote: Hi! This is my first post here so please bear with me; we have a Debian Lenny system with kernel 2.6.28 and kvm-84, and can't start a guest with more than 3536 MB Ram.

Re: [PATCH] extboot should update number of HDs reported by BIOS

Gleb Natapov wrote: On Tue, Mar 24, 2009 at 11:03:12AM +0100, Tomasz Chmielewski wrote: Gleb Natapov schrieb: This fixes Vista boot from virtio-blk issue. Did I miss Windows virtio block drivers? ;) With this patch you'll get better experience with virtio block drivers

Re: kvm-84 and guests with more than 3536 MB Ram?

Am Dienstag, den 24.03.2009, 17:04 +0100 schrieb Tomasz Chmielewski: Anthony Liguori schrieb: Lukas Kolbe wrote: On Di, 2009-03-24 at 14:59 +0200, Avi Kivity wrote: Lukas Kolbe wrote: Hi! This is my first post here so please bear with me; we have a Debian Lenny system with

svn change r6839 breaks screendump from monitor

Running a something simple like: % ./x86_64-softmmu/qemu-system-x86_64 -L pc-bios -hda /dev/null -monitor stdio Could not open '/dev/kqemu' - QEMU acceleration layer not activated: No such file or directory QEMU 0.10.0 monitor - type 'help' for more information (qemu) screendump /tmp/f.ppm

Re: kvm-84 and guests with more than 3536 MB Ram?

* Lukas Kolbe l-li...@einfachkaffee.de [2009-03-24 14:32]: Am Dienstag, den 24.03.2009, 17:04 +0100 schrieb Tomasz Chmielewski: Anthony Liguori schrieb: Lukas Kolbe wrote: On Di, 2009-03-24 at 14:59 +0200, Avi Kivity wrote: Lukas Kolbe wrote: Hi! This is my first

[PATCH] qemu: fix physical memory migration

Hi, Attaching patch that: 1. Fix physical memory live migration. - Stop dirty memory tracking after completion of memory transfer. - In stage 3, updating dirty memory bits before collecting remaining dirty blocks in order to prevent missing dirty blokes in the

[PATCH] fix bad physical address in kvm_update_dirty_pages_log()

Hi, Attaching patch that fix updating qemu dirty region. Previous kvm_update_dirty_pages_log() imp treat physical ram as if it is linear mapped to guest physical memory. This patch fix it by mapping physical ram to guest physical memory areas and for etch area call kvm_get_dirty_pages_range()

Re: kvm-84 and guests with more than 3536 MB Ram?

Am Dienstag, den 24.03.2009, 15:40 -0500 schrieb Ryan Harper: Hi Ryan, Doesn't he say that it did work for him with kvm-72, but does not with kvm-84? Exactly that :) kvm-72 works like a charm, with the noted exception that it crashes every now and than on our system (during heavy

Re: Inter VM Communication

Cam Macdonell wrote: If you just want to share a page (or a bunch of memory), write a qemu PCI device model that exposes that page through a BAR. The guests can then map the BAR and access the page. To share the page, use normal Linux memory sharing, such as shared memory segments or mapped

Can't boot guest with more than 3585MB when using large pages

On a 2.6.29, x86_64 host/guest, what's special about specifying a guest size of -m 3586 when using -mem-path backed by hugetlbfs? 3585 works, 3586 hangs here: ... PCI-DMA: Using software bounce buffering for IO (SWIOTLB) Placing 64MB software IO TLB between 88002000 - 88002400

Re: Inter VM Communication

Avi Kivity wrote: Kumar, Venkat wrote: Just like how Xen has Xenbus, Emulated Platform-PCI device and Events for Inter VM communication, Does KVM has any mechanism for Inter VM communication? How to share a page between two virtual machines running on KVM? If you just want to share a

Re: [PATCH] fix bad physical address in kvm_update_dirty_pages_log()

@@ -1223,12 +1244,44 @@ static int kvm_get_dirty_bitmap_cb(unsigned long start, unsigned long len, int kvm_update_dirty_pages_log(void) { int r = 0; +ram_addr_t now = 0; +ram_addr_t end = phys_ram_size; +ram_addr_t offset; +target_phys_addr_t area_start; +ram_addr_t

Re: [PATCH] fix bad physical address in kvm_update_dirty_pages_log()

Glauber Costa wrote: @@ -1223,12 +1244,44 @@ static int kvm_get_dirty_bitmap_cb(unsigned long start, unsigned long len, int kvm_update_dirty_pages_log(void) { int r = 0; +ram_addr_t now = 0; +ram_addr_t end = phys_ram_size; +ram_addr_t offset; +target_phys_addr_t

Re: kvm-84 and guests with more than 3536 MB Ram?

* Lukas Kolbe l-li...@einfachkaffee.de [2009-03-24 16:04]: Am Dienstag, den 24.03.2009, 15:40 -0500 schrieb Ryan Harper: Hi Ryan, Doesn't he say that it did work for him with kvm-72, but does not with kvm-84? Exactly that :) kvm-72 works like a charm, with the noted

Re: [PATCH] fix bad physical address in kvm_update_dirty_pages_log()

On Tue, Mar 24, 2009 at 6:27 PM, Yaniv Kamay yka...@redhat.com wrote: Glauber Costa wrote: @@ -1223,12 +1244,44 @@ static int kvm_get_dirty_bitmap_cb(unsigned long start, unsigned long len,  int kvm_update_dirty_pages_log(void)  {     int r = 0; +    ram_addr_t now = 0; +    ram_addr_t

Re: Can't boot guest with more than 3585MB when using large pages

* Alex Williamson alex.william...@hp.com [2009-03-24 16:07]: On a 2.6.29, x86_64 host/guest, what's special about specifying a guest size of -m 3586 when using -mem-path backed by hugetlbfs? 3585 works, 3586 hangs here: ... PCI-DMA: Using software bounce buffering for IO (SWIOTLB)

[PATCH 1/1] KVM: Correct wrong vmcs reading

Some 64bit reading should be natrual wide reading... Signed-off-by: Sheng Yang sh...@linux.intel.com --- arch/x86/kvm/vmx.c | 12 ++-- 1 files changed, 6 insertions(+), 6 deletions(-) diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c index d3919ac..ab736f6 100644 ---

Re: Inter VM Communication

Avi Kivity wrote: Kumar, Venkat wrote: Just like how Xen has Xenbus, Emulated Platform-PCI device and Events for Inter VM communication, Does KVM has any mechanism for Inter VM communication? How to share a page between two virtual machines running on KVM? If you just want to share a