On Tue, Feb 20, 2007 at 09:46:17AM +0200, Avi Kivity wrote:
> 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
On 2/19/07, Omar Khan <[EMAIL PROTECTED]> wrote:
> 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?
> >
>
> We
Rusty Russell wrote:
> On Tue, 2007-02-20 at 11:55 +0900, 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 infrastru
On Tue, 2007-02-20 at 11:55 +0900, 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
> > b
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
Andreas Hasenack wrote:
>> This looks like another case of missing real mode emulation on Intel
>> hosts. If you have access to an AMD machine with svm support, you might
>> try it on that to confirm.
>>
>
> I don't, sorry.
>
>
Ok. I'll try it later on.
--
error compiling committee.c:
On Tuesday 20 February 2007 13:54:53 Avi Kivity wrote:
> Andreas Hasenack wrote:
> > kernel 2.6.20 vanilla
> > kvm 14 kernel modules and userspace + "qemu kvm target" patch
> > everything built with gcc 4
> >
> > Is this supposed to work? The vdisk.img was created with qemu-img
> > following the ho
Andreas Hasenack wrote:
> kernel 2.6.20 vanilla
> kvm 14 kernel modules and userspace + "qemu kvm target" patch
> everything built with gcc 4
>
> Is this supposed to work? The vdisk.img was created with qemu-img following
> the howto (http://kvm.qumranet.com/kvmwiki/HOWTO). I don't have the iso fo
Anthony Liguori wrote:
>
> Can you wait on that? I'll submit a better one tonight. It was just
> an RFC :-)
>
Ok.
--
error compiling committee.c: too many arguments to function
-
Take Surveys. Earn Cash. Influence the
Avi Kivity wrote:
> Anthony Liguori wrote:
That kills the -no-kvm switch, which allows a single binary to be
used both with and without kvm. Or do you think both
target-i386+kvm and target-kvm ought to be kept?
>>>
>>> I meant here: target-i386 (with kvm support)
Anthony Liguori wrote:
>>>
>>> That kills the -no-kvm switch, which allows a single binary to be
>>> used both with and without kvm. Or do you think both
>>> target-i386+kvm and target-kvm ought to be kept?
>>>
>>>
>>
>> I meant here: target-i386 (with kvm support) and target-i386-kvm.
>
> ta
Avi Kivity wrote:
> Avi Kivity wrote:
>> 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
>>> mea
On Tuesday 20 February 2007 13:16:00 Andreas Hasenack wrote:
> kernel 2.6.20 vanilla
> kvm 14 kernel modules and userspace + "qemu kvm target" patch
> everything built with gcc 4
>
> Is this supposed to work? The vdisk.img was created with qemu-img following
> the howto (http://kvm.qumranet.com/kvm
kernel 2.6.20 vanilla
kvm 14 kernel modules and userspace + "qemu kvm target" patch
everything built with gcc 4
Is this supposed to work? The vdisk.img was created with qemu-img following
the howto (http://kvm.qumranet.com/kvmwiki/HOWTO). I don't have the iso for a
boot image, so inserted an ubu
Avi Kivity wrote:
> 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
Avi Kivity wrote:
> 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
>> >Why so many vm switches? First up, a typical I/O system maxes at
>> >about 1Gb/s, right? That would be a gigabit NIC, or striped RAID,
or
>> >something like that. This suggests an average of only about 300
>> >bytes/transfer, to get >150k individual transfers per second? I
>> >thought block
Sweet deal. I just applied the patch to v14, and compiled with gcc
4.1.1. Thanks a lot!
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opini
>
> "This utilizes the cr3 filter capability of the hardware - if this works out
> then no VM exit happens"
>
> NO VM-exits happen. h... maybe I need to go over the intel manuals more
> thoroughly, however any hints will be most welcomed.
Hi,
I think you're confused a bit ;)
the cr3 filt
19 matches
Mail list logo
