Skip to contentSkip to conversation

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

DISCUSSION Christian Ehrhardt 3 participants 4 messages Oct 1, 2007 3 messages not in the archive KVM

lore
Share & tools
lore
#0 lore raw

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?

Signature · 18 lines
Grüsse / regards, 
Christian Ehrhardt

IBM Linux Technology Center, Open Virtualization
+49 7031/16-3385
[email protected]
[email protected]

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/

A message that is not in the archive (sent off-list or not yet received): 47008C5B.2080006-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org

#2 lore raw
Quoted 3 lines · 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?

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.

Signature · 7 lines
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/

A message that is not in the archive (sent off-list or not yet received): 4700930D.2030903-atKUWr5tajBWk0Htik3J/[email protected]

#4 lore raw

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

Quoted 10 lines · Avi Kivity
Quoted 8 lines · 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?

Quoted 6 lines

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/

A message that is not in the archive (sent off-list or not yet received): 42DFA526FC41B1429CE7279EF83C6BDC754272-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org

#6 lore raw
Quoted 7 lines · 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?

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

Signature · 7 lines
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/