From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1K8IqE-0002ov-JR
	for qemu-devel@nongnu.org; Mon, 16 Jun 2008 13:50:06 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1K8IqC-0002nI-Dh
	for qemu-devel@nongnu.org; Mon, 16 Jun 2008 13:50:05 -0400
Received: from [199.232.76.173] (port=48853 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1K8IqC-0002n8-1i
	for qemu-devel@nongnu.org; Mon, 16 Jun 2008 13:50:04 -0400
Received: from mail.codesourcery.com ([65.74.133.4]:47341)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <paul@codesourcery.com>) id 1K8IqB-00014Y-EB
	for qemu-devel@nongnu.org; Mon, 16 Jun 2008 13:50:03 -0400
From: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] Re: Boot Failure (CDROM boot failure code : 0004)
Date: Mon, 16 Jun 2008 18:49:25 +0100
References: <874p7tinv3.fsf@alamut.mobiliz.com.tr>
	<87zlplh68t.fsf_-_@alamut.mobiliz.com.tr>
	<20080616172649.GP20851@kernel.dk>
In-Reply-To: <20080616172649.GP20851@kernel.dk>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <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: qemu-devel@nongnu.org
Cc: Laurent Vivier <Laurent.Vivier@bull.net>

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.

AFAIK the only times dd isn't give you a sufficient is when you have a 
multimode CD (i.e. audio tracks), when your drive is lying to you because of 
all the encryption stuff, or "copy protection" systems which use deliberately 
broken disks.

Paul