From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:54035) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V8yyF-0008Ot-7K for qemu-devel@nongnu.org; Mon, 12 Aug 2013 16:44:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V8yy9-0000pX-T3 for qemu-devel@nongnu.org; Mon, 12 Aug 2013 16:44:07 -0400 Sender: fluxion Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable From: Michael Roth In-Reply-To: References: Message-ID: <20130812204345.26907.87122@loki> Date: Mon, 12 Aug 2013 15:43:45 -0500 Subject: Re: [Qemu-devel] [Qemu-stable] Possible bug in qemu-1.4.2: boot=off not honoured for -drive instances of virtio-scsi devices? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: George Diamantopoulos , qemu-stable@nongnu.org Cc: qemu-devel@nongnu.org Quoting George Diamantopoulos (2013-06-26 12:48:20) > Hello, > = > I've been testing out qemu-kvm 1.4.2 with virtio-scsi drives and I thi= nk I > might have encountered a bug. The VM is configured with: 1) a virtio-b= lk > drive, which is the one I want to boot, 2) another virtio-blk cdrom dr= ive > and two virtio-scsi drives. > = > Although I have set the boot=3Doff flag for the virtio-scsi drives, I > believe the VM tries two boot off one of these drives, because 1) if I > start the VM without initializing these two virtio-scsi devices, it bo= ots > off the virtio-blk disk and 2) if I initialize the virtio-scsi drives,= the > VM stalls during booting. > = > However, if I use "-boot order=3Dc,menu=3Don" when starting qemu-kvm, = and then > enter the boot menu, all devices appear in the list there, and the > virtio-scsi drives make it to the top, despite my having set the boot= =3Doff > flag for the virtio-scsi drives. If I manually choose the virtio-blk d= rive > from the boot menu, the instance boots successfully, even if the > virtio-scsi disks are present. > = > I could get around the issue perhaps by setting proper bootindex > priorities, but unfortunately ganeti won't let me choose bootindex val= ue > for the disk instances it manages itself (namely the virtio-blk drives= ). > = > Here's how ganeti starts the instance: > = > /usr/bin/qemu-system-x86_64 -machine accel=3Dkvm -name nas.mydomain.tl= d -m > 2560 -smp 1 -pidfile /var/run/ganeti/kvm-hypervisor/pid/nas.mydomain.t= ld > -balloon virtio -daemonize -machine pc-i440fx-1.4 -boot c -drive > file=3D/var/run/ganeti/instance-disks/nas.mydomain.tld:0,format=3Draw,= if=3Dvirtio > -drive > file=3D/srv/ganeti/isos/FreeNAS-9.1.0-BETA-a9c3cf1-x64.iso,format=3Dra= w,media=3Dcdrom,if=3Dvirtio > -monitor > unix:/var/run/ganeti/kvm-hypervisor/ctrl/nas.mydomain.tld.monitor,serv= er,nowait > -serial > unix:/var/run/ganeti/kvm-hypervisor/ctrl/nas.mydomain.tld.serial,serve= r,nowait > -usb -usbdevice tablet -vnc 10.2.24.30:5101 -cpu host -device > virtio-scsi-pci,id=3Dscsihw0 -drive > file=3D/dev/sdb,if=3Dnone,id=3Dsdb,cache=3Dwriteback,boot=3Doff,aio=3D= native -device > scsi-hd,drive=3Dsdb,id=3Dscsi1,bus=3Dscsihw0.0,channel=3D0,scsi-id=3D0= ,lun=3D0,bootindex=3D100 > -drive file=3D/dev/sdc,if=3Dnone,id=3Dsdc,cache=3Dwriteback,boot=3Doff= ,aio=3Dnative > -device > scsi-hd,drive=3Dsdc,id=3Dscsi2,bus=3Dscsihw0.0,channel=3D0,scsi-id=3D1= ,lun=3D0,bootindex=3D101 > -boot order=3Dc,menu=3Don -netdev type=3Dtap,id=3Dnetdev0,fd=3D9 -devi= ce > virtio-net-pci,mac=3Daa:00:00:3c:89:c2,netdev=3Dnetdev0 -qmp > unix:/var/run/ganeti/kvm-hypervisor/ctrl/nas.mydomain.tld.qmp,server,n= owait > -S > = > Shouldn't this result in only the virtio-blk device being selected for > boot, given these arguments That would be my expectation. This might be a known issue with SeaBIOS: https://lists.gnu.org/archive/html/qemu-devel/2012-09/msg00417.html Are you seeing this upstream as well? CC'ing qemu-devel just in case. > boot, given these arguments, or is this behaviour intended? Thanks. > Best regards, > George Diamantopoulos