Custom Query (16363 matches)
Results (1957 - 1959 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #9132 | fixed | Switching from 32-bit to 64-bit OS Type/version doesn't work | ||
| Description |
We inadvertently chose the default "Windows 7" (32-bit) OS type when defining a VM and then installing from a 64-bit Windows 7 .iso file. Windows 7 provided an error message, and we eventually figured out it was because we were running a 32-bit VM for a 64-bit OS. So, in the VirtualBox GUI we switched the Version (os type) to "Windows 7 (64 bit)", and started the VM again with the same .iso file, and the same error message appeared when Windows 7 tried to install. We then defined another VM using "Windows 7 (64 bit)", used the same 64-bit Windows 7 .iso file to start the installation, and it worked fine. Consequently, I think something is wrong when switching between OS types, at least for "Windows 7" os type and "Windows 7 (64 bit)" -- that it doesn't set up the 64-bit environment properly. |
|||
| #9204 | duplicate | Invalid settings detected | ||
| Description |
"Invalid settings detected" is the only message you receive at the bottom of the VirtualBox GUI's Settings page if there is a problem with settings. The lack of specifics makes it difficult to determine which settings are invalid. In our case, we had checked the "External Display" setting but did not provide any other information. Is it possible to provide the name of the tab or something else that would allow us to focus on the setting in error? |
|||
| #11423 | fixed | VBoxManage controlvm cannot change NIC promiscuous mode => Fixed in SVN | ||
| Description |
The VirtualBox GUI allows setting the promiscuous mode of a network adapter, but there is no corresponding way to do this via a VBoxManage controlvm option. Our use of VMs requires us to script the settings of many VMs at once while they are running -- at least, to the same extent as the GUI can -- so the more control we have via VBoxManage, the better. Of course, we can do this with a powered-off VM using modifyvm and this option: --nicpromisc<1-N> deny|allow-vms|allow-all but we want to do this without powering off the VM. |
|||

