> The media argument seems a perfectly natural
> way to select between the two.
Then how do you distinguish between a virtio-scsi and a virtio-blk hard
disk? These may even require changes to the guest, since one becomes
/dev/vda and the other becomes /dev/sda.
virtio-scsi will grow more and mor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3/18/2013 11:17 AM, Paolo Bonzini wrote:
> if=virtio means virtio-blk, not virtio-something.
Why do you say that? I would say that virtio means use
paravirtualized IO rather than emulating some real hardware. Whether
that ends up being done with
if=virtio means virtio-blk, not virtio-something.
Also, Linux is perfectly fine with ISO images on virtio, the Ubuntu
installer is wrong in not scanning virtio disks. Since Ubuntu wouldn't
work either way, they should first fix the installer and then we can re-
evaluate if QEMU can do something (
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3/18/2013 5:13 AM, Paolo Bonzini wrote:
>> Or better yet, shouldn't it automatically use virtio-scsi
>> instead?
>
> No, virtio-scsi is relatively new and not all distros have picked
> it up yet.
And not all distros ship hybrid cd images that thei
> It seems the installer does not consider virtio devices when doing its
search.
That's another bug in the installer then.
> it seems a bit wasteful to go through a layer of scsi emulation.
Indeed treating the virtio disk similarly to installation from a USB
stick is better, but SCSI emulation i
Consider filing a Debian/Ubuntu bug so that their initramfs / installer
/ live disk comes with virtio-scsi. See eg.
https://bugzilla.redhat.com/show_bug.cgi?id=864012
** Bug watch added: Red Hat Bugzilla #864012
https://bugzilla.redhat.com/show_bug.cgi?id=864012
--
You received this bug notif
It seems the installer does not consider virtio devices when doing its
search. It also seems the installer does not have the virtio-scsi
module, and it seems a bit wasteful to go through a layer of scsi
emulation.
Shouldn't qemu at least warn you that the media=argument does nothing on
virtio dev
There's no such thing as a virtio-blk CD-ROM, only hard-disks. For
installation it shouldn't matter, since .iso images usually can work
also as hard-disk images (for putting them on a USB stick).
If you want to test installation from a "real" virtio CD-ROM, use
virtio-scsi:
-drive file=/path/to/f
I see, misunderstood.
Reproduced with latest git://git.qemu.org/qemu.git as well, so marked as
affecting upstream QEMU project.
** Also affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Order does not matter, and it isn't whether it boots or not, but whether
the installer will mount the cdrom. If you are using the netinst iso,
then it doesn't bother looking for the cdrom since it downloads
everything from the net.
** Changed in: qemu (Ubuntu)
Importance: Low => Medium
--
Y
Quoting Phillip Susi (ps...@ubuntu.com):
> Are you sure you booted from the cd, not the hd? I'm using the raring-
> server-amd64.iso and it doesn't work. It has also been reported in
Yes. However I just noticed that if I list the hard drive first, then
it boots from the hd. If I list the cdrom
Are you sure you booted from the cd, not the hd? I'm using the raring-
server-amd64.iso and it doesn't work. It has also been reported in
debian:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=+689528
Looking at the output of udevadm info --query --path=/dev/vda it is
pretty obvious what the
Are you sure the cdrom image is valid? It works fine for me, with
kvm -drive file=raring-mini-amd64.iso,if=virtio,media=cdrom -drive
file=x.img,if=virtio,cache=none -m 1024
using either the latest raring full server iso, or a minimal netinst
image from
release=raring
arch=amd64
f=${release}-min
The current raring version, which appears to be 1.4.0+dfsg-1expubuntu3.
Also I guess this should be under just the "qemu" package now rather
than -kvm.
The command line is qemu -drive file=whatever.iso,if=virtio,media=cdrom.
With or without the media argument seems to make no difference; either
wa
Could you please give the exact command line you're using, and your
release and qemu package versions?
** Changed in: qemu-kvm (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
15 matches
Mail list logo
