Custom Query (16363 matches)
Results (1981 - 1983 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #16342 | fixed | Host Popup Menu doesn't popup (regression) | ||
| Description |
In 5.1.10 and 5.1.12, the Host Popup Menu (Host Key + Home) doesn't work. It's fine in 5.0.30. (My normal Host Key is Scroll Lock, but the default Right-Ctrl also has the same problem). Other "Host+<key>" combinations (e.g. Host+N / Session Info) are fine, even on 5.1.12: it's only the popup menu that does nothing. |
|||
| #16340 | worksforme | UI no longer reports active RDP port when using range | ||
| Description |
When specifying a range in the RDP port field, I recall the previous UI would update to show the issued port for that VM once the VM starts. I also recall there used to be a builtin Java based RDP client that seems to have been removed. I'm unsure if the two are related. Currently, the only way to find the assigned RDP port when using a range is by digging through the VM's startup log. While this works, it is in no way efficient because you have to search the log for this information. It would be far simpler if the UI would update the Display area to show the assigned port while the VM is running. The version I am running: Version 5.1.12 r112440 (Qt5.6.2) Please fix/add/correct. Thanks. |
|||
| #16337 | invalid | VM hangs with huge I/O | ||
| Description |
Hi all, I've been experiencing a strange problem. Basically, after the guest OS is completely booted, it starts to read the virtual disk at about 1/4 of the maximum speed and gets stuck. I've experienced it with 5 fresh installs of Windows Vista SP1 at random points in usage (right after install, in the middle of updates, after installing SP2). Each install was creating a new VDI. I've also experienced it using a resize of a working Mac OS X 10.11 VM. Original disk image was VMDK converted to VDI by qemu-img. The only way to stop the VM was killing them. Most of the times then the VDI gets so corrupt the VM is unable to start. Then taking the VDI that doesn't work, and converting it to VMDK by qemu-img, and it works perfectly. (Except corrupt images, they block qemu-img also). It doesn't seem to happen with all VDIs, other VMs have not experienced this problem. And it ONLY happens after the OS is fully loaded up to login screen or desktop. Host disk is Samsung 850 Pro 1Tb SSD. When the VM gets stuck it goes a constant reading of ~100Mb/s (no other app accessing it). |
|||

