George, I have reverted the controversial patch about the start of the PCI hole in qemu-xen. It needs to be reverted because even if we wanted to go with that change for the release we would need a corresponding patch to hvmloader and libxc. Everything else new in the tree are stable fixes that we have already agreed should be part of the release. Hence I am proposing that the next Xen RC should use the latest qemu-xen (commit id 79c097d5fe7cb0b4788ed509240cde7e210650bf). Of course we''ll still be missing a fix for the PCI passthrough problem, but that''s not ready yet. Cheers, Stefano
Stefano Stabellini writes ("qemu-xen and the next
RC"):> I have reverted the controversial patch about the start of the PCI hole
> in qemu-xen. It needs to be reverted because even if we wanted to go
> with that change for the release we would need a corresponding patch to
> hvmloader and libxc.
> Everything else new in the tree are stable fixes that we have already
> agreed should be part of the release. Hence I am proposing that the
> next Xen RC should use the latest qemu-xen (commit id
> 79c097d5fe7cb0b4788ed509240cde7e210650bf).
Thanks for the email, Stefano.
I intend to wait for the revert to get a test pass, and then push a
change to xen.git#staging''s Config.mk to name this commit id.
Hopefully this will be tomorrow.
Ian.
Ian Jackson writes ("Re: qemu-xen and the next
RC"):> I intend to wait for the revert to get a test pass, and then push a
> change to xen.git#staging''s Config.mk to name this commit id.
> Hopefully this will be tomorrow.
This is now done.
Ian.