Before enabling, execution of rdtscp in guest would result in #UD.
Signed-off-by: Sheng Yang sh...@linux.intel.com
---
arch/x86/include/asm/vmx.h |1 +
arch/x86/kvm/vmx.c |3 ++-
2 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/arch/x86/include/asm/vmx.h
So you mean Sles11-ia64 will include it ?
Xiantao
-Original Message-
From: kvm-ia64-ow...@vger.kernel.org [mailto:kvm-ia64-ow...@vger.kernel.org] On
Behalf Of Alexander Graf
Sent: Wednesday, December 09, 2009 2:59 PM
To: Zhang, Xiantao
Cc: a...@redhat.com; kvm-i...@vger.kernel.org;
On 12/09/2009 11:11 AM, Sheng Yang wrote:
Before enabling, execution of rdtscp in guest would result in #UD.
Signed-off-by: Sheng Yangsh...@linux.intel.com
---
arch/x86/include/asm/vmx.h |1 +
arch/x86/kvm/vmx.c |3 ++-
2 files changed, 3 insertions(+), 1 deletions(-)
diff
No, I mean sles11-ia64 includes it already as 'Technology Preview'
and I either need to keep the update path open or drop it :).
Alex
Am 09.12.2009 um 10:50 schrieb Zhang, Xiantao
xiantao.zh...@intel.com:
So you mean Sles11-ia64 will include it ?
Xiantao
-Original Message-
On Mon, Dec 07, 2009 at 06:33:35PM +0100, Joanna Rutkowska wrote:
Avi Kivity wrote:
On 12/07/2009 07:15 PM, Joanna Rutkowska wrote:
But the difference is that in case of Xen one can *easily* move the
backends to small unprivileged VMs. In that case it doesn't matter the
code is in
I've been seeing lots of crashes on a new Dell Precision T7500,
running the KVM in Fedora 12. Finally managed to capture an Oops,
which is shown below (hand-transcribed):
BUG: unable to handle kernel paging request at 00200200
IP: [8139aab7] destroy_conntrack+0x82/0x11f
PGD
On 12/09/2009 03:46 PM, Adam Huffman wrote:
I've been seeing lots of crashes on a new Dell Precision T7500,
running the KVM in Fedora 12. Finally managed to capture an Oops,
which is shown below (hand-transcribed):
BUG: unable to handle kernel paging request at 00200200
IP:
While trying to get device passthrough working with an emulex hba, kvm
refused to pass it through because it has a BAR of 256 bytes:
Region 0: Memory at d210 (64-bit, non-prefetchable) [size=4K]
Region 2: Memory at d2101000 (64-bit, non-prefetchable) [size=256]
Region
Otherwise a zero apic base is loaded into KVM, which results
in interrupts being lost until a proper apic base with enabled
bit set is loaded.
Fixes WinXP migration in qemu-kvm origin/next.
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
diff --git a/hw/apic.c b/hw/apic.c
index
When using -pcidevice on a device that is already in use by a kernel driver
all the user gets is the following (very useful) information:
Failed to assign device 04:00.0 : Device or resource busy
Failed to deassign device 04:00.0 : Invalid argument
Error initializing device pci-assign
On Wed, Dec 09, 2009 at 07:04:13PM +0100, Alexander Graf wrote:
When using -pcidevice on a device that is already in use by a kernel driver
all the user gets is the following (very useful) information:
Failed to assign device 04:00.0 : Device or resource busy
Failed to deassign device
Marcelo Tosatti wrote:
Otherwise a zero apic base is loaded into KVM, which results
in interrupts being lost until a proper apic base with enabled
bit set is loaded.
Fixes WinXP migration in qemu-kvm origin/next.
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
diff --git
On Wed, Dec 09, 2009 at 03:46:54PM -0200, Marcelo Tosatti wrote:
Otherwise a zero apic base is loaded into KVM, which results
in interrupts being lost until a proper apic base with enabled
bit set is loaded.
Fixes WinXP migration in qemu-kvm origin/next.
Signed-off-by: Marcelo Tosatti
Glauber Costa wrote:
On Wed, Dec 09, 2009 at 03:46:54PM -0200, Marcelo Tosatti wrote:
Otherwise a zero apic base is loaded into KVM, which results
in interrupts being lost until a proper apic base with enabled
bit set is loaded.
Fixes WinXP migration in qemu-kvm origin/next.
Daniel P. Berrange wrote:
On Wed, Dec 09, 2009 at 07:04:13PM +0100, Alexander Graf wrote:
When using -pcidevice on a device that is already in use by a kernel driver
all the user gets is the following (very useful) information:
Failed to assign device 04:00.0 : Device or resource busy
On Wed, Dec 09, 2009 at 03:46:54PM -0200, Marcelo Tosatti wrote:
Otherwise a zero apic base is loaded into KVM, which results
in interrupts being lost until a proper apic base with enabled
bit set is loaded.
Fixes WinXP migration in qemu-kvm origin/next.
Signed-off-by: Marcelo Tosatti
On Wed, Dec 09, 2009 at 07:23:38PM +0100, Jan Kiszka wrote:
Marcelo Tosatti wrote:
Otherwise a zero apic base is loaded into KVM, which results
in interrupts being lost until a proper apic base with enabled
bit set is loaded.
Fixes WinXP migration in qemu-kvm origin/next.
On Wed, Dec 09, 2009 at 08:18:21PM +0100, Alexander Graf wrote:
Daniel P. Berrange wrote:
Unconditionally telling people to run rmmod is a pretty dangerous thing
todo. If they typod and gave the PCI addr of their disk controller instead
of the NIC, they'll be less than happy at the
Daniel P. Berrange wrote:
On Wed, Dec 09, 2009 at 08:18:21PM +0100, Alexander Graf wrote:
Daniel P. Berrange wrote:
Unconditionally telling people to run rmmod is a pretty dangerous thing
todo. If they typod and gave the PCI addr of their disk controller instead
of the NIC, they'll
Gleb Natapov wrote:
On Wed, Dec 09, 2009 at 07:23:38PM +0100, Jan Kiszka wrote:
Marcelo Tosatti wrote:
Otherwise a zero apic base is loaded into KVM, which results
in interrupts being lost until a proper apic base with enabled
bit set is loaded.
Fixes WinXP migration in qemu-kvm
When using -pcidevice on a device that is already in use by a kernel driver
all the user gets is the following (very useful) information:
Failed to assign device 04:00.0 : Device or resource busy
Failed to deassign device 04:00.0 : Invalid argument
Error initializing device pci-assign
On Wed, Dec 09, 2009 at 09:09:54PM +0100, Jan Kiszka wrote:
Gleb Natapov wrote:
On Wed, Dec 09, 2009 at 07:23:38PM +0100, Jan Kiszka wrote:
Marcelo Tosatti wrote:
Otherwise a zero apic base is loaded into KVM, which results
in interrupts being lost until a proper apic base with enabled
On Wed, Dec 09, 2009 at 04:25:45PM -0200, Glauber Costa wrote:
On Wed, Dec 09, 2009 at 03:46:54PM -0200, Marcelo Tosatti wrote:
Otherwise a zero apic base is loaded into KVM, which results
in interrupts being lost until a proper apic base with enabled
bit set is loaded.
Fixes WinXP
On Wed, Dec 09, 2009 at 08:44:06PM +0100, Alexander Graf wrote:
Daniel P. Berrange wrote:
On Wed, Dec 09, 2009 at 08:18:21PM +0100, Alexander Graf wrote:
Daniel P. Berrange wrote:
Unconditionally telling people to run rmmod is a pretty dangerous thing
todo. If they typod and
On Wed, Dec 09, 2009 at 07:23:38PM +0100, Jan Kiszka wrote:
Marcelo Tosatti wrote:
Otherwise a zero apic base is loaded into KVM, which results
in interrupts being lost until a proper apic base with enabled
bit set is loaded.
Fixes WinXP migration in qemu-kvm origin/next.
Daniel P. Berrange wrote:
On Wed, Dec 09, 2009 at 08:44:06PM +0100, Alexander Graf wrote:
Daniel P. Berrange wrote:
On Wed, Dec 09, 2009 at 08:18:21PM +0100, Alexander Graf wrote:
Daniel P. Berrange wrote:
Unconditionally telling people to run rmmod is a
On Wed, Dec 09, 2009 at 08:00:41PM +0100, Jan Kiszka wrote:
Glauber Costa wrote:
On Wed, Dec 09, 2009 at 03:46:54PM -0200, Marcelo Tosatti wrote:
Otherwise a zero apic base is loaded into KVM, which results
in interrupts being lost until a proper apic base with enabled
bit set is loaded.
On Wed, Dec 09, 2009 at 07:23:38PM +0100, Jan Kiszka wrote:
Marcelo Tosatti wrote:
Otherwise a zero apic base is loaded into KVM, which results
in interrupts being lost until a proper apic base with enabled
bit set is loaded.
Fixes WinXP migration in qemu-kvm origin/next.
Marcelo Tosatti wrote:
On Wed, Dec 09, 2009 at 09:09:54PM +0100, Jan Kiszka wrote:
Gleb Natapov wrote:
On Wed, Dec 09, 2009 at 07:23:38PM +0100, Jan Kiszka wrote:
Marcelo Tosatti wrote:
Otherwise a zero apic base is loaded into KVM, which results
in interrupts being lost until a proper apic
On Wed, Dec 09, 2009 at 09:20:49PM +0200, Gleb Natapov wrote:
On Wed, Dec 09, 2009 at 03:46:54PM -0200, Marcelo Tosatti wrote:
Otherwise a zero apic base is loaded into KVM, which results
in interrupts being lost until a proper apic base with enabled
bit set is loaded.
Fixes WinXP
On Wed, Dec 9, 2009 at 3:11 PM, Avi Kivity a...@redhat.com wrote:
On 12/09/2009 03:46 PM, Adam Huffman wrote:
I've been seeing lots of crashes on a new Dell Precision T7500,
running the KVM in Fedora 12. Finally managed to capture an Oops,
which is shown below (hand-transcribed):
BUG:
On Wed, Dec 09, 2009 at 09:09:54PM +0100, Jan Kiszka wrote:
Gleb Natapov wrote:
On Wed, Dec 09, 2009 at 07:23:38PM +0100, Jan Kiszka wrote:
Marcelo Tosatti wrote:
Otherwise a zero apic base is loaded into KVM, which results
in interrupts being lost until a proper apic base with enabled
On Wed, Dec 09, 2009 at 06:38:54PM +0100, Alexander Graf wrote:
While trying to get device passthrough working with an emulex hba, kvm
refused to pass it through because it has a BAR of 256 bytes:
Region 0: Memory at d210 (64-bit, non-prefetchable) [size=4K]
Region 2:
Hi,
Is there a good way to record KVM guest session into a video?
I tried the following approach; it worked with some issues, which are
making the solution unusable. I tried to capture the video (using
screen recorders like gtk-recmydesktop and VLC) while running VISTA
guest in full-screen. The
Le 09/12/2009 16:11, Avi Kivity a écrit :
On 12/09/2009 03:46 PM, Adam Huffman wrote:
I've been seeing lots of crashes on a new Dell Precision T7500,
running the KVM in Fedora 12. Finally managed to capture an Oops,
which is shown below (hand-transcribed):
BUG: unable to handle kernel
Gleb Natapov wrote:
On Wed, Dec 09, 2009 at 09:09:54PM +0100, Jan Kiszka wrote:
Gleb Natapov wrote:
On Wed, Dec 09, 2009 at 07:23:38PM +0100, Jan Kiszka wrote:
Marcelo Tosatti wrote:
Otherwise a zero apic base is loaded into KVM, which results
in interrupts being lost until a proper apic
Am 09.12.2009 um 21:49 schrieb Michael S. Tsirkin m...@redhat.com:
On Wed, Dec 09, 2009 at 06:38:54PM +0100, Alexander Graf wrote:
While trying to get device passthrough working with an emulex hba,
kvm
refused to pass it through because it has a BAR of 256 bytes:
Region 0: Memory at
Am 09.12.2009 um 21:54 schrieb Bhaskar Muppana mgvbhas...@gmail.com:
Hi,
Is there a good way to record KVM guest session into a video?
I tried the following approach; it worked with some issues, which are
making the solution unusable. I tried to capture the video (using
screen recorders like
When I try to build it recently I get the following:
Compiling - virtio_stor_hw_helper.c
1errors in directory c:\src\kvm-guest-drivers-windows\viostor
1c:\src\kvm-guest-drivers-windows\viostor\virtio_stor_hw_helper.c(99) : error
C2039: 'requests' : is not a member of '_ADAPTER_EXTENSION'
On Wednesday 09 December 2009 17:54:46 Avi Kivity wrote:
On 12/09/2009 11:11 AM, Sheng Yang wrote:
Before enabling, execution of rdtscp in guest would result in #UD.
Signed-off-by: Sheng Yangsh...@linux.intel.com
---
arch/x86/include/asm/vmx.h |1 +
arch/x86/kvm/vmx.c |
On Wed, Dec 09, 2009 at 06:38:54PM +0100, Alexander Graf wrote:
While trying to get device passthrough working with an emulex hba,
kvm refused to pass it through because it has a BAR of 256 bytes:
Region 0: Memory at d210 (64-bit, non-prefetchable) [size=4K]
Region 2:
On Wed, Dec 09, 2009 at 10:01:36PM +0100, Jan Kiszka wrote:
Gleb Natapov wrote:
On Wed, Dec 09, 2009 at 09:09:54PM +0100, Jan Kiszka wrote:
Gleb Natapov wrote:
On Wed, Dec 09, 2009 at 07:23:38PM +0100, Jan Kiszka wrote:
Marcelo Tosatti wrote:
Otherwise a zero apic base is loaded into
Hi,
I noticed that using libvirt to save running domain is terribly slow,
I mean it can take even 10 minutes to save VM with 2GB RAM, although
the host is almost idle (8CPU, 16GB RAM). If I understand correctly,
libvirt first pauses the vm and then migrates it to file (optionally through
gzip).
43 matches
Mail list logo
