On Wed, Nov 11, 2009 at 05:58:38AM -, Matt Zimmerman wrote:
I don't understand why this option should be necessary. Following the
steps in my original report, I would expect one of two things to
happen:
* The CD-ROM boot fails (because the disc is ejected) and it falls back
to
1. kvm-img create hda.img 4G
2. kvm -hda hda.img -cdrom jaunty-desktop-i386.iso -m 512
3. Install Ubuntu onto hda
4. Reboot, following the prompts (press enter to eject the CD)
5. System boots into installed OS.
It's the use of '-boot d' that is creating problems for you. By
default, the order=
On Wed, Nov 11, 2009 at 09:43:20AM -, Soren Hansen wrote:
On Wed, Nov 11, 2009 at 05:58:38AM -, Matt Zimmerman wrote:
I don't understand why this option should be necessary. Following the
steps in my original report, I would expect one of two things to
happen:
* The CD-ROM
I'll convert it into a Question, since this stems from a
misunderstanding of the behavior of qemu and its -boot option, now
explained clearly by Anthony.
** Changed in: qemu-kvm (Ubuntu)
Status: Incomplete = New
--
Fails to boot from CD after reboot: CDROM boot failure code: 0003
** Changed in: qemu-kvm (Ubuntu)
Status: New = Invalid
--
Fails to boot from CD after reboot: CDROM boot failure code: 0003
https://bugs.launchpad.net/bugs/348633
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
Matt, Evan-
From the kvm(1) manpage, I think the option you want is:
# boot from CD-ROM first, switch back to default order after reboot
-boot once=d
Can you give that a try and see if that gives you the behavior you
expect?
I tested here with a real, working disk image, and a live ISO.
On Wed, Nov 11, 2009 at 01:46:49AM -, Dustin Kirkland wrote:
Matt, Evan-
From the kvm(1) manpage, I think the option you want is:
# boot from CD-ROM first, switch back to default order after reboot
-boot once=d
Can you give that a try and see if that gives you the behavior you
I think this deserves a higher priority than wishlist.
This bit me hard over the past two days in testing Wubi. wubildr
(grub2) would hang on reading from the CDROM on first boot, since it had
been ejected and left in that state.
--
Fails to boot from CD after reboot: CDROM boot failure code:
Evan-
What's your kvm command line?
:-Dustin
** Changed in: kvm (Ubuntu)
Importance: Wishlist = Low
** Package changed: kvm (Ubuntu) = qemu-kvm (Ubuntu)
** Also affects: qemu
Importance: Undecided
Status: New
--
Fails to boot from CD after reboot: CDROM boot failure code: 0003
This is expected behavior.
You probably should be using -boot dc. This will cause the VM to boot
into the install OS after installation. This is precisely why
distributions eject the CD after installation (to prevent booting into
the installer again).
** Changed in: qemu
Status: New =
Evan-
Can you try adding -boot dc to your kvm command line?
This would tell qemu to try boot from the cdrom first, then from the
hard drive.
:-Dustin
--
Fails to boot from CD after reboot: CDROM boot failure code: 0003
https://bugs.launchpad.net/bugs/348633
You received this bug notification
I think this is really a simple matter of which type of cdrom is being emulated
by kvm. In my experience, there are at least two behaviors of CDroms that have
their tray ejected on boot.
a.) pull in the tray (eject -t) which would have a cd in it, and then would be
available for the bios boot
12 matches
Mail list logo
