Opened 16 years ago
Closed 14 years ago
#4070 closed defect (invalid)
A cloned openSuse disk (clonehd) doesn't boot on Windows XP host
Reported by: | Len Alt | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 2.2.2 |
Keywords: | Cc: | ||
Guest type: | other | Host type: | other |
Description
A cloned disk doesn't boot (VBoxManage clonehd original.vdi clone.vdi). The original disk is a freshly build expandable disk with 30 GB size. The disk was created with default options using openSuse 11.1 installation DVD. Disk formatting is partition based.
Log files for sessions with the original and cloned disks are attached. Also attached is a screen shot for the failed boot.
Note:
Clones of Fedora 10 disks work fine (LVM formatting)
Attachments (1)
Change History (3)
by , 16 years ago
comment:1 by , 15 years ago
- Please make sure both VMs are configured similarly.
- Retry with 3.2.0
- Try to use OVF VM Import/Export
-Technologov
comment:2 by , 14 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
This is caused by openSUSE bolting itself to the hard disk serial number (which by default is derived from the disk image UUID). The documentation already mentions how one can override this hard disk serial number logic.
From my perspective it's plain silly to configure a system this way (not your fault, it's the SUSE people making this decision for you). The very same problem would happen on real hardware, e.g. if you copy the image of a failing disk to a new one.
logs of sessions with clone and original vdis and failed boot screen shot