Any plans to rebase kvm to current qemu at the moment ?

Any plans to rebase kvm to current qemu at the moment ?

[Christian Ehrhardt]

Hi,
while working on the embedded powerpc port for kvm we have a lot of dependencies on current qemu 0.9.0 code for ppc support. Internally we currently run with a modified qemu, but eventually strive for integration with kvm-userspace. Therefor I wanted to ask if there are already detailed plans (if any) regarding the re-base of kvm-userspace to the new qemu source?

-- 

Grüsse / regards, 
Christian Ehrhardt

IBM Linux Technology Center, Open Virtualization
+49 7031/16-3385
Ehrhardt-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org
Ehrhardt-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org

IBM Deutschland Entwicklung GmbH
Vorsitzender des Aufsichtsrats: Johann Weihen 
Geschäftsführung: Herbert Kircher 
Sitz der Gesellschaft: Böblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

Re: Any plans to rebase kvm to current qemu at the moment ?

[Avi Kivity]

Christian Ehrhardt wrote:
> Hi,
> while working on the embedded powerpc port for kvm we have a lot of dependencies on current qemu 0.9.0 code for ppc support. Internally we currently run with a modified qemu, but eventually strive for integration with kvm-userspace. Therefor I wanted to ask if there are already detailed plans (if any) regarding the re-base of kvm-userspace to the new qemu source?
>   

I'm currently debating this.  On the one hand, upstream qemu has a lot
of fixes and new goodies.  On the other hand, we still haven't recovered
completely from the lapic merge and I don't want to rock the boat further.

I'll try to merge in the next few days and see what breaks.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

Re: Any plans to rebase kvm to current qemu at the moment ?

[Zhang, Xiantao]

Hi Avi,
      We also the similar problems, when we enable kvm/ipf. You know,
Qemu doesn't work on IPF both at host and guest sides. 
So, we have some changes, and new-added stuffs to current Qemu code. Do
you think which tree we should push them to?  Qemu upstream 
or kvm-userspace?  
Thanks 
Xiantao 

Avi Kivity wrote:
> Christian Ehrhardt wrote:
>> Hi,
>> while working on the embedded powerpc port for kvm we have a lot of
>> dependencies on current qemu 0.9.0 code for ppc support. Internally
>> we currently run with a modified qemu, but eventually strive for
>> integration with kvm-userspace. Therefor I wanted to ask if there
>> are already detailed plans (if any) regarding the re-base of
>> kvm-userspace to the new qemu source?     
>> 
> 
> I'm currently debating this.  On the one hand, upstream qemu has a lot
> of fixes and new goodies.  On the other hand, we still haven't
> recovered completely from the lapic merge and I don't want to rock
> the boat further. 
> 
> I'll try to merge in the next few days and see what breaks.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

Re: Any plans to rebase kvm to current qemu at the moment ?

[Avi Kivity]

Zhang, Xiantao wrote:
> Hi Avi,
>       We also the similar problems, when we enable kvm/ipf. You know,
> Qemu doesn't work on IPF both at host and guest sides. 
> So, we have some changes, and new-added stuffs to current Qemu code. Do
> you think which tree we should push them to?  Qemu upstream 
> or kvm-userspace?  
>   

qemu-upstream is best for changes that would benefit regular qemu. 
Changes that are only good for kvm should be in kvm-userspace.


-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/