Avi Kivity wrote:
> 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 pr
Anthony Liguori wrote:
> Avi Kivity wrote:
>> Anthony Liguori wrote:
>>> Avi Kivity wrote:
Laurent Vivier wrote:
> There are remaining issues : libposix-aio uses kernel AIO, so files
> must be
> opened using O_DIRECT and buffers must be aligned. libposix-aio is
> able to
Avi Kivity wrote:
> Laurent Vivier wrote:
>>
>>> Would it be possible to merge the kvm part, and maybe to send it to the
>>> qemu mailing list?
>>>
>>
>> I can try to send it to qemu mailing list but I think it is not useful
>> for pure
>> qemu. It seems to improve performance only with kvm.
Laurent Vivier wrote:
>
>> Would it be possible to merge the kvm part, and maybe to send it to the
>> qemu mailing list?
>>
>
> I can try to send it to qemu mailing list but I think it is not useful for
> pure
> qemu. It seems to improve performance only with kvm.
>
> Avi, your opinion ?
Aurelien Jarno wrote:
> Laurent Vivier a écrit :
>> Anthony Liguori wrote:
>>> Laurent Vivier wrote:
Avi Kivity wrote:
> Aurelien Jarno wrote:
>
>>
>>
>>> What is your disk image file format, or are you using a partition?
>>>
>>>
Laurent Vivier a écrit :
> Anthony Liguori wrote:
>> Laurent Vivier wrote:
>>> Avi Kivity wrote:
>>>
Aurelien Jarno wrote:
>
>
>> What is your disk image file format, or are you using a partition?
>>
>>
> I am using a raw image file
Avi Kivity wrote:
> Anthony Liguori wrote:
>> Avi Kivity wrote:
>>> Laurent Vivier wrote:
There are remaining issues : libposix-aio uses kernel AIO, so files
must be
opened using O_DIRECT and buffers must be aligned. libposix-aio is
able to
manage other cases but this has
Anthony Liguori wrote:
> Avi Kivity wrote:
>> Laurent Vivier wrote:
>>> There are remaining issues : libposix-aio uses kernel AIO, so files
>>> must be
>>> opened using O_DIRECT and buffers must be aligned. libposix-aio is
>>> able to
>>> manage other cases but this has a performance cost.
>>>
>>
Avi Kivity wrote:
> Laurent Vivier wrote:
>> There are remaining issues : libposix-aio uses kernel AIO, so files
>> must be
>> opened using O_DIRECT and buffers must be aligned. libposix-aio is
>> able to
>> manage other cases but this has a performance cost.
>>
>>
>
> Because the guest is als
Laurent Vivier wrote:
> There are remaining issues : libposix-aio uses kernel AIO, so files must be
> opened using O_DIRECT and buffers must be aligned. libposix-aio is able to
> manage other cases but this has a performance cost.
>
>
Because the guest is also doing dma, the buffers are expecte
Anthony Liguori wrote:
> Laurent Vivier wrote:
>> Avi Kivity wrote:
>>
>>> Aurelien Jarno wrote:
>>>
> What is your disk image file format, or are you using a partition?
>
>
I am using a raw image file on an ext3 partition.
>>>
Anthony Liguori wrote:
> Laurent Vivier wrote:
>> Avi Kivity wrote:
>>
>>> Aurelien Jarno wrote:
>>>
> What is your disk image file format, or are you using a partition?
>
>
I am using a raw image file on an ext3 partition.
>>>
Laurent Vivier wrote:
> Avi Kivity wrote:
>
>> Aurelien Jarno wrote:
>>
>>>
>>>
What is your disk image file format, or are you using a partition?
>>> I am using a raw image file on an ext3 partition.
>>>
>>>
>>>
Do the results change (o
Avi Kivity wrote:
> Aurelien Jarno wrote:
>>
>>> What is your disk image file format, or are you using a partition?
>>>
>> I am using a raw image file on an ext3 partition.
>>
>>
>>> Do the results change (on kvm-14) if you pin the guest to a core with
>>> 'taskset 1 qemu ...'
>>>
Aurelien Jarno wrote:
>
>> What is your disk image file format, or are you using a partition?
>>
>
> I am using a raw image file on an ext3 partition.
>
>
>> Do the results change (on kvm-14) if you pin the guest to a core with
>> 'taskset 1 qemu ...'
>>
>
> Bingo. It now works eve
Avi Kivity a écrit :
> Aurelien Jarno wrote:
>> Avi Kivity a écrit :
>>
>>> 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 th
Aurelien Jarno wrote:
> Avi Kivity a écrit :
>
>> 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 slo
Avi Kivity a écrit :
> 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...
>>
>> D
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
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
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
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
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
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
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)
31 matches
Mail list logo
