Avi Kivity wrote:
> Farkas Levente wrote:
>> Avi Kivity wrote:
>>
>>> Farkas Levente wrote:
>>>
>> we did a quick test against this version and it's turn out the smp
>> guests are still not working. even if we start only one linux guest
>> with
>> 4cpu on 4cpu host the guest
Izik Eidus wrote:
> can you send me your kvmctl.c file so i will look at it?
> it is somewhat hard to me understand how you did the things that way
I'm trying to back a vm with memory coming from a file map, see patch
attached against kvm-46 (was also attached earlier in this thread).
I've made k
On Mon, 2007-10-15 at 13:15 +0200, Gerd Hoffmann wrote:
> Izik Eidus wrote:
> > On Mon, 2007-10-15 at 13:00 +0200, Gerd Hoffmann wrote:
> >> Gerd Hoffmann wrote:
> >>
> >>> Something like this? (compiles, not tested yet).
> >> Hmm, no-go, results in "kvm_create_vcpu: Cannot allocate memory".
> >
>
Izik Eidus wrote:
> On Mon, 2007-10-15 at 13:00 +0200, Gerd Hoffmann wrote:
>> Gerd Hoffmann wrote:
>>
>>> Something like this? (compiles, not tested yet).
>> Hmm, no-go, results in "kvm_create_vcpu: Cannot allocate memory".
>
> try use slot bigger bigger than 5 and smaller than 8
It doesn't come
On Mon, 2007-10-15 at 13:00 +0200, Gerd Hoffmann wrote:
> Gerd Hoffmann wrote:
>
> > Something like this? (compiles, not tested yet).
>
> Hmm, no-go, results in "kvm_create_vcpu: Cannot allocate memory".
try use slot bigger bigger than 5 and smaller than 8
> cheers,
> Gerd
>
> ---
Gerd Hoffmann wrote:
> Something like this? (compiles, not tested yet).
Hmm, no-go, results in "kvm_create_vcpu: Cannot allocate memory".
cheers,
Gerd
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping throug
Avi Kivity wrote:
> Gerd Hoffmann wrote:
>> Avi Kivity wrote:
>>
>>> We've now switched to allocating guest memory in userspace rather than
>>> in the kernel.
>>>
>> Hmm, a quick glimpse over kvmctl.h doesn't show an obvious way how to
>> use that. If I want to back vm memory with a file m
Farkas Levente wrote:
> Avi Kivity wrote:
>
>> Farkas Levente wrote:
>>
> we did a quick test against this version and it's turn out the smp
> guests are still not working. even if we start only one linux guest
> with
> 4cpu on 4cpu host the guest kernel hangs at random stag
Gerd Hoffmann wrote:
> Avi Kivity wrote:
>
>> We've now switched to allocating guest memory in userspace rather than
>> in the kernel.
>>
>
> Hmm, a quick glimpse over kvmctl.h doesn't show an obvious way how to
> use that. If I want to back vm memory with a file mapping, how can I do
> th
Avi Kivity wrote:
> We've now switched to allocating guest memory in userspace rather than
> in the kernel.
Hmm, a quick glimpse over kvmctl.h doesn't show an obvious way how to
use that. If I want to back vm memory with a file mapping, how can I do
that?
cheers,
Gerd
---
Jun Koi wrote:
> On 10/10/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
>
>> Jun Koi wrote:
>>
>>> On 10/10/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
>>>
>>>
Jun Koi wrote:
> Hi,
>
> On 10/10/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
>
>
>
On 10/10/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
> Jun Koi wrote:
> > On 10/10/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
> >
> >> Jun Koi wrote:
> >>
> >>> Hi,
> >>>
> >>> On 10/10/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
> >>>
> >>>
> We've now switched to allocating guest memory in usersp
Thanks for clearing that up.
On 10/10/07, Dor Laor <[EMAIL PROTECTED]> wrote:
>
> Haydn Solomon wrote:
> > Should we be seeing a mmap file when running guests now or do we have
> > to use a special flag when running kvm?
> >
> Nope, the default is user space allocation were a regular malloc is us
Haydn Solomon wrote:
> Should we be seeing a mmap file when running guests now or do we have
> to use a special flag when running kvm?
>
Nope, the default is user space allocation were a regular malloc is used
for allocating the guest ram from userspace.
The mmap is for future shared memory imple
Should we be seeing a mmap file when running guests now or do we have to use
a special flag when running kvm?
On 10/10/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
>
> Daniel P. Berrange wrote:
> > On Wed, Oct 10, 2007 at 10:28:24AM +0200, Avi Kivity wrote:
> >
> >> We've now switched to allocating g
Daniel P. Berrange wrote:
> On Wed, Oct 10, 2007 at 10:28:24AM +0200, Avi Kivity wrote:
>
>> We've now switched to allocating guest memory in userspace rather than
>> in the kernel. This is important if you have a mainframe, but also if
>> you want to share memory between guests and implement n
On Wed, Oct 10, 2007 at 10:28:24AM +0200, Avi Kivity wrote:
> We've now switched to allocating guest memory in userspace rather than
> in the kernel. This is important if you have a mainframe, but also if
> you want to share memory between guests and implement nice features like
> swapping.
Is th
Avi Kivity wrote:
> Farkas Levente wrote:
we did a quick test against this version and it's turn out the smp
guests are still not working. even if we start only one linux guest
with
4cpu on 4cpu host the guest kernel hangs at random stages of the kernel
loading process (if
Farkas Levente wrote:
>>> we did a quick test against this version and it's turn out the smp
>>> guests are still not working. even if we start only one linux guest with
>>> 4cpu on 4cpu host the guest kernel hangs at random stages of the kernel
>>> loading process (if we run more smp guests then t
Avi Kivity wrote:
> Farkas Levente wrote:
>> Avi Kivity wrote:
>>
>>> We've now switched to allocating guest memory in userspace rather than
>>> in the kernel. This is important if you have a mainframe, but also if
>>> you want to share memory between guests and implement nice features like
>>>
Farkas Levente wrote:
> Avi Kivity wrote:
>
>> We've now switched to allocating guest memory in userspace rather than
>> in the kernel. This is important if you have a mainframe, but also if
>> you want to share memory between guests and implement nice features like
>> swapping.
>>
>
> we
Avi Kivity wrote:
> We've now switched to allocating guest memory in userspace rather than
> in the kernel. This is important if you have a mainframe, but also if
> you want to share memory between guests and implement nice features like
> swapping.
we did a quick test against this version and it
Avi Kivity wrote:
> Farkas Levente wrote:
>> Avi Kivity wrote:
>>
>>> We've now switched to allocating guest memory in userspace rather than
>>> in the kernel. This is important if you have a mainframe, but also if
>>> you want to share memory between guests and implement nice features like
>>>
Farkas Levente wrote:
> Avi Kivity wrote:
>> We've now switched to allocating guest memory in userspace rather than
>> in the kernel. This is important if you have a mainframe, but also if
>> you want to share memory between guests and implement nice features like
>> swapping.
>>
>> Changes since
Farkas Levente wrote:
> Avi Kivity wrote:
>
>> We've now switched to allocating guest memory in userspace rather than
>> in the kernel. This is important if you have a mainframe, but also if
>> you want to share memory between guests and implement nice features like
>> swapping.
>>
>> Changes s
Avi Kivity wrote:
> We've now switched to allocating guest memory in userspace rather than
> in the kernel. This is important if you have a mainframe, but also if
> you want to share memory between guests and implement nice features like
> swapping.
>
> Changes since kvm-45:
> - fix host oops on
Jun Koi wrote:
> On 10/10/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
>
>> Jun Koi wrote:
>>
>>> Hi,
>>>
>>> On 10/10/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
>>>
>>>
We've now switched to allocating guest memory in userspace rather than
in the kernel. This is important if
On 10/10/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
> Jun Koi wrote:
> > Hi,
> >
> > On 10/10/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
> >
> >> We've now switched to allocating guest memory in userspace rather than
> >> in the kernel. This is important if you have a mainframe, but also if
> >> you
Jun Koi wrote:
> Hi,
>
> On 10/10/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
>
>> We've now switched to allocating guest memory in userspace rather than
>> in the kernel. This is important if you have a mainframe, but also if
>> you want to share memory between guests and implement nice features
Hi,
On 10/10/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
> We've now switched to allocating guest memory in userspace rather than
> in the kernel. This is important if you have a mainframe, but also if
> you want to share memory between guests and implement nice features like
> swapping.
This is i
30 matches
Mail list logo
