Custom Query (16363 matches)
Results (418 - 420 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #4053 | obsolete | GUI: Don't enable VT-x/AMD-V by default if unsupported by the host CPU | ||
| Description |
Only socket AM2 versions of AMD64/AMD64 X2 actually have CPU virtualization. I have a socket 939 version and it has none. The virtual machine shows VT-x/AMD-V to be enabled and I can't find any way to disable it since the option is greyed out in the virtual machine configuration. (possibly because I don't actually have it) |
|||
| #4058 | obsolete | Replacing a file (saving over a file) on \vboxsrv\shared\file.ext gives access denied | ||
| Description |
Replacing a file or doing saving as, over an existing file on \vboxsrv\shared\file.ext gives access denied. If I use Photoshop to save a file on the shared folder it gives an error of access denied. Work-around:
This behaviour was not happening many versions before (dont know which version). |
|||
| #4064 | obsolete | Internal network very slow gPXE booting a VM from another (Linux) VM | ||
| Description |
I am trying to develop a system where I load gPXE's undionly.kpxe via TFTP and then complete the process using HTTP under control of gPXE. Normally it gets gPXE very quickly, gets the tiny script, and then gets the next images very slowly - about 14 or so 1518 byte packets per second. This rate seems independant of the NIC used in the client VM and also independant of the web server in use. The boot server is Xubuntu 9.04. Sometimes (very infrequently) the performance is much, much faster. Debugging flags in gPXE do not show any errors being detected and the packet size is consistent. |
|||

