15.11.2010 02:56, Josselin Mouette wrote:
> Le lundi 15 novembre 2010 à 00:23 +0300, Michael Tokarev a écrit :
>> But even if it were non-bootable -- a regression from what?
>> Kvm version on lenny was completely unreliable. It was
>> nothing more than a development snapshot, a code drop, not
>> even an alpha release.
>
> This is completely unrelated, but how did it end up in a stable release
> if it was in that case?
At the time lenny was out, we only had these code drops for
kvm (at version kvm-72). We had 2 alternatives: either ship
it as it were, or not ship it. The technology is cool and
hot and so on, even if it were known to be pre-alpha version.
Besides, no one knew at that time how many bugs and issues
it had, it looked like a stable-behaving software.
Even kernel part of kvm _guest_ (especially timer stuff) in
lenny is broken in numerous ways.
>>> Virtio is the recommended I/O driver in basically all KVM documentation,
>>> and I think there are good reasons for that. Not being able to boot from
>>> it anymore means you have to provide 2 disks to all your guests, which
>>> makes the setup a monstrosity if you have a lot of them.
>>
>> Again, it boots perfectly here, no problems. Maybe
>> squeeze can not _install_ into it -- this is a different
>> matter, and at least it does not look like from your
>> bug description.
>>
>> As far as I understand your problem, you can't _install_
>> squeeze into a virtio disk, but if you install to ide
>> but later use virtio it works. Is it the right understanding?
>
> No, it’s the complete opposite. I can install squeeze on a virtio disk,
> but it won’t boot.
>
> And it won’t boot until I upgrade seabios. With a freshly built seabios
> from today’s git, it boots.
Um. Now it's you who did not understand me ;)
But this is no surprize - I were very very tired
yesterday after a hard work, so my wording isn't
at all clear, even to me myself when I read what
I wrote :)
What I tried to say is that when you install it
to virtio disk, the install goes find but the
guest isn't bootable after that. I.e., you
can't reboot a guest from virtio if you booted
it from a virtial CD.
Scratch what I said above about IDE. Yes that
can be used too, and you can install into IDE
virtual disk and later switch to using virtio,
but that requires quite some understanding --
at least, /etc/fstab and grub conf files has
to be edited to change /dev/sda to /dev/vda.
But ok...
> Le lundi 15 novembre 2010 à 00:40 +0300, Michael Tokarev a écrit :
>> I can't reproduce this. I just installed squeeze
>> in a fresh virtual machine, installed grub2 (it were
>> installed automatically) to /dev/vda, and it boots
>> just fine.
>>
>> What I'm doing wrong?
>
> The only “special” thing I can think of on my setup is that the virtual
> disk is a LVM device on the host, instead of a file. I don’t know
> whether this could have an impact, but if otherwise you did the same
> things, that could be it.
It does not matter where physically the guest disk image is
located and which format it uses on the host. From the guest
point of view, including guest bios, it is completely transparent.
Except that some variants are faster, some slower and the like.
But let's make this thing clear.
What I do to install squeeze into a virtual machine:
1. Create a new image or clear previously existing one.
Just to be sure there's nothing in the target virtual drive.
$ kvm-img create guest.raw 2G
Not doing so with an existing image does not hurt, you'll
just have to tell the installer to remove unnecessary
partitions and answer to a few "Are you sure?" questions.
You can clear an lvm image too, using, for example,
dd if=/dev/zero of=/dev/lvm/guestimg bs=1M count=1
(this clears first megabyte of the volume). But this
is not related to the issue at hand, just some side
notes.
2. Now install the guest using netinst cd:
$ kvm \
-drive file=guest.raw,if=virtio \
-cdrom squeeze-netinst.iso \
-boot d \
-net [enable networking so it can access debian mirrors]
I omited other options here for brevity.
Here I told it to boot from a (virtual) CD-Rom drive.
3. When install completes, the installer reboots, and if
you reboot the virtual machine at this point, it will
boot from cdrom again. Not what we need.
So I edit kvm command line to tell it to boot the newly
installed OS:
$ kvm \
-drive file=guest.raw,if=virtio,boot=on \
-net [enable networking so it can access debian mirrors]
At this point it boots just fine.
This is like going into BIOS of a physical machine and changing
the device to boot from, if your machine does not have a
working "BOOT Menu" feature.
This is how I install it. Now please show me how do _you_
install things, so I can reproduce your issue.
Thanks.
/mjt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
