[CC'ing d-hurd@ to get more ideas/opinions] On Tue, Mar 18, 2014 at 4:00 PM, Holger Levsen <hol...@layer-acht.org> wrote: > (as a very minor comment on this: why hurd-i386 and not hurd-amd64?)
(http://www.gnu.org/software/hurd/faq/64-bit.html) > On Montag, 17. März 2014, Gabriele Giacone wrote: >> The intention is adding hurd-i386 to jenkins.d.n CI [0]. Currently VMs >> are booted with --kernel/--initrd options to pass preseed file url >> [1]. >> I'm about proposing changes to boot hurd with qemu multiboot options [2]. > > is multiboot the only way to boot the hurd from within qemu? We could boot it from CD but I guess we should recreate netinst CD to pass preseed file url to kernel or automate url insertion on grub with vncdo. With multiboot, I just tried to adhere to current (linux) configuration as much as possible. Current qemu on wheezy (1.1.2) can boot hurd CD only on systems with hwaccel and by specifying --enable-kvm. it crashes without hwaccel, see [0]. Not a real problem on jenkins.d.n which has hwaccel, but IMHO [0] is important enough to get an upload to stable, it makes installing a hurd VM on a wheezy host hardware dependent. Whereas this bug affects Debian infrastructure, assuming d.n as part of Debian infrastructure and assuming that would count something if it was d.o. How about identifying changes to backport fixing this bug and proposing both to release team? No way? wheezy-backports. [0] https://bugs.debian.org/719633 -- G..e -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
