From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MawSA-0007KI-3p
	for qemu-devel@nongnu.org; Tue, 11 Aug 2009 14:52:10 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MawS2-0007JV-Gz
	for qemu-devel@nongnu.org; Tue, 11 Aug 2009 14:52:07 -0400
Received: from [199.232.76.173] (port=51815 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MawS2-0007JS-Bn
	for qemu-devel@nongnu.org; Tue, 11 Aug 2009 14:52:02 -0400
Received: from smtp-vbr13.xs4all.nl ([194.109.24.33]:4085)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <bruinjm@xs4all.nl>) id 1MawS1-0002T2-Uh
	for qemu-devel@nongnu.org; Tue, 11 Aug 2009 14:52:02 -0400
Message-ID: <4A81BDCF.4080908@xs4all.nl>
Date: Tue, 11 Aug 2009 20:51:59 +0200
From: Hans de Bruin <bruinjm@xs4all.nl>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] virtio disk
References: <4A807BD7.70403@xs4all.nl> <4A815E3C.7060506@redhat.com>
	<4A81A6A6.50006@xs4all.nl>
In-Reply-To: <4A81A6A6.50006@xs4all.nl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel@nongnu.org

Hans de Bruin wrote:
> Avi Kivity wrote:
>  > On 08/10/2009 10:58 PM, Hans de Bruin wrote:
>  >> I am trying to get my qemu vm to boot of 'VIRTIO_BLOCK', but am not
>  >> very successful. I have got two setups:
>  >>
>  >> A two day old qemu tree from git://git.savannah.nongnu.org/qemu
>  >> on a jetway board with a non kvm capable via c7 proc (30W),
>  >>
>  >> and an older qemu-kvm (kvm-88-6-g2ebe329 (10.?)) on a AMD proc (130W)
>  >>
>  >> The AMD boots guests with virtio_block, either with the -kernel switch
>  >> or via the bios. The ViaC7 wil not. Nor the bios nor the kernel detect
>  >> the vitio block device.
>  >>
>  >> Somewhere on the internet I found this qemu-kvm option:
>  >>
>  >>  -drive file=vmdisk1,if=virtio,boot=on
>  >>
>  >> This boot=on, isn't in either of the man pages. qemu doesn't accept
>  >> this option. qemu-kvm needs it to let the bios boot from the
>  >> virtio_block device. I also noticed the qemu-kvm bios has a boot menu
>  >> which can be accessed by F12. qemu has not.
>  >>
>  >
>  > boot=on is in qemu-kvm.git but not in qemu.git yet.
> 
> That is clear, but with or without boot=on, the qemu tree should provide 
> my guest with a blockdevice, which somehow I am missing. For me the 
> solution is simple just switch to the kvm tree.
> 

And loze kqemu, I should be more patient.

-- 
Hans