Custom Query (16363 matches)
Results (172 - 174 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #9012 | invalid | Bridge device assignments unreliable if two identical NICs are installed on a windows host. | ||
| Description |
I have two identical (same chipset and same driver) ethernet NICs installed in a Windows 7 SP1 host. They appear on the device manager as two devices with identical names. I'd like to bridge each to a different virtual interface in a Linux guest. Unfortunately, the VirtualBox machine configuration files identify interfaces in bridging configurations only by their name, leading to an ambiguity in this case (since both devices are identical) and resulting in the two devices being randomly re-assigned to a different virtual guest interface every time. A more precise way of specifying host network devices needs to be used, perhaps mac address or the windows UUID. |
|||
| #14211 | obsolete | Incorrect handling of lack of disk space during import of ova | ||
| Description |
My system had run out of space during import of ova, but vbox is finished import in same manner like it was successful, but VM disk was corrupted. I thing there is 2 task here: app must check disk space == before import ==, correctly handle situation when system runs out of disk space, e.g. show message with option to delete or keep files. |
|||
| #14270 | obsolete | No Icon for VirtualBox application in Linux host | ||
| Description |
The icon is installing as "/usr/share/pixmaps/VBox.png". But a file virtualbox.desktop has string Icon=virtualbox |
|||

