> -Original Message-
> From: kvm-ow...@vger.kernel.org [mailto:kvm-ow...@vger.kernel.org]
> On Behalf Of Xiao Guangrong
> Sent: Monday, August 19, 2013 4:18 PM
> To: Zhou, Chao
> Cc: kvm@vger.kernel.org
> Subject: Re: KVM Test report, kernel 205befd9... qemu ca916d37...
>
> On 08/19/2013 0
> -Original Message-
> From: Paolo Bonzini [mailto:pbonz...@redhat.com]
> Sent: Thursday, August 08, 2013 8:24 PM
> To: Ren, Yongjie
> Cc: Arthur Chunqi Li; Gleb Natapov; kvm@vger.kernel.org
> Subject: Re: KVM Test report, kernel bf640876... qemu 0779caeb...
>
> &
> -Original Message-
> From: Arthur Chunqi Li [mailto:yzt...@gmail.com]
> Sent: Monday, August 05, 2013 12:21 PM
> To: Gleb Natapov
> Cc: Ren, Yongjie; kvm@vger.kernel.org; pbonz...@redhat.com
> Subject: Re: KVM Test report, kernel bf640876... qemu 0779caeb...
>
>
> -Original Message-
> From: Gleb Natapov [mailto:g...@redhat.com]
> Sent: Sunday, August 04, 2013 8:08 PM
> To: kvm@vger.kernel.org
> Cc: Ren, Yongjie; pbonz...@redhat.com; yzt...@gmail.com
> Subject: [PATCH] KVM: nVMX: correctly set tr base on nested vmexit
> emulat
Hi All,
This is KVM upstream test result against kvm.git next branch and qemu-kvm.git
uq/master branch.
kvm.git next branch: bf640876e21fe603f7f52b0c27d66b7716da0384 based
on kernel 3.11.0-rc1
qemu-kvm.git uq/master branch: 0779caeb1a17f4d3ed14e2925b36ba09b084fb7b
We found tw
x86-run: replace the deprecated 'fgrep' with 'grep -F'.
Signed-off-by: Yongjie Ren
---
x86-run |8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/x86-run b/x86-run
index 6093a72..14ff331 100755
--- a/x86-run
+++ b/x86-run
@@ -3,12 +3,12 @@
qemukvm="${QEMU:-qemu-kvm}"
x86-run: keep constant coding style for the 'if' statement
Signed-off-by: Yongjie Ren
---
x86-run |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/x86-run b/x86-run
index daefd4a..6093a72 100755
--- a/x86-run
+++ b/x86-run
@@ -17,7 +17,8 @@ else
fi
fi
-if ${qem
'bash' should be always located in /bin/bash instead of /usr/bin/bash.
Other bash scripts in kvm-unit-tests also use '/bin/bash' as the interpreter.
Signed-off-by: Yongjie Ren
---
x86-run |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/x86-run b/x86-run
index 9526a0b..daef
x86-run: correct a typo 'qemsystem' -> 'qemusystem'
Before this fix, you should always get error info as below when running
'x86-run' script.
"QEMU binary has no support for test device. Exiting."
Signed-off-by: Yongjie Ren
---
x86-run |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
d
> -Original Message-
> From: kvm-ow...@vger.kernel.org [mailto:kvm-ow...@vger.kernel.org]
> On Behalf Of Gleb Natapov
> Sent: Monday, June 24, 2013 4:03 PM
> To: Ren, Yongjie
> Cc: kvm@vger.kernel.org; pbonz...@redhat.com
> Subject: Re: [PATCH kvm-unit-tests 1/3] x8
'bash' should be always located in /bin/bash instead of /usr/bin/bash.
Other bash scripts in kvm-unit-tests also use '/bin/bash' as the interpreter.
Signed-off-by: Yongjie Ren
---
x86-run |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/x86-run b/x86-run
index 9526a0b..daef
x86-run: keep constant coding style for the 'if' statement
Signed-off-by: Yongjie Ren
---
x86-run |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/x86-run b/x86-run
index daefd4a..6093a72 100755
--- a/x86-run
+++ b/x86-run
@@ -17,7 +17,8 @@ else
fi
fi
-if ${qemu
x86-run: correct a typo 'qemsystem' -> 'qemusystem'
Before this fix, you should always get error info as below when running
'x86-run' script.
"QEMU binary has no support for test device. Exiting."
Signed-off-by: Yongjie Ren
---
x86-run |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
d
Hi All,
This is KVM upstream test result against kvm.git next branch and qemu-kvm.git
uq/master branch.
kvm.git next branch: e47a5f5fb715b90b40747e9e235de557c6abd56c based
on kernel 3.10.0-rc1
qemu-kvm.git uq/master branch: 58fcb1ed2bdeb8565a14e7e516a21bd4e6fdb2c7
We found no
> -Original Message-
> From: kvm-ow...@vger.kernel.org [mailto:kvm-ow...@vger.kernel.org]
> On Behalf Of an...@ssl.serc.iisc.in
> Sent: Thursday, June 13, 2013 9:18 PM
> To: kvm@vger.kernel.org
> Subject: Bottleneck in KVM
>
> Hello All
>
> I am relatively new to kvm.
> I have installed a
> -Original Message-
> From: Gleb Natapov [mailto:g...@redhat.com]
> Sent: Thursday, June 06, 2013 4:54 PM
> To: Jan Kiszka
> Cc: kvm@vger.kernel.org; Ren, Yongjie
> Subject: Regression after "Remove support for reporting coalesced APIC
> IRQs"
>
@vger.kernel.org [mailto:kvm-ow...@vger.kernel.org]
> On Behalf Of Ren, Yongjie
> Sent: Wednesday, May 29, 2013 4:13 PM
> To: kvm@vger.kernel.org
> Subject: KVM Test report, kernel e47a5f5f... qemu b5803aa3...
>
> Hi All,
>
> This is KVM upstream test result against
> -Original Message-
> From: Paolo Bonzini [mailto:paolo.bonz...@gmail.com] On Behalf Of Paolo
> Bonzini
> Sent: Thursday, May 30, 2013 5:27 AM
> To: Ren, Yongjie
> Cc: kvm@vger.kernel.org
> Subject: Re: KVM Test report, kernel e47a5f5f... qemu b5803aa3...
>
&g
Hi All,
This is KVM upstream test result against kvm.git next branch and qemu-kvm.git
uq/master branch.
kvm.git next branch: e47a5f5fb715b90b40747e9e235de557c6abd56c based on
kernel 3.10.0-rc1
qemu-kvm.git uq/master branch: b5803aa3583e82e5133f7621121bc15ee694f4a1
We found 5 n
> -Original Message-
> From: kvm-ow...@vger.kernel.org [mailto:kvm-ow...@vger.kernel.org]
> On Behalf Of Alex Palesandro
> Sent: Tuesday, May 14, 2013 10:51 PM
> To: kvm@vger.kernel.org
> Subject: Fwd: Xen as L1 support
>
> Hi,
> I'm new to KVM. I'm doing some test on nested Virtualization
> -Original Message-
> From: Kashyap Chamarthy [mailto:kashyap...@gmail.com]
> Sent: Monday, May 13, 2013 3:07 PM
> To: Ren, Yongjie
> Cc: kvm@vger.kernel.org
> Subject: Re: [nVMX Test] Build kernel (defconfig) on L2, w/ VMCS
> Shadowing enabled on L0
>
> On Mo
> -Original Message-
> From: kvm-ow...@vger.kernel.org [mailto:kvm-ow...@vger.kernel.org]
> On Behalf Of Gleb Natapov
> Sent: Monday, May 13, 2013 2:39 PM
> To: Jan Kiszka
> Cc: Kashyap Chamarthy; Abel Gordon; Nakajima, Jun;
> kvm@vger.kernel.org; kvm-ow...@vger.kernel.org
> Subject: Re: [n
> -Original Message-
> From: kvm-ow...@vger.kernel.org [mailto:kvm-ow...@vger.kernel.org]
> On Behalf Of Kashyap Chamarthy
> Sent: Monday, May 13, 2013 12:59 PM
> To: kvm@vger.kernel.org
> Subject: [nVMX Test] Build kernel (defconfig) on L2, w/ VMCS Shadowing
> enabled on L0
>
> I should p
> -Original Message-
> From: kvm-ow...@vger.kernel.org [mailto:kvm-ow...@vger.kernel.org]
> On Behalf Of Gleb Natapov
> Sent: Sunday, April 28, 2013 10:34 PM
> To: Ren, Yongjie
> Cc: Jan Kiszka; Marcelo Tosatti; kvm; Nakajima, Jun
> Subject: Re: [PATCH] KVM: nVMX:
> -Original Message-
> From: kvm-ow...@vger.kernel.org [mailto:kvm-ow...@vger.kernel.org]
> On Behalf Of Jan Kiszka
> Sent: Sunday, April 28, 2013 3:25 PM
> To: Gleb Natapov; Marcelo Tosatti
> Cc: kvm; Nakajima, Jun; Ren, Yongjie
> Subject: [PATCH] KVM: nVMX: Skip
CCed Jan Kiszka.
I did some bisection and found the following commit introduced this bug.
The bug still exists in the latest kvm.git next branch.
commit 5f3d5799974b89100268ba813cec8db7bd0693fb
Author: Jan Kiszka
Date: Sun Apr 14 12:12:46 2013 +0200
KVM: nVMX: Rework event injection and re
> -Original Message-
> From: Shah, Ashish N
> Sent: Wednesday, April 24, 2013 4:31 AM
> To: Rose, Gregory V; Ren, Yongjie; e1000-de...@lists.sourceforge.net;
> kvm@vger.kernel.org
> Subject: RE: [E1000-devel] [Bug 56981] New: [SR-IOV] Intel I350 NIC VF
> cannot work in
Added e1000-devel list to see whether this's a known issue.
Best Regards,
Yongjie (Jay)
> -Original Message-
> From: kvm-ow...@vger.kernel.org [mailto:kvm-ow...@vger.kernel.org]
> On Behalf Of bugzilla-dae...@bugzilla.kernel.org
> Sent: Monday, April 22, 2013 10:41 PM
> To: kvm@vger
> -Original Message-
> From: Gleb Natapov [mailto:g...@redhat.com]
> Sent: Thursday, April 18, 2013 7:08 PM
> To: Ren, Yongjie
> Cc: Marcelo Tosatti; kvm@vger.kernel.org; qemu-de...@nongnu.org;
> ehabk...@redhat.com
> Subject: Re: [PATCH] target-i386: upgrade family
qemu64 is the default CPU model for QEMU/KVM on x86-64, but its family number
definition is not accurate. The vendor of 'qemu64' is defined as 'AMD'. For AMD
processors, AMD K8 (i.e. Family 15) firstly introduced SSE3 instruction set.
'qemu64' already has 'CPUID_EXT_SSE3' in its ext_features, bu
Hi All,
This is KVM upstream test result against kvm.git next branch and qemu-kvm.git
uq/master branch.
kvm.git next branch: 81f4f76bbc712a2dff8bb020057c554e285370e1 based on
kernel 3.9.0-rc3
qemu-kvm.git uq/master branch: 8912bdea01e8671e59fe0287314379be9c1f40ec
We found 1 ne
Hi All,
This is KVM upstream test result against kvm.git next branch and qemu-kvm.git
master branch.
kvm.git next branch: 3f0c3d0bb2bcc4b88b22452a7cf0073ee9a0f1e6 based on
kernel 3.7.0
qemu-kvm.git master branch: 4d9367b76f71c6d938cf8201392abe4bfb1136cb
We found no new bug and
> -Original Message-
> From: Gleb Natapov [mailto:g...@redhat.com]
> Sent: Monday, January 07, 2013 5:21 PM
> To: Ren, Yongjie
> Cc: Stefan Pietsch; kvm@vger.kernel.org
> Subject: Re: Installation of Windows 8 hangs with KVM
>
> On Mon, Jan 07, 2013 at 09:13:37AM +
> -Original Message-
> From: kvm-ow...@vger.kernel.org [mailto:kvm-ow...@vger.kernel.org]
> On Behalf Of Gleb Natapov
> Sent: Monday, January 07, 2013 4:54 PM
> To: Ren, Yongjie
> Cc: Stefan Pietsch; kvm@vger.kernel.org
> Subject: Re: Installation of Windows 8 hangs
> -Original Message-
> From: kvm-ow...@vger.kernel.org [mailto:kvm-ow...@vger.kernel.org]
> On Behalf Of Stefan Pietsch
> Sent: Monday, January 07, 2013 2:25 AM
> To: Gleb Natapov
> Cc: kvm@vger.kernel.org
> Subject: Re: Installation of Windows 8 hangs with KVM
>
> * Gleb Natapov [2013-01
Hi All,
This is KVM upstream test result against kvm.git next branch and qemu-kvm.git
master branch.
kvm.git next branch: 9a7819774e4236e8736a074b7e85276967911924 based on
kernel 3.6.0-rc3
qemu-kvm.git master branch: 4c3e02beed9878a5f760eeceb6cd42c475cf0127
We found 1 new bug
Checks and operations on the INVPCID feature bit should use EBX of CPUID leaf 7
instead of ECX.
Changes from v1:
- fixed patch format issue.
Signed-off-by: Junjie Mao
Signed-off-by: Yongjie Ren
---
arch/x86/kvm/vmx.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff
Hi All,
This is KVM upstream test result against kvm.git next branch and qemu-kvm.git
master branch.
kvm.git next branch: a81aba14dc0ea499f4c218b5db0303b2ea8151d3 based on
kernel 3.6.0-rc3
qemu-kvm.git master branch: 47d70a2bcd70994d398cfb696c19ee1851e9f0ca
We filed 2 new bugs
> -Original Message-
> From: kvm-ow...@vger.kernel.org [mailto:kvm-ow...@vger.kernel.org]
> On Behalf Of Avi Kivity
> Sent: Monday, August 20, 2012 6:45 PM
> To: Ren, Yongjie
> Cc: kvm@vger.kernel.org
> Subject: Re: when will kvm merge update from upstream linux?
>
Hi Avi,
With latest kvm.git tree, igb VF can't be enabled.
But it can work fine with upstream linux.git tree.
When will kvm merge the latest update in upstream linux?
The following commit in upstream linux.git should be the fix.
commit 7f46f9c13041c8fde331142791f3994a8fdbec6f
Merge: cab 31fe94
> -Original Message-
> From: Avi Kivity [mailto:a...@redhat.com]
> Sent: Sunday, August 12, 2012 4:52 PM
> To: Ren, Yongjie
> Cc: kvm@vger.kernel.org; Marcelo Tosatti
> Subject: Re: Will KVM support "Xen on KVM" type in nested virtualization ?
>
> On
Hi folks,
I did some basic testing on nested virtualization on Intel x86-64 platform.
Will KVM support Xen as L1 guest in nested virtualization ?
When I tried "Xen on KVM" mode, I found VMX can't be initialized in L1 Xen
hypervisor.
I tried both "-cpu host" and "-cpu qemu64,+vmx" parameters in qe
Hi All,
This is KVM upstream test result against kvm.git next branch and qemu-kvm.git
master branch.
kvm.git next branch: 58d8b1728ea3da391ef01c43a384ea06ce4b7c8a based on
kernel 3.5.0-rc1
qemu-kvm.git master branch: 28c3a9b197900c88f27b14f8862a7a15c00dc7f0
We found no new bug
kvm.git next branch
commit: ebf7d2e9
arch/x86/built-in.o: In function `init_hypervisor_platform':
(.init.text+0x56b1): undefined reference to `x86_hyper_kvm'
arch/x86/built-in.o: In function `init_hypervisor_platform':
(.init.text+0x56bc): undefined reference to `x86_hyper_kvm'
make: *** [vmlinux]
> -Original Message-
> From: Jan Kiszka [mailto:jan.kis...@siemens.com]
> Sent: Wednesday, July 04, 2012 10:43 PM
> To: Ren, Yongjie
> Cc: KVM; Avi Kivity
> Subject: Re: Biweekly KVM Test report, kernel ae7a2a3f... qemu a212f79f...
>
> On 2012-07-03 09:11, Ren, Y
Hi All,
This is KVM upstream test result against kvm.git next branch and qemu-kvm.git
master branch.
kvm.git next branch: ae7a2a3fb6f8b784c2752863f4f1f20c656f76fb based on
kernel 3.5.0-rc1
qemu-kvm.git master branch: a212f79fc4596570124fb864425b980c157cd001
We found 1 new bug a
> -Original Message-
> From: Michael S. Tsirkin [mailto:m...@redhat.com]
> Sent: Monday, June 11, 2012 6:22 PM
> To: Avi Kivity
> Cc: Jan Kiszka; Thomas Gleixner; Alex Williamson; kvm@vger.kernel.org;
> mtosa...@redhat.com; linux-ker...@vger.kernel.org; Ren, Yongjie
>
Hi All,
This is KVM upstream test result against kvm.git next branch and qemu-kvm.git
master branch.
kvm.git next branch: 25e531a988ea5a64bd97a72dc9d3c65ad5850120 based on
kernel 3.5.0-rc1
qemu-kvm.git master branch: 0a948cbb1835e5f36990e173966d30bc4c8cc038
We found 1 new bug an
> -Original Message-
> From: Kevin Wolf [mailto:kw...@redhat.com]
> Sent: Wednesday, June 13, 2012 6:33 PM
> To: Ren, Yongjie
> Cc: Marcelo Tosatti; Stefan Hajnoczi; Avi Kivity; kvm@vger.kernel.org; Liu,
> RongrongX; Anthony Liguori
> Subject: Re: Biweekly KVM Test re
> -Original Message-
> From: Marcelo Tosatti [mailto:mtosa...@redhat.com]
> Sent: Wednesday, June 13, 2012 7:25 AM
> To: Kevin Wolf
> Cc: Stefan Hajnoczi; Ren, Yongjie; Avi Kivity; kvm@vger.kernel.org; Liu,
> RongrongX; Anthony Liguori
> Subject: Re: Biweekly KV
> -Original Message-
> From: kvm-ow...@vger.kernel.org [mailto:kvm-ow...@vger.kernel.org]
> On Behalf Of Avi Kivity
> Sent: Thursday, June 07, 2012 3:28 PM
> To: Michael Tokarev
> Cc: KVM list
> Subject: Re: 1.1 release?
>
> On 06/07/2012 10:19 AM, Michael Tokarev wrote:
> > On 07.06.2012
> -Original Message-
> From: Kevin Wolf [mailto:kw...@redhat.com]
> Sent: Monday, June 04, 2012 9:51 PM
> To: Ren, Yongjie
> Cc: Marcelo Tosatti; Avi Kivity; kvm@vger.kernel.org; Liu, RongrongX
> Subject: Re: Biweekly KVM Test report, kernel 51bfd299... qemu
>
Hi All,
This is KVM upstream test result against kvm.git next branch and qemu-kvm.git
master branch.
kvm.git next branch: b48b2c3e50433ff6f7e46186daa7f986bd960215 based on
kernel 3.4.0
qemu-kvm.git master branch: f9dc38843a540d8e5a5a851da260e5372a941f1c
We found 2 new bugs and
> -Original Message-
> From: Marcelo Tosatti [mailto:mtosa...@redhat.com]
> Sent: Thursday, May 31, 2012 4:30 AM
> To: Ren, Yongjie
> Cc: Kevin Wolf; Avi Kivity; kvm@vger.kernel.org; Liu, RongrongX
> Subject: Re: Biweekly KVM Test report, kernel 51bfd299... qemu
> a1
> -Original Message-
> From: Marcelo Tosatti [mailto:mtosa...@redhat.com]
> Sent: Thursday, May 31, 2012 4:28 AM
> To: Ren, Yongjie
> Cc: Kevin Wolf; Avi Kivity; kvm@vger.kernel.org; Liu, RongrongX
> Subject: Re: Biweekly KVM Test report, kernel 51bfd299... qemu
> a1
> -Original Message-
> From: Avi Kivity [mailto:a...@redhat.com]
> Sent: Thursday, May 24, 2012 5:46 PM
> To: Ren, Yongjie
> Cc: KVM; Marcelo Tosatti
> Subject: Re: which branch of kvm.git should I do regular testing against?
>
> On 05/24/2012 12:33 PM, Ren, Yongji
> -Original Message-
> From: Avi Kivity [mailto:a...@redhat.com]
> Sent: Thursday, May 24, 2012 5:29 PM
> To: Ren, Yongjie
> Cc: KVM; Marcelo Tosatti
> Subject: Re: which branch of kvm.git should I do regular testing against?
>
> On 05/24/2012 12:24 PM, Ren, Y
Hi Avi,
Our team spare some effort in regular nightly testing against KVM upstream.
We're using master branch now and all the test reports I sent out are based on
master branch.
Which branch of kvm.git should we do regular testing against?
Your suggestion?
I know next branch contains latest KVM p
> -Original Message-
> From: Kevin Wolf [mailto:kw...@redhat.com]
> Sent: Monday, May 21, 2012 11:30 PM
> To: Ren, Yongjie
> Cc: Avi Kivity; kvm@vger.kernel.org; Liu, RongrongX
> Subject: Re: Biweekly KVM Test report, kernel 51bfd299... qemu
> a1fce560...
>
> A
> -Original Message-
> From: Kevin Wolf [mailto:kw...@redhat.com]
> Sent: Monday, May 21, 2012 5:05 PM
> To: Avi Kivity
> Cc: Ren, Yongjie; kvm@vger.kernel.org
> Subject: Re: Biweekly KVM Test report, kernel 51bfd299... qemu
> a1fce560...
>
> Am 21.05.201
Hi All,
This is KVM upstream test result against kvm.git
51bfd2998113e1f8ce8dcf853407b76a04b5f2a0 based on kernel 3.4.0-rc7, and
qemu-kvm.git a1fce560c0e5f287ed65d2aaadb3e59578aaa983.
We found 1 new bug and 1 bug got fixed in the past two weeks.
New issue (1):
1. disk error when guest boot up
Hi All,
This is KVM upstream test result against kvm.git
95f714727436836bb46236ce2bcd8ee8f9274aed based on kernel 3.4.0-rc4, and
qemu-kvm.git b320b8b70bd4f5f6800b85bc95981a8ed09f943c.
We found 1 new bug and 1 bug got fixed in the past two weeks.
New issue (1):
1. (Nested-virt) L1 (kvm on kvm)g
Hi All,
This is KVM upstream test result against kvm.git
3efca44f37c21f2d50411b2b52617631fa1ba772 based on kernel 3.3.0, and
qemu-kvm.git 24853eece248d4a58d705c2ddf8818647b11b1e9.
We found 1 new bug and no bug got fixed in the past two weeks.
The new bug is about timer, and it’s a bug in qemu s
Hi All,
This is KVM upstream test result against kvm.git
3efca44f37c21f2d50411b2b52617631fa1ba772 based on kernel 3.3.0, and
qemu-kvm.git a0bc8c313ce7da8937e190b1e0cfd051a9ba243e.
We found 1 new bug and 1 bug got fixed in the past two weeks.
New issue(1):
1. one of the two assigned NICs doesn’
Hi All,
This is KVM upstream test result against kvm.git
4f324a1bdfba2a29bbd5485e72ba2b4adeb8147c based on kernel 3.3.0-rc5, and
qemu-kvm.git b5ed4b6f6f0d31e0d8210f4b444ba67bfa5d6de2.
We found no new bug and no bug got fixed in the past two weeks.
New issue(0):
Fixed issue(0):
Old issue (1):
This patch works fine.
Tested by: Yongjie Ren
Best Regards,
Yongjie Ren (Jay)
> -Original Message-
> From: Jan Kiszka [mailto:jan.kis...@siemens.com]
> Sent: Friday, March 02, 2012 5:21 PM
> To: Avi Kivity; Marcelo Tosatti
> Cc: Zhang, Yang Z; Ren, Yongjie; KVM
Hi Avi,
I can't restore a guest saved by an older qemu. I wonder if this issue is
introduced by some latest commits on the file 'hw/i8254.c'.
The new commit: b5ed4b6f (on Mar 1)I tried to restore a guest using this
qemu.
The old commit: 9d636ae7 (on Feb 11)I saved a guest using this qem
Hi All,
This is KVM upstream test result against kvm.git
6a2c5be53bb97247ef8c7a0b3c75173bfc05ef94 based on kernel 3.3.0, and
qemu-kvm.git 9d636ae7488edfa9c7f03ceee62c838d505aac3e.
We found no new bug and no bug got fixed in the past two weeks.
New issue(0):
Fixed issue(0):
Old issue (1):
Hi All,
This is KVM upstream test result against kvm.git
e27aad2f39d85009e8b6ce8f58b9809b22083c23 based on kernel 3.3.0, and
qemu-kvm.git 2793248c5427c0bc585fdf9c101680bab29f4839.
We found 2 bugs got fixed during the past two weeks.
New issue(0):
Fixed issues (2):
1. rhel5u5 guest panic when
Hi All,
This is KVM upstream test result against kvm.git
188fc33198ddb1469562d40de33bcc29e7e2ed5f based on kernel 3.2.0, and
qemu-kvm.git 9501d0f1b6efc83f69d06b27a625bad71d30d58b.
We found 2 new bugs and no bug got fixed during the past two weeks.
New issues (2):
1. rhel5u5 guest panic when boo
show_bug.cgi?id=42563
Best Regards,
Yongjie Ren (Jay)
> -Original Message-
> From: kvm-ow...@vger.kernel.org [mailto:kvm-ow...@vger.kernel.org] On
> Behalf Of Ren, Yongjie
> Sent: Friday, January 06, 2012 11:27 AM
> To: John 'Warthog9' Hawley; Av
> -Original Message-
> From: John 'Warthog9' Hawley [mailto:warth...@kernel.org]
> Sent: Friday, January 06, 2012 10:34 AM
> To: Avi Kivity
> Cc: Konstantin Ryabitsev; Ren, Yongjie; kvm@vger.kernel.org; ftpadmin
> Subject: Re: where should I report kvm kernel b
> -Original Message-
> From: Avi Kivity [mailto:a...@redhat.com]
> Sent: Wednesday, January 04, 2012 1:08 AM
> To: Konstantin Ryabitsev
> Cc: Ren, Yongjie; kvm@vger.kernel.org; ftpadmin
> Subject: Re: where should I report kvm kernel bug?
>
> On 01/03/2012 06:28
Hi folks,
I reported some kvm kernel bugs at "bugzilla.kernel.org" before the kernel.org
was attacked.
Though kernel.org resumes, its bugzilla can't be accessed so far.
So, where should I report a kvm kernel bug? I mean not just reporting in this
mailing list but in a bugzilla to track.
Or, could
Hi All,
This is KVM upstream test result against kvm.git
781f306789361d671187d9ddb518eea3ffda786a based on kernel 3.2.0-rc7, and
qemu-kvm.git fcfeed4a398a8524ce8f84eaaba984bd9c27354e.
We found no new bug and no bug got fixed during our test.
New issue (0):
Fixed issue (0):
Old issue (1):
> -Original Message-
> From: Gleb Natapov [mailto:g...@redhat.com]
> Sent: Thursday, December 29, 2011 5:46 PM
> To: Ren, Yongjie
> Cc: a...@redhat.com; kvm@vger.kernel.org
> Subject: Re: [PATCH] KVM: fix a syntax error in pmu.c
>
> On Thu, Dec 29, 2011 at 09:40:
Fix a syntax error in arch/x86/kvm/pmu.c
Signed-off-by: Yongjie Ren
---
diff --git a/arch/x86/kvm/pmu.c b/arch/x86/kvm/pmu.c
index 061a03f..8f142bf 100644
--- a/arch/x86/kvm/pmu.c
+++ b/arch/x86/kvm/pmu.c
@@ -170,9 +170,9 @@ static void reprogram_counter(struct kvm_pmc *pmc, u32 type,
Hi All,
This is KVM test result against kvm.git
1db6efe35afcda0bd05e5f4449ea814a9071da7f based on 3.2.0-rc2, and qemu-kvm.git
9ac357fdfc51bac582a61f95b32565648b844878.
We found no new bug and 1 bug was fixed during our test.
The fixed bug is the SR-IOV detachment issue (qemu BZ #875723). Alex (@
Hi All,
This is KVM test result against kvm.git
b796a09c5d808f4013f27ad45953db604dac18fd based on 3.1.0, and qemu.git
7879db7e9c09b92d9af1c143fbe2cc212ec89e4b.
We filed 3 new bugs during our test.
One of them is that kvm is not enabled by default when qemu starting a
guest. This bug has alr
> -Original Message-
> From: kvm-ow...@vger.kernel.org [mailto:kvm-ow...@vger.kernel.org] On
> Behalf Of Ren, Yongjie
> Sent: Thursday, October 27, 2011 3:03 PM
> To: Markus Armbruster
> Cc: Alex Williamson; KVM General; Avi Kivity
> Subject: RE: [qemu bug] device as
> -Original Message-
> From: Markus Armbruster [mailto:arm...@redhat.com]
> Sent: Thursday, October 27, 2011 2:50 PM
> To: Ren, Yongjie
> Cc: Alex Williamson; KVM General; Avi Kivity
> Subject: Re: [qemu bug] device assignment doesn't work: "error: requi
> -Original Message-
> From: Alex Williamson [mailto:alex.william...@redhat.com]
> Sent: Thursday, October 27, 2011 11:04 AM
> To: Ren, Yongjie
> Cc: KVM General; Avi Kivity
> Subject: Re: [qemu bug] device assignment doesn't work: "error: requires KVM
> supp
Hi,
When doing device assignment with qemu and kvm upstream, I met "error: requires
KVM support".
Please also refer to the bug in qemu bugzilla.
https://bugs.launchpad.net/qemu/+bug/882358
qemu.git commit:8843cf40c0f482949e6ae9d0119e45d6b96fe890
I met the following error when doing device ass
> -Original Message-
> From: Marcelo Tosatti [mailto:mtosa...@redhat.com]
> Sent: Friday, September 30, 2011 1:30 AM
> To: Ren, Yongjie
> Cc: KVM General
> Subject: Re: Biweekly KVM Test report, kernel 1e0e12af... qemu ad305c9f...
>
> On Sun, Sep 25, 2011 at 10:28:
> -Original Message-
> From: Chris Wright [mailto:chr...@sous-sol.org]
> Sent: Thursday, September 29, 2011 12:33 PM
> To: Ren, Yongjie
> Cc: Chris Wright; Avi Kivity; KVM General
> Subject: Re: how to assign a pci device to guest [with qemu.git upstream]?
>
> * C
issue?
Best Regards,
Yongjie Ren (Jay)
> -Original Message-
> From: Chris Wright [mailto:chr...@sous-sol.org]
> Sent: Thursday, September 29, 2011 8:57 AM
> To: Ren, Yongjie
> Cc: KVM General
> Subject: Re: how to assign a pci device to guest [with qemu.git upstrea
Hi All,
This is KVM test result against kvm.git
1e0e12af7606a7d4063654eb294c8fd554c71a25 based on kernel 3.1.0-rc5+, and
qemu.git ad305c9fc6f2c037f47b3274ceace4ebc81160ed.
We found 2 new bugs during the past two weeks. Both of them are qemu bugs.
One of them is that guest boot up too slowly.
The
Hi All,
This is KVM test result against kvm.git
1e0e12af7606a7d4063654eb294c8fd554c71a25 based on kernel 3.1.0-rc5+, and
qemu.git ad305c9fc6f2c037f47b3274ceace4ebc81160ed.
We found 2 new bugs during the past two weeks. Both of them are qemu bugs.
One of them is that guest boot up too slowly.
The
Hi folks,
I'm using kvm and qemu upstream on https://github.com/avikivity
The following command line was right for me about three weeks ago, but now I
meet some error.
# qemu-system-x86_64 -m 1024 -smp 2 -device pci-assign,host=0e:00.0 -hda
/root/rhel6u1.img
output error is like following.
qemu-s
Hi All,
This is KVM test result against kvm.git
902c502f0b0efec3a784a8ef65057298025e5e11 based on kernel 3.1.0-rc3+, and
qemu-kvm.git a040d28b1d245253754f3b82b78c9f85c5b8baea.
We found 2 new bugs during the past two weeks. Both of them blocked many test
cases in our test system.
One of them is
11 4:17 AM
> To: Avi Kivity
> Cc: Pekka Enberg; Rafael J. Wysocki; Linux Kernel Mailing List; Kernel Testers
> List; Maciej Rutecki; Ren, Yongjie; stefa...@linux.vnet.ibm.com; KVM
> General
> Subject: Re: [Bug #39412] Win Vista and Win2K8 guests' network breaks
> down
>
&
Hi All,
This is KVM test result against kvm.git
e72ef590a3ef3047f6ed5bcb8808a9734f6c4b32 based on kernel 3.0.0+, and
qemu-kvm.git fda19064e889d4419dd3dc69ca8e6e7a1535fdf5.
We found no new bugs during the past two weeks.
We found 2 bugs got fixed. One fixed bug is about Win2k8 and Vista guest’s
Hi All,
This is KVM test result against kvm.git
0af9df4e80a3a620c52c3a9777191c54e615d068 based on kernel 3.0.0-rc6+, and
qemu-kvm.git 525e3df73e40290e95743d4c8f8b64d8d9cbe021.
We found a new bug about Win2K8 and Vista guest’s NIC driver. Win Vista and
Win2K8 guests can't find NIC driver.
I also
_init delayacct_setup_disable(char *str)
> -Original Message-
> From: Avi Kivity [mailto:a...@redhat.com]
> Sent: Wednesday, July 13, 2011 9:19 PM
> To: Tian, Kevin
> Cc: Ren, Yongjie; kvm@vger.kernel.org; Glauber Costa
> Subject: Re: kvm upstream build error..
>
>
Hi Avi,
KVM upstream have a build error in our build system. Do you have some comments
on this issue? my kvm commit is 0af9df4e80a3a620c52c3a9777191c54e615d068
build error info:
LD arch/x86/boot/setup.elf
OBJCOPY arch/x86/boot/setup.bin
BUILD arch/x86/boot/bzImage
Root device is (8, 1
Hi All,
This is KVM test result against kvm.git
2e0d8e289ef23d0e56923d778e9bea0601a0edb4 based on kernel 3.0.0-rc5+, and
qemu-kvm.git d58931037dbb4fbc2fbb33858629d3fabfd1b0d4.
We found a make error issue of qemu-kvm.git. This issue was reported in qemu’s
bugzilla by someone else.
I commented
Hi All,
This is KVM test result against kvm.git
681fb677ace0754589792c92b8dbee9884d07158 based on kernel 3.0.0-rc2+, and
qemu-kvm.git 05f1737582ab6c075476bde931c5eafbc62a9349.
We found a new vt-d bug about “NIC assignment order in command line makes some
NIC can't work”.
A vt-d bug was fixed in
Hi All,
This is KVM test result against kvm.git
19c17b5c14e0b3e9131e55a92b961ea9eabbc56b based on kernel 2.6.39+, and
qemu-kvm.git c007db193eb6b2557acb5caf2dc4d7023639e6f3.
We found no bug and no fix in our nightly test during the past two weeks.
New issue:
Fixed issue:
Old Issues:
==
Hi All,
This is KVM test result against kvm.git
6f1bd0daae731ff07f4755b4f56730a6e4a3c1cb based on kernel 2.6.39-rc7+, and
qemu-kvm.git db8b5127f8a16c251592023de814be248fa84dda.
We found no bug and no fix in our nightly test during the past two weeks.
The qemu [vt-d] bug 754591 exists for a month
Hi All,
This is KVM test result against kvm.git
40f4a244a3687d390e97f8e5240f5a701e630ccc based on kernel 2.6.39-rc2+, and
qemu-kvm.git 28262112181f27f302b5186f0df6428df6b513e7.
We found no bug and no fix in our nightly test during the past two weeks.
The qemu [vt-d] bug 754591 exists for a month
1 - 100 of 109 matches
Mail list logo
