Custom Query (16363 matches)
Results (715 - 717 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #5538 | obsolete | Cannot assign specific mac address for bridged networking | ||
| Description |
In our networking environment we all MAC addresses must be pre-registered before the computer can even get on the network. Hence I would very much like to specify a specific address in Settings / Network / Adapter 1 / Attached to: (Click on cog wheel) / Guest MAC Address. However it seems I cannot enter any text to the text widget. It appears I can just have VirtualBox assign another random address by clicking on the green cycle. I can change the setting by editing the XML file manually after creating the virtual machine, but it would be much simpler to just assign one my registered addresses in the GUI. |
|||
| #5540 | obsolete | Vertex Buffer Objects are not shared between contexts in X11 guest | ||
| Description |
When creating a vertex buffer object (VBO) inside a GLX application which uses multiple GL contexts, the VBO's are not shared between contexts. The VBO ID's which are returned by glGenBuffers start at 1 for each context. This issue does not occur for textures generated by glGenTextures. This was tested on both Ubuntu 9.10 and OpenSuse 11.2 guests with a Windows host, in VirtualBox 3.0.12. |
|||
| #5541 | obsolete | VMMR0.r0 expects C: drive to be the Windows System drive | ||
| Description |
I was getting the VERR_NO_MEMORY (can't remember exactly, but something like this) on starting VMs. I am using the Windows version of VirtualBox. I was getting an "unknown error" loading VMMR0.r0. Since I could not think of any reason why VMMR0.ro should fail to load, I took a guess that because my system drive is E: and not C:, perhaps that was the problem. I ran the command subst C: E:\ and that gas definitely resolved the problem. Make VirtualBox more tolerant of non-C: system drives. |
|||

