Hi All,
This is today's KVM test result against kvm.git
9154fb8731388041c448c3838c548f36b67ed9af and kvm-userspace.git
163308a5a4e694f33368f8e0a874017e2e186d12.
There's no new issue today.
Three Old Issues:
1. 32bits Rhel5/FC6 guest may fail
Hi All,
This is today's KVM test result against kvm.git
9154fb8731388041c448c3838c548f36b67ed9af and kvm-userspace.git
163308a5a4e694f33368f8e0a874017e2e186d12.
There's no new issue today.
Three Old Issues:
1. 32bits Rhel5/FC6 guest may fail
Hi Avi,
On Thu, 2008-07-03 at 05:51 +, SourceForge.net wrote:
Bugs item #2009439, was opened at 2008-07-03 11:21
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
Weidong,
There seems to be line wrapping issues with the patch.
Please resend it.
Thanks,
Ben
On Thu, 2008-07-03 at 17:05 +0800, Han, Weidong wrote:
Multiple devices may under different IOMMUs, so one dmar_domain cannot
cover this. This patch abstracts a structure kvm_vtd_domain, which let
Ben,
Thanks for your reminder. I attach the patch.
Randy (Weidong)
Ben-Ami Yassour wrote:
Weidong,
There seems to be line wrapping issues with the patch.
Please resend it.
Thanks,
Ben
On Thu, 2008-07-03 at 17:05 +0800, Han, Weidong wrote:
Multiple devices may under different
On Jul 3, 2008, at 9:31 AM, Matthias Pfafferodt wrote:
Hello,
you could try the openSUSE build service:
ftp://ftp5.gwdg.de/pub/opensuse/repositories/Virtualization:/KVM:/git/SLE_10
This is actually the current git repository, so if things work
correctly this is the absolute bleeding-edge
If we're emulating an instruction, either it will succeed, in which case
any previously queued exception will be spurious, or we will requeue the
same exception.
Signed-off-by: Avi Kivity [EMAIL PROTECTED]
---
arch/x86/kvm/x86.c |2 ++
arch/x86/kvm/x86.h | 11 +++
2 files changed,
The vmx code assumes that IDT-Vectoring can only be set when an exception
is injected due to the exception in question. That's not true, however:
if the exception is injected correctly, and later another exception occurs
but its delivery is blocked due to a fault, then we will incorrectly assume
Instead of looking at failed injections in the vm entry path, move
processing to the exit path in vmx_complete_interrupts(). This simplifes
the logic and removes any state that is hidden in vmx registers.
Signed-off-by: Avi Kivity [EMAIL PROTECTED]
---
arch/x86/kvm/vmx.c | 73
On Thu, 2008-07-03 at 17:03 +0300, Avi Kivity wrote:
Mark McLoughlin wrote:
2) Although we currently build virtio_pci as a module in Fedora, it
leads to a pretty strange situation where e.g. mkinitrd and
anaconda need to explicitly include the virtio_pci module; I
On Thu, Jul 3, 2008 at 3:03 AM, Mark McLoughlin [EMAIL PROTECTED] wrote:
I think the below fixes the data corrupter, but I'm still tracking down
another issue where the guest is hanging waiting for I/O to complete
with the latest virtio-blk backend.
is that a common case? i haven't been able
Hi Marcelo and everyone,
I cleanedup the mmu notifier kvm patch. I also like math guarantee
that there won't be overflow (gfn_to_pfn may be slow compared to a
flood of invalidate_page unmapping ptes) so I changed the counter to
long and the sequence number to unsigned long. I'm quite sure it was
Bugs item #1967368, was opened at 2008-05-19 13:51
Message generated for change (Comment added) made by alex_williamson
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=1967368group_id=180599
Please note that this message will contain a full copy of the
kvm_mmu_zap_page() needs slots lock held (rmap_remove-gfn_to_memslot,
for example).
Since kvm_lock spinlock is held in mmu_shrink(), do a non-blocking
down_read_trylock().
Untested.
Index: kvm/arch/x86/kvm/mmu.c
===
---
It is not, since it also happens with -no-kvm-irqchip, that does not
exercise this path.
I looked into it today, will look further, but my current impression
is that hlt is working fine.
It might be the case that the problem lies in any kind of interrupt
injection that were supposed to wake
Sorry for the scrambled message. Here is the patch
diff --git a/arch/x86/kvm/x86_emulate.c b/arch/x86/kvm/x86_emulate.c
index dd4efe1..8643ee5 100644
--- a/arch/x86/kvm/x86_emulate.c
+++ b/arch/x86/kvm/x86_emulate.c
@@ -294,6 +294,7 @@ static u16 group2_table[] = {
/* EFLAGS bit definitions. */
Ben-Ami Yassour wrote:
Weidong,
I agree that supporting multiple devices is important, but I think
that supporting a single device is good enough for a first merge with
the main kvm tree. I suggest that we focus on merging with the main
tree and work on this in the background.
I agree
17 matches
Mail list logo