qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <qemu@kernel.dk>
To: Paul Brook <paul@codesourcery.com>
Cc: Laurent Vivier <Laurent.Vivier@bull.net>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: Boot Failure (CDROM boot failure code : 0004)
Date: Mon, 16 Jun 2008 20:00:28 +0200	[thread overview]
Message-ID: <20080616180027.GQ20851@kernel.dk> (raw)
In-Reply-To: <200806161849.26294.paul@codesourcery.com>

On Mon, Jun 16 2008, Paul Brook wrote:
> On Monday 16 June 2008, Jens Axboe wrote:
> > On Mon, Jun 16 2008, Volkan YAZICI wrote:
> > > On Mon, 16 Jun 2008, Laurent Vivier <Laurent.Vivier@bull.net> writes:
> > > > could you burn a CD with your .iso and try to boot a real PC ?
> > >
> > > I created the ISO image from the same CD that's inserted into the
> > > /dev/scd0 using below command:
> > >
> > >   root:~# dd bs=$[1024 * 32] \
> > >
> > >   > if=/dev/scd0 \
> > >   > of=/root/windows-server-2003-standard-x86-64-sp2.iso
> > >
> > > And I'm sure CD is bootable. (Not pirated, original.) OTOH, if we'd
> > > assume the ISO image is corrupted for some unknown reason, why "-cdrom
> > > /dev/scd0" didn't work?
> >
> > You can't just do a dd and expect the output to be bootable, that wont
> > include the floppy boot image.
> 
> Are you sure? 
> Copying all the files and creating a new iso image won't work, but I'm fairly 
> sure dd should. My understanding is that the image (which is effectively what 
> dd gives you) contains all the data for the el torito bits, but they're not 
> neccly accessible via the mounted filesystem.

I was slightly off, in hindsight, didn't think properly about that
before replying :-)

The dd image should indeed be bootable, but a burned version of the
image will not be. And copying alone will of course not work.

Sorry for the misinformation!

-- 
Jens Axboe

  reply	other threads:[~2008-06-16 18:00 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 [this message]
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
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=20080616180027.GQ20851@kernel.dk \
    --to=qemu@kernel.dk \
    --cc=Laurent.Vivier@bull.net \
    --cc=paul@codesourcery.com \
    --cc=qemu-devel@nongnu.org \
    /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).