On Thu, Jul 09, 2009 at 12:11:33AM +0300, Pasi Kärkkäinen wrote: > On Wed, Jul 08, 2009 at 11:34:18PM +0300, Pasi Kärkkäinen wrote: > > On Wed, Jul 08, 2009 at 04:38:10PM +0200, Csillag Kristof wrote: > > > We should move this to this thread (#536175), > > > because the other bug report (#536176) is about a different issue. > > > > > > Pasi Kärkkäinen wrote: > > > > On Wed, Jul 08, 2009 at 04:10:31PM +0200, Bastian Blank wrote: > > > > > > > >> On Wed, Jul 08, 2009 at 04:19:39PM +0300, Pasi Kärkkäinen wrote: > > > >> > > > >>> Uhm, that's really weird. What was the reason for disabling Xen HVM > > > >>> support? > > > >>> It's removing half of the Xen functionality in Debian.. > > > >>> > > > >> Xen upstream decided to move the patches in qemu upstream. So this > > > >> needs > > > >> to be built from qemu in the future, but this is not nearly ready. > > > >> > > > >> > > > > > > > > Oh, it's about ioemu-remote stuff. > > > > > > > > You could also include a tarball of qemu-xen tree (or whatever the > > > > correct tree > > > > is) if that helps? > > > > > > > > Actually I don't think you should build the upstream qemu for xen 3.4.0. > > Xen 3.4.0 uses it's own version of qemu, not the upstream qemu, afaik. > > > > If I understand this correctly, as a default Xen 3.4 hg/mercurial source tree > [1] > uses 'ioemu-remote', which means the Xen version of Qemu (qemu-xen) > is developed on a separate git tree [2]. > > The official Xen 3.4.0 release tarball [3] contains embedded copy of this > ioemu-remote qemu-xen tree on "tools/ioemu-qemu-xen" directory, so the release > tarball can be built without internet/git access. >
For example Fedora's Xen 3.4.0 source RPM contains the xen-3.4.0.tar.gz release tarball, and they build the included ioemu, just like in earlier Xen releases. That is the correct way to do it. -- Pasi > > [1] http://xenbits.xen.org/xen-3.4-testing.hg > [2] http://xenbits.xen.org/git-http/qemu-xen-3.4-testing.git > [3] http://bits.xensource.com/oss-xen/release/3.4.0/xen-3.4.0.tar.gz > > -- Pasi > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
