From: Avi Kivity a...@redhat.com
Signed-off-by: Avi Kivity a...@redhat.com
diff --git a/Makefile.target b/Makefile.target
index f89a9ec..68c0c94 100644
--- a/Makefile.target
+++ b/Makefile.target
@@ -599,7 +599,7 @@ endif
ifdef CONFIG_KVM_KERNEL_INC
CFLAGS += -I $(CONFIG_KVM_KERNEL_INC)
LIBS
From: Avi Kivity a...@redhat.com
This allows building with kvm without requiring updated headers from somewhere.
Signed-off-by: Avi Kivity a...@redhat.com
diff --git a/configure b/configure
index fe94f96..0638822 100755
--- a/configure
+++ b/configure
@@ -196,6 +196,9 @@ signalfd=no
eventfd=no
From: Avi Kivity a...@redhat.com
We already specify libkvm.a explicitly.
Signed-off-by: Avi Kivity a...@redhat.com
diff --git a/Makefile.target b/Makefile.target
index 09f71d4..0041a46 100644
--- a/Makefile.target
+++ b/Makefile.target
@@ -603,7 +603,6 @@ endif
ifdef CONFIG_KVM_KERNEL_INC
From: Avi Kivity a...@redhat.com
Signed-off-by: Avi Kivity a...@redhat.com
diff --git a/configure b/configure
index f46eff2..3d91a58 100755
--- a/configure
+++ b/configure
@@ -98,7 +98,7 @@ else
cpu=`uname -m`
fi
-target_list=
+target_list=x86_64-softmmu
case $cpu in
From: Avi Kivity a...@redhat.com
* commit 'master': (180 commits)
xen: add -vga xenfb option, configure xenfb (Gerd Hoffmann)
simplify vga selection (Gerd Hoffmann)
xen: pv domain builder. (Gerd Hoffmann)
xen: blk nic configuration via cmd line. (Gerd Hoffmann)
xen: add net backend
From: Avi Kivity a...@redhat.com
Signed-off-by: Avi Kivity a...@redhat.com
diff --git a/configure b/configure
index 3d91a58..7c92411 100755
--- a/configure
+++ b/configure
@@ -1790,7 +1790,7 @@ configure_kvm() {
\( $cpu = i386 -o $cpu = x86_64 -o $cpu = ia64 -o $cpu
= powerpc \);
From: Avi Kivity a...@redhat.com
Unbreaks vga text mode after switching from graphics mode.
Signed-off-by: Avi Kivity a...@redhat.com
diff --git a/qemu-kvm.c b/qemu-kvm.c
index c4a1bfc..68a9218 100644
--- a/qemu-kvm.c
+++ b/qemu-kvm.c
@@ -892,7 +892,7 @@ void
From: Avi Kivity a...@redhat.com
Signed-off-by: Avi Kivity a...@redhat.com
diff --git a/configure b/configure
index 454cb7b..f46eff2 100755
--- a/configure
+++ b/configure
@@ -504,6 +504,8 @@ if test $werror = yes ; then
CFLAGS=$CFLAGS -Werror
fi
+CFLAGS=$CFLAGS -I$(readlink -f kvm/libkvm)
+
On Wed, Apr 22, 2009 at 10:55:24PM +0800, alex wrote:
the code for credit scheduler
---
diff --git a/arch/x86/kvm/lapic.c b/arch/x86/kvm/lapic.c
index 4d76bb6..9e88ff0 100644
Memory aliases with different memory type is a problem for guest. For the guest
without assigned device, the memory type of guest memory would always been the
same as host(WB); but for the assigned device, some part of memory may be used
as DMA and then set to uncacheable memory type(UC/WC), which
Signed-off-by: Sheng Yang sh...@linux.intel.com
---
kernel/external-module-compat-comm.h | 13 +
kernel/external-module-compat.c |7 +++
2 files changed, 20 insertions(+), 0 deletions(-)
diff --git a/kernel/external-module-compat-comm.h
Hi,
I just tried to upgrade my kvm (from 79) to the new 85. I'm using qemu-kvm-
devel with the kvm-modules (and kernel-includes) that came with 2.6.29.1.
Qemu-blockdevices and virtio-net work well. But virtio blockdevices are not
accessible from within the guest system. Neither can the BIOS
Avi Kivity wrote:
Jan Kiszka wrote:
Huh, it is! Then the problem is a KVM-only thing: The kernel part hooks
onto those resources but doesn't communicate changes to this user space
backend.
In this case, the -no-kvm-pit option should help.
Probably fine in many cases (where the PIT is
Jan Kiszka wrote:
Avi Kivity wrote:
Jan Kiszka wrote:
Huh, it is! Then the problem is a KVM-only thing: The kernel part hooks
onto those resources but doesn't communicate changes to this user space
backend.
In this case, the -no-kvm-pit option should help.
Probably
Hello!
After an upgrade from kvm-84 to kvm-85 all my guests won't start because
no boot device could be found.
The kvm host is an 2xDual-Opteron 2212 with 8 GB RAM installed on debian
lenny 2.6.26-2-amd64.
All the guests are debian etch 2.6.26-1-amd64 or debian lenny
2.6.26-2-amd64 with 1 CPU
On Thu, Apr 23, 2009 at 2:15 PM, Gleb Natapov g...@redhat.com wrote:
On Wed, Apr 22, 2009 at 10:55:24PM +0800, alex wrote:
the code for credit scheduler
---
diff --git
I am re-organisming my code, so that it is a standalone module, only
requiring a few lines of changes to the standard KVM.
So that I can concentrate myself on functions like co-scheduling.
Please wait.
Regards,
alex.
On Thu, Apr 23, 2009 at 2:15 PM, Gleb Natapov g...@redhat.com wrote:
On Wed,
On Thu, Apr 23, 2009 at 07:34:46PM +0800, alex wrote:
On Thu, Apr 23, 2009 at 2:15 PM, Gleb Natapov g...@redhat.com wrote:
On Wed, Apr 22, 2009 at 10:55:24PM +0800, alex wrote:
the code for credit scheduler
Hi Darius,
After an upgrade from kvm-84 to kvm-85 all my guests won't start because
no boot device could be found.
[...]
A rollback to kvm-84 OR changing the hdd from vda to ide for the guests
and everything is OK again
I'm having the same problem and repored it to the list just some hours
Linus, please pull the following kvm fixes from repo and branch at:
git://git.kernel.org/pub/scm/virt/kvm/kvm.git kvm-updates/2.6.30
The only noteworthy fix is that a bug in kvm global page handling during
guest invlpg breaks the FreeBSD kernel, so we're dropping that optimization
until
After an upgrade from kvm-84 to kvm-85 all my guests won't start because
no boot device could be found.
[...]
A rollback to kvm-84 OR changing the hdd from vda to ide for the guests
and everything is OK again
I'm having the same problem and repored it to the list just some hours ago.
No
Hi Bernhard,
After an upgrade from kvm-84 to kvm-85 all my guests won't start because
no boot device could be found.
No problem here, my guests run fine with kvm-85 and 2.6.29.1:
-drive file=$IMG,format=raw,cache=none
Are you sure you are using a virtio blockdevice and not a regular
After an upgrade from kvm-84 to kvm-85 all my guests won't start because
no boot device could be found.
No problem here, my guests run fine with kvm-85 and 2.6.29.1:
-drive file=$IMG,format=raw,cache=none
Are you sure you are using a virtio blockdevice and not a regular ide one?
IIRC,
Hi Bernhard,
After an upgrade from kvm-84 to kvm-85 all my guests won't start
because no boot device could be found.
No problem here, my guests run fine with kvm-85 and 2.6.29.1:
-drive file=$IMG,format=raw,cache=none
This is the right example:
-drive
If a task switch caused by an event remove it from the event queue.
VMX already does that.
Signed-off-by: Gleb Natapov g...@redhat.com
diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c
index 44bb4f8..5134e0e 100644
--- a/arch/x86/kvm/svm.c
+++ b/arch/x86/kvm/svm.c
@@ -1800,6 +1800,10 @@
Please use this patch instead of previous one. The difference is that in
this one if fault happens during soft interrupt (int) or soft exceptions
(into, int3) the event is not re-injected since instruction will be
re-executed anyway.
Start to use interrupt/exception queues like VMX does.
This
(Applies to kvm.git b59cd3560111)
This series implements a mechanism called irqfd. It lets you create
an eventfd based file-desriptor to inject interrupts to the guest. We
associate one gsi per fd for proper routing granularity.
We do not have a user of this interface in this series, though
We will use this later in the series
Signed-off-by: Gregory Haskins ghask...@novell.com
---
fs/eventfd.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/fs/eventfd.c b/fs/eventfd.c
index 2a701d5..3f0e197 100644
--- a/fs/eventfd.c
+++ b/fs/eventfd.c
@@ -16,6 +16,7 @@
This allows synchronous notifications to register with the eventfd
infrastructure. Unlike traditional vfs based eventfd readers, notifiees
do not implictly clear the counter on reception. However, the clearing
is primarily important to allowing threads to block waiting for events
anyway, so its
This allows an eventfd to be registered as an irq source with a guest. Any
signaling operation on the eventfd (via userspace or kernel) will inject
the registered GSI at the next available window.
Signed-off-by: Gregory Haskins ghask...@novell.com
---
arch/x86/kvm/Makefile|2 -
(applies to kvm-userspace.git 84474e4f39)
This adds userspace support for the irqfd mechanism in the kernel, published
here:
http://lkml.org/lkml/2009/4/23/328
There are no current users, though the future virtual-bus v4 has plans to
adopt it.
Signed-off-by: Gregory Haskins ghask...@novell.com
Mark McLoughlin wrote:
If you do e.g. set_link virtio.0 down and there are packets
pending on the tap interface, we currently buffer a packet
and constantly try and send it until the link is up again.
We actually just want to drop the packet if the NIC is down.
Upstream qemu already does this,
On Thu, Apr 23, 2009 at 12:52 AM, Cameron Macdonell c...@cs.ualberta.ca wrote:
Hi Valdir,
Documentation is under development. I have some simple test programs that I
can supply when you get it up and running. As well as boot scripts to
create the /dev file.
Are you running the patched
After a lengthy testing phase, qemu-kvm.git has replaced
kvm-userspace.git as the source repository for kvm userspace development.
Differences from kvm-userspace.git are as follows:
- everything under qemu/ has been moved to the top-level directory
- everything not under qemu/ has been moved
Your problem is that index's are per interface type, so both of your drives
should be index=0 since they are different interface types.
On Thursday 23 April 2009 03:43:03 Gerd v. Egidy wrote:
Hi,
I just tried to upgrade my kvm (from 79) to the new 85. I'm using qemu-kvm-
devel with the
Brian Jackson wrote:
Your problem is that index's are per interface type, so both of your drives
should be index=0 since they are different interface types.
More specifically, with virtio-blk, you cannot have discontinuous
indexes. In other words, having index=0, index=1, index=2 is
On Thu, Apr 23, 2009 at 10:43:03AM +0200, Gerd v. Egidy wrote:
I am (or better libvirt is) starting the guest like this:
-drive file=/dev/VolGroup00/testboot,if=ide,index=0 \
-drive file=/dev/VolGroup00/testvirt,if=virtio,index=1 \
Both should have index=0 (or no index at all), since the
alex wrote:
the following patchs provide an extra control(besides the control of
Linux scheduler) over the execution of vcpu threads.
In this patch, Xen's credit
scheduler(http://wiki.xensource.com/xenwiki/CreditScheduler) is used.
User can use cat and
echo command to view and control a guest
On Thu, Apr 23, 2009 at 11:13:50AM -0500, Anthony Liguori wrote:
Brian Jackson wrote:
Your problem is that index's are per interface type, so both of your
drives should be index=0 since they are different interface types.
More specifically, with virtio-blk, you cannot have discontinuous
On Thu, 23 Apr 2009, Gregory Haskins wrote:
This allows synchronous notifications to register with the eventfd
infrastructure. Unlike traditional vfs based eventfd readers, notifiees
do not implictly clear the counter on reception. However, the clearing
is primarily important to allowing
subbu kl wrote:
Cam,
just a wild though about alternative approach.
Ideas are always good.
Once specific set of
address range of one guest is visible to other guest its just a matter
of DMA/single memcpy will transfer the data across.
My idea is to eliminate unnecessary copying. This
Davide Libenzi wrote:
On Thu, 23 Apr 2009, Gregory Haskins wrote:
This allows synchronous notifications to register with the eventfd
infrastructure. Unlike traditional vfs based eventfd readers, notifiees
do not implictly clear the counter on reception. However, the clearing
is
Hi Andreas,
I am (or better libvirt is) starting the guest like this:
-drive file=/dev/VolGroup00/testboot,if=ide,index=0 \
-drive file=/dev/VolGroup00/testvirt,if=virtio,index=1 \
Both should have index=0 (or no index at all), since the index is
internal to the driver.
sorry, I'm not
Valdir Stumm Junior wrote:
On Thu, Apr 23, 2009 at 12:52 AM, Cameron Macdonell c...@cs.ualberta.ca wrote:
Hi Valdir,
Documentation is under development. I have some simple test programs that I
can supply when you get it up and running. As well as boot scripts to
create the /dev file.
Are you
Jim Keniston wrote:
On Tue, 2009-04-21 at 20:17 -0400, Masami Hiramatsu wrote:
...
Hi Peter and Jim,
Now what I'm doing is making opcode tables like this.
Table: 1-byte opcode
Alias: none
00: ADD Eb,Gb
01: ADD Ev,Gv
02: ADD Gb,Eb
03: ADD Gv,Ev
04: ADD AL,Ib
05: ADD rAX,Iz
06: PUSH
Avi Kivity wrote:
After a lengthy testing phase, qemu-kvm.git has replaced
kvm-userspace.git as the source repository for kvm userspace development.
Differences from kvm-userspace.git are as follows:
- everything under qemu/ has been moved to the top-level directory
- everything not under qemu/
On Thu, Apr 23, 2009 at 06:57:45PM +0200, Gerd v. Egidy wrote:
sorry, I'm not getting that far to make this a problem. I just added the
second disk (the virtio one) to test if virtio is working when the guest is
running.
I first tried it with just one virtio disk and no ide ones: it
Avi Kivity wrote:
After a lengthy testing phase, qemu-kvm.git has replaced
kvm-userspace.git as the source repository for kvm userspace development.
Differences from kvm-userspace.git are as follows:
- everything under qemu/ has been moved to the top-level directory
- everything not under
Avi Kivity wrote:
Jan Kiszka wrote:
Avi Kivity wrote:
Jan Kiszka wrote:
Huh, it is! Then the problem is a KVM-only thing: The kernel part hooks
onto those resources but doesn't communicate changes to this user space
backend.
In this case, the -no-kvm-pit option should
Daniel P. Berrange wrote:
On Thu, Apr 23, 2009 at 11:13:50AM -0500, Anthony Liguori wrote:
Brian Jackson wrote:
Your problem is that index's are per interface type, so both of your
drives should be index=0 since they are different interface types.
More specifically, with
Hi
When updating to kernel 2.6.29.1, I'm unable to boot my Windows XP Pro 32bit
guest. The problem is consistent (actually on both of my laptops, with two
different WinXP guests) and it is fixed immediately when downgrading to kernel
2.6.28.8 or an older kernel version.
Scenario:
I'm booting
The in-kernel speaker emulation is only a dummy and also unneeded from
the performance point of view. Rather, it takes user space support to
generate sound output on the host, e.g. console beeps.
To allow this, introduce KVM_CREATE_PIT_NOSPKR which is simply
KVM_CREATE_PIT without registration of
When using the in-kernel PIT the speaker emulation has to synchronize
the PIT state with KVM. Enhance the existing speaker sound device and
allow it to take over port 0x61 by using KVM_CREATE_PIT_NOSPKR when
available. This unbreaks -soundhw pcspk in KVM mode.
Signed-off-by: Jan Kiszka
When updating to kernel 2.6.29.1, I'm unable to boot my Windows XP Pro 32bit
guest. The problem is consistent (actually on both of my laptops, with two
different WinXP guests) and it is fixed immediately when downgrading to
kernel 2.6.28.8 or an older kernel version.
Works for me with
On Thu, 23 Apr 2009, Gregory Haskins wrote:
Davide Libenzi wrote:
On Thu, 23 Apr 2009, Gregory Haskins wrote:
This allows synchronous notifications to register with the eventfd
infrastructure. Unlike traditional vfs based eventfd readers, notifiees
do not implictly clear the
Davide Libenzi wrote:
On Thu, 23 Apr 2009, Gregory Haskins wrote:
Davide Libenzi wrote:
On Thu, 23 Apr 2009, Gregory Haskins wrote:
This allows synchronous notifications to register with the eventfd
infrastructure. Unlike traditional vfs based eventfd readers,
On Thu, 2009-04-23 at 13:29 -0400, Masami Hiramatsu wrote:
...
Hmm, maybe, parser can handle (extra_info) as a solid keyword.
so let's define actual format.
opcode maps
Table: table-name
Referrer: escamed-name
opcode: mnemonic|Grp [operand1[,operand2...]] [(extra1)[,(extra2)...] [|
On Fri, Apr 24, 2009 at 12:18 AM, Andrew Theurer
haban...@linux.vnet.ibm.com wrote:
Just wondering, was it not possible to introduce a new scheduling class in
the current scheduler? My impression was that the current scheduler was
fairly modular and should allow this.
-Andrew
The reasons
刘志建 wrote:
Hello folks,
In the past, it was said KVM would like to treat the guest OS threads
differently in scheduling. However, till now, the qemu thread is regarded as a
conventional user thread. Therefore, it is hard to control how much CPU slices
one guest OS can utilize. I don't think a
On Thu, 23 Apr 2009, Gregory Haskins wrote:
Take a look at init_waitqueue_func_entry(), in particula at that func
parameter. Then look at how __wake_up_common() does its thing.
You don't need to be waiting for our wakeup system to work. Callbacks
works just fine, otherwise things like
-Original Message-
From: kvm-ppc-ow...@vger.kernel.org
[mailto:kvm-ppc-ow...@vger.kernel.org] On Behalf Of Avi Kivity
Sent: Thursday, April 23, 2009 11:40 PM
To: KVM list
Cc: Anthony Liguori; Hollis Blanchard; Zhang, Xiantao;
kvm-ppc; kvm-i...@vger.kernel.org; Carsten Otte
From: Anthony Liguori anthony at codemonkey.ws
By standard thread scheduling, I presume you mean scheduling that
doesn't take into account IO? That is, this paper is arguing that in a
virtualization environment, you want to provide temporary
disproportionate scheduling to favor IO bound
Jim Keniston wrote:
On Thu, 2009-04-23 at 13:29 -0400, Masami Hiramatsu wrote:
...
Hmm, maybe, parser can handle (extra_info) as a solid keyword.
so let's define actual format.
opcode maps
Table: table-name
Referrer: escamed-name
opcode: mnemonic|Grp [operand1[,operand2...]]
On Apr 23, 2009, at 9:19 PM, Anthony Liguori wrote:
刘志建 wrote:
Hello folks,
In the past, it was said KVM would like to treat the guest OS
threads differently in scheduling. However, till now, the qemu
thread is regarded as a conventional user thread. Therefore, it is
hard to control how
Davide Libenzi wrote:
On Thu, 23 Apr 2009, Gregory Haskins wrote:
Take a look at init_waitqueue_func_entry(), in particula at that func
parameter. Then look at how __wake_up_common() does its thing.
You don't need to be waiting for our wakeup system to work. Callbacks
works just fine,
(Applies to kvm.git b59cd3560111)
This series implements a mechanism called irqfd. It lets you create
an eventfd based file-desriptor to inject interrupts to the guest. We
associate one gsi per fd for proper routing granularity.
This is v2. Changes since v1
*) Dropped notifier_chain based
We will use this later in the series
Signed-off-by: Gregory Haskins ghask...@novell.com
---
fs/eventfd.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/fs/eventfd.c b/fs/eventfd.c
index 2a701d5..3f0e197 100644
--- a/fs/eventfd.c
+++ b/fs/eventfd.c
@@ -16,6 +16,7 @@
This allows an eventfd to be registered as an irq source with a guest. Any
signaling operation on the eventfd (via userspace or kernel) will inject
the registered GSI at the next available window.
Signed-off-by: Gregory Haskins ghask...@novell.com
---
arch/x86/kvm/Makefile|2 -
(applies to kvm-userspace.git 84474e4f39)
This adds userspace support for the irqfd mechanism in the kernel, published
here:
http://lkml.org/lkml/2009/4/24/6
This is v2. Changes since v1:
*) bug-fix to prevent returning 0 for success on allocation
-
There are no current
After a lengthy testing phase, qemu-kvm.git has replaced
kvm-userspace.git as the source repository for kvm userspace development.
Differences from kvm-userspace.git are as follows:
- everything under qemu/ has been moved to the top-level directory
- everything not under qemu/ has been moved
-Original Message-
From: kvm-ppc-ow...@vger.kernel.org
[mailto:kvm-ppc-ow...@vger.kernel.org] On Behalf Of Avi Kivity
Sent: Thursday, April 23, 2009 11:40 PM
To: KVM list
Cc: Anthony Liguori; Hollis Blanchard; Zhang, Xiantao;
kvm-ppc; kvm-i...@vger.kernel.org; Carsten Otte
71 matches
Mail list logo
