2010/4/6 Gleb Natapov :
> On Tue, Apr 06, 2010 at 01:11:23PM +0900, Yoshiaki Tamura wrote:
>> Hi.
>>
>> When handle_io() is called, rip is currently proceeded *before* actually
>> having
>> I/O handled by qemu in userland. Upon implementing Kemari for
>> KVM(http://www.mail-archive.com/kvm@vger.k
On 04/01/2010 10:35 PM, Wenhao Xu wrote:
Does current qemu-kvm (qemu v0.12.3) use the irqchip, pit of KVM? I
cannot find any KVM_CREATE_IRQCHIP and KVM_CREATE_PIT in the qemu
code.
Are you looking at qemu or qemu-kvm?
Concerning the interface between qemu and kvm, I have the following co
On 03/31/2010 06:18 PM, Chris Wright wrote:
Hrm, I'm not sure these would be related to the small BAR region patch.
It looks more like a timing issue.
small BAR == slow path == timing issue?
Would be interesting to verify using perf with the 'kvm:kvm_mmio'
software event, see how
On 04/07/2010 01:31 AM, Richard Simpson wrote:
2.6.27 should be plenty fine for nx. Really the important bit is that
the host kernel has nx enabled. Can you check if that is so?
Umm, could you give me a clue about how to do that. It is some time
since I configured the host kernel, bu
Michael,
>> Qemu needs a userspace write, is that a synchronous one or
>>asynchronous one?
>It's a synchronous non-blocking write.
Sorry, why the Qemu live migration needs the device have a userspace write?
how does the write operation work? And why a read operation is not cared here?
Thanks
Xi
The Buildbot has detected a new failure of disable_kvm_x86_64_out_of_tree on
qemu-kvm.
Full details are available at:
http://buildbot.b1-systems.de/qemu-kvm/builders/disable_kvm_x86_64_out_of_tree/builds/285
Buildbot URL: http://buildbot.b1-systems.de/qemu-kvm/
Buildslave for this Build: b1_qe
The Buildbot has detected a new failure of disable_kvm_i386_out_of_tree on
qemu-kvm.
Full details are available at:
http://buildbot.b1-systems.de/qemu-kvm/builders/disable_kvm_i386_out_of_tree/builds/285
Buildbot URL: http://buildbot.b1-systems.de/qemu-kvm/
Buildslave for this Build: b1_qemu_k
The Buildbot has detected a new failure of disable_kvm_i386_debian_5_0 on
qemu-kvm.
Full details are available at:
http://buildbot.b1-systems.de/qemu-kvm/builders/disable_kvm_i386_debian_5_0/builds/337
Buildbot URL: http://buildbot.b1-systems.de/qemu-kvm/
Buildslave for this Build: b1_qemu_kvm
The Buildbot has detected a new failure of disable_kvm_x86_64_debian_5_0 on
qemu-kvm.
Full details are available at:
http://buildbot.b1-systems.de/qemu-kvm/builders/disable_kvm_x86_64_debian_5_0/builds/336
Buildbot URL: http://buildbot.b1-systems.de/qemu-kvm/
Buildslave for this Build: b1_qemu
As part of the performance testing effort for KVM,
introduce a base performance testset for the
sample KVM control file. It will execute several
benchmarks on a Fedora 12 guest, bringing back the
results to the host. This base testset can be tweaked
for folks interested on getting figures from a
pa
Michael,
> > For the write logging, do you have a function in hand that we can
> > recompute the log? If that, I think I can use it to recompute the
> > log info when the logging is suddenly enabled.
> > For the outstanding requests, do you mean all the user buffers have
> >
On Tue, 06 Apr 2010 09:35:09 +0800
Gui Jianfeng wrote:
> Hi all,
>
> I'm not sure whether it's appropriate to post the problem here.
> I played with "virsh" under Fedora 12, and started a KVM fedora12 guest
> by "virsh start" command. The fedora12 guest is successfully started.
> Than I run the
Hi All,
Here is the latest version of vhost-blk implementation.
Major difference from my previous implementation is that, I
now merge all contiguous requests (both read and write), before
submitting them. This significantly improved IO performance.
I am still collecting performance numbers, I will
Fix some typos found on the utility function that runs
autotest tests on a guest.
Signed-off-by: Lucas Meneghel Rodrigues
---
client/tests/kvm/kvm_test_utils.py |8
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/client/tests/kvm/kvm_test_utils.py
b/client/tests/kvm/
On 05/04/10 09:27, Avi Kivity wrote:
> On 04/03/2010 12:07 AM, Richard Simpson wrote:
>> Nope, both Kernels are 64 bit.
>>
>> uname -a Host: Linux gordon 2.6.27-gentoo-r8 #5 Sat Mar 14 18:01:59 GMT
>> 2009 x86_64 AMD Athlon(tm) 64 Processor 3200+ AuthenticAMD GNU/Linux
>>
>> uname -a Guest: Linux a
This patch adds support for the Mergeable Receive Buffers feature to
vhost_net.
+-DLS
Changes from previous revision:
1) renamed:
vhost_discard_vq_desc -> vhost_discard_desc
vhost_get_heads -> vhost_get_desc_n
vhost_get_vq_d
On Sun, Apr 04, 2010 at 07:30:20PM +0300, Avi Kivity wrote:
> On 04/04/2010 02:46 PM, Michael S. Tsirkin wrote:
> >On Wed, Mar 24, 2010 at 02:38:57PM +0200, Avi Kivity wrote:
> >>On 03/17/2010 03:04 PM, Michael S. Tsirkin wrote:
> >>>This is port of vhost v6 patch set I posted previously to qemu-kv
On Tue, Apr 06, 2010 at 12:38:00AM +0300, Avi Kivity wrote:
> On 04/05/2010 09:44 PM, Marcelo Tosatti wrote:
> >On Thu, Mar 25, 2010 at 05:02:56PM +0200, Avi Kivity wrote:
> >>Log emulated instructions in ftrace, especially if they failed.
> >Why not log all emulated instructions? Seems useful to m
On 04/05/2010 08:35 PM, Sridhar Samudrala wrote:
On Sun, 2010-04-04 at 14:14 +0300, Michael S. Tsirkin wrote:
On Fri, Apr 02, 2010 at 10:31:20AM -0700, Sridhar Samudrala wrote:
Make vhost scalable by creating a separate vhost thread per vhost
device. This provides better scaling acros
Management stack again
- qemud?
- external mgmt stack, qemu/kvm devs less inclined to care
- "Oh, you're using virsh, try #virt on OFTC"
- standard libvirt issues
- concern about speed of adopting kvm features
- complicated, XML hard to understand
- being slowed by hv agnositc
- ...
- b
Chris Wright wrote:
> Please send in any agenda items you are interested in covering.
>
Management stack discussion (again :))
Alex
--
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.kern
Hi,
I am interested in the "Shared memory transport between guest(s) and
host" project for GSoC 2010. The description of the project is pretty
straightforward, but I am a little bit lost on some parts:
1- Is there any documentation available on KVM shared memory
transport. This'd definitely help u
Thanks! I'll try a new kernel. Interestingly two guests with 2.6.32-r3
(Gentoo naming not rc3) with much more NFS traffic don't show
this behavior of 2.6.32-r5. So I'll try 2.6.32-r8. I've found
some threads with NFS and kernel 2.6.32.x related problems
which seems to be fixed in later versions.
-
Am Tue, 06 Apr 2010 14:15:10 +0200 schrieb kvm:
> Hi,
>
> running kernel 2.6.32 (kvm 0.12.3) in host and 2.6.30 in guest (using
> Gentoo) works fine. Now I've upgraded several guests to 2.6.32 too and
> have had no problems so far. But with one guest after 2-3 hours the
> guest hangs and I always
After is_rsvd_bits_set() checks, EFER.NXE must be enabled if NX bit is seted
Signed-off-by: Xiao Guangrong
---
arch/x86/kvm/paging_tmpl.h |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/x86/kvm/paging_tmpl.h b/arch/x86/kvm/paging_tmpl.h
index 067797a..d9dea28 10064
kvm_mmu_page.oos_link is not used, so remove it
Signed-off-by: Xiao Guangrong
---
arch/x86/include/asm/kvm_host.h |2 --
arch/x86/kvm/mmu.c |1 -
2 files changed, 0 insertions(+), 3 deletions(-)
diff --git a/arch/x86/include/asm/kvm_host.h b/arch/x86/include/asm/kvm_host.h
Hi,
running kernel 2.6.32 (kvm 0.12.3) in host
and 2.6.30 in guest (using Gentoo) works fine.
Now I've upgraded several guests to 2.6.32 too
and have had no problems so far. But with one
guest after 2-3 hours the guest hangs and I
always get a message like this:
[ 1392.030904] rpciod/0: page allo
On Tue, Apr 06, 2010 at 01:11:23PM +0900, Yoshiaki Tamura wrote:
> Hi.
>
> When handle_io() is called, rip is currently proceeded *before* actually
> having
> I/O handled by qemu in userland. Upon implementing Kemari for
> KVM(http://www.mail-archive.com/kvm@vger.kernel.org/msg25141.html) mainly
Avi Kivity wrote:
> On 02/18/2010 06:13 PM, Jan Kiszka wrote:
>> Instead of saving the old INT 0x13 and 0x19 handlers in ROM which fails
>> under QEMU as it enforces protection, keep them in spare vectors of the
>> interrupt table, namely INT 0x80 and 0x81.
>>
>>
>
> Applied both, thanks.
For
On Tue, Apr 06, 2010 at 01:46:56PM +0800, Xin, Xiaohui wrote:
> Michael,
> > >>> For the write logging, do you have a function in hand that we can
> > >>> recompute the log? If that, I think I can use it to recompute the
> > >>>log info when the logging is suddenly enabled.
> > >>> For the outstand
On Tue, Apr 06, 2010 at 01:41:37PM +0800, Xin, Xiaohui wrote:
> Michael,
> >>
> >>For the DOS issue, I'm not sure how much the limit get_user_pages()
> >> can pin is reasonable, should we compute the bindwidth to make it?
>
> >There's a ulimit for locked memory. Can we use this, decreasing
> >the
31 matches
Mail list logo
