Muli Ben-Yehuda wrote:
> Thanks for the analysis, this problem is understood. Avi commited a
> fix for -14 a few days back, but the fix re-breaks
> --kerneldir. Reenabling --kerneldir is simple - see attached patch -
> but since this is obviously a fragile area, I decided not to push for
> its incl
Anthony Liguori wrote:
> Howdy,
>
> Here's a tiny patch that adds a i386-kvm target. The main difference
> between the i386-kvm and i386-softmmu target is that the -kvm target
> does not have any of the dyngen infrastructure. This means that it
> will build with gcc-4. I know you can do --cc=
Aurelien Jarno wrote:
> The bad news is that kvm-14 seems to be a lot slower than kvm-12 +
> modules from kernel 2.6.20. This is the case with a GNU/kFreeBSD guest.
> kvm-12 was about 1.5 time faster than qemu + kqemu. kvm-20 is slower
> than qemu without kqemu...
>
> Does anybody have an idea abou
Omar Khan wrote:
> Dor Laor <[EMAIL PROTECTED]> writes:
>
>
>
>> Theoretically speaking the answer is yes, vmcall is a special
>> instruction that it one and only purpose is the exit from the guest.
>> While mov cr3 instruction might be bound to other actions of the
>> processor and might have m
On Tue, 20 Feb 2007, Rusty Russell wrote:
> Stable ABIs are hard, and this is CONFIG_EXPERIMENTAL after all. I
> don't think KVM needs ABI stability until CONFIG_EXPERIMENTAL is removed
> (of course, sooner is always nice if it doesn't create problems).
FC7 will ship with kvm and 2.6.21, so chan
Jun Koi wrote:
> Howdy Anthony,
>
>> Here's a tiny patch that adds a i386-kvm target. The main difference
>> between the i386-kvm and i386-softmmu target is that the -kvm target
>> does not have any of the dyngen infrastructure. This means that it will
>> build with gcc-4. I know you can do --cc
Howdy Anthony,
> Here's a tiny patch that adds a i386-kvm target. The main difference
> between the i386-kvm and i386-softmmu target is that the -kvm target
> does not have any of the dyngen infrastructure. This means that it will
> build with gcc-4. I know you can do --cc=gcc to use gcc-4 but
Howdy,
Here's a tiny patch that adds a i386-kvm target. The main difference
between the i386-kvm and i386-softmmu target is that the -kvm target
does not have any of the dyngen infrastructure. This means that it will
build with gcc-4. I know you can do --cc=gcc to use gcc-4 but quite a
few
On Mon, 2007-02-19 at 10:37 -0500, James Morris wrote:
> On Mon, 19 Feb 2007, Avi Kivity wrote:
>
> > Daniel P. Berrange wrote:
> > >> Note that if you use the modules from Linux 2.6.20, you need to use
> > >> kvm-12. You can use kvm-14 with Linux 2.6.20, provided you use the
> > >> external mo
Dor Laor <[EMAIL PROTECTED]> writes:
>
> Theoretically speaking the answer is yes, vmcall is a special
> instruction that it one and only purpose is the exit from the guest.
> While mov cr3 instruction might be bound to other actions of the
> processor and might have more effects on the pipeline
Thanks for the analysis, this problem is understood. Avi commited a
fix for -14 a few days back, but the fix re-breaks
--kerneldir. Reenabling --kerneldir is simple - see attached patch -
but since this is obviously a fragile area, I decided not to push for
its inclusion. Maybe I'm the sole --kerne
Avi Kivity a écrit :
> The big news here is the update to qemu 0.9.0.
>
> Changes from kvm-13:
> - qemu 0.9.0
>- too many goodies to list
>- kvm can no longer share qemu's bios on Intel hosts due to real mode
> trouble. use the supplied bios.
> - migration now based on Anthony Liguori's
Muli Ben-Yehuda <[EMAIL PROTECTED]> writes:
> That does not explain why the change you made (from ?= to :=) made any
> difference. Could you send a full log of ./configure && make && make
> install with and without your change?
>
Well from what I have observed this makes a difference because in
>> The hypercall sequence does not avoid a vmexit. The guest issues a
>> vmcall instruction, which is trapped and processed by the host.
>>
>
>Thanks for replying Avi. In your response
> (http://article.gmane.org/gmane.linux.kernel/481457) to the
announcement
>of the
> KVM paravirtualization patch
Avi Kivity <[EMAIL PROTECTED]> writes:
> The hypercall sequence does not avoid a vmexit. The guest issues a
> vmcall instruction, which is trapped and processed by the host.
>
Thanks for replying Avi. In your response
(http://article.gmane.org/gmane.linux.kernel/481457) to the announcement o
Jorge Boncompte [DTI2] wrote:
> Hi,
>
> My kvm/qemu setup exits realiably with the error from the subject every
> time that I do a reboot at the guest. Aside from this annoyance kvm/qemu
> works pretty well on my workload.
>
> HOST: Debian (etch) + kernel.org 2.6.20 (32bits) + kvm-14
Hi,
My kvm/qemu setup exits realiably with the error from the subject every
time that I do a reboot at the guest. Aside from this annoyance kvm/qemu
works pretty well on my workload.
HOST: Debian (etch) + kernel.org 2.6.20 (32bits) + kvm-14
GUEST: Custom embedded distribution +
James Morris wrote:
> It's traditional for the mainline kernel to maintain backward
> compatibility with existing userspace ABIs (e.g. syscalls).
>
> The idea of a userspace application breaking because of a mainline kernel
> upgrade is not acceptable to users and also pretty much unsupportable b
On Mon, 19 Feb 2007, Avi Kivity wrote:
> Daniel P. Berrange wrote:
> >> Note that if you use the modules from Linux 2.6.20, you need to use
> >> kvm-12. You can use kvm-14 with Linux 2.6.20, provided you use the
> >> external module included in kvm-14.
> >>
> >
> > Is there back-compatabil
Omar Khan wrote:
> Andreas Hasenack <[EMAIL PROTECTED]> writes:
>
>> How are you guys in general dealing with the gcc-3.x requirement? Most
>> distros
>> already use gcc-4.x.
>>
>>
>
> gcc-3.x for qemu? Here is how you can install gcc-3.x without breaking
> gcc-4.x:
>
> http://en.opensus
Omar Khan wrote:
> hi,
>
>I have a couple of kvm/kernel newbie questions:
>
>1. What is the sequence of events for a paravirtualization hypercall? I
> understand how VMX architecture works, but how does the paravirt fit in? When
> we
> make a paravirt sys call we avoid a VMexit, but which
Andreas Hasenack <[EMAIL PROTECTED]> writes:
>
> How are you guys in general dealing with the gcc-3.x requirement? Most
> distros
> already use gcc-4.x.
>
gcc-3.x for qemu? Here is how you can install gcc-3.x without breaking gcc-4.x:
http://en.opensuse.org/Qemu_with_kqemu_kernel_module_suppo
hi,
I have a couple of kvm/kernel newbie questions:
1. What is the sequence of events for a paravirtualization hypercall? I
understand how VMX architecture works, but how does the paravirt fit in? When we
make a paravirt sys call we avoid a VMexit, but which address space does the
call go t
kvm kernel code is now developed using git. This was done for two reasons:
- with the paravirtualization work, we have code in the kernel beyond
drivers/kvm/. Subversion is not quite up to hosting an entire kernel
tree efficiently.
- people have expressed interest in maintaining long-term branc
Andreas Hasenack wrote:
> How are you guys in general dealing with the gcc-3.x requirement? Most
> distros
> already use gcc-4.x.
>
If you're not planning to use the -no-kvm option, you can use gcc 4.
Otherwise, you can use the gcc 3 compat packages that most distros provide.
Note that onl
On Monday 19 February 2007 09:01:36 Avi Kivity wrote:
> The big news here is the update to qemu 0.9.0.
>
> Changes from kvm-13:
> - qemu 0.9.0
>- too many goodies to list
>- kvm can no longer share qemu's bios on Intel hosts due to real mode
> trouble. use the supplied bios.
> - migration
Daniel P. Berrange wrote:
>> Note that if you use the modules from Linux 2.6.20, you need to use
>> kvm-12. You can use kvm-14 with Linux 2.6.20, provided you use the
>> external module included in kvm-14.
>>
>
> Is there back-compatability in the reverse direction ? ie, will the
> new kmod
On Mon, Feb 19, 2007 at 01:01:36PM +0200, Avi Kivity wrote:
> The big news here is the update to qemu 0.9.0.
>
> Changes from kvm-13:
> - qemu 0.9.0
>- too many goodies to list
>- kvm can no longer share qemu's bios on Intel hosts due to real mode
> trouble. use the supplied bios.
> - mi
The big news here is the update to qemu 0.9.0.
Changes from kvm-13:
- qemu 0.9.0
- too many goodies to list
- kvm can no longer share qemu's bios on Intel hosts due to real mode
trouble. use the supplied bios.
- migration now based on Anthony Liguori's live migration patches (Uri
Lublin)
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
Index: linux-2.6/drivers/kvm/kvm_main.c
===
--- linux-2.6.orig/drivers/kvm/kvm_main.c
+++ linux-2.6/drivers/kvm/kvm_main.c
@@ -2229,13 +2229,13 @@ static void kvm_exit_debug(void)
static
From: Joerg Roedel <[EMAIL PROTECTED]>
This patch changes the SVM code to intercept SMIs and handle it
outside the guest.
Signed-off-by: Joerg Roedel <[EMAIL PROTECTED]>
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
Index: linux-2.6/drivers/kvm/svm.c
=
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
Index: linux-2.6/drivers/kvm/svm.c
===
--- linux-2.6.orig/drivers/kvm/svm.c
+++ linux-2.6/drivers/kvm/svm.c
@@ -554,7 +554,7 @@ static void init_vmcb(struct vmcb *vmcb)
* cr0 val
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
Index: linux-2.6/drivers/kvm/kvm_main.c
===
--- linux-2.6.orig/drivers/kvm/kvm_main.c
+++ linux-2.6/drivers/kvm/kvm_main.c
@@ -1138,6 +1138,42 @@ int emulate_instruction(struct kvm_vcpu
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
Index: linux-2.6/drivers/kvm/svm.c
===
--- linux-2.6.orig/drivers/kvm/svm.c
+++ linux-2.6/drivers/kvm/svm.c
@@ -1076,6 +1076,20 @@ static int halt_interception(struct kvm_
return 0
From: Ingo Molnar <[EMAIL PROTECTED]>
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
Index: linux-2.6/include/linux/kvm_para.h
===
--- linux-2.6.orig/include/linux/kvm_para.h
+++ linux-2.6/include/linux/kvm_para.h
@@ -52,4 +52,22 @@ s
From: Ingo Molnar <[EMAIL PROTECTED]>
This adds a special MSR based hypercall API to KVM. This is to be
used by paravirtual kernels and virtual drivers.
Signed-off-by: Ingo Molnar <[EMAIL PROTECTED]>
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
Index: linux-2.6/drivers/kvm/kvm_main.c
==
From: Markus Rechberger <[EMAIL PROTECTED]>
Besides using an established api, this allows using kvm in older kernels.
Signed-off-by: Markus Rechberger <[EMAIL PROTECTED]>
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
Index: linux-2.6/drivers/kvm/mmu.c
From: Ahmed S. Darwish <[EMAIL PROTECTED]>
Signed-off-by: Ahmed S. Darwish <[EMAIL PROTECTED]>
Signed-off-by: Dor Laor <[EMAIL PROTECTED]>
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
Index: linux-2.6/drivers/kvm/svm.c
===
--- linux
From: Markus Rechberger <[EMAIL PROTECTED]>
From: Joerg Roedel <[EMAIL PROTECTED]>
The whole thing is rotten, but this allows vmx to boot with the guest reboot
fix.
Signed-off-by: Markus Rechberger <[EMAIL PROTECTED]>
Signed-off-by: Joerg Roedel <[EMAIL PROTECTED]>
Signed-off-by: Avi Kivity <[EMA
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
Index: linux-2.6/drivers/kvm/kvm_main.c
===
--- linux-2.6.orig/drivers/kvm/kvm_main.c
+++ linux-2.6/drivers/kvm/kvm_main.c
@@ -126,10 +126,8 @@ static inline int valid_vcpu(int n)
From: Jeremy Katz <[EMAIL PROTECTED]>
This gives it more chances of surviving suspend.
Signed-off-by: Jeremy Katz <[EMAIL PROTECTED]>
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
Index: linux-2.6/drivers/kvm/kvm_main.c
===
--- linu
We fail to mark a page dirty in three cases:
- setting the accessed bit in a pte
- setting the dirty bit in a pte
- emulating a write into a pagetable
This fix adds the missing cases.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
Index: linux-2.6/drivers/kvm/paging_tmpl.h
==
Following is a series of kvm updates. Please apply to Linux 2.6.21.
--
error compiling committee.c: too many arguments to function
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel
Anthony Liguori wrote:
> Avi Kivity wrote:
>> Avi Kivity wrote:
I'll have to try and setup a 64 bit system. I cannot reproduce on
my 32bit system with your test program.
>>>
>>> It may be related to 64-bit (as that uses sse for floating point),
>>> or to the fact that I use ssh on
44 matches
Mail list logo
