Bryon Roche wrote:
>If you're playing with kvm-git, you should be able to pull these fixes in
>via cherry picking 16f197e29c19a4366a1d2ba3dcd0b4b8b0f86ce6, then
>86030aade7ae09f4cedfb13973e37ba30f3db073.
In fact, I compiled and installed kvm-84 today, and it seems to have
resolved the problem w
Fix the typo of || to &&.
Signed-off-by: Wei Yongjun
---
arch/x86/kvm/vmx.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
index 6259d74..3f3cab2 100644
--- a/arch/x86/kvm/vmx.c
+++ b/arch/x86/kvm/vmx.c
@@ -1813,7 +1813,7 @@ st
Signed-off-by: Yu Zhao
---
Documentation/DocBook/kernel-api.tmpl |1 +
Documentation/PCI/pci-iov-howto.txt | 99 +
2 files changed, 100 insertions(+), 0 deletions(-)
create mode 100644 Documentation/PCI/pci-iov-howto.txt
diff --git a/Documentation/DocBook
Signed-off-by: Yu Zhao
---
Documentation/ABI/testing/sysfs-bus-pci | 27 +++
1 files changed, 27 insertions(+), 0 deletions(-)
diff --git a/Documentation/ABI/testing/sysfs-bus-pci
b/Documentation/ABI/testing/sysfs-bus-pci
index ceddcff..84dc100 100644
--- a/Documentati
Signed-off-by: Yu Zhao
---
drivers/pci/iov.c | 348 +++
drivers/pci/pci.h |3 +
include/linux/pci.h | 14 ++
3 files changed, 365 insertions(+), 0 deletions(-)
diff --git a/drivers/pci/iov.c b/drivers/pci/iov.c
index c89fcb1..e4e2dac 100
Signed-off-by: Yu Zhao
---
drivers/pci/iov.c | 119 +++
drivers/pci/pci.h |4 ++
include/linux/pci.h |6 +++
3 files changed, 129 insertions(+), 0 deletions(-)
diff --git a/drivers/pci/iov.c b/drivers/pci/iov.c
index e4e2dac..127f643 1
Signed-off-by: Yu Zhao
---
drivers/pci/iov.c | 34 ++
drivers/pci/pci.h |5 +
drivers/pci/probe.c |3 +++
3 files changed, 42 insertions(+), 0 deletions(-)
diff --git a/drivers/pci/iov.c b/drivers/pci/iov.c
index 1cc879b..c89fcb1 100644
--- a/dri
Signed-off-by: Yu Zhao
---
drivers/pci/iov.c | 25 +
drivers/pci/pci.c |1 +
drivers/pci/pci.h |4
3 files changed, 30 insertions(+), 0 deletions(-)
diff --git a/drivers/pci/iov.c b/drivers/pci/iov.c
index e6736d4..1cc879b 100644
--- a/drivers/pci/iov.c
+++
Signed-off-by: Yu Zhao
---
drivers/pci/Kconfig | 13
drivers/pci/Makefile |3 +
drivers/pci/iov.c| 181 ++
drivers/pci/pci.c|7 ++
drivers/pci/pci.h| 37 ++
drivers/pci/probe.c |4 +
in
Greetings,
Following patches are intended to support SR-IOV capability in the
Linux kernel. With these patches, people can turn a PCI device with
the capability into multiple ones from software perspective, which
will benefit KVM and achieve other purposes such as QoS, security,
and etc.
SR-IOV s
Avi,
Please help to check-in this patch, and it breaks ia64's build.
Xiantao
-Original Message-
From: Zhang, Yang
Sent: Monday, February 16, 2009 4:31 PM
To: kvm-i...@vger.kernel.org
Cc: kvm@vger.kernel.org; Avi Kivity; Zhang, Xiantao
Subject: [PATCH]remove some redundant args
Introduce KVM_SET_MSIX_NR and KVM_SET_MSIX_ENTRY two ioctls.
This two ioctls are used by userspace to specific guest device MSI-X entry
number and correlate MSI-X entry with GSI during the initialization stage.
MSI-X should be well initialzed before enabling.
Don't support change MSI-X entry num
On Tuesday 17 February 2009 07:23:23 Marcelo Tosatti wrote:
> On Mon, Feb 16, 2009 at 01:49:29PM +0800, Sheng Yang wrote:
> > (oops... fix a typo)
> >
> > Introduce KVM_SET_MSIX_NR and KVM_SET_MSIX_ENTRY two ioctls.
> >
> > This two ioctls are used by userspace to specific guest device MSI-X
> > en
Kevin Wolf wrote:
> >> By the way and completely off-topic: Have you already tried to use the
> >> VHD patches? I would really like to know if they fix your problems.
> >
> > Are those patches in kvm-83? I still have the image that was causing
> > problems way back, and I'm converting it to raw n
On 2/12/09, Glauber Costa wrote:
> We don't have any kind of kvm support for linux-user targets,
> but conditionalizing the inclusion of kvm header make
> linux-user compilation break. And we don't have a reason to
> prevent that, do we?
Ack, again, same problem here. The lack of inclusion of
On 2/13/09, Glauber Costa wrote:
> ppc should compile with upstream qemu code, so, put these
> defines in ppc specific code that references kvm functions.
>
> We don put them in config.h in this case, since there are
> files (like vl.c) that includes both kvm.h and qemu-kvm.h,
> and would brea
On Mon, Feb 16, 2009 at 01:49:29PM +0800, Sheng Yang wrote:
> (oops... fix a typo)
>
> Introduce KVM_SET_MSIX_NR and KVM_SET_MSIX_ENTRY two ioctls.
>
> This two ioctls are used by userspace to specific guest device MSI-X entry
> number and correlate MSI-X entry with GSI during the initialization
Bryon Roche wrote:
>If you're playing with kvm-git, you should be able to pull these fixes in
>via cherry picking 16f197e29c19a4366a1d2ba3dcd0b4b8b0f86ce6, then
>86030aade7ae09f4cedfb13973e37ba30f3db073.
Thanks, but I have "other problems" at present so I'm just accepting
source tarballs to bui
Hi all,
I've successfully installed KVM (version 83 with 2.6.28 kernel) and
windows as guest. I start it with
kvm -net nic,macaddr=46:0e:b3:53:9f:3a \
-net user -localtime -smb /home/horn \
~/kvm/windows.img
and basically it works fine. I have network access in the guest,
perform
Has anyone (esp. the KVM core developers) tried to determine whether KVM
works on the new Via Nano CPUs? They claim to support the Intel-style VT-x
instruction set extensions and show up in cpuinfo that way. But, according to
some Google searching, folks who have tried to use KVM (or Hyper-V) hav
On 16.02.2009, at 19:01, Neo Jia wrote:
On Sun, Jan 25, 2009 at 10:00 AM, Anthony Liguori > wrote:
Alexander Graf wrote:
Hi,
On 25.01.2009, at 09:16, Neo Jia wrote:
hi,
I am thinking if it is possible to port KVM to Mac OS (leopard). Is
there anybody doing this already?
I've considered
On Sun, Jan 25, 2009 at 10:00 AM, Anthony Liguori wrote:
> Alexander Graf wrote:
>>
>> Hi,
>>
>> On 25.01.2009, at 09:16, Neo Jia wrote:
>>
>>> hi,
>>>
>>> I am thinking if it is possible to port KVM to Mac OS (leopard). Is
>>> there anybody doing this already?
>>
>> I've considered doing it, but
Avi Kivity wrote:
> A long list of changes due to an unusually late release. As is becoming
> usual, many of the changes come from upstream qemu; the kvm specific
> changes are mostly bugfixes, but also include infrastructure intended
> for message-signalled interrupts (MSI).
>
> kvm-84 is slower
On Fri, 13 Feb 2009 12:56:56 +1100, Ross McKay wrote:
> NB: don't use recent sources (post v80) if you want to run compressed
> qcow2 images, as you'll only get corruption. I was told on this list
> that QEMU has resolved the problem but that the patch hasn't been ported
> across to the KVM branc
Ross McKay wrote:
dnjap wrote:
I'm looking for a laptop on which I can run KVM.
1. Does anyone have a list of AMD-V or VT-x capable laptop CPU's?
Is it not as simple as checking for the svm or vt flags?
egrep '(vt|svm)' /proc/cpuinfo
Take a bootable LiveCD into your local computer
Jamie Lokier schrieb:
> Kevin Wolf wrote:
>> Besides reviewing the code over and over again, I think the only real
>> chance is that you can get a non-productive copy of your image and add
>> some debug code so that we can see at least which code path is causing
>> problems.
>
> I have a copy of m
cpuid function 2 can have multiple values to describe cache behaviour.
Loop till we have fetched all the values.
Signed-off-by: Amit Shah
---
qemu/qemu-kvm-x86.c | 27 +--
1 files changed, 25 insertions(+), 2 deletions(-)
diff --git a/qemu/qemu-kvm-x86.c b/qemu/qemu-kv
Hi
This patch remove some redundant args in function pci_vga_init(),isa_vga_init(),
rtc_init() in ipf.c
Please review it
yang
>From 2a7c4cdf02c992da36f25bfe62ab1e4b0d9e3e91 Mon Sep 17 00:00:00 2001
From: Yang Zhang
Date: Mon, 16 Feb 2009 01:17:52 -0600
Subject: [PATCH] kvm : qemu: remove some
28 matches
Mail list logo
