, EventNotifier *n, int virq);
-
-#ifdef NEED_CPU_H
-#include qemu-kvm.h
-#endif
-
#endif
diff --git a/qemu-kvm.c b/qemu-kvm.c
deleted file mode 100644
index 3dc56ea..000
--- a/qemu-kvm.c
+++ /dev/null
@@ -1,37 +0,0 @@
-/*
- * qemu/kvm integration
- *
- * Copyright (C) 2006-2008 Qumranet Technologies
Hi all,
is there a summary existing that shows up the rough or actual differences
between qemu --enable-kvm and qemu-kvm? I tested both versions with the
same compile and start options, the CPU performance results are identical,
only the bootup time of my guest system with qemu-kvm seemed
On Sun, Apr 24, 2011 at 12:38 AM, Ryan Wang openspace.w...@gmail.com wrote:
I read some writings on the qemu, and found some demo examples use the
command qemu, some use kvm, and some mention the qemu-kvm?
I wonder are there any difference between these commands? Or they just
point
In common cases, guest SRAO MCE will cause corresponding poisoned page
be un-mapped and SIGBUS be sent to QEMU-KVM, then QEMU-KVM will relay
the MCE to guest OS.
But it is reported that if the poisoned page is accessed in guest
after un-mapped and before MCE is relayed to guest OS, QEMU-KVM
On 05/31/2010 09:28 AM, Huang Ying wrote:
In common cases, guest SRAO MCE will cause corresponding poisoned page
be un-mapped and SIGBUS be sent to QEMU-KVM, then QEMU-KVM will relay
the MCE to guest OS.
But it is reported that if the poisoned page is accessed in guest
after un-mapped
In common cases, guest SRAO MCE will cause corresponding poisoned page
be un-mapped and SIGBUS be sent to QEMU-KVM, then QEMU-KVM will relay
the MCE to guest OS.
But it is reported that if the poisoned page is accessed in guest
after un-mapped and before MCE is relayed to guest OS, QEMU-KVM
On Wed, May 12, 2010 at 02:44:03PM +0800, Huang Ying wrote:
In common cases, guest SRAO MCE will cause corresponding poisoned page
be un-mapped and SIGBUS be sent to QEMU-KVM, then QEMU-KVM will relay
the MCE to guest OS.
But it is reported that if the poisoned page is accessed in guest
).
They have different semantics and processed differently in QEMU-KVM and
guest OS.
For example the guest Linux kernel may ignore SRAO MCE (raised by
QEMU-KVM after receiving SRAO SIGBUS), because it is optional, but for
SRAR MCE (raised by QEMU-KVM after receiving SRAR SIGBUS) the guest
Linux kernel
In common cases, guest SRAO MCE will cause corresponding poisoned page
be un-mapped and SIGBUS be sent to QEMU-KVM, then QEMU-KVM will relay
the MCE to guest OS.
But it is reported that if the poisoned page is accessed in guest
after un-mapped and before MCE is relayed to guest OS, QEMU-KVM
On 04/28/2010 05:56 AM, Huang Ying wrote:
Just want to use the side effect of copy_from_user, SIGBUS will be sent
to current process because the page touched is marked as poisoned. That
is, failure is expected, so the return value is not checked.
What if the failure doesn't
On Wed, 2010-04-28 at 17:47 +0800, Avi Kivity wrote:
On 04/28/2010 05:56 AM, Huang Ying wrote:
Just want to use the side effect of copy_from_user, SIGBUS will be sent
to current process because the page touched is marked as poisoned. That
is, failure is expected, so the return value
On Tue, 2010-04-27 at 15:47 +0800, Avi Kivity wrote:
(please copy kvm@vger.kernel.org on kvm patches)
Sorry, will do that for all future patches.
On 04/27/2010 10:04 AM, Huang Ying wrote:
+static void kvm_send_hwpoison_signal(struct kvm *kvm, gfn_t gfn)
+{
+ char buf[1];
+ void
On 04/27/2010 12:25 PM, Huang Ying wrote:
On 04/27/2010 10:04 AM, Huang Ying wrote:
+static void kvm_send_hwpoison_signal(struct kvm *kvm, gfn_t gfn)
+{
+ char buf[1];
+ void __user *hva;
+ int r;
+
+ /* Touch the page, so send SIGBUS */
+ hva = (void
On Tue, 2010-04-27 at 17:30 +0800, Avi Kivity wrote:
On 04/27/2010 12:25 PM, Huang Ying wrote:
On 04/27/2010 10:04 AM, Huang Ying wrote:
+static void kvm_send_hwpoison_signal(struct kvm *kvm, gfn_t gfn)
+{
+ char buf[1];
+ void __user *hva;
+ int r;
+
+ /* Touch the
Lenny), I figured
getting the current source and building it myself would be the best
move. For other reasons I'm already running a 2.6.30 kernel from
Debian, which includes kernel side kvm. So I figure I only need to mess
with user space.
Right, stick with your kernel's kvm.ko, qemu-kvm
René Pfeiffer wrote:
On Oct 01, 2009 at 1902 +0200, Avi Kivity appeared and said:
[]
Right, stick with your kernel's kvm.ko, qemu-kvm-0.11.0 should make a
good fit.
Just to be sure: If I use Debian Lenny with a kernel from kernel.org,
then I can use the qemu-kvm packages and be fine. Right
and supporting userspace, you can
download the latest version from
http://sourceforge.net/project/showfiles.php?group_id=180599.;
That page shows the latest version is qemu-kvm-0.11.0.tar.gz.
The most recent kvm-release.tar.gz appears to be for kvm-88.
So which file should I start from
the latest version from
http://sourceforge.net/project/showfiles.php?group_id=180599.;
That page shows the latest version is qemu-kvm-0.11.0.tar.gz.
The most recent kvm-release.tar.gz appears to be for kvm-88.
So which file should I start from?
qemu-kvm is the userspace component, kvm-kmod
kernel modules and supporting userspace, you can
download the latest version from
http://sourceforge.net/project/showfiles.php?group_id=180599.;
That page shows the latest version is qemu-kvm-0.11.0.tar.gz.
The most recent kvm-release.tar.gz appears to be for kvm-88.
So which file should
On 10/01/2009 06:51 PM, Ross Boylan wrote:
So which file should I start from?
qemu-kvm is the userspace component, kvm-kmod is the kernel component as
an external module. 'kvm' is a package containing both.
That helps a lot; maybe that info could go up on the bugs or faq page
Avi Kivity wrote:
On 10/01/2009 08:06 PM, Jim Paris wrote:
That's what I do. Just as a warning, if you're using the libvirt
packages from Debian unstable, make sure you also install
linux-libc-dev from unstable before building qemu-kvm.
Otherwise, virtio networking will fail. The reason
://sourceforge.net/project/showfiles.php?group_id=180599.;
That page shows the latest version is qemu-kvm-0.11.0.tar.gz.
The most recent kvm-release.tar.gz appears to be for kvm-88.
So which file should I start from?
If you don't know what you want, you want qemu-kvm, which is based off a
stable
/project/showfiles.php?group_id=180599.;
That page shows the latest version is qemu-kvm-0.11.0.tar.gz.
The most recent kvm-release.tar.gz appears to be for kvm-88.
So which file should I start from?
Thanks.
Ross Boylan
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body
An ioeventfd allows an eventfd to attach to a specific PIO/MMIO region in the
guest. Any guest-writes to that region will trigger an eventfd signal.
Signed-off-by: Gregory Haskins ghask...@novell.com
---
libkvm-all.h | 44 +
qemu-kvm.c | 69
24 matches
Mail list logo
