On Sat, 2009-05-02 at 10:52 +0300, Avi Kivity wrote:
> Hollis Blanchard wrote:
> >> In that case it's sufficient to have the build system use the upstream
> >> kvm integration (CONFIG_KVM) rather than the qemu-kvm integration
> >> (USE_KVM).
> >>
> >
> > OK, I give up... how is this supposed
On Fri, May 01, 2009 at 04:23:45PM -0500, Hollis Blanchard wrote:
> I can use output from an old 'make sync' for now, but obviously that
> doesn't help with future changes to these headers. Defining a
> process for updating those headers would be useful.
Two thumbs up. People doing kvm developmen
Hollis Blanchard wrote:
On Wed, 2009-04-29 at 11:29 +0300, Avi Kivity wrote:
* configure completely ignores --kerneldir and only uses
kvm/kernel headers instead.
That's intentional.
Huh? If --kerneldir does nothing, why does it exist?
--kerneldir pred
Hollis Blanchard wrote:
They were generated by the old 'make sync' to remove CONFIG_
dependencies. I guess a better way to generate them is a 'make
headers-install' from the kernel tree and grab the results.
'make headers_install' only produces include/asm/kvm.h, which apparent
Hollis Blanchard wrote:
In that case it's sufficient to have the build system use the upstream
kvm integration (CONFIG_KVM) rather than the qemu-kvm integration (USE_KVM).
OK, I give up... how is this supposed to work? Nobody ever sets
CONFIG_KVM or KVM_UPSTREAM, but there are a couple tes
Anthony Liguori wrote:
Hollis Blanchard wrote:
On Wed, 2009-04-29 at 11:29 +0300, Avi Kivity wrote:
* configure completely ignores --kerneldir and only uses
kvm/kernel headers instead.
That's intentional.
Huh? If --kerneldir does nothing, why does it exist?
Hollis Blanchard wrote:
On Wed, 2009-04-29 at 11:29 +0300, Avi Kivity wrote:
* configure completely ignores --kerneldir and only uses
kvm/kernel headers instead.
That's intentional.
Huh? If --kerneldir does nothing, why does it exist?
BTW Avi, if you
On Wed, 2009-04-29 at 11:31 +0300, Avi Kivity wrote:
> Hollis Blanchard wrote:
> >> Since PPC is now supported in upstream QEMU, does it really matter if it
> >> works in qemu-kvm.git?
> >>
> >
> > I was going to take that position too, except Avi asked me specifically
> > if some of the code
On Wed, 2009-04-29 at 11:29 +0300, Avi Kivity wrote:
>
>
> > * configure completely ignores --kerneldir and only uses
> > kvm/kernel headers instead.
> >
>
> That's intentional.
Huh? If --kerneldir does nothing, why does it exist?
> > * The headers in kvm/kernel/arch/foo
Jan Kiszka wrote:
Pushing things upstream is quite difficult because of the very different
infrastructure.
Isn't the midterm goal to get rid of most of these differences (namely
libkvm)?
Yes, but not by removing existing functionality.
No one s
Avi Kivity wrote:
> Jan Kiszka wrote:
>> Avi Kivity wrote:
>>
>> Where/how does the
>> migration code disable dirty logging?
>>
> Should be phase 3 of ram_save_live().
>
But only in qemu-kvm. What is the plan about pushing it upstream? Then
Jan Kiszka wrote:
Avi Kivity wrote:
Where/how does the
migration code disable dirty logging?
Should be phase 3 of ram_save_live().
But only in qemu-kvm. What is the plan about pushing it upstream? Then
we could discuss how to extend the exiting support best
Avi Kivity wrote:
Where/how does the
migration code disable dirty logging?
>>> Should be phase 3 of ram_save_live().
>>>
>>
>> But only in qemu-kvm. What is the plan about pushing it upstream? Then
>> we could discuss how to extend the exiting support best.
>>
>
> P
Jan Kiszka wrote:
That's sort of what's implemented in qemu-kvm.git. In qemu.git vga
logging does not get disabled, which is really broken. It prevents
optimizations like disabling logging when the screen is not displayed to
a human.
Is there a channel that tells vga "nothing will be dis
Avi Kivity wrote:
> Jan Kiszka wrote:
>>> If migration disables dirty memory logging, it must keep the vga logging
>>> enabled, and vice versa.
>>>
>>
>> So we need some notifier callbacks on slot changes so that all users can
>> re-enable dirty logging after the update as required.
>
> Simp
Jan Kiszka wrote:
If migration disables dirty memory logging, it must keep the vga logging
enabled, and vice versa.
So we need some notifier callbacks on slot changes so that all users can
re-enable dirty logging after the update as required.
Simpler to do reference counting. When a us
Avi Kivity wrote:
> Jan Kiszka wrote:
>>> I'm unhappy with both qemu.git and qemu-kvm.git memory slot management;
>>> qemu-kvm.git is clumsy, and qemu.git is too simplistic (for example, it
>>> ignores the fact that dirty logging is a global resource with multiple
>>> users).
>>>
>>
>> Don't g
Jan Kiszka wrote:
I'm unhappy with both qemu.git and qemu-kvm.git memory slot management;
qemu-kvm.git is clumsy, and qemu.git is too simplistic (for example, it
ignores the fact that dirty logging is a global resource with multiple
users).
Don't get your point yet. Can you name a concrete
Avi Kivity wrote:
> Jan Kiszka wrote:
>> Avi Kivity wrote:
>>
>>> After a lengthy testing phase, qemu-kvm.git has replaced
>>> kvm-userspace.git as the source repository for kvm userspace
>>> development.
>>>
>>> Differences from kvm-userspace.git are as follows:
>>> - everything under qemu/ has
Jan Kiszka wrote:
Avi Kivity wrote:
After a lengthy testing phase, qemu-kvm.git has replaced
kvm-userspace.git as the source repository for kvm userspace development.
Differences from kvm-userspace.git are as follows:
- everything under qemu/ has been moved to the top-level directory
- every
Avi Kivity wrote:
> After a lengthy testing phase, qemu-kvm.git has replaced
> kvm-userspace.git as the source repository for kvm userspace development.
>
> Differences from kvm-userspace.git are as follows:
> - everything under qemu/ has been moved to the top-level directory
> - everything not un
Hollis Blanchard wrote:
Since PPC is now supported in upstream QEMU, does it really matter if it
works in qemu-kvm.git?
I was going to take that position too, except Avi asked me specifically
if some of the code inside TARGET_I386 ifdefs in qemu-kvm.c works for
other architectures.
I
Hollis Blanchard wrote:
On Thu, 2009-04-23 at 18:40 +0300, Avi Kivity wrote:
Still missing:
- I have not tested powerpc or ia64. Patches welcome!
This repository seems pretty messed up; I'm not even sure what you want
from me. Some of the bigger problems:
* configure completely
On Tue, 2009-04-28 at 17:28 -0500, Anthony Liguori wrote:
> Glauber Costa wrote:
> > Yes. There are people (me) who still rely on building everything from
> > the same source.
> > It can only be done by the superset (qemu-kvm.git)
> >
>
> Fedora doesn't package a KVM enabled qemu-system-ppcemb,
On Tue, 2009-04-28 at 17:20 -0500, Anthony Liguori wrote:
> Hollis Blanchard wrote:
> > On Thu, 2009-04-23 at 18:40 +0300, Avi Kivity wrote:
> >
> >> Still missing:
> >> - I have not tested powerpc or ia64. Patches welcome!
> >>
> >
> > This repository seems pretty messed up; I'm not even
Glauber Costa wrote:
Yes. There are people (me) who still rely on building everything from
the same source.
It can only be done by the superset (qemu-kvm.git)
Fedora doesn't package a KVM enabled qemu-system-ppcemb, do they?
Regards,
Anthony Liguori
--
To unsubscribe from this list: send
On Tue, Apr 28, 2009 at 7:20 PM, Anthony Liguori wrote:
> Hollis Blanchard wrote:
>>
>> On Thu, 2009-04-23 at 18:40 +0300, Avi Kivity wrote:
>>
>>>
>>> Still missing:
>>> - I have not tested powerpc or ia64. Patches welcome!
>>>
>>
>> This repository seems pretty messed up; I'm not even sure what
Hollis Blanchard wrote:
On Thu, 2009-04-23 at 18:40 +0300, Avi Kivity wrote:
Still missing:
- I have not tested powerpc or ia64. Patches welcome!
This repository seems pretty messed up; I'm not even sure what you want
from me.
Since PPC is now supported in upstream QEMU, does it reall
On Thu, 2009-04-23 at 18:40 +0300, Avi Kivity wrote:
>
> Still missing:
> - I have not tested powerpc or ia64. Patches welcome!
This repository seems pretty messed up; I'm not even sure what you want
from me. Some of the bigger problems:
* configure completely ignores --kerneldir and only
Cameron Macdonell wrote:
Great. They work as expected. One thing I noticed is that make clean
doesn't remove libkvm.{o,a} and .libkvm.d. Should it?
Should, but doesn't. Another thing to fix.
--
Do not meddle in the internals of kernels, for they are subtle and quick to
panic.
--
To unsu
On 26-Apr-09, at 3:20 AM, Avi Kivity wrote:
Cam Macdonell wrote:
When I run configure on a clean copy I get this error:
KVM support no - (field 'arch' has incomplete type, field
'arch' has incomplete type)
I think it's caused by the include/asm and include-compat/asm
symlinks not
Liu Yu-B13201 wrote:
git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git
Is there a http interface?
http://www.kernel.org/pub/scm/virt/kvm/qemu-kvm.git
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
Cam Macdonell wrote:
When I run configure on a clean copy I get this error:
KVM support no - (field 'arch' has incomplete type, field 'arch'
has incomplete type)
I think it's caused by the include/asm and include-compat/asm symlinks
not being created until the kvm/configure script run
On Thu, 2009-04-23 at 11:42 -0600, Cam Macdonell wrote:
> Avi Kivity wrote:
> > After a lengthy testing phase, qemu-kvm.git has replaced
> > kvm-userspace.git as the source repository for kvm userspace development.
> >
> > Differences from kvm-userspace.git are as follows:
> > - everything under
Hi,
Liu Yu-B13201 freescale.com> writes:
> > After a lengthy testing phase, qemu-kvm.git has replaced
> > kvm-userspace.git as the source repository for kvm userspace
> > development.
> >
> > git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git
> >
>
> Is there a http interface?
Yes. http://
nel.org; Carsten Otte
> Subject: qemu-kvm.git now live
>
> After a lengthy testing phase, qemu-kvm.git has replaced
> kvm-userspace.git as the source repository for kvm userspace
> development.
>
> Differences from kvm-userspace.git are as follows:
> - everything under qe
Avi Kivity wrote:
After a lengthy testing phase, qemu-kvm.git has replaced
kvm-userspace.git as the source repository for kvm userspace development.
Differences from kvm-userspace.git are as follows:
- everything under qemu/ has been moved to the top-level directory
- everything not under qemu/
Avi Kivity wrote:
After a lengthy testing phase, qemu-kvm.git has replaced
kvm-userspace.git as the source repository for kvm userspace development.
Differences from kvm-userspace.git are as follows:
- everything under qemu/ has been moved to the top-level directory
- everything not under qemu/
After a lengthy testing phase, qemu-kvm.git has replaced
kvm-userspace.git as the source repository for kvm userspace development.
Differences from kvm-userspace.git are as follows:
- everything under qemu/ has been moved to the top-level directory
- everything not under qemu/ has been moved und
39 matches
Mail list logo
