On Tuesday 25 September 2007, Rusty Russell wrote:
On Tue, 2007-09-25 at 00:18 +0200, Arnd Bergmann wrote:
This is a pattern I've seen a few times before, but could never understand
what it's good for. What is your reason for defining a new data structure
that is used only once, instead of
Anthony Liguori wrote:
I think you forgot to include the patch?
Regards,
Anthony Liguori
yes i forgot :)
here it is...
commit 3ed7059496e6e7d802dfb46e604d0af4abc2b040
Author: Izik Eidus [EMAIL PROTECTED]
Date: Mon Sep 24 13:35:12 2007 +0200
Remove the usage of the private field by
Ryan Harper wrote:
* Avi Kivity [EMAIL PROTECTED] [2007-09-24 02:57]:
Ryan Harper wrote:
I've run into a nasty bug while trying to install a Linux guest using
VMware Server inside a kvm guest (full dmesg attached and recreate
instructions below bug).
Can you reproduce
On Tue, 25 Sep 2007 09:37:38 +1000,
Rusty Russell [EMAIL PROTECTED] wrote:
On Tue, 2007-09-25 at 00:18 +0200, Arnd Bergmann wrote:
On Monday 24 September 2007, Rusty Russell wrote:
+
+struct virtio_bus {
+ struct bus_type bus;
+ struct device dev;
+};
+
+static struct
Yang, Sheng wrote:
These patches enable memory mapped TPR shadow (FlexPriority).
Since TPR is accessed very frequently by 32bit Windows, especially SMP
guest, with FlexPriority enabled, we saw significant performance gain.
The issue is: FlexPriority needs to add a memory slot to the vm to
On Tue, Sep 25, 2007 at 03:28:24AM +0200, andrzej zaborowski wrote:
Hi,
On 24/09/2007, Dan Kenigsberg [EMAIL PROTECTED] wrote:
As with previous Takes of this patch, its purpose is to expose host
+{
+asm(cpuid
+: =a (*ax),
+ =b (*bx),
+ =c (*cx),
+
We are using XP x64 Edition Version 2003 SP1 in the test case.
Thanks
Yunfeng
-Original Message-
From: Avi Kivity [mailto:[EMAIL PROTECTED]
Sent: 2007年9月25日 15:53
To: Zhao, Yunfeng
Cc: Laurent Vivier; kvm-devel@lists.sourceforge.net
Subject: Re: [kvm-devel] Test result for KVM, kernel
Dan Kenigsberg wrote:
On Tue, Sep 25, 2007 at 03:28:24AM +0200, andrzej zaborowski wrote:
Hi,
On 24/09/2007, Dan Kenigsberg [EMAIL PROTECTED] wrote:
As with previous Takes of this patch, its purpose is to expose host
+{
+asm(cpuid
+: =a (*ax),
+ =b (*bx),
+
Zhao, Yunfeng wrote:
We are using XP x64 Edition Version 2003 SP1 in the test case.
All my tests were 32-bit XP... that's probably the difference.
--
Do not meddle in the internals of kernels, for they are subtle and quick to
panic.
64bit 2003 has a similar issue but, it doesn’t happen very time.
Did you have problem to boot smp win2k?
smp win2k on 64bit host got a blue screen in today's testing.
I also found that booting 4 linux guests may cause host to hang.
I tried to repeat the test case of booting 4 linux guests many
On Tue, 2007-09-25 at 11:01 +0200, Avi Kivity wrote:
Dan Kenigsberg wrote:
On Tue, Sep 25, 2007 at 03:28:24AM +0200, andrzej zaborowski wrote:
Hi,
On 24/09/2007, Dan Kenigsberg [EMAIL PROTECTED] wrote:
As with previous Takes of this patch, its purpose is to expose host
+{
J. Mayer wrote:
On Tue, 2007-09-25 at 11:01 +0200, Avi Kivity wrote:
Dan Kenigsberg wrote:
On Tue, Sep 25, 2007 at 03:28:24AM +0200, andrzej zaborowski wrote:
Hi,
On 24/09/2007, Dan Kenigsberg [EMAIL PROTECTED] wrote:
As with previous Takes of this
On 9/25/07, Carlo Marcelo Arenas Belon [EMAIL PROTECTED] wrote:
diff --git a/scripts/qemu-ifup b/scripts/qemu-ifup
index 3bf8801..989fe9a 100755
--- a/scripts/qemu-ifup
+++ b/scripts/qemu-ifup
@@ -1,5 +1,18 @@
#!/bin/sh
-switch=$(/sbin/ip route list | awk '/^default / { print $NF }')
+if
On Tue, 2007-09-25 at 08:36 +0200, Arnd Bergmann wrote:
On Tuesday 25 September 2007, Rusty Russell wrote:
I don't mind: we could expose it.
What I mean with setting the parent appropriately is not to have a global
device that is used by the hv-specific probing code, but to make sure
that
On Tue, 2007-09-25 at 12:40 +0200, Avi Kivity wrote:
Avi Kivity wrote:
I've got a remark about this: why this has to be added to the Qemu
code ?
Imho, all is needed is an implementation of the -cpu option for
x86/x86_64 target. Then, an external tool (even a shell script)
J. Mayer wrote:
On Tue, 2007-09-25 at 12:40 +0200, Avi Kivity wrote:
Avi Kivity wrote:
I've got a remark about this: why this has to be added to the Qemu
code ?
Imho, all is needed is an implementation of the -cpu option for
x86/x86_64 target. Then, an
This patch modifies the management of REX prefix according behavior I saw in
Xen 3.1.
In Xen, this modification has been introduced by Jan Beulich.
http://lists.xensource.com/archives/html/xen-changelog/2007-01/msg00081.html
Signed-off-by: Laurent Vivier [EMAIL PROTECTED]
---
Avi Kivity wrote:
J. Mayer wrote:
On Tue, 2007-09-25 at 12:40 +0200, Avi Kivity wrote:
Avi Kivity wrote:
I've got a remark about this: why this has to be added to the Qemu
code ?
Imho, all is needed is an implementation of the -cpu option for
x86/x86_64 target.
Laurent Vivier wrote:
This patch modifies the management of REX prefix according behavior I saw in
Xen 3.1.
In Xen, this modification has been introduced by Jan Beulich.
Applied, thanks.
--
Any sufficiently difficult bug is indistinguishable from a feature.
On Tue, 2007-09-25 at 13:36 +0200, Avi Kivity wrote:
J. Mayer wrote:
On Tue, 2007-09-25 at 12:40 +0200, Avi Kivity wrote:
Avi Kivity wrote:
I've got a remark about this: why this has to be added to the Qemu
code ?
Imho, all is needed is an
Jocelyn Mayer wrote:
On Tue, 2007-09-25 at 13:36 +0200, Avi Kivity wrote:
J. Mayer wrote:
On Tue, 2007-09-25 at 12:40 +0200, Avi Kivity wrote:
Avi Kivity wrote:
I've got a remark about this: why this has to be
Paul Brook wrote:
Indeed for regular qemu this is useless. But it is useful for kqemu
(for which there is support in mainline qemu), and for kvm (which we
hope to merge one day).
And, as discussed before, it should be asking the hypervisor what features it
supports instead of trying
On Tue, Sep 25, 2007 at 03:07:44PM +0200, Jocelyn Mayer wrote:
So, running qemu without any parameters would use host capabilities if
kvm is available and the default qemu cpu if not. The -cpu option can
be used to override this if necessary.
Well, it may be needed to integrate the -cpu
Remove unused variable introduced by commit
5ed6627ee96f0a6802d99e71879d98610ba17e01
(I missed it, sorry)
Signed-off-by: Laurent Vivier [EMAIL PROTECTED]
---
drivers/kvm/x86_emulate.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/drivers/kvm/x86_emulate.c
Bugs item #1802082, was opened at 2007-09-25 09:44
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=1802082group_id=180599
Please note that this message will contain a full copy of
Rusty Russell wrote:
On Mon, 2007-09-24 at 15:44 +0200, Dor Laor wrote:
Rusty Russell wrote:
+irqreturn_t vring_interrupt(int irq, void *_vq)
+{
+ struct vring_virtqueue *vq = to_vvq(_vq);
+
+ pr_debug(virtqueue interrupt for %p\n, vq);
+
+ if
Bugs item #1802223, was opened at 2007-09-25 22:59
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=1802223group_id=180599
Please note that this message will contain a full copy of
Bugs item #1802227, was opened at 2007-09-25 23:07
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=1802227group_id=180599
Please note that this message will contain a full copy of
Hello,
Starting with kvm-40, I am not able to install a Win XP SP2 guest any more.
I consistently get a BSOD somewhere in the 2nd stage install.
Sometimes it is IRQL_NOT_LESS_OR_EQUAL, otherwise STOP: 0x008E
or STOP: 0x000A
In most failure cases I also get a kernel message:
emulation
Hello,
Similar (the same?) as in 2.6.23-rc6-mm1?
http://www.mail-archive.com/linux-kernel%40vger.kernel.org/msg208812.html
CC [M] drivers/kvm/ioapic.o
drivers/kvm/ioapic.c: In function 'ioapic_deliver':
drivers/kvm/ioapic.c:208: error: 'dest_LowestPrio' undeclared (first use
On Tue, 2007-09-25 at 19:15 +0200, Dor Laor wrote:
At the moment it's not good enough, there is a potential race were the
guest optimistically turn off
the VRING_AVAIL_F_NO_INTERRUPT in the vring_restart and afterwards
finds there are more_used so
it consume them in the poll function.
If in
-Original Message-
From: Avi Kivity [mailto:[EMAIL PROTECTED]
Sent: 2007年9月24日 21:24
To: He, Qing
Cc: kvm-devel
Subject: Re: [kvm-devel] [PATCH] KVM: x86_emulator: no writeback for bt
He, Qing wrote:
(p.s., this patch is before Laurent's patch of no_wb removal, the change
is minor to
32 matches
Mail list logo
