Custom Query (16363 matches)
Results (451 - 453 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #12244 | fixed | VirtualBox 4.3 - wrong hardwareuuid => Fixed in SVN | ||
| Description |
If you run the following command: VBoxManage --nologo showinfo --machinereadable "YOUR MACHINE NAME" | grep 'hardwareuuid'
You get the following result: This is very annoying, because lot's of scripts use the variable hardwareuuid to start or modify a virtual machine. But with such a hardwareuuid all scripts won't work anymore. Please correct this. By the way: The following command doesn't have any effect in version 4.3: VBoxManage modifyvm "YOUR MACHINE NAME" --hardwareuuid "30761f24-1e22-49c8-a4a5-dedc4a7ed74c" The hardware uuid is after this command still full of zeros. |
|||
| #12182 | fixed | Failed to create the host network interface => Fixed in SVN | ||
| Description |
I have two VMs that worked properly on v4.2.6. I upgraded vbox to 4.3 today and now can only start-up the VMs if I have a Bridged Adapter. The Host-Only adapter has defaults of IP: 0.0.0.0, Subnet 0.0.0.0 and will not save any changes (I tried updating to 192.168.56.1 and 255.255.255.0). When that didn't work I tried deleting and recreating the Host-Only adapter and received this error: Failed to create the host network interface.
Assertion failed: [!aGuid.isValid()] at 'D:\tinderbox\win-4.3\src\VBox\Main\src-server\HostNetworkInterfaceImpl.cpp' (74) in long __cdecl HostNetworkInterface::init(class com::Bstr,class com::Bstr,class com::Guid,enum __MIDL___MIDL_itf_VirtualBox_0000_0000_0034).
Please contact the product vendor!.
Result Code: E_FAIL (0x80004005)
Component: HostNetworkInterface
Interface: IHostNetworkInterface {f6e556f9-d598-409b-898c-8ba99d9b05ae}
Although the adapter deleted here, as soon as I restarted Vbox, the default Host-only adapter was back. These VMs are a lab build that must be separated completely from both the internal network and the internet. |
|||
| #13554 | duplicate | Unable to get out of scaled mode in Mac OS X | ||
| Description |
When running VirtualBox on Mac OS X, it is impossible to get out of scaled mode once entered. Neither pressing host-c nor using the menu allows one to return to the normal windowed mode. The only way to return to windowed mode is to shut down the virtual machine and restart it. My machine is a 13.3 inch MacBook Pro running OS X 10.9 Mavericks. My guest is a Windows 10 machine. |
|||

