From: Marcelo Tosatti [EMAIL PROTECTED]
The pvmmu TLB flush handler should request a root sync, similarly to
a native read-write CR3.
Signed-off-by: Marcelo Tosatti [EMAIL PROTECTED]
Signed-off-by: Avi Kivity [EMAIL PROTECTED]
diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c
index
From: Sheng Yang [EMAIL PROTECTED]
Notice that the patch exclude kernel directory in cscope.files of userspace.
Signed-off-by: Sheng Yang [EMAIL PROTECTED]
Signed-off-by: Avi Kivity [EMAIL PROTECTED]
diff --git a/Makefile b/Makefile
index 402c3e9..6581679 100644
--- a/Makefile
+++ b/Makefile
@@
From: Avi Kivity [EMAIL PROTECTED]
Conflicts:
qemu/Makefile.target
qemu/block.c
qemu/configure
qemu/cpu-all.h
qemu/exec.c
qemu/gdbstub.c
qemu/migration.c
qemu/migration.h
qemu/monitor.c
qemu/sysemu.h
qemu/vl.c
Am Dienstag, 14. Oktober 2008 schrieb Glauber Costa:
Hi Carsten,
libkvm/libkvm.c, in function get_free_slot(), we see:
#if defined(KVM_CAP_SET_TSS_ADDR) !defined(__s390__)
tss_ext = ioctl(kvm-fd, KVM_CHECK_EXTENSION, KVM_CAP_SET_TSS_ADDR);
#else
tss_ext = 0;
#endif
On Wednesday 15 October 2008 15:03:39 Amit Shah wrote:
* On Wednesday 15 Oct 2008 08:06:30 Sheng Yang wrote:
@@ -4115,6 +4116,9 @@ struct kvm *kvm_arch_create_vm(void)
INIT_LIST_HEAD(kvm-arch.active_mmu_pages);
INIT_LIST_HEAD(kvm-arch.assigned_dev_head);
+
* On Tuesday 14 Oct 2008 14:15:19 Zhang, Xiantao wrote:
Hi, Amit/Sheng
See the comments below.
Xiantao
Hello Xiantao, can you send a followup patch to this to accomodate these
changes? We can merge the two patches and then ask Avi to apply so that the
ia64 build doesn't break unless
* On Wednesday 15 Oct 2008 08:06:30 Sheng Yang wrote:
@@ -4115,6 +4116,9 @@ struct kvm *kvm_arch_create_vm(void)
INIT_LIST_HEAD(kvm-arch.active_mmu_pages);
INIT_LIST_HEAD(kvm-arch.assigned_dev_head);
+ /* Reserve bit 0 of irq_sources_bitmap for userspace irq
Hi!
My desktop machine is HP dc5750 SFF, CPU is AMD Athlon(tm) 64 X2 Dual
Core Processor 4600+, /proc/cpuinfo lists svm flag. I'm using 2.6.27
kernel on FC9, qemu-system-x86_64 info version 0.9.1.
How can I be absolutely sure, that my kvm virtual machines are using AMD-V?
--
Veiko Kukk
--
Bugs item #2168057, was opened at 2008-10-15 12:15
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2168057group_id=180599
Please note that this message will contain a full copy of
Linus, please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/avi/kvm.git kvm-updates/2.6.28
to receive the kvm updates for the 2.6.28 merge window. Changes include
performance improvement, pci device assignment, and improved emulation
accuracy.
Alexander Graf (1):
KVM: Ignore
Hi, Avi
I have made it work on kvm/ia64. Please apply! Thanks!
Xiantao
From c0d1ad6327c01ba0584922022bef48c971bbf18a Mon Sep 17 00:00:00 2001
From: Xiantao Zhang [EMAIL PROTECTED]
Date: Wed, 15 Oct 2008 20:15:06 +0800
Subject: [PATCH] KVM: Fix guest shared interrupt with in-kernel irqchip
Hi, Avi
This is the key fix for 2.6.28 merge. Without this patch, guest
may hang once configured with more than 2 vcpus, it is because x86 side
changed the halt handling's common logic, but it misses to change ia64
side.
Thanks
Xiantao
From 82b5626f9e3e422e1cd4352ecdff08c1c0dd394e Mon
Forget to mention Jes had tested to boot 16vcpus, and didn't meet any
issue. Sorry! :)
Acked-by : Jes Sorensen [EMAIL PROTECTED]
Zhang, Xiantao wrote:
Hi, Avi
This is the key fix for 2.6.28 merge. Without this patch, guest
may
hang once configured with more than 2 vcpus, it is because
Sheng Yang wrote:
Notice that the patch exclude kernel directory in cscope.files of userspace.
Applied, thanks.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to [EMAIL PROTECTED]
More
Sheng Yang wrote:
Remove one left improper comment of removed CR2.
Applied, thanks.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Forget to modify the from item generated automatically by git. Modified
to Sheng Yang [EMAIL PROTECTED] :)
Xiantao
From c0d1ad6327c01ba0584922022bef48c971bbf18a Mon Sep 17 00:00:00 2001
From: Sheng Yang [EMAIL PROTECTED]
Date: Wed, 15 Oct 2008 20:15:06 +0800
Subject: [PATCH] KVM: Fix guest
Anthony Liguori wrote:
Why not merge these bits prior to merging virtio? They aren't kvm
specific and would be good in mainline qemu.
I'd rather have a consumer of an interface before merging the actual
infrastructure.
So merge them all into qemu at the same time (as separate
Gleb Natapov wrote:
On Tue, Oct 14, 2008 at 01:16:19PM -0500, Anthony Liguori wrote:
One thing that's been discussed is to use something that looked much
Where is has been discussed? Was it on a public mailing list with online
archive?
Probably? This subject has been discussed
Avi Kivity wrote:
Anthony Liguori wrote:
Why not merge these bits prior to merging virtio? They aren't kvm
specific and would be good in mainline qemu.
I'd rather have a consumer of an interface before merging the actual
infrastructure.
So merge them all into qemu at the same
Bugs item #2168011, was opened at 2008-10-15 09:53
Message generated for change (Comment added) made by nuitari3
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2168011group_id=180599
Please note that this message will contain a full copy of the comment
Gleb Natapov [EMAIL PROTECTED] wrote:
Of course, you should also take a look at VMware's VMCI. If we're going
to have a socket interface, if we can have a compatible userspace
interface, that would probably be a good thing.
I looked at what I could find about VMCI
As suggested by Avi, this patch introduces a counter of VCPUs that have
LVT0 set to NMI mode. Only if the counter 0, we push the PIT ticks via
all LAPIC LVT0 lines to enable NMI watchdog support.
Signed-off-by: Jan Kiszka [EMAIL PROTECTED]
---
arch/x86/kvm/i8254.c | 13 +++--
This fixes Windows 64-bit boot regressions: PIT IRQs must not be
delivered via LVT0 lines if they are masked.
Signed-off-by: Jan Kiszka [EMAIL PROTECTED]
---
arch/x86/kvm/i8254.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: b/arch/x86/kvm/i8254.c
Aligning in-kernel kvm_apic_accept_pic_intr with its user space mate,
this patch relaxes the conditions under which PIC IRQs are accepted
by LVT0. This reflects reality and allows to reuse the service for the
NMI watchdog use case.
Signed-off-by: Jan Kiszka [EMAIL PROTECTED]
---
Bug tracker reports 2149609 and 2168057 pointed out boot issues of
Windows 64-bit versions. This series fixes the underlying problem.
It furthermore stacks the earlier posted optimization on top which
shortens the PIT IRQ delivery path in case the NMI-watchdog-via-PIT
trick is not used by the
On Wed, Oct 15, 2008 at 07:18:52AM -0700, Andrew Biggadike wrote:
Gleb Natapov [EMAIL PROTECTED] wrote:
Of course, you should also take a look at VMware's VMCI. If we're going
to have a socket interface, if we can have a compatible userspace
interface, that would probably be a good
Linus, please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/avi/kvm.git kvm-updates/2.6.28
to receive the kvm updates for the 2.6.28 merge window. Changes include
performance improvement, pci device assignment, and improved emulation
accuracy.
Alexander Graf (1):
KVM: Ignore
Hi,
while trying to run the current openSUSE on git KVM I found that the
installation doesn't even boot properly. I bisected the problem down to
commit 641fb03992b20aa640781a245f6b7136f0b845e4, as of which udev shows
strange errors.
I reproduced the incorrect behavior reliably on an AMD machine
Andrew,
On Wed, Oct 15, 2008 at 07:18:52AM -0700, Andrew Biggadike wrote:
Gleb Natapov [EMAIL PROTECTED] wrote:
Of course, you should also take a look at VMware's VMCI. If we're going
to have a socket interface, if we can have a compatible userspace
interface, that would probably be a
Gleb Natapov wrote:
Andrew,
On Wed, Oct 15, 2008 at 07:18:52AM -0700, Andrew Biggadike wrote:
Gleb Natapov [EMAIL PROTECTED] wrote:
Of course, you should also take a look at VMware's VMCI. If we're going
to have a socket interface, if we can have a compatible userspace
interface,
Bugs item #2149609, was opened at 2008-10-06 16:25
Message generated for change (Comment added) made by kiszka
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2149609group_id=180599
Please note that this message will contain a full copy of the comment
Bugs item #2168011, was opened at 2008-10-15 09:53
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2168011group_id=180599
Please note that this message will contain a full copy of
Sorry if for the cross-post but I posted on this issue the Fedora list
and this seems to work for others.
I am trying to run Fedora 10 beta on KVM-77 (F9 host), during boot I get:
1) Either mouse or keyboard, or both is dead
2) In text mode install, no harddrives are detected.
3) In every case
Gleb Natapov [EMAIL PROTECTED] wrote:
On Wed, Oct 15, 2008 at 07:18:52AM -0700, Andrew Biggadike wrote:
Gleb Natapov [EMAIL PROTECTED] wrote:
Of course, you should also take a look at VMware's VMCI. If we're going
to have a socket interface, if we can have a compatible userspace
* On Tuesday 14 Oct 2008 22:46:37 Zwane Mwaikambo wrote:
On Tue, 14 Oct 2008, Han, Weidong wrote:
Zwane Mwaikambo wrote:
Hi,
I've been trying to get a Linux guest working with PCI
passthrough
of an ethernet card using the vtd branches. The device detection
works and the
Avi Kivity wrote:
Farkas Levente wrote:
ok i don't know any other solution so
- install kvm-71 to the host
- install a guest mandrake-10 truly minimal install into file image
- upgrade to kvm-76 and the guest no longer boot.
so i've uploaded it for you into:
Gleb Natapov [EMAIL PROTECTED] wrote:
On Wed, Oct 15, 2008 at 07:18:52AM -0700, Andrew Biggadike wrote:
Gleb Natapov [EMAIL PROTECTED] wrote:
Of course, you should also take a look at VMware's VMCI. If we're going
to have a socket interface, if we can have a compatible userspace
* On Wednesday 15 Oct 2008 12:41:17 Sheng Yang wrote:
On Wednesday 15 October 2008 15:03:39 Amit Shah wrote:
* On Wednesday 15 Oct 2008 08:06:30 Sheng Yang wrote:
@@ -4115,6 +4116,9 @@ struct kvm *kvm_arch_create_vm(void)
INIT_LIST_HEAD(kvm-arch.active_mmu_pages);
Kevin O'Connor wrote:
Kevin, will you accept qemu-specific and kvm-specific patches to
SeaBIOS? I'd like to avoid permanent deltas.
Yes.
Thanks.
There is already code specific to qemu and coreboot. I don't see any
issues with having a CONFIG_KVM build option.
Most kvm
Bugs item #2168057, was opened at 2008-10-15 12:15
Message generated for change (Comment added) made by kiszka
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2168057group_id=180599
Please note that this message will contain a full copy of the comment
On Tue, Oct 14, 2008 at 01:16:19PM -0500, Anthony Liguori wrote:
sockets have a concept of addressing and a vfs has a natural
namespace. That's what I was suggesting those interfaces.
What address should look like if we will choose to use new address family?
An example will help me
On 19.09.2008, at 17:56, Joerg Roedel wrote:
On Fri, Sep 19, 2008 at 04:36:00PM +0200, Joerg Roedel wrote:
On Wed, Sep 17, 2008 at 03:41:17PM +0200, Alexander Graf wrote:
To be usable, this patchset requires the two simple changes in the
userspace
part, that I sent to the list with the
Amit Shah wrote:
* On Wednesday 15 Oct 2008 12:41:17 Sheng Yang wrote:
On Wednesday 15 October 2008 15:03:39 Amit Shah wrote:
* On Wednesday 15 Oct 2008 08:06:30 Sheng Yang wrote:
@@ -4115,6 +4116,9 @@ struct kvm *kvm_arch_create_vm(void)
INIT_LIST_HEAD(kvm-arch.active_mmu_pages);
Bugs item #2168011, was opened at 2008-10-15 09:53
Message generated for change (Comment added) made by nuitari3
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2168011group_id=180599
Please note that this message will contain a full copy of the comment
This patch implements the GIF flag and the clgi and stgi instructions that
set this flag. Only if the flag is set (default), interrupts can be received by
the CPU.
To keep the information about that somewhere, this patch adds a new hidden
flags vector. that is used to store information that does
This adds the #VMEXIT intercept, so we return to the level 1 guest
when something happens in the level 2 guest that should return to
the level 1 guest.
v2 implements HIF handling and cleans up exception interception
v3 adds support for V_INTR_MASKING_MASK
v4 uses the host page hsave
These are helpers for the nested SVM implementation.
- nsvm_printk implements a debug printk variant
- nested_svm_do calls a handler that can accesses gpa-based memory
v3 makes use of the new permission checker
Signed-off-by: Alexander Graf [EMAIL PROTECTED]
---
arch/x86/kvm/svm.c | 88
This implements the VMLOAD and VMSAVE instructions, that usually surround
the VMRUN instructions. Both instructions load / restore the same elements,
so we only need to implement them once.
v2 fixes CPL checking and replaces memcpy by assignments
v3 makes use of the new permission checking
This patch adds the CPUID feature flag for SVM in the x86 Linux headers.
Signed-off-by: Alexander Graf [EMAIL PROTECTED]
---
include/asm-x86/cpufeature.h |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/include/asm-x86/cpufeature.h b/include/asm-x86/cpufeature.h
index
Implement the hsave MSR, that gives the VCPU a GPA to save the
old guest state in.
v2 allows userspace to save/restore hsave
v4 dummys out the hsave MSR, so we use a host page
Signed-off-by: Alexander Graf [EMAIL PROTECTED]
---
arch/x86/kvm/kvm_svm.h |1 +
arch/x86/kvm/svm.c | 12
This patch provides a relatively simple method for exercising various
features of qemu by interacting with the guest via serial and qemu
via the monitor that individual developers can use to validate that
their changes haven't broken feature/function. Such tests
need to be very accessable and
This patch places the qemu-test framework and tests into the qemu source tree.
There are a number of components to this patch:
- Python-based framework for interacting with the qemu process and the guest
via serial console and qemu monitor.
- Several intial tests cases for exercising various
On Wednesday 15 October 2008, Ryan Harper wrote:
This patch places the qemu-test framework and tests into the qemu source
tree. There are a number of components to this patch:
Is there any point having this in the qemu repository?
AFAICS it gains nothing from being integrated with qemu. It
Avi Kivity wrote:
Uri Lublin wrote:
Currently qemu_fopen_ops accepts both get_buffer and put_buffer, but
if both are given (non NULL) we encounter problems:
1. There is only one buffer and index, which may mean data corruption.
2. qemu_flush (which is also called by qemu_fclose) is writing
On Wed, Oct 15, 2008 at 07:46:49PM +0200, Avi Kivity wrote:
Kevin O'Connor wrote:
There is already code specific to qemu and coreboot. I don't see any
issues with having a CONFIG_KVM build option.
Most kvm specific patches would actually be fairly generic features that
haven't been
Is there a bugzilla I can post this issue to?
I'm still unable to get freebsd 7.0 booting after install with if=scsi on
kvm-77
Thanks in advance,
Sterling Windmill
- Forwarded Message -
From: Sterling Windmill [EMAIL PROTECTED]
To: Avi Kivity [EMAIL PROTECTED]
Cc:
Anthony Liguori wrote:
Anthony Liguori wrote:
Also, having checks and the read and write functions to determine if
the is_write flag is set along with whether buf_index 0 that
fprintf()'d and aborted would be good for debugging.
I have a patch that does this along with fixing a few other
Hello
My aim is to have a VM with 2 network interfaces, one bridged to the outside
world and the other bridged on a private network. From the private interface
this VM runs DHCP and PXE services to start and install VM's which have one
network interface tapped on the private bridge.
All
Uri Lublin wrote:
Anthony, this is a problem with qemu-upstream so I'd like to solve it
in a way that's acceptable for upstream.
The proposed patch is less that ideal IMO as it introduces
limitations on what you can do with a file. An alternative
implementation would add a read/write mode
Uri Lublin wrote:
Anthony Liguori wrote:
I have already cut your text, but I don't understand the comment about
not being full duplex. Is there a reason why migration needs to be
bidirectional? I don't think there's a fundamental reason it needs to
be and I think there are some advantages
Paul Brook wrote:
On Wednesday 15 October 2008, Ryan Harper wrote:
This patch places the qemu-test framework and tests into the qemu source
tree. There are a number of components to this patch:
Is there any point having this in the qemu repository?
In tree unit testing. The
61 matches
Mail list logo
