Hi,
after upgrading from qemu-kvm-0.12.0-rc2 to qemu-kvm-0.12.1 I cannot
start my Windows 7 (64Bit) VM any more. I get the following error on
start-up:
rom: requested regions overlap (rom vapic.bin. free=0x0600,
addr=0x)
rom loading failed
I used to run it with this
On 12/21/2009 05:39 AM, Dustin Kirkland wrote:
What about the qemu-system-arm build break I also mentioned? That's
currently blocking my packaging.
I'm looking into it, though of course patches are welcome as usual.
--
error compiling committee.c: too many arguments to function
--
To
On 12/21/2009 09:22 AM, Gleb Natapov wrote:
Can you try kvm modules from latest kvm.git please? It looks like emulation of
push %ds fails and it was added after 2.6.32.
We shouldn't be emulating 'push %ds' at all. It's not used either for
mmio or for updating page tables. Something
Am Mon, 21 Dec 2009 09:14:13 +0100 schrieb Ingmar Schraub:
Hi,
after upgrading from qemu-kvm-0.12.0-rc2 to qemu-kvm-0.12.1 I cannot
start my Windows 7 (64Bit) VM any more. I get the following error on
start-up:
rom: requested regions overlap (rom vapic.bin. free=0x0600,
Thomas Mueller wrote:
Am Mon, 21 Dec 2009 09:14:13 +0100 schrieb Ingmar Schraub:
Hi,
after upgrading from qemu-kvm-0.12.0-rc2 to qemu-kvm-0.12.1 I cannot
start my Windows 7 (64Bit) VM any more. I get the following error on
start-up:
rom: requested regions overlap (rom vapic.bin.
On 12/21/2009 08:33 AM, Nikola Ciprich wrote:
Hi Alex,
well, I see, I based my rpm on latest fedora spec and it builds all
targets by default. But using just plain configure doesn't help either,
as others already reported in the meantime, seems like (default)
x86_64-softmmu target is broken as
On 12/20/2009 06:57 PM, Nikola Ciprich wrote:
Hi Avi,
I just tried compiling and the same problem I've reported minutes ago:
gcc -I/usr/src/redhat/BUILD/qemu-kvm-0.12.1/slirp -m64 -Wold-style-definition
-I. -I/usr/src/redhat/BUILD/qemu-kvm-0.12.1 -U_FORTIFY_SOURCE -D_GNU_SOURCE
Great!
when will you push it? I don't see it in git yet...
sorry to be so pushy, but I just can't wait to try new release :)
n.
On Mon, Dec 21, 2009 at 02:33:13PM +0200, Avi Kivity wrote:
On 12/20/2009 06:57 PM, Nikola Ciprich wrote:
Hi Avi,
I just tried compiling and the same problem I've
We're using a switch table to find the irqprio that belongs to a specific
interrupt vector. This table is part of the interrupt inject logic.
Since we'll add a new function to stop interrupts, let's move this table
out of the injection logic into a separate function.
Signed-off-by: Alexander
Because we now emulate the DEC interrupt according to real life behavior,
there's no need to keep the AGGRESSIVE_DEC hack around.
Let's just remove it.
Signed-off-by: Alexander Graf ag...@suse.de
---
arch/powerpc/kvm/book3s.c | 16 +---
1 files changed, 1 insertions(+), 15
We treated the DEC interrupt like an edge based one. This is not true for
Book3s. The DEC keeps firing until mtdec is issued again and thus clears
the interrupt line.
So let's implement this logic in KVM too. This patch moves the line clearing
from the firing of the interrupt to the mtdec
On 12/21/2009 04:16 PM, David S. Ahern wrote:
I still have not been able to capture a core, but I did get this from
stderr:
unhandled vm exit: 0x31 vcpu_id 3
This was fixed by 083e9e10dd9.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list:
We currently have an ugly hack called AGGRESSIVE_DEC that makes the Decrementor
either work well for PPC32 or PPC64 targets.
This patchset removes that hack, bringing the decrementor implementation closer
to real hardware.
Alexander Graf (3):
Move vector to irqprio resolving to separate
On 12/14/2009 09:04 AM, Luiz Capitulino wrote:
On Sat, 12 Dec 2009 11:09:38 -0700
David S. Ahern daah...@cisco.com wrote:
Thanks for the responses. I had forgotten that SIGABRT==abort() which
means I have to get the core file to get to the root cause. To date the
only information I have is
Avi Kivity 提到:
qemu-kvm-0.12.1 is now available. This release is is based on the
upstream qemu 0.12.1, plus kvm-specific enhancements. Please see the
original qemu 0.12.1 release announcement for details.
This release can be used with the kvm kernel modules provided by your
distribution
After upgrade to qemu-kvm-0.12.1 can not boot 64bit Windows XP. It work
fine with (qemu-kvm.git at 27-dec-2009) An error messages like this:
rom: requested regions overlap (rom vapic.bin. free=0x0600,
addr=0x)
rom loading failed
I can find vapic.bin in
On 12/21/2009 11:43 AM, Thomas Mueller wrote:
Am Mon, 21 Dec 2009 09:14:13 +0100 schrieb Ingmar Schraub:
Hi,
after upgrading from qemu-kvm-0.12.0-rc2 to qemu-kvm-0.12.1 I cannot
start my Windows 7 (64Bit) VM any more. I get the following error on
start-up:
rom: requested regions overlap
On 12/18/09 4:51 PM, Ingo Molnar wrote:
* Gregory Haskins gregory.hask...@gmail.com wrote:
Hi Linus,
Please pull AlacrityVM guest support for 2.6.33 from:
git://git.kernel.org/pub/scm/linux/kernel/git/ghaskins/alacrityvm/linux-2.6.git
for-linus
All of these patches have stewed in
Avi Kivity wrote:
On 12/21/2009 11:43 AM, Thomas Mueller wrote:
Am Mon, 21 Dec 2009 09:14:13 +0100 schrieb Ingmar Schraub:
Hi,
after upgrading from qemu-kvm-0.12.0-rc2 to qemu-kvm-0.12.1 I cannot
start my Windows 7 (64Bit) VM any more. I get the following error on
start-up:
rom:
On 12/21/2009 05:34 PM, Gregory Haskins wrote:
I think it would be fair to point out that these patches have been objected to
by the KVM folks quite extensively,
Actually, these patches have nothing to do with the KVM folks. You are
perhaps confusing this with the hypervisor-side
Thomas Mueller 提到:
After upgrade to qemu-kvm-0.12.1 can not boot 64bit Windows XP. It work
fine with (qemu-kvm.git at 27-dec-2009) An error messages like this:
rom: requested regions overlap (rom vapic.bin. free=0x0600,
addr=0x)
rom loading failed
I can find
On Sun, Dec 20, 2009 at 09:04:49PM +0200, Avi Kivity wrote:
Since VMX was not originally designed to be nested that wouldn't
surprise me.
vmx was designed to correct the non-virtualizability of x86. It
would have been criminal to design it without nesting in mind,
especially given all the
On 12/21/2009 05:52 PM, Muli Ben-Yehuda wrote:
I would say that VMX only supports nesting if you define supports as
does not make it impossible. The fact that VMX operations in
executed in non-root mode are trapped is welcome, but there's so much
more that could be done in hardware to make
On 12/21/09 10:43 AM, Avi Kivity wrote:
On 12/21/2009 05:34 PM, Gregory Haskins wrote:
I think it would be fair to point out that these patches have been
objected to
by the KVM folks quite extensively,
Actually, these patches have nothing to do with the KVM folks. You are
perhaps
On 12/21/2009 10:04 AM, Gregory Haskins wrote:
No, B and C definitely are, but A is lacking. And the performance
suffers as a result in my testing (vhost-net still throws a ton of exits
as its limited by virtio-pci and only adds about 1Gb/s to virtio-u, far
behind venet even with things like
You say this version.. is there a newer version with this patch already
apply to it?
Thanks
On 12/17/09 20:27 p.m., Herbert Xu wrote:
On Thu, Dec 17, 2009 at 01:15:46PM -0500, rek2 wrote:
I been told that today the network when down again and one of the guys
here had to log using the
On 12/21/2009 06:37 PM, Anthony Liguori wrote:
Since virtio-pci supports MSI-X, there should be no IO exits on
host-guest notification other than EOI in the virtual APIC. This is
a light weight exit today and will likely disappear entirely with
newer hardware.
I'm working on disappearing
On 12/21/09 11:37 AM, Anthony Liguori wrote:
On 12/21/2009 10:04 AM, Gregory Haskins wrote:
No, B and C definitely are, but A is lacking. And the performance
suffers as a result in my testing (vhost-net still throws a ton of exits
as its limited by virtio-pci and only adds about 1Gb/s to
I'm also having both of these problems (booting from virtio and
vgabios.bin). Debian 5, kernel 2.6.32 and qemu-kvm-0.12.1.
--
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
Dmitri Seletski wrote:
Hello folks.
My goal is to make my pci based network card work under windows
guest.(obviously using windows drivers)
this is device i am interested in:
01:07.0 Network controller: Atheros Communications Inc. AR5416
802.11abgn Wireless PCI Adapter (rev 01)
On 12/21/09 11:40 AM, Avi Kivity wrote:
On 12/21/2009 06:37 PM, Anthony Liguori wrote:
Since virtio-pci supports MSI-X, there should be no IO exits on
host-guest notification other than EOI in the virtual APIC. This is
a light weight exit today and will likely disappear entirely with
newer
On 12/21/2009 06:56 PM, Gregory Haskins wrote:
I'm working on disappearing EOI exits on older hardware as well. Same
idea as the old TPR patching, without most of the magic.
While I applaud any engineering effort that results in more optimal
execution, if you are talking about what we
On 12/21/2009 10:46 AM, Gregory Haskins wrote:
The very best you can hope to achieve is 1:1 EOI per signal (though
today virtio-pci is even worse than that). As I indicated above, I can
eliminate more than 50% of even the EOIs in trivial examples, and even
more as we scale up the number of
On 12/21/09 12:05 PM, Avi Kivity wrote:
On 12/21/2009 06:56 PM, Gregory Haskins wrote:
I'm working on disappearing EOI exits on older hardware as well. Same
idea as the old TPR patching, without most of the magic.
While I applaud any engineering effort that results in more optimal
On 12/21/09 12:20 PM, Anthony Liguori wrote:
On 12/21/2009 10:46 AM, Gregory Haskins wrote:
The very best you can hope to achieve is 1:1 EOI per signal (though
today virtio-pci is even worse than that). As I indicated above, I can
eliminate more than 50% of even the EOIs in trivial examples,
On Mon, Dec 21, 2009 at 6:22 AM, Alexander Graf ag...@suse.de wrote:
We treated the DEC interrupt like an edge based one. This is not true for
Book3s. The DEC keeps firing until mtdec is issued again and thus clears
the interrupt line.
That's not quite right. The decrementer keeps firing until
I am running Fedora Core 12 with a 2.6.31 kernel. I use the Intel 82576 SR-IOV
network card and want to assign its Virtual Functions (VFs) to separate KVM
guests. My guests also run Fedora Core 12 with a 2.6.31 kernel. I use the
latest igb driver in the host OS and load it with 2 VFs activated.
On Mon, Dec 21, 2009 at 10:13 AM, Hollis Blanchard
hol...@penguinppc.org wrote:
void kvmppc_emulate_dec(struct kvm_vcpu *vcpu)
{
unsigned long dec_nsec;
pr_debug(mtDEC: %x\n, vcpu-arch.dec);
#ifdef CONFIG_PPC64
/* POWER4+ triggers a dec interrupt if the value is 0
Hollis Blanchard wrote:
On Mon, Dec 21, 2009 at 6:22 AM, Alexander Graf ag...@suse.de wrote:
We treated the DEC interrupt like an edge based one. This is not true for
Book3s. The DEC keeps firing until mtdec is issued again and thus clears
the interrupt line.
That's not quite
Hollis Blanchard wrote:
On Mon, Dec 21, 2009 at 10:13 AM, Hollis Blanchard
hol...@penguinppc.org wrote:
void kvmppc_emulate_dec(struct kvm_vcpu *vcpu)
{
unsigned long dec_nsec;
pr_debug(mtDEC: %x\n, vcpu-arch.dec);
#ifdef CONFIG_PPC64
/* POWER4+ triggers a dec
For the record, we've discussed more by IRC, and I think revised
patches will be forthcoming.
-Hollis
--
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 http://vger.kernel.org/majordomo-info.html
* Fischer, Anna (anna.fisc...@hp.com) wrote:
I am running Fedora Core 12 with a 2.6.31 kernel. I use the Intel
82576 SR-IOV network card and want to assign its Virtual Functions (VFs)
to separate KVM guests. My guests also run Fedora Core 12 with a 2.6.31
kernel. I use the latest igb driver in
We're using a switch table to find the irqprio that belongs to a specific
interrupt vector. This table is part of the interrupt inject logic.
Since we'll add a new function to stop interrupts, let's move this table
out of the injection logic into a separate function.
Signed-off-by: Alexander
We treated the DEC interrupt like an edge based one. This is not true for
Book3s. The DEC keeps firing until mtdec is issued again and thus clears
the interrupt line.
So let's implement this logic in KVM too. This patch moves the line clearing
from the firing of the interrupt to the mtdec
Because we now emulate the DEC interrupt according to real life behavior,
there's no need to keep the AGGRESSIVE_DEC hack around.
Let's just remove it.
Signed-off-by: Alexander Graf ag...@suse.de
---
arch/powerpc/kvm/book3s.c | 16 +---
1 files changed, 1 insertions(+), 15
We currently have an ugly hack called AGGRESSIVE_DEC that makes the Decrementor
either work well for PPC32 or PPC64 targets.
This patchset removes that hack, bringing the decrementor implementation closer
to real hardware.
V1 - V2:
- make DEC clearing code on mtdec book3s specific
- rename
Subject: Re: pci-stub error and MSI-X for KVM guest
* Fischer, Anna (anna.fisc...@hp.com) wrote:
I am running Fedora Core 12 with a 2.6.31 kernel. I use the Intel
82576 SR-IOV network card and want to assign its Virtual Functions
(VFs)
to separate KVM guests. My guests also run Fedora
* Dmitri Seletski (drj...@gmail.com) wrote:
Dmitri Seletski wrote:
Hello folks.
My goal is to make my pci based network card work under windows
guest.(obviously using windows drivers)
this is device i am interested in:
01:07.0 Network controller: Atheros Communications Inc. AR5416
* Fischer, Anna (anna.fisc...@hp.com) wrote:
Subject: Re: pci-stub error and MSI-X for KVM guest
This works fine in principle and I can see the PCI device in the
guest under lspci. However, the 82576 VF driver requires the OS
to support MSI-X. My Fedora installation is configured with
Michael,
There is a 64-bit put_user(), so SET actually works already, but
there just isn't a 64-bit get_user().
It doesn't hurt to make them symmetric, though. The changes look
fine to me, if you want to do both.
I'm looking at adding mergeable rx buffer support and doing the
development
On Mon, Dec 21, 2009 at 09:22:52AM +0200, Gleb Natapov wrote:
I have personal interest in resolving RedHat's bz #508801, unfortunately
I cannot do that myself, so I wanted to ask on the list for help, but now
I'm confused where should I go.
Can you try kvm modules from latest kvm.git
On Mon, Dec 21, 2009 at 11:21 AM, Alexander Graf ag...@suse.de wrote:
We currently have an ugly hack called AGGRESSIVE_DEC that makes the
Decrementor
either work well for PPC32 or PPC64 targets.
This patchset removes that hack, bringing the decrementor implementation
closer
to real
On 12/21/2009 11:44 AM, Gregory Haskins wrote:
Well, surely something like SR-IOV is moving in that direction, no?
Not really, but that's a different discussion.
But let's focus on concrete data. For a given workload,
how many exits do you see due to EOI?
Its of course highly
Hi,
after upgrading from qemu-kvm-0.11.1 to 0.12.1 i get the following error
starting my kvm (guest is linux 2.6.32):
rom: requested regions overlap (rom linuxboot.bin.
free=0x2300, addr=0x)
rom loading failed
I have no -drive option and no -boot option, only -kernel
* Gregory Haskins gregory.hask...@gmail.com wrote:
On 12/18/09 4:51 PM, Ingo Molnar wrote:
* Gregory Haskins gregory.hask...@gmail.com wrote:
Hi Linus,
Please pull AlacrityVM guest support for 2.6.33 from:
We're using a switch table to find the irqprio that belongs to a specific
interrupt vector. This table is part of the interrupt inject logic.
Since we'll add a new function to stop interrupts, let's move this table
out of the injection logic into a separate function.
Signed-off-by: Alexander
Because we now emulate the DEC interrupt according to real life behavior,
there's no need to keep the AGGRESSIVE_DEC hack around.
Let's just remove it.
Signed-off-by: Alexander Graf ag...@suse.de
---
arch/powerpc/kvm/book3s.c | 16 +---
1 files changed, 1 insertions(+), 15
We currently have an ugly hack called AGGRESSIVE_DEC that makes the Decrementor
either work well for PPC32 or PPC64 targets.
This patchset removes that hack, bringing the decrementor implementation closer
to real hardware.
Alexander Graf (3):
Move vector to irqprio resolving to separate
On Mon, Dec 21, 2009 at 6:22 AM, Alexander Graf ag...@suse.de wrote:
We treated the DEC interrupt like an edge based one. This is not true for
Book3s. The DEC keeps firing until mtdec is issued again and thus clears
the interrupt line.
That's not quite right. The decrementer keeps firing until
On Mon, Dec 21, 2009 at 10:13 AM, Hollis Blanchard
hol...@penguinppc.org wrote:
void kvmppc_emulate_dec(struct kvm_vcpu *vcpu)
{
unsigned long dec_nsec;
pr_debug(mtDEC: %x\n, vcpu-arch.dec);
#ifdef CONFIG_PPC64
/* POWER4+ triggers a dec interrupt if the value is 0
Hollis Blanchard wrote:
On Mon, Dec 21, 2009 at 10:13 AM, Hollis Blanchard
hol...@penguinppc.org wrote:
void kvmppc_emulate_dec(struct kvm_vcpu *vcpu)
{
unsigned long dec_nsec;
pr_debug(mtDEC: %x\n, vcpu-arch.dec);
#ifdef CONFIG_PPC64
/* POWER4+ triggers a dec
61 matches
Mail list logo
