From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1K8J0K-0005S4-Fu
	for qemu-devel@nongnu.org; Mon, 16 Jun 2008 14:00:32 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1K8J0J-0005Rs-Iy
	for qemu-devel@nongnu.org; Mon, 16 Jun 2008 14:00:32 -0400
Received: from [199.232.76.173] (port=47653 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1K8J0J-0005Rp-C2
	for qemu-devel@nongnu.org; Mon, 16 Jun 2008 14:00:31 -0400
Received: from brick.kernel.dk ([87.55.233.238]:18532 helo=kernel.dk)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <axboe@kernel.dk>) id 1K8J0I-0002Xj-SJ
	for qemu-devel@nongnu.org; Mon, 16 Jun 2008 14:00:31 -0400
Date: Mon, 16 Jun 2008 20:00:28 +0200
From: Jens Axboe <qemu@kernel.dk>
Subject: Re: [Qemu-devel] Re: Boot Failure (CDROM boot failure code : 0004)
Message-ID: <20080616180027.GQ20851@kernel.dk>
References: <874p7tinv3.fsf@alamut.mobiliz.com.tr>
	<87zlplh68t.fsf_-_@alamut.mobiliz.com.tr>
	<20080616172649.GP20851@kernel.dk>
	<200806161849.26294.paul@codesourcery.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200806161849.26294.paul@codesourcery.com>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Paul Brook <paul@codesourcery.com>
Cc: Laurent Vivier <Laurent.Vivier@bull.net>, qemu-devel@nongnu.org

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