[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [RFC for-4.7] Switching to a single qemu tree each per qemu-xen and qemu-trad

On Thu, Jul 30, 2015 at 3:51 PM, Vitaly Kuznetsov <vkuznets@xxxxxxxxxx> wrote:
> Ian Campbell <ian.campbell@xxxxxxxxxx> writes:
>> (CC-ing 2x QEMU maintainers and stable release manager)
>> The separate trees are a holdover from mercurial, which didn't (at the
>> time) have a good in-repo branching model.
>> I propose that Xen 4.6 should be the last release which uses these split
>> trees and that instead we combine them into just qemu-xen.git (upstream)
>> and qemu-xen-traditional.git (our old fork)
> (sorry my question is a bit unrelated)
> is there a proposed time frame for the retirement of
> qemu-xen-traditional? http://wiki.xenproject.org/wiki/QEMU_Upstream only
> mentions VGA passthrough as a missing feature but maybe it can be fixed
> for 4.7?

We also don't yet have a good story for stub domains; and there are
some rather hacky things related to PCI pass-through that still have
to be worked around in qemu-upstream. (Namely, hvmloader cannot resize
the MMIO hole because it can't tell qemu about the resize; so when
passing through a device that doesn't fit in the default hole size,
you have to manually specify the size in the config file.)

We're working on stub domains with rump kernels, but we're not there yet.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.