* [Qemu-devel] virtio disk
@ 2009-08-10 19:58 Hans de Bruin
2009-08-11 12:04 ` Avi Kivity
0 siblings, 1 reply; 4+ messages in thread
From: Hans de Bruin @ 2009-08-10 19:58 UTC (permalink / raw)
To: qemu-devel
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.
How to get my ViaC7 to run guest oses from virtio?
--
Hans
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Qemu-devel] virtio disk
2009-08-10 19:58 [Qemu-devel] virtio disk Hans de Bruin
@ 2009-08-11 12:04 ` Avi Kivity
2009-08-11 17:13 ` Hans de Bruin
0 siblings, 1 reply; 4+ messages in thread
From: Avi Kivity @ 2009-08-11 12:04 UTC (permalink / raw)
To: Hans de Bruin; +Cc: qemu-devel
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.
--
error compiling committee.c: too many arguments to function
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Qemu-devel] virtio disk
2009-08-11 12:04 ` Avi Kivity
@ 2009-08-11 17:13 ` Hans de Bruin
2009-08-11 18:51 ` Hans de Bruin
0 siblings, 1 reply; 4+ messages in thread
From: Hans de Bruin @ 2009-08-11 17:13 UTC (permalink / raw)
To: Avi Kivity; +Cc: qemu-devel
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.
In wat way will this boot=on eventually end up in the man pages? In both
trees the MAINTAINERS file does not contain a word about documentation.
--
Hans
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Qemu-devel] virtio disk
2009-08-11 17:13 ` Hans de Bruin
@ 2009-08-11 18:51 ` Hans de Bruin
0 siblings, 0 replies; 4+ messages in thread
From: Hans de Bruin @ 2009-08-11 18:51 UTC (permalink / raw)
To: Avi Kivity; +Cc: qemu-devel
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
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2009-08-11 18:52 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-08-10 19:58 [Qemu-devel] virtio disk Hans de Bruin
2009-08-11 12:04 ` Avi Kivity
2009-08-11 17:13 ` Hans de Bruin
2009-08-11 18:51 ` Hans de Bruin
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).