repository: C:/dev/kvm-guest-drivers-windows
branch: master
commit 4153629590c846862f095bbe3689df9e7fd70e06
Author: Yan Vugenfirer yvuge...@redhat.com
Date: Wed Nov 25 13:19:13 2009 +0200
[WIN-GUEST_DRIVERS]
viostor driver. some steps toward better performance on XP.
repository: C:/dev/kvm-guest-drivers-windows
branch: master
commit f148ef98de5cf2c53bfe6cb743bee7424c907397
Author: Yan Vugenfirer yvuge...@redhat.com
Date: Wed Nov 25 13:22:26 2009 +0200
[WIN-GUEST_DRIVERS] viostor driver. fix PREfast warnings.
Signed-off-by: Vadim
repository: C:/dev/kvm-guest-drivers-windows
branch: master
commit 3f938d806abf9aa3c8fe9e3dd825cdd6b5332301
Author: Yan Vugenfirer yvuge...@redhat.com
Date: Wed Nov 25 13:35:11 2009 +0200
[WIN-GUEST_DRIVERS]
viostor driver. small fix in startio routine (storport related path).
On Sat, Oct 31, 2009 at 3:37 AM, Lucas Meneghel Rodrigues
l...@redhat.com wrote:
Recently autoserv changed its default behavior of rsyncing
the whole client directory to the test machine, now it
will copy only the needed tests to the client machine.
Also, the way the tests are loaded when
On Wed, Nov 25, 2009 at 10:42:06AM +1030, Rusty Russell wrote:
On Tue, 24 Nov 2009 10:07:54 pm Michael S. Tsirkin wrote:
On Tue, Nov 24, 2009 at 08:54:23AM +1030, Rusty Russell wrote:
On Tue, 24 Nov 2009 02:37:01 am Shirley Ma wrote:
+ skb = (struct sk_buff *)buf;
This
On Wed, Nov 18, 2009 at 3:19 PM, Harald Dunkel harald.dun...@aixigo.de wrote:
Hi folks,
If I migrate a virtual machine (2.6.31.6, amd64) from a host with
AMD cpu to an Intel host, then the guest is terminated on the old
host as expected, but it gets stuck on the new host. Every 60 seconds
it
On 11/18/2009 11:49 AM, Harald Dunkel wrote:
Hi folks,
If I migrate a virtual machine (2.6.31.6, amd64) from a host with
AMD cpu to an Intel host, then the guest is terminated on the old
host as expected, but it gets stuck on the new host. Every 60 seconds
it prints a message on the virtual
On 11/19/2009 05:54 PM, Gleb Natapov wrote:
It's actually less readable. I know 11 is between 10 and 13, but is
NP_VECTOR between TS_VECTOR and GP_VECTOR?
This is better as a switch, or even:
u8 exception_class[] = {
[PF_VECTOR] EXPT_PF,
etc.
OK what about this then:
From: Eddie
On Wed, 25 Nov 2009 07:45:30 pm Michael S. Tsirkin wrote:
Hmm, is it really worth it to save a header copy if it's linear? We are
going to access it anyway, and it fits into one cacheline nicely. On
the other hand we have more code making life harder for compiler and
processor.
Not sure: I
- sudhir kumar smalik...@gmail.com wrote:
On Sat, Oct 31, 2009 at 3:37 AM, Lucas Meneghel Rodrigues
l...@redhat.com wrote:
Recently autoserv changed its default behavior of rsyncing
the whole client directory to the test machine, now it
will copy only the needed tests to the client
On Wed, Nov 25, 2009 at 08:50:21PM +1030, Rusty Russell wrote:
On Wed, 25 Nov 2009 07:45:30 pm Michael S. Tsirkin wrote:
Hmm, is it really worth it to save a header copy if it's linear? We are
going to access it anyway, and it fits into one cacheline nicely. On
the other hand we have more
On 11/23/2009 04:05 PM, Gleb Natapov wrote:
Signed-off-by: Gleb Natapovg...@redhat.com
---
arch/x86/include/asm/kvm_host.h |3 ++
arch/x86/include/asm/kvm_para.h |2 +
arch/x86/kvm/x86.c | 42 +-
include/linux/kvm.h |
On 11/23/2009 04:06 PM, Gleb Natapov wrote:
Asynchronous page fault notifies vcpu that page it is trying to access
is swapped out by a host. In response guest puts a task that caused the
fault to sleep until page is swapped in again. When missing page is
brought back into the memory guest is
On Tue, Nov 24, 2009 at 06:17:42PM +0800, Sheng Yang wrote:
Commit 6b5bbd04 qdev-ify device assignment forgot to put assigned devices
to devs list. So when IRQ routing changed in pci configure space, calling to
assigned_dev_update_irqs() won't update device guest IRQ, then assigned INTx
On Thu, Nov 19, 2009 at 05:54:07PM +0200, Gleb Natapov wrote:
It's actually less readable. I know 11 is between 10 and 13, but is
NP_VECTOR between TS_VECTOR and GP_VECTOR?
This is better as a switch, or even:
u8 exception_class[] = {
[PF_VECTOR] EXPT_PF,
etc.
OK what
On 11/23/2009 04:06 PM, Gleb Natapov wrote:
If guest access swapped out memory do not swap it in from vcpu thread
context. Setup slow work to do swapping and send async page fault to
a guest.
Allow async page fault injection only when guest is in user mode since
otherwise guest may be in
Bugs item #2902983, was opened at 2009-11-24 10:17
Message generated for change (Comment added) made by avik
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2902983group_id=180599
Please note that this message will contain a full copy of the comment
Michael Tokarev wrote:
I'm havin yet another fancy prob with time in guests.
It never happened before so far, but now it is like
this for quite some time.
Here's the result of hourly ntpdate invocation on one
of the guests, other guests shows very similar results:
Nov 25 06:17:09 isrv
This is a patch to have the guest virtio-blk driver get the value for the
maximum I/O size from the host bdrv, rather than assume that there is no
limit. Right now we use it for an in-house bdrv driver that needs this
option. The patches are below, against the latest gits, split into kernel
Bugs item #2902983, was opened at 2009-11-24 04:17
Message generated for change (Comment added) made by mtosatti
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2902983group_id=180599
Please note that this message will contain a full copy of the comment
Tejun Heo wrote:
Hello,
11/01/2009 08:31 PM, Avi Kivity wrote:
Here is the code in question:
3ae7: 75 05 jne
3aeevmx_vcpu_run+0x26a
3ae9: 0f 01 c2vmlaunch
3aec: eb 03 jmp
Hello,
11/26/2009 10:35 AM, Andrew Theurer wrote:
I just tried testing tip of kvm.git, but unfortunately I think I might
be hitting a different problem, where processes run 100% in kernel mode.
In my case, cpus 9 and 13 were stuck, running qemu processes. A stack
backtrace for both cpus are
Increase the sleeping time before the first check to 10 seconds,
and try every 2 seconds.
But increasing these values cannot really solve the following problem:
Guest is too heavy loaded, and have no time to response the
rebooting (method=shell) request, so session.is_responsive returns
- Chen Cao k...@redhat.com wrote:
Increase the sleeping time before the first check to 10 seconds,
and try every 2 seconds.
But increasing these values cannot really solve the following
problem:
Guest is too heavy loaded, and have no time to response the
rebooting
I think Kurt have a clear view on interrupt deliver routine.
Maybe when a outer physical interrupt yield durning the guest running
on cpu, this interrupt cause the guest exit
and eventually delived to the host to be disposed. Is that right ?
Thanks for everybody's reply.
On Tue, Nov 24, 2009 at
On Thu, Nov 26, 2009 at 02:08:23AM -0500, Michael Goldish wrote:
- Chen Cao k...@redhat.com wrote:
Increase the sleeping time before the first check to 10 seconds,
and try every 2 seconds.
But increasing these values cannot really solve the following
problem:
Guest is too
26 matches
Mail list logo
