Opened 15 years ago
Closed 12 years ago
#7343 closed defect (fixed)
Cannot import VM on 3.2.8 exported from 3.2.6
Reported by: | Attila Nagy | Owned by: | |
---|---|---|---|
Component: | virtual disk | Version: | VirtualBox 3.2.8 |
Keywords: | Cc: | ||
Guest type: | Solaris | Host type: | other |
Description (last modified by )
I installed Osol b134 into Vbox on Solaris. I then exported it, and now import attempts fail, both on WinXP (32 bit), and Mac (exact version not known).
I created two virtual disks, one for rpool (a 20 GB sparse file, now ~3.5GB ), and one 2 GB for swap (sparse too. now ~150MB).
This same virtual machine could successfully be exported from my machine, and imported back on both mac and xp with VBox 3.2.6 (and earlier). With 3.2.8, if I import it, only the swap image is imported - twice (swap.vmdk and swap_1.vmdk).
Upon the startup of the guest, all we get is "bad pbr sig", which is true, since we have two swaps, both without a boot record.
If I manually remove swap_1.vmdk, move swap.vmdk to secondary slave (as in the original setup)(ICH6 is used), and manually add the rpool root image to pri master, then Osol begins to boot. If we break into the console, we can see that the copyright is displayed, but after that a lot of ata read errors pop up, and the guest OS goes into a continuous reboot cycle.
If I boot from an osolb134 cd iso, and try zpool import , it shows the disk in question, but I'm unable to import the rpool - Solaris says, that devices in the pool are not available.
Attachments (4)
Change History (6)
by , 15 years ago
Attachment: | slicer-opensolaris-2010-08-17-12-34-23.log added |
---|
by , 15 years ago
Attachment: | slicer-3.6.1-opensolaris.ovf added |
---|
by , 15 years ago
Attachment: | vbox.bug-copyright-ata.errors.PNG added |
---|
screenshot showing the begin of ata errors with the end of the copyright notice
by , 15 years ago
Attachment: | vbox.bug-mountroot.PNG added |
---|
the end of the boot process, after that reboot follows
comment:1 by , 15 years ago
I have the same problem, running Solaris10u8 patched upto July 2010, exporting image to VN on MAc and linux failed.
Downgraded Mac and tried to import the image again got the same result. Downgraded the solaris to 3.2.6 and tried again, same result.
Looks like its an issue on EXPORT, the .ovf file gives the same UUID for both disks. I expect its the code for eport on solaris with more then 1 disk (SATA in this case controller name SATA Controller).
As you can't edit the ovf file to fix the UUID on the AttachedDEvice Image uuid there is no work around for this.
comment:2 by , 12 years ago
Description: | modified (diff) |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Closing, please reopen if still relevant with a recent release of VirtualBox.
the exported ovf file