VirtualBox

Ticket #9881 (new defect)

Opened 2 years ago

Last modified 2 years ago

VBoxManage convertfromraw diskboot.img does not work as expected

Reported by: tru Owned by:
Priority: major Component: virtual disk
Version: VirtualBox 4.1.6 Keywords:
Cc: Guest type: other
Host type: Linux

Description

VirtualBox-4.1-4.1.4_74291_rhel5-1.x86_64

diskboot.img is the CentOS 4 i386 usb diskboot image from  http://mirror.centos.org/centos/4/os/i386/images/diskboot.img

VBoxManage convertfromraw diskboot.img a.vdi does not produce a bootable disk

reproduce with: 1) VBoxManage createvm --name testing --ostype RedHat --register 2) VBoxManage modifyvm testing --memory 1024 --nictype1 82540EM --boot1 disk --boot2 none --boot3 none --boot4 none 3) VBoxManage convertfromraw -format VDI diskboot.img a.vdi 4) VBoxManage storagectl testing --name 'IDE Controller' --add ide --controller PIIX4 5) VBoxManage storageattach testing --storagectl 'IDE Controller' --port 0 --device 0 --type hdd --medium a.vdi 6) VBoxManage startvm testing

workaround: a) lvcreate --name testing --size 13M volumegroup b) dd if=diskboot.img of=/dev/volumegroup/testing c) VBoxManage internalcommands createrawvmdk -filename b.vdi -rawdisk /dev/volumegroup/testing d) VBoxManage clonehd b.vdi c.vdi

replace a.vdi by either b.vdi or c.vdi and the machine boots

Change History

comment:1 Changed 2 years ago by tru

reformatting VirtualBox-4.1-4.1.4_74291_rhel5-1.x86_64

diskboot.img is the CentOS 4 i386 usb diskboot image from  http://mirror.centos.org/centos/4/os/i386/images/diskboot.img

VBoxManage convertfromraw diskboot.img a.vdi does not produce a bootable disk

reproduce with:
1) VBoxManage createvm --name testing --ostype RedHat --register
2) VBoxManage modifyvm testing --memory 1024 --nictype1 82540EM --boot1 disk --boot2 none --boot3 none --boot4 none 
3) VBoxManage convertfromraw -format VDI diskboot.img a.vdi 
4) VBoxManage storagectl testing --name 'IDE Controller' --add ide --controller PIIX4 
5) VBoxManage storageattach testing --storagectl 'IDE Controller' --port 0 --device 0 --type hdd --medium a.vdi
6) VBoxManage startvm testing

workaround: 
a) lvcreate --name testing --size 13M volumegroup 
b) dd if=diskboot.img of=/dev/volumegroup/testing 
c) VBoxManage internalcommands createrawvmdk -filename b.vdi -rawdisk /dev/volumegroup/testing
d) VBoxManage clonehd b.vdi c.vdi

replace a.vdi by either b.vdi or c.vdi and the machine boots 

comment:2 Changed 2 years ago by tru

4.1.6 VirtualBox-4.1-4.1.6_74727_rhel5-1.x86_64 shows the same issue.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use