Custom Query (16363 matches)
Results (1804 - 1806 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #9663 | fixed | Cannot go beyond 256 colors on highest res | ||
| Description |
On Mac OS X Snow Leopard host, Windows 2000 SP4 client, vm additions installed. Only 256 colors are supported when set to highest resolution (regardless of this resolution). i.e. if windows size is 1280x1024, 1024x768 does support 32bit color, but 1280x1024 doesn't, if window size is 1920x1080, 1440x990 will support 32bit color but 1920x1080 won't. |
|||
| #7343 | fixed | Cannot import VM on 3.2.8 exported from 3.2.6 | ||
| Description |
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. |
|||
| #11127 | obsolete | Cannot import ovf with disk line --ignore | ||
| Description |
The command "VBoxManage import ~/.vagrant.d/boxes/lucid32/box.ovf -n" mentions: 9: Hard disk image: source image=box-disk1.vmdk, target path=/Users/mcobden/VirtualBox VMs/lucid32/box-disk1.vmdk, controller=8;channel=0
(change target path with "--vsys 0 --unit 9 --disk path";
disable with "--vsys 0 --unit 9 --ignore")
When I try "VBoxManage import ~/.vagrant.d/boxes/lucid32/box.ovf --vsys 0 --unit 9 --ignore " I get the error: Progress state: NS_ERROR_FAILURE VBoxManage: error: Internal inconsistency looking up disk image 'vmdisk1' VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component Appliance, interface IAppliance, callee Context: "ImportAppliance" at line 793 of file VBoxManageAppliance.cpp The full output looks like this: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interpreting /Users/mcobden/.vagrant.d/boxes/lucid32/box.ovf...
OK.
Disks: vmdisk1 85899345920 -1 http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized box-disk1.vmdk -1 -1
Virtual system 0:
0: Suggested OS type: "Ubuntu"
(change with "--vsys 0 --ostype <type>"; use "list ostypes" to list all possible values)
1: Suggested VM name "lucid32"
(change with "--vsys 0 --vmname <name>")
2: Number of CPUs: 1
(change with "--vsys 0 --cpus <n>")
3: Guest memory: 384 MB
(change with "--vsys 0 --memory <MB>")
4: Network adapter: orig NAT, config 3, extra slot=0;type=NAT
5: CD-ROM
(disable with "--vsys 0 --unit 5 --ignore")
6: IDE controller, type PIIX4
(disable with "--vsys 0 --unit 6 --ignore")
7: IDE controller, type PIIX4
(disable with "--vsys 0 --unit 7 --ignore")
8: SATA controller, type AHCI
(disable with "--vsys 0 --unit 8 --ignore")
9: Hard disk image: source image=box-disk1.vmdk -- disabled
0%...
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Internal inconsistency looking up disk image 'vmdisk1'
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component Appliance, interface IAppliance, callee
Context: "ImportAppliance" at line 793 of file VBoxManageAppliance.cpp
Also, the correct version is not in the bug dropdown VBoxManage --version 4.1.23r80870 |
|||

