Custom Query (16363 matches)
Results (1351 - 1353 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #5680 | worksforme | iso-Image of a CD leads to an error from virtual media manager | ||
| Description |
After updating to 3.10 I received an error when I start up Virtual Box, caused by an older cd-image. This occurs on 2 different macs, the image is mountable under Mac OS-X 10.5.8. deleting the image from the list of CD/DVD-images in virtual media manager and adding it again, leads to the same error-message(see below). In the log-files are not any related errors, so I don't include them here. ----
Could not open the medium '/Users/Shared/vpc-images/cd dvd images/notcd.iso'.
VD: error VERR_VD_RAW_INVALID_HEADER opening image file '/Users/Shared/vpc-images/cd dvd images/notcd.iso' (VERR_VD_RAW_INVALID_HEADER).
Fehlercode:
NS_ERROR_FAILURE (0x80004005)
Komponente:
Medium
Interface:
IMedium {aa8167ba-df72-4738-b740-9b84377ba9f1}
Callee:
IVirtualBox {2158464a-f706-414b-a8c4-fb589dfc6b62}
----
|
|||
| #13915 | fixed | Windows 8.1 host, VB 4.3.24 DNS for NAT Network stopped working | ||
| Description |
Host: Windows 8.1, VB 4.3.24
Guests: 2 Lubuntu 14.04.2, configured with NAT Network The reason I want static IPs is so that the VMs can talk to each other and to have stable names for them in /etc/hosts. Also, this is running on a laptop that moves between networks so I cannot do bridge as in some cases I can't get more than 1 IP.
With 4.3.22, I could set "C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" modifyvm "Lubuntu" --natdnshostresolver1 on but it does not help.
The only solution so far is to use a different DNS server (e.g. |
|||
| #13987 | fixed | VBox 4.3.26 NAT Network unstable | ||
| Description |
VBox 4.3.26 running on Windows 8.1 x64 host 2 Ubuntu 14.04.2 VMs configured to use a NAT network After a while (maybe under heavy network load between the 2 VMs?) the NAT network stops passing traffic to the outside world. The 2 VMs can still talk to each other but not with the outside world until they are both rebooted. This started with the upgrade to 4.3.26, the same setup worked OK before. |
|||

