Gleb Natapov wrote:
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
On 12/10/2009 03:17 AM, Sheng Yang wrote:
Yeah, I realize this later last night... Though it passed my testing
program.
Please post the test program as well... it's now easy to extend
kvm/user/test since it runs with qemu -kernel.
--
error compiling committee.c: too many arguments to
On 12/10/2009 11:33 AM, Avi Kivity wrote:
On 12/09/2009 07:46 PM, 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.
Thanks,
On Thu, Dec 10, 2009 at 07:16:04AM +0200, Muli Ben-Yehuda wrote:
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
On 10.12.2009, at 10:43, Michael S. Tsirkin wrote:
On Thu, Dec 10, 2009 at 07:16:04AM +0200, Muli Ben-Yehuda wrote:
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
On 10.12.2009, at 10:52, Alexander Graf wrote:
On 10.12.2009, at 10:43, Michael S. Tsirkin wrote:
On Thu, Dec 10, 2009 at 07:16:04AM +0200, Muli Ben-Yehuda wrote:
On Wed, Dec 09, 2009 at 06:38:54PM +0100, Alexander Graf wrote:
While trying to get device passthrough working with an
We just used vm.create() to create those cloned VMs whereas ignored catching
screendumps of them. This patch fix this problem.
Signed-off-by: Yolkfull Chow yz...@redhat.com
---
client/tests/kvm/tests/stress_boot.py |8 +++-
1 files changed, 3 insertions(+), 5 deletions(-)
diff --git
On Thu, Dec 10, 2009 at 10:35:41AM +0100, Alexander Graf wrote:
That's exactly what this patch does. It only allows access to the
region defined in the BAR.
Sorry, missed it!
Cheers,
Muli
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to
On Thu, Dec 10, 2009 at 10:52:46AM +0100, Alexander Graf wrote:
Either way, FWIW the device assignment stuff needs to be completely
rewritten for qemu upstream anyways. So while it's good to collect
ideas for now, let's not too put too much effort code-wise into the
current code (unless it
On Thu, Dec 10, 2009 at 11:08:58AM +0100, Alexander Graf wrote:
On 10.12.2009, at 10:52, Alexander Graf wrote:
On 10.12.2009, at 10:43, Michael S. Tsirkin wrote:
On Thu, Dec 10, 2009 at 07:16:04AM +0200, Muli Ben-Yehuda wrote:
On Wed, Dec 09, 2009 at 06:38:54PM +0100, Alexander
On 10.12.2009, at 11:23, Muli Ben-Yehuda wrote:
On Thu, Dec 10, 2009 at 10:52:46AM +0100, Alexander Graf wrote:
Either way, FWIW the device assignment stuff needs to be completely
rewritten for qemu upstream anyways. So while it's good to collect
ideas for now, let's not too put too much
On 10.12.2009, at 11:27, Michael S. Tsirkin wrote:
On Thu, Dec 10, 2009 at 11:08:58AM +0100, Alexander Graf wrote:
On 10.12.2009, at 10:52, Alexander Graf wrote:
On 10.12.2009, at 10:43, Michael S. Tsirkin wrote:
On Thu, Dec 10, 2009 at 07:16:04AM +0200, Muli Ben-Yehuda wrote:
On
On 12/09/2009 11:06 PM, Alexander Graf wrote:
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
On Thu, Dec 10, 2009 at 11:31:01AM +0100, Alexander Graf wrote:
What do you have in mind for such a rewrite?
I'd like to see it more well-abstracted and versatile. I don't see
an obvious reason why we shouldn't be able to use a physical device
in a TCG target :-).
mmio and pio are easy,
On Thu, Dec 10, 2009 at 11:31:54AM +0100, Alexander Graf wrote:
On 10.12.2009, at 11:27, Michael S. Tsirkin wrote:
On Thu, Dec 10, 2009 at 11:08:58AM +0100, Alexander Graf wrote:
On 10.12.2009, at 10:52, Alexander Graf wrote:
On 10.12.2009, at 10:43, Michael S. Tsirkin wrote:
On Thu, Dec 10, 2009 at 12:37:37PM +0200, Muli Ben-Yehuda wrote:
On Thu, Dec 10, 2009 at 11:31:01AM +0100, Alexander Graf wrote:
What do you have in mind for such a rewrite?
I'd like to see it more well-abstracted and versatile. I don't see
an obvious reason why we shouldn't be able
On Wed, Dec 09, 2009 at 06:21:38PM -0200, Marcelo Tosatti wrote:
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
On 10.12.2009, at 11:56, Michael S. Tsirkin wrote:
On Thu, Dec 10, 2009 at 12:37:37PM +0200, Muli Ben-Yehuda wrote:
On Thu, Dec 10, 2009 at 11:31:01AM +0100, Alexander Graf wrote:
What do you have in mind for such a rewrite?
I'd like to see it more well-abstracted and versatile. I don't
Eric Dumazet wrote:
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
On Thu, Dec 10, 2009 at 12:09:13PM +0100, Alexander Graf wrote:
On 10.12.2009, at 11:56, Michael S. Tsirkin wrote:
On Thu, Dec 10, 2009 at 12:37:37PM +0200, Muli Ben-Yehuda wrote:
On Thu, Dec 10, 2009 at 11:31:01AM +0100, Alexander Graf wrote:
What do you have in mind for such a
On Thu, Dec 10, 2009 at 12:56:56PM +0200, Michael S. Tsirkin wrote:
mmio and pio are easy, DMA you'd need an IOMMU for security, or
whatever uio does just for translation,
uio currently does not support DMA, but I plan to fix this
With or without an IOMMU?
and interrupts you probably
On Thu, Dec 10, 2009 at 12:34:38PM +0100, Alexander Graf wrote:
On 10.12.2009, at 12:28, Muli Ben-Yehuda wrote:
On Thu, Dec 10, 2009 at 12:56:56PM +0200, Michael S. Tsirkin wrote:
mmio and pio are easy, DMA you'd need an IOMMU for security, or
whatever uio does just for translation,
On Thu, Dec 10, 2009 at 01:21:40PM +0200, Michael S. Tsirkin wrote:
On Thu, Dec 10, 2009 at 12:09:13PM +0100, Alexander Graf wrote:
On 10.12.2009, at 11:56, Michael S. Tsirkin wrote:
On Thu, Dec 10, 2009 at 12:37:37PM +0200, Muli Ben-Yehuda wrote:
On Thu, Dec 10, 2009 at 11:31:01AM
On 10 déc. 2009, at 12:44, Daniel P. Berrange wrote:
On Thu, Dec 10, 2009 at 08:05:12AM +0100, Nikola Ciprich wrote:
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,
QEMU 0.12.0-rc1 does not support KVM
https://bugs.launchpad.net/bugs/494500
Boils down to the fact that 1) we don't include kernel headers in qemu (whereas
qemu-kvm does) and 2) kvm-kmod does not install those headers on make install.
I think we've discussed (2) as being the preferred
On 12/10/2009 03:07 PM, Anthony Liguori wrote:
QEMU 0.12.0-rc1 does not support KVM
https://bugs.launchpad.net/bugs/494500
Boils down to the fact that 1) we don't include kernel headers in qemu
(whereas qemu-kvm does) and 2) kvm-kmod does not install those headers
on make install.
I think
Anthony Liguori wrote:
QEMU 0.12.0-rc1 does not support KVM
https://bugs.launchpad.net/bugs/494500
Boils down to the fact that 1) we don't include kernel headers in qemu
(whereas qemu-kvm does) and 2) kvm-kmod does not install those headers
on make install.
I think we've discussed (2) as
Hi, I'm using redhat enterprise 5.4 with newest redhat kvm/qemu packages
installed for testing purposes.
I'm trying to install debian lenny from ISO on the machine with only
ssh access using virt-install python script and the output is like this
-
[r...@localhost ~]#
On 12/10/2009 04:50 PM, Arnd Bergmann wrote:
On Thursday 10 December 2009, Jan Kiszka wrote:
Anthony Liguori wrote:
QEMU 0.12.0-rc1 does not support KVM
https://bugs.launchpad.net/bugs/494500
Boils down to the fact that 1) we don't include kernel headers in qemu
(whereas qemu-kvm
Arnd Bergmann wrote:
On Thursday 10 December 2009, Jan Kiszka wrote:
Anthony Liguori wrote:
QEMU 0.12.0-rc1 does not support KVM
https://bugs.launchpad.net/bugs/494500
Boils down to the fact that 1) we don't include kernel headers in qemu
(whereas qemu-kvm does) and 2) kvm-kmod does not
On Thursday 10 December 2009, Avi Kivity wrote:
Maybe even /usr/local/include/kvm-kmod-$version/, and a symlink
/usr/local/include/kvm-kmod.
Depends on how fine-grained you want to do the packaging.
Most distributions split packages between code and development
packages. The kvm-kmod code
Bugs item #2912026, was opened at 2009-12-10 16:31
Message generated for change (Comment added) made by avik
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2912026group_id=180599
Please note that this message will contain a full copy of the comment
Arnd Bergmann wrote:
On Thursday 10 December 2009, Avi Kivity wrote:
Maybe even /usr/local/include/kvm-kmod-$version/, and a symlink
/usr/local/include/kvm-kmod.
Depends on how fine-grained you want to do the packaging.
Most distributions split packages between code and development
On 12/10/2009 06:42 PM, Jan Kiszka wrote:
I've just (forced-)pushed the simple version with
/usr/include/kvm-kmod as destination. The user headers are now stored
under usr/include in the kvm-kmod sources and installed from there.
It's customary to install to /usr/local, not to /usr (qemu
Avi Kivity wrote:
On 12/10/2009 06:42 PM, Jan Kiszka wrote:
I've just (forced-)pushed the simple version with
/usr/include/kvm-kmod as destination. The user headers are now stored
under usr/include in the kvm-kmod sources and installed from there.
It's customary to install to
Avi,
We have addressed all of the comments, please apply.
The following patches implement nested VMX support. The patches enable a guest
to use the VMX APIs in order to run its own nested guest (i.e., enable running
other
From: Orit Wasserman or...@il.ibm.com
---
arch/x86/kvm/svm.c |3 -
arch/x86/kvm/vmx.c | 265 +++-
arch/x86/kvm/x86.c | 11 ++-
arch/x86/kvm/x86.h |2 +
4 files changed, 274 insertions(+), 7 deletions(-)
diff --git a/arch/x86/kvm/svm.c
From: Orit Wasserman or...@il.ibm.com
---
arch/x86/kvm/vmx.c | 235 +++-
arch/x86/kvm/x86.c |5 +-
arch/x86/kvm/x86.h |3 +
3 files changed, 240 insertions(+), 3 deletions(-)
diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
index
From: Orit Wasserman or...@il.ibm.com
---
arch/x86/kvm/vmx.c | 292 ++--
arch/x86/kvm/x86.c |6 +-
arch/x86/kvm/x86.h |3 +
3 files changed, 289 insertions(+), 12 deletions(-)
diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
index
From: Orit Wasserman or...@il.ibm.com
---
arch/x86/kvm/vmx.c | 670 +++-
1 files changed, 660 insertions(+), 10 deletions(-)
diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
index 46a4f3a..8745d44 100644
--- a/arch/x86/kvm/vmx.c
+++
From: Orit Wasserman or...@il.ibm.com
---
arch/x86/kvm/vmx.c | 27 +--
1 files changed, 17 insertions(+), 10 deletions(-)
diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
index 8745d44..de1f596 100644
--- a/arch/x86/kvm/vmx.c
+++ b/arch/x86/kvm/vmx.c
@@ -1244,8
From: Orit Wasserman or...@il.ibm.com
---
arch/x86/kvm/vmx.c | 890 +++-
1 files changed, 873 insertions(+), 17 deletions(-)
diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
index de1f596..0d36b49 100644
--- a/arch/x86/kvm/vmx.c
+++
From: Orit Wasserman or...@il.ibm.com
---
arch/x86/kvm/vmx.c | 521 +++-
1 files changed, 515 insertions(+), 6 deletions(-)
diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
index 0d36b49..203f016 100644
--- a/arch/x86/kvm/vmx.c
+++
On Tue, Nov 24, 2009 at 08:08:37PM -0200, Marcelo Tosatti wrote:
On Sun, Nov 15, 2009 at 04:41:26PM +0100, Jan Kiszka wrote:
Avi Kivity wrote:
On 11/15/2009 05:02 PM, Jan Kiszka wrote:
Where should I add /* next version to use: 13 */, and who will take
care that this comment will
On Thursday 10 December 2009 17:14:40 Jan Kiszka wrote:
Avi Kivity wrote:
On 12/10/2009 06:42 PM, Jan Kiszka wrote:
I've just (forced-)pushed the simple version with
/usr/include/kvm-kmod as destination. The user headers are now stored
under usr/include in the kvm-kmod sources and
On 12/10/2009 10:26 PM, Arnd Bergmann wrote:
On Thursday 10 December 2009 17:14:40 Jan Kiszka wrote:
Avi Kivity wrote:
On 12/10/2009 06:42 PM, Jan Kiszka wrote:
I've just (forced-)pushed the simple version with
/usr/include/kvm-kmod as destination. The user headers are now
Hi all,
I'm currently running kvm-88 with a parallel port forwarding and Win XP as
guest. The Windows XP guest talks directly to the hardware registers of the
parallel port and tries to programm a piece of hardware over a proprietary
softwar tool. The hardware is connected via Parallel port
Avi Kivity wrote:
On 12/10/2009 04:50 PM, Arnd Bergmann wrote:
On Thursday 10 December 2009, Jan Kiszka wrote:
Anthony Liguori wrote:
QEMU 0.12.0-rc1 does not support KVM
https://bugs.launchpad.net/bugs/494500
Boils down to the fact that 1) we don't include kernel headers in qemu
Hi everyone, I'm new to the list and I have a couple questions that we
are wondering about here at work...
we have notice that the KVM processes on the host take much more memory
than the memory we have told the VM to use.. a ruff example..
if we tell KVM to use 2 gigs for one VM it will end up
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
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
Hello all.
As there's very little info about network performance in KVM on the web,
let's share your experience or findings about running KVM guests with
non-trivial network traffic (like iSCSI access, fileservers etc.).
- Do you enable KVM guests to directly use host's PCI network interface
52 matches
Mail list logo
