On 2011-03-01 13:58, Alon Levy wrote:
On Sun, Feb 27, 2011 at 08:11:26PM +0100, Jan Kiszka wrote:
On 2011-02-27 20:03, Alon Levy wrote:
On Sat, Feb 26, 2011 at 01:29:01PM +0100, Jan Kiszka wrote:
On 2011-02-26 12:43, xming wrote:
When trying to start X (and it loads qxl driver) the kvm
On Wed, Mar 02, 2011 at 03:26:53PM +0800, Sheng Yang wrote:
Change from v10:
1. Update according to the comments of Michael.
2. Use mmio_needed to exit to userspace according to Marcelo's comments.
PCI-wise, I don't see anything to complain about.
So ack the PCI bits.
You guys decide on the
On Tue, Mar 01, 2011 at 09:32:56PM +0530, Krishna Kumar2 wrote:
Michael S. Tsirkin m...@redhat.com wrote on 02/28/2011 03:13:20 PM:
Thank you once again for your feedback on both these patches.
I will send the qemu patch tomorrow. I will also send the next
version incorporating these
On Tue, Mar 01, 2011 at 09:34:35PM +0530, Krishna Kumar2 wrote:
Michael S. Tsirkin m...@redhat.com wrote on 02/28/2011 03:34:23 PM:
The number of vhost threads is = #txqs. Threads handle more
than one txq when #txqs is more than MAX_VHOST_THREADS (4).
It is this sharing that prevents
There are a lot of variables here. Are you using virtio-blk
devices and Windows guest drivers?
No, those measurements were taken when I was using IDE emulated drives. To
further clarify the NFS server is also software, not hardware, RAID-5.
But your subtle hint and IBMs Best practices
hi,all:
io_thread bt as the following:
#0 0x7f3086eaa034 in __lll_lock_wait () from /lib64/libpthread.so.0
#1 0x7f3086ea5345 in _L_lock_870 () from /lib64/libpthread.so.0
#2 0x7f3086ea5217 in pthread_mutex_lock () from /lib64/libpthread.so.0
#3 0x00436018 in kvm_mutex_lock
On 03/02/2011 07:30 AM, Jason Wang wrote:
Lucas Meneghel Rodrigues writes:
A method to verify guest kernel panics can be very
useful for a number of tests. Adapted from a function
present on virtio_console test, create VM.verify_kernel_crash()
and use it on unattended_install.
On Wed, Mar 02, 2011 at 09:22:35AM +0100, Jan Kiszka wrote:
On 2011-03-01 13:58, Alon Levy wrote:
On Sun, Feb 27, 2011 at 08:11:26PM +0100, Jan Kiszka wrote:
On 2011-02-27 20:03, Alon Levy wrote:
On Sat, Feb 26, 2011 at 01:29:01PM +0100, Jan Kiszka wrote:
On 2011-02-26 12:43, xming wrote:
On 03/02/2011 05:46 AM, Lucas Meneghel Rodrigues wrote:
A method to verify guest kernel panics can be very
useful for a number of tests. Adapted from a function
present on virtio_console test, create VM.verify_kernel_crash()
and use it on unattended_install.
Signed-off-by: Lucas Meneghel
On 2011-03-02 11:56, Alon Levy wrote:
On Wed, Mar 02, 2011 at 09:22:35AM +0100, Jan Kiszka wrote:
On 2011-03-01 13:58, Alon Levy wrote:
On Sun, Feb 27, 2011 at 08:11:26PM +0100, Jan Kiszka wrote:
On 2011-02-27 20:03, Alon Levy wrote:
On Sat, Feb 26, 2011 at 01:29:01PM +0100, Jan Kiszka wrote:
On Wed, Mar 02, 2011 at 12:34:24PM +0100, Jan Kiszka wrote:
On 2011-03-02 11:56, Alon Levy wrote:
On Wed, Mar 02, 2011 at 09:22:35AM +0100, Jan Kiszka wrote:
On 2011-03-01 13:58, Alon Levy wrote:
On Sun, Feb 27, 2011 at 08:11:26PM +0100, Jan Kiszka wrote:
On 2011-02-27 20:03, Alon Levy
On Wed, 2011-03-02 at 13:05 +0200, Michael Goldish wrote:
On 03/02/2011 05:46 AM, Lucas Meneghel Rodrigues wrote:
+def verify_kernel_crash(self, timeout=2):
+
+Find kernel crash message on serial console.
+
+@param timeout: Timeout used to verify expected
On 03/01/2011 08:20 PM, Alex Williamson wrote:
It seems like we need a good mixed workload benchmark. So far we've
only tested worst case, with a pure emulated I/O test, and best case,
with a pure memory test. Ordering an array only helps the latter, and
only barely beats the
On 03/01/2011 09:47 PM, Marcelo Tosatti wrote:
On Sun, Feb 27, 2011 at 11:54:29AM +0200, Avi Kivity wrote:
On 02/24/2011 07:35 PM, Alex Williamson wrote:
On Thu, 2011-02-24 at 12:06 +0200, Avi Kivity wrote:
On 02/23/2011 09:28 PM, Alex Williamson wrote:
I had forgotten about1M
On Wed, Mar 2, 2011 at 10:39 AM, ya su suya94...@gmail.com wrote:
io_thread bt as the following:
#0 0x7f3086eaa034 in __lll_lock_wait () from /lib64/libpthread.so.0
#1 0x7f3086ea5345 in _L_lock_870 () from /lib64/libpthread.so.0
#2 0x7f3086ea5217 in pthread_mutex_lock () from
On Wed, Mar 2, 2011 at 10:30 AM, Kevin Clark kevin.cl...@csoft.co.uk wrote:
The results are much better, with 64MB writes on the system drive coming in
at 39MB/s and reads 310MB/s. The second drive gives me 94MB/s for writes and
777MB/s for reads for a 64MB file. Again, that's wildy
On Sat, Feb 26, 2011 at 04:38:58PM +, Prasad Joshi wrote:
I pulled the latest qemu-kvm code and configured it with disabled-kvm
and related options. Configuration finishes well, but the compilation
fails.
prasad@prasad-kvm:~/KVM/qemu-kvm$ ./configure --disable-kvm
On Wed, Mar 02, 2011 at 11:23:14AM +0200, Michael S. Tsirkin wrote:
On Wed, Mar 02, 2011 at 03:26:53PM +0800, Sheng Yang wrote:
Change from v10:
1. Update according to the comments of Michael.
2. Use mmio_needed to exit to userspace according to Marcelo's comments.
PCI-wise, I don't see
On Tue, Mar 01, 2011 at 02:35:56PM +0200, Avi Kivity wrote:
On 02/28/2011 04:05 PM, Paolo Bonzini wrote:
On 02/28/2011 01:13 PM, Avi Kivity wrote:
If there's a git tree of this I'll be happy to do an autotest run.
Sure, it's branch iothread-win32 of git://github.com/bonzini/qemu.git
On 2011-03-02 19:43, Marcelo Tosatti wrote:
On Tue, Mar 01, 2011 at 02:35:56PM +0200, Avi Kivity wrote:
On 02/28/2011 04:05 PM, Paolo Bonzini wrote:
On 02/28/2011 01:13 PM, Avi Kivity wrote:
If there's a git tree of this I'll be happy to do an autotest run.
Sure, it's branch iothread-win32
On Wed, Mar 02, 2011 at 08:03:42PM +0100, Jan Kiszka wrote:
On 2011-03-02 19:43, Marcelo Tosatti wrote:
On Tue, Mar 01, 2011 at 02:35:56PM +0200, Avi Kivity wrote:
On 02/28/2011 04:05 PM, Paolo Bonzini wrote:
On 02/28/2011 01:13 PM, Avi Kivity wrote:
If there's a git tree of this I'll
On Wed, Mar 02, 2011 at 04:36:34PM -0300, Marcelo Tosatti wrote:
On Wed, Mar 02, 2011 at 08:03:42PM +0100, Jan Kiszka wrote:
On 2011-03-02 19:43, Marcelo Tosatti wrote:
On Tue, Mar 01, 2011 at 02:35:56PM +0200, Avi Kivity wrote:
On 02/28/2011 04:05 PM, Paolo Bonzini wrote:
On
On Wed, Mar 02, 2011 at 03:51:20PM -0300, Marcelo Tosatti wrote:
On Wed, Mar 02, 2011 at 11:23:14AM +0200, Michael S. Tsirkin wrote:
On Wed, Mar 02, 2011 at 03:26:53PM +0800, Sheng Yang wrote:
Change from v10:
1. Update according to the comments of Michael.
2. Use mmio_needed to exit
Clarify a comment in kvm/eventfd.c: we do
rcu_assign_pointer without explicit synchronize_rcu
afterwards, and the reason this works is because we
use a spinlock to synch against another place
which does call synchronize_rcu.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
diff --git
The behave is difference on RHEL6.0 and RHEL5.
On RHEL5, qxl and vag are two parameters. But on RHEL6, qxl
is one option in vga.
This patch could work on RHEL5 and RHEL6 hosts.
On RHEL6, if we set qxl and vga together in tests_base.cfg,
vga will be set to qxl, no matter what you set to vga.
(resend, sorry for the mess)
No worries. What mess?
I have two things you can try:
first is running a single VCPU guest, if you have not done so already.
Second is adding the bootparameter clocksource=acpi_pm to your guest
kernel.
If either of those fixes the problem, it very well
From 19d8130e2fabd8a36fc8183749efaf1c0fdcd225 Mon Sep 17 00:00:00 2001
From: Duan Jiong djduanji...@gmail.com
Date: Wed, 2 Mar 2011 17:18:57 +0800
Just remove useless function define kvm_inject_pit_timer_irqs() from
file arch/x86/kvm/i8254.h
Signed-off-by:Duan Jiongdjduanji...@gmail.com
---
格式好像有问题，你用的什么邮件客户端？你设置了80个字符自动换行？
把邮件保存了，在用git am能够打上去么？
改好了先重新发送一个给我。
发出来应该是这样的：
--
diff --git a/arch/x86/kvm/i8254.h b/arch/x86/kvm/i8254.h
index 46d08ca..9f3cea3 100644
--- a/arch/x86/kvm/i8254.h
+++ b/arch/x86/kvm/i8254.h
@@
I am sorry for mail to wrong address, please ignore this mail, thanks.
--snip--
...
From 19d8130e2fabd8a36fc8183749efaf1c0fdcd225 Mon Sep 17 00:00:00 2001
From: Duan Jiong djduanji...@gmail.com
Date: Wed, 2 Mar 2011 17:18:57 +0800
Just remove useless function define
No worries. What mess?
twice sending the same mail, nevermind :)
I have two things you can try:
first is running a single VCPU guest, if you have not done so already.
yup, UP guest is fine, just SMP doesn't work.
Second is adding the bootparameter clocksource=acpi_pm to your guest
From 19d8130e2fabd8a36fc8183749efaf1c0fdcd225 Mon Sep 17 00:00:00 2001
From: Duan Jiong djduanji...@gmail.com
Date: Wed, 2 Mar 2011 17:18:57 +0800
Just remove useless function define kvm_inject_pit_timer_irqs() from file
arch/x86/kvm/i8254.h
Signed-off-by:Duan Jiongdjduanji...@gmail.com
---
31 matches
Mail list logo
