qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Sebastian Herbszt" <herbszt@gmx.de>
To: Volkan YAZICI <yazicivo@ttmail.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Boot Failure (CDROM boot failure code : 0004)
Date: Tue, 17 Jun 2008 15:59:47 +0200	[thread overview]
Message-ID: <02f101c8d082$a6ab28e0$0201a8c0@zeug> (raw)
In-Reply-To: 87zlpktw9p.fsf_-_@alamut.mobiliz.com.tr

>  QEMU BIOS - build: 04/28/08
>  $Revision: 1.207 $ $Date: 2008/04/21 14:22:01 $
>  Options: apmbios pcibios eltorito rombios32
> 
>  ata0 master: QEMU HARDDISK ATA-7 Hard-Disk (20480 MBytes)
>  ata1 master: QEMU CD-ROM ATAPI-4 Cd-Rom/Dvd-Rom
> 
>  Press F12 for boot menu.
> 
>  Booting from CD-Rom...
>  4615MB medium detected
>  CDROM boot failure code : 0004
>  Boot failed: could not read the boot disk
> 
>  FATAL: No bootable device.
> 
> I tried above command with below combinations, but same result.
> 
>  -cdrom /dev/scd0
>  -cdrom /root/scd0.iso (Created using "dd bs=2048 ..." command.)
>  -cdrom /home/windows/windows-server-2003-standard-x86-64-sp2.iso
> 
> Any ideas?

The size looks like a dvd. Do other dvd images work? What are their sizes?

> What does "could not read the boot disk" mean exactly?

>From rombios.c
//   - Here are the cdrom boot failure codes:
//       1 : no atapi device found
//       2 : no atapi cdrom found
//       3 : can not read cd - BRVD
//       4 : cd is not eltorito (BRVD)
//       5 : cd is not eltorito (ISO TAG)
//       6 : cd is not eltorito (ELTORITO TAG)
//       7 : can not read cd - boot catalog
//       8 : boot catalog : bad header
//       9 : boot catalog : bad platform
//      10 : boot catalog : bad signature
//      11 : boot catalog : bootable flag not set
//      12 : can not read cd - boot image

- Sebastian

  reply	other threads:[~2008-06-17 14:01 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-16 12:08 [Qemu-devel] Boot Failure (CDROM boot failure code : 0004) Volkan YAZICI
2008-06-16 12:36 ` Laurent Vivier
2008-06-16 13:14   ` [Qemu-devel] " Volkan YAZICI
2008-06-16 17:26     ` Jens Axboe
2008-06-16 17:41       ` Avi Kivity
2008-06-16 18:01         ` Jens Axboe
2008-06-16 17:43       ` Natalia Portillo
2008-06-16 17:49       ` Paul Brook
2008-06-16 18:00         ` Jens Axboe
2008-06-16 18:29           ` Avi Kivity
2008-06-17 18:29             ` Jens Axboe
2008-06-17  8:25           ` Brad Campbell
2008-06-16 17:46     ` Natalia Portillo
2008-06-17  5:33       ` Volkan YAZICI
2008-06-17 20:01         ` Natalia Portillo
2008-06-16 22:00     ` Anthony Liguori
2008-06-17  6:09       ` Volkan YAZICI
2008-06-17  8:06         ` Volkan YAZICI
2008-06-17 18:12           ` Anthony Liguori
2008-06-16 14:00 ` [Qemu-devel] " Avi Kivity
2008-06-17  6:40   ` [Qemu-devel] " Volkan YAZICI
2008-06-16 16:04 ` Sebastian Herbszt
2008-06-17  6:23   ` Volkan YAZICI
2008-06-17 13:59     ` Sebastian Herbszt [this message]
2008-06-17 14:36       ` Volkan YAZICI
2008-06-17 20:05         ` Natalia Portillo
2008-06-16 22:09 ` [Qemu-devel] " Anthony Liguori
  -- strict thread matches above, loose matches on Subject: below --
2008-06-17 14:27 [Qemu-devel] " Juergen Keil
2008-06-18  8:38 Juergen Keil

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='02f101c8d082$a6ab28e0$0201a8c0@zeug' \
    --to=herbszt@gmx.de \
    --cc=qemu-devel@nongnu.org \
    --cc=yazicivo@ttmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).