[Qemu-devel] Re: Boot Failure (CDROM boot failure code : 0004)

[Qemu-devel] Re: Boot Failure (CDROM boot failure code : 0004)

[Volkan YAZICI]

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?


Regards.

[Qemu-devel] Re: Boot Failure (CDROM boot failure code : 0004)

[Sebastian Herbszt]

>  QEMU BIOS - build: 02/08/07
>  $Revision: 1.174 $ $Date: 2006/10/17 16:48:05 $
>  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
> 
>  CDROM boot failure code : 0004
>  Boot from Cd-Rom failed
>  FATAL: Could not read the boot disk

Can you reproduce the problem with a recent bios version?
You can get the latest qemu version (based on 1.207) from
http://svn.savannah.gnu.org/viewvc/*checkout*/trunk/pc-bios/bios.bin?root=qemu

- Sebastian

Re: [Qemu-devel] Re: Boot Failure (CDROM boot failure code : 0004)

[Jens Axboe]

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. So nothing wrong with qemu, that iso
would not be bootable if burned either.

-- 
Jens Axboe

Re: [Qemu-devel] Re: Boot Failure (CDROM boot failure code : 0004)

[Avi Kivity]

Jens Axboe wrote:
> You can't just do a dd and expect the output to be bootable, that wont
> include the floppy boot image. So nothing wrong with qemu, that iso
> would not be bootable if burned either.
>
>   

How does one reliably rip bootable isos?

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.

Re: [Qemu-devel] Re: Boot Failure (CDROM boot failure code : 0004)

[Natalia Portillo]

You are absolutely wrong.

If the CD is bootable, with the down dd command, the .ISO file is bootable.

That is true, checked by myself, for Power Macintosh, PReP, El Torito 
(IBM PC compatibles 32-bit and 64-bit, and AmigaONE), Sparc, Intel Mac, 
Pegasos/Efika and Amiga.
Surely it is true also for other architectures, as long as the CD is 
standard at 2048-bytes/sec or 512-bytes/sec and dd gave no errors.

Jens Axboe escribió:
> 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. So nothing wrong with qemu, that iso
> would not be bootable if burned either.
>
>   

Re: [Qemu-devel] Re: Boot Failure (CDROM boot failure code : 0004)

[Natalia Portillo]

Could you do the following and paste the results here?

sudo file -s /dev/scd0
file <iso-image>

Both should say something like:
ISO 9660 CD-ROM filesystem data '****************' (bootable)

Volkan YAZICI escribió:
> 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?
>
>
> Regards.
>
>
>
>   

Re: [Qemu-devel] Re: Boot Failure (CDROM boot failure code : 0004)

[Paul Brook]

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

Re: [Qemu-devel] Re: Boot Failure (CDROM boot failure code : 0004)

[Jens Axboe]

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

Re: [Qemu-devel] Re: Boot Failure (CDROM boot failure code : 0004)

[Jens Axboe]

On Mon, Jun 16 2008, Avi Kivity wrote:
> Jens Axboe wrote:
> >You can't just do a dd and expect the output to be bootable, that wont
> >include the floppy boot image. So nothing wrong with qemu, that iso
> >would not be bootable if burned either.
> >
> >  
> 
> How does one reliably rip bootable isos?

dd should be fine, disgard (most) of that email.

-- 
Jens Axboe

Re: [Qemu-devel] Re: Boot Failure (CDROM boot failure code : 0004)

[Avi Kivity]

Jens Axboe wrote:
> 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. 

Why is that?  What's different in the ripped image compared to the image 
used to burn the CD?

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.

Re: [Qemu-devel] Re: Boot Failure (CDROM boot failure code : 0004)

[Anthony Liguori]

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
>   

Your dd line is very suspect.  Why are you using a block size of 32k?  
The sector size of most CD-ROMs is 2k.  I've certainly encountered my 
fair share of CD-ROMS that were an odd multiple of 2k.  dd will silently 
truncate the ISO if the size is not a multiple of 32k.

Regards,

Anthony Liguori

> 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?
>
>
> Regards.
>
>
>   

[Qemu-devel] Re: Boot Failure (CDROM boot failure code : 0004)

[Volkan YAZICI]

On Mon, 16 Jun 2008, Natalia Portillo <claunia@claunia.com> writes:
> Could you do the following and paste the results here?
>
> sudo file -s /dev/scd0
> file <iso-image>
>
> Both should say something like:
> ISO 9660 CD-ROM filesystem data '****************' (bootable)

Below are the related command outputs:

  root:~# file -s /dev/scd0
  /dev/scd0: ISO 9660 CD-ROM filesystem data 'EN_OS_2939.3'
  
  root:~# file /home/windows/windows-server-2003-standard-x86-64-sp2.iso
  /home/windows/windows-server-2003-standard-x86-64-sp2.iso: ISO 9660 CD-ROM filesystem data 'EN_OS_2939.3


Regards.

[Qemu-devel] Re: Boot Failure (CDROM boot failure code : 0004)

[Volkan YAZICI]

On Mon, 16 Jun 2008, Anthony Liguori <anthony@codemonkey.ws> writes:
> Volkan YAZICI wrote:
>>   root:~# dd bs=$[1024 * 32] \
>>   > if=/dev/scd0 \
>>   > of=/root/windows-server-2003-standard-x86-64-sp2.iso
>>   
>
> Your dd line is very suspect.  Why are you using a block size of 32k?
> The sector size of most CD-ROMs is 2k.  I've certainly encountered my
> fair share of CD-ROMS that were an odd multiple of 2k.  dd will
> silently truncate the ISO if the size is not a multiple of 32k.

You seem to be right. See below command outputs.

  windows:~$ md5sum windows-server-2003-standard-x86-64-sp2.iso \
  > >windows-server-2003-standard-x86-64-sp2.iso.md5sum

  root:~# dd bs=2048 if=/dev/scd0 of=/root/scd0.iso
  root:~# md5sum scd0.iso >scd0.iso.md5sum

  root:~# diff \
  > /root/scd0.iso.md5sum
  > /home/windows/windows-server-2003-standard-x86-64-sp2.iso.md5sum
  1c1
  < b5d670b7360dc43af8157a50de43bac1  scd0.iso
  ---
  > cfcf3b24d9b44e75826259c9e914bf40  windows-server-2003-standard-x86-64-sp2.iso

  root:~# ls -lb \
  > /home/windows/windows-server-2003-standard-x86-64-sp2.iso \
  > /root/scd0.iso
  -rw-r--r-- 1 windows windows 4840085504 2008-06-13 17:54 /home/windows/windows-server-2003-standard-x86-64-sp2.iso
  -rw-r--r-- 1 root    root    4840085504 2008-06-17 08:54 /root/scd0.iso

But trying to start qemu with the scd0.iso didn't make any
difference. Should I try with a different bs value?


Regards.

[Qemu-devel] Re: Boot Failure (CDROM boot failure code : 0004)

[Volkan YAZICI]

On Mon, 16 Jun 2008, "Sebastian Herbszt" <herbszt@gmx.de> writes:
>>  QEMU BIOS - build: 02/08/07
>>  $Revision: 1.174 $ $Date: 2006/10/17 16:48:05 $
>>  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
>>
>>  CDROM boot failure code : 0004
>>  Boot from Cd-Rom failed
>>  FATAL: Could not read the boot disk
>
> Can you reproduce the problem with a recent bios version?
> You can get the latest qemu version (based on 1.207) from
> http://svn.savannah.gnu.org/viewvc/*checkout*/trunk/pc-bios/bios.bin?root=qemu

See below output:

  windows:~/qemu/share/qemu$ mv bios.bin bios.bin.org
  windows:~/qemu/share/qemu$ wget \
  > "http://svn.savannah.gnu.org/viewvc/*checkout*/trunk/pc-bios/bios.bin?root=qemu" \
  > -O bios.bin

  root:~# /home/windows/qemu/bin/qemu-system-x86_64 \
  > -cdrom /root/scd0.iso \
  > -hda /home/windows/disk-qcow2-20g.img \
  > -boot d -localtime -m 512 -L /home/windows/qemu/share/qemu

  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? What does "could not read the boot disk" mean exactly?


Regards.

[Qemu-devel] Re: Boot Failure (CDROM boot failure code : 0004)

[Volkan YAZICI]

On Mon, 16 Jun 2008, Avi Kivity <avi@qumranet.com> writes:
> You need to use qemu-system-x86_64 for 64-bit guests.  However, that
> problem doesn't quite fit the error you get.  Worth trying though.

Sorry, no change.

> Is the cd image mountable on the host?

It appears to be:

  root:# for ISO in \
  > /home/windows/windows-server-2003-standard-x86-64-sp2.iso \
  > /root/scd0.iso; \
  > do mount -o loop $ISO /mnt && umount /mnt; done

Above command runs without a problem.


Regards.

[Qemu-devel] Re: Boot Failure (CDROM boot failure code : 0004)

[Volkan YAZICI]

On Tue, 17 Jun 2008, Volkan YAZICI <yazicivo@ttmail.com> writes:
>   root:~# diff \
>   > /root/scd0.iso.md5sum
>   > /home/windows/windows-server-2003-standard-x86-64-sp2.iso.md5sum
>   1c1
>   < b5d670b7360dc43af8157a50de43bac1  scd0.iso
>   ---
>   > cfcf3b24d9b44e75826259c9e914bf40  windows-server-2003-standard-x86-64-sp2.iso

More interesting results:

  windows:~# md5sum windows-server-2003-standard-x86-64-sp2-dd-bs-*
  b5d670b7360dc43af8157a50de43bac1  windows-server-2003-standard-x86-64-sp2-dd-bs-1024.iso
  b253aa547f8a7269b6589caa001bd566  windows-server-2003-standard-x86-64-sp2-dd-bs-2048.iso
  64a9d318690bfe223b0e3c5c15b392e3  windows-server-2003-standard-x86-64-sp2-dd-bs-32768.iso
  b5d670b7360dc43af8157a50de43bac1  windows-server-2003-standard-x86-64-sp2-dd-bs-512.iso

Quite funny. (By the way, all of them are of same size.) Should I trust
that bs={1024,512} produce the right result?  Anyway, neither of them
solve the problem. Any ideas?



Regards.

Re: [Qemu-devel] Re: Boot Failure (CDROM boot failure code : 0004)

[Brad Campbell]

Jens Axboe wrote:

> 
> 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.
> 

Actually, I rip all my CD's to .iso using dd and I've never had one fail to boot when I burned the 
.iso back to a CD. It's a bit for bit copy. Why would it not work?

brad@bklaptop2:/media/raid3/isos$ ls *.iso | wc -l
59

Every single image in that directory has been burned to a CD-RW at one point or another and always 
booted flawlessly. They were _all_ ripped using dd from originals either pressed or burned.

Brad
-- 
"Human beings, who are almost unique in having the ability
to learn from the experience of others, are also remarkable
for their apparent disinclination to do so." -- Douglas Adams

[Qemu-devel] Re: Boot Failure (CDROM boot failure code : 0004)

[Sebastian Herbszt]

>  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

Re: [Qemu-devel] Re: Boot Failure (CDROM boot failure code : 0004)

[Juergen Keil]

Volkan YAZICI writes:
> 
> On Tue, 17 Jun 2008, Volkan YAZICI <yazicivo@ttmail.com> writes:
> >   root:~# diff \
> >   > /root/scd0.iso.md5sum
> >   > /home/windows/windows-server-2003-standard-x86-64-sp2.iso.md5sum
> >   1c1
> >   < b5d670b7360dc43af8157a50de43bac1  scd0.iso
> >   ---
> >   > cfcf3b24d9b44e75826259c9e914bf40  
windows-server-2003-standard-x86-64-sp2.iso
> 
> More interesting results:
> 
>   windows:~# md5sum windows-server-2003-standard-x86-64-sp2-dd-bs-*
>   b5d670b7360dc43af8157a50de43bac1  
windows-server-2003-standard-x86-64-sp2-dd-bs-1024.iso
>   b253aa547f8a7269b6589caa001bd566  
windows-server-2003-standard-x86-64-sp2-dd-bs-2048.iso
>   64a9d318690bfe223b0e3c5c15b392e3  
windows-server-2003-standard-x86-64-sp2-dd-bs-32768.iso
>   b5d670b7360dc43af8157a50de43bac1  
windows-server-2003-standard-x86-64-sp2-dd-bs-512.iso
> 
> Quite funny. (By the way, all of them are of same size.) Should I trust
> that bs={1024,512} produce the right result?  Anyway, neither of them
> solve the problem. Any ideas?

That is unexpected.  I'd expect that you get exactly the same
bits no matter what block size >= 2048 (and power of 2) you use.

Some drives (or the OS) also allow block sizes of 1024 or
512 bytes, but you should still get exactly the same bits.


Smells like a bug, either with the optical drive, or some
driver, filesystem, or OS issue.


What happens when you use "cmp -l" on a pair of the above
iso images which have not have the same md5 checksum?  

At what file offset does it find differences?  Only on the
last 2-3 blocks of the file, perhaps?

Does cmp -l only find a few differences per iso image pair?
What are the differences?

[Qemu-devel] Re: Boot Failure (CDROM boot failure code : 0004)

[Volkan YAZICI]

On Tue, 17 Jun 2008, "Sebastian Herbszt" <herbszt@gmx.de> writes:
> The size looks like a dvd. Do other dvd images work? What are their
> sizes?

Awkwardly, another DVD of the same Microsoft Windows Server version
works without a problem. Pff...

Anyway, thanks everybody for their kindly help. I'll re-post this single
Microsoft DVD to Redmond trash.



Regards.

Re: [Qemu-devel] Re: Boot Failure (CDROM boot failure code : 0004)

[Anthony Liguori]

Volkan YAZICI wrote:
> On Tue, 17 Jun 2008, Volkan YAZICI <yazicivo@ttmail.com> writes:
>   
>>   root:~# diff \
>>   > /root/scd0.iso.md5sum
>>   > /home/windows/windows-server-2003-standard-x86-64-sp2.iso.md5sum
>>   1c1
>>   < b5d670b7360dc43af8157a50de43bac1  scd0.iso
>>   ---
>>   > cfcf3b24d9b44e75826259c9e914bf40  windows-server-2003-standard-x86-64-sp2.iso
>>     
>
> More interesting results:
>
>   windows:~# md5sum windows-server-2003-standard-x86-64-sp2-dd-bs-*
>   b5d670b7360dc43af8157a50de43bac1  windows-server-2003-standard-x86-64-sp2-dd-bs-1024.iso
>   b253aa547f8a7269b6589caa001bd566  windows-server-2003-standard-x86-64-sp2-dd-bs-2048.iso
>   64a9d318690bfe223b0e3c5c15b392e3  windows-server-2003-standard-x86-64-sp2-dd-bs-32768.iso
>   b5d670b7360dc43af8157a50de43bac1  windows-server-2003-standard-x86-64-sp2-dd-bs-512.iso
>
> Quite funny. (By the way, all of them are of same size.) Should I trust
> that bs={1024,512} produce the right result?  Anyway, neither of them
> solve the problem. Any ideas?
>   

Sounds like there are errors on your disk.

Regards,

Anthony Liguori

>
> Regards.
>
>
>   

Re: [Qemu-devel] Re: Boot Failure (CDROM boot failure code : 0004)

[Jens Axboe]

On Mon, Jun 16 2008, Avi Kivity wrote:
> Jens Axboe wrote:
> >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. 
> 
> Why is that?  What's different in the ripped image compared to the image 
> used to burn the CD?

Just ignore me, apparently didn't have my head on last night at all.

-- 
Jens Axboe

Re: [Qemu-devel] Re: Boot Failure (CDROM boot failure code : 0004)

[Natalia Portillo]

It does not boot because that CD does not contain the needed El Torito 
pieces.

Anything you do, it won't boot.

Cannot give you more help without the CD itself.

Volkan YAZICI escribió:
> On Mon, 16 Jun 2008, Natalia Portillo <claunia@claunia.com> writes:
>   
>> Could you do the following and paste the results here?
>>
>> sudo file -s /dev/scd0
>> file <iso-image>
>>
>> Both should say something like:
>> ISO 9660 CD-ROM filesystem data '****************' (bootable)
>>     
>
> Below are the related command outputs:
>
>   root:~# file -s /dev/scd0
>   /dev/scd0: ISO 9660 CD-ROM filesystem data 'EN_OS_2939.3'
>   
>   root:~# file /home/windows/windows-server-2003-standard-x86-64-sp2.iso
>   /home/windows/windows-server-2003-standard-x86-64-sp2.iso: ISO 9660 CD-ROM filesystem data 'EN_OS_2939.3
>
>
> Regards.
>
>
>
>   

Re: [Qemu-devel] Re: Boot Failure (CDROM boot failure code : 0004)

[Natalia Portillo]

The question is.

Is it really a bootable CD or just a CD with all the SP2s integrated?
Or a DVD with multiple images from MDSN?

I know there where DVDs with multiple language images, that come from 
MDSN, with an utility to make separate ISOs of each one, but the DVD 
itself is not bootable.

Should consult your Microsoft contract documentation.

Volkan YAZICI escribió:
> On Tue, 17 Jun 2008, "Sebastian Herbszt" <herbszt@gmx.de> writes:
>   
>> The size looks like a dvd. Do other dvd images work? What are their
>> sizes?
>>     
>
> Awkwardly, another DVD of the same Microsoft Windows Server version
> works without a problem. Pff...
>
> Anyway, thanks everybody for their kindly help. I'll re-post this single
> Microsoft DVD to Redmond trash.
>
>
>
> Regards.
>
>
>
>   

Re: [Qemu-devel] Re: Boot Failure (CDROM boot failure code : 0004)

[Juergen Keil]

Anthony Liguori wrote:

> Volkan YAZICI wrote:
> > On Tue, 17 Jun 2008, Volkan YAZICI <yazicivo@ttmail.com> writes:
> >   
> >>   root:~# diff \
> >>   > /root/scd0.iso.md5sum
> >>   > /home/windows/windows-server-2003-standard-x86-64-sp2.iso.md5sum
> >>   1c1
> >>   < b5d670b7360dc43af8157a50de43bac1  scd0.iso
> >>   ---
> >>   > cfcf3b24d9b44e75826259c9e914bf40  
windows-server-2003-standard-x86-64-sp2.iso
> >>     
> >
> > More interesting results:
> >
> >   windows:~# md5sum windows-server-2003-standard-x86-64-sp2-dd-bs-*
> >   b5d670b7360dc43af8157a50de43bac1  
windows-server-2003-standard-x86-64-sp2-dd-bs-1024.iso
> >   b253aa547f8a7269b6589caa001bd566  
windows-server-2003-standard-x86-64-sp2-dd-bs-2048.iso
> >   64a9d318690bfe223b0e3c5c15b392e3  
windows-server-2003-standard-x86-64-sp2-dd-bs-32768.iso
> >   b5d670b7360dc43af8157a50de43bac1  
windows-server-2003-standard-x86-64-sp2-dd-bs-512.iso
> >
> > Quite funny. (By the way, all of them are of same size.) Should I trust
> > that bs={1024,512} produce the right result?  Anyway, neither of them
> > solve the problem. Any ideas?
> >   
> 
> Sounds like there are errors on your disk.


Assuming these are errors on the optical media:  Why doesn't the
drive detect and report them?  Shouldn't the "dd" have failed with
some sort of EIO errors?