Opened 16 years ago
Closed 15 years ago
#981 closed defect (wontfix)
Suse10.3 guest won't recognize virtual hd after clonevdi
| Reported by: | mwp | Owned by: | |
|---|---|---|---|
| Component: | virtual disk | Version: | VirtualBox 1.5.2 |
| Keywords: | Cc: | ||
| Guest type: | other | Host type: | other |
Description
see: http://forums.virtualbox.org/viewtopic.php?p=11859
Summary: The problems seams to be that clonedvi changed the ids of the virtual harddrives but Suse somehow still expects the ones from the original.
Change History (3)
comment:1 by , 16 years ago
comment:2 by , 16 years ago
| Component: | other → virtual disk |
|---|
comment:3 by , 15 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
As I wrote there this is not really a bug but the intended behavior. The ID of a virtual disk is built from the UUID of the .vdi image which changes when cloning the image. You have to adapt the ID in your bootloader script. Note that you had to do the same if you would clone an OpenSUSE installation from only real hard disk to another real hard disk.