Bugs item #2055584, was opened at 2008-08-16 23:10
Message generated for change (Comment added) made by jiajun
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2055584group_id=180599
Please note that this message will contain a full copy of the comment
Hi All,
This is our Weekly KVM Testing Report against lastest kvm.git
ce094fc0d25cb364bce6f854dffc6849876ab89 and kvm-userspace.git
55ff0bb298456450a81448200fea8f50246893b4.
No new issue found this week and one issue fixed. All failed cases can
pass by manual.
One Issue Fixed:
* On Friday 22 Aug 2008 23:48:42 Avi Kivity wrote:
Amit Shah wrote:
diff --git a/include/linux/kvm.h b/include/linux/kvm.h
index d9ef7d3..2956e35 100644
--- a/include/linux/kvm.h
+++ b/include/linux/kvm.h
@@ -495,4 +495,6 @@ struct kvm_assigned_irq {
__u32 flags;
};
* On Friday 22 Aug 2008 23:51:15 Avi Kivity wrote:
Amit Shah wrote:
The following two patches contain VT-d support for device assignment
for KVM guests.
The first patch contains the changes that are required to the generic
VT-d code.
The second patch contains the changes to KVM.
Amit Shah wrote:
* On Friday 22 Aug 2008 23:48:42 Avi Kivity wrote:
Amit Shah wrote:
diff --git a/include/linux/kvm.h b/include/linux/kvm.h
index d9ef7d3..2956e35 100644
--- a/include/linux/kvm.h
+++ b/include/linux/kvm.h
@@ -495,4 +495,6 @@ struct kvm_assigned_irq {
__u32
Amit Shah wrote:
* On Friday 22 Aug 2008 23:51:15 Avi Kivity wrote:
Amit Shah wrote:
The following two patches contain VT-d support for device assignment
for KVM guests.
The first patch contains the changes that are required to the generic
VT-d code.
The second patch contains the
* On Saturday 23 Aug 2008 14:58:50 Avi Kivity wrote:
Amit Shah wrote:
Also, is KVM_CAP_foo needed for this? This is the only #define that'll be
used and we can simply do something like
#ifdef KVM_DEV_ASSIGN_USE_VTD
flags |= KVM_DEV_ASSIGN_USE_VTD
#endif
?
That only detects if
* On Saturday 23 Aug 2008 15:03:46 Avi Kivity wrote:
Amit Shah wrote:
* On Friday 22 Aug 2008 23:51:15 Avi Kivity wrote:
Amit Shah wrote:
The following two patches contain VT-d support for device assignment
for KVM guests.
The first patch contains the changes that are required to the
On Fri, Aug 22, 2008 at 10:10:52AM +0300, Amit Shah wrote:
The second patch contains the changes to KVM.
I've updated the 2nd patch to use VT-d only when requested by a
parameter on the command line, making it easier to support iommu
with pvdma and multiple iommu types.
The command line
* On Saturday 23 Aug 2008 15:27:47 Muli Ben-Yehuda wrote:
On Fri, Aug 22, 2008 at 10:10:52AM +0300, Amit Shah wrote:
The second patch contains the changes to KVM.
I've updated the 2nd patch to use VT-d only when requested by a
parameter on the command line, making it easier to support
On Sat, Aug 23, 2008 at 03:55:25PM +0530, Amit Shah wrote:
The authorship info and the commit log stays the same; just contains
my signoff.
Actually, unless you add an explicit 'From:' header, the email From
header is used by git as the author of the patch.
Cheers,
Muli
--
Workshop on I/O
* On Saturday 23 Aug 2008 16:10:54 Muli Ben-Yehuda wrote:
On Sat, Aug 23, 2008 at 03:55:25PM +0530, Amit Shah wrote:
The authorship info and the commit log stays the same; just contains
my signoff.
Actually, unless you add an explicit 'From:' header, the email From
header is used by git as
On Sat, Aug 23, 2008 at 04:41:02PM +0530, Amit Shah wrote:
* On Saturday 23 Aug 2008 16:10:54 Muli Ben-Yehuda wrote:
On Sat, Aug 23, 2008 at 03:55:25PM +0530, Amit Shah wrote:
The authorship info and the commit log stays the same; just contains
my signoff.
Actually, unless you add an
* On Saturday 23 Aug 2008 17:41:32 Muli Ben-Yehuda wrote:
On Sat, Aug 23, 2008 at 04:41:02PM +0530, Amit Shah wrote:
* On Saturday 23 Aug 2008 16:10:54 Muli Ben-Yehuda wrote:
On Sat, Aug 23, 2008 at 03:55:25PM +0530, Amit Shah wrote:
The authorship info and the commit log stays the same;
On Friday, August 22, 2008 12:10 am Amit Shah wrote:
From: Kay, Allen M [EMAIL PROTECTED]
This patch extends the VT-d driver to support KVM
[Ben: fixed memory pinning]
Signed-off-by: Kay, Allen M [EMAIL PROTECTED]
Signed-off-by: Weidong Han [EMAIL PROTECTED]
Signed-off-by: Ben-Ami Yassour
After movong from KVM-72 to KVM-73 I do get the Notice
vmport: unknown command 13
The Message appears on starting emulation. In an Netboot environment it
does appear before booting from Network is asked.
What might go wrong here?
Elmar
--
To unsubscribe from this list: send the line
Elmar Haneke wrote:
After movong from KVM-72 to KVM-73 I do get the Notice
vmport: unknown command 13
The Message appears on starting emulation. In an Netboot environment it
does appear before booting from Network is asked.
What might go wrong here?
It's actually harmless; it's the
Having given up getting normal ESX booting from within KVM, I thought i'd
give ESXi a go.
PXE booting the hypervisor image outside of KVM I have working fine.
When trying within KVM i had a few issues:
The 'vmport' breaks ESXi, so for now I commented out vmport_init();
Then it complains about
Yuksel Gunal wrote:
Hi,
I have been playing with KVM and was wondering about the following
question: is there a resource configuration setting that would enforce
a fraction of CPU to be guaranteed for a KVM guest? What I have on
mind is something similar to the reservation setting on VMware
19 matches
Mail list logo
