Opened 6 years ago
Closed 6 years ago
#18518 closed defect (fixed)
RDPing to a VM with VMSVGA sends only 1 frame, then screen updates stop -> fixed after 6.0.4
| Reported by: | Socratis | Owned by: | |
|---|---|---|---|
| Component: | RDP | Version: | VirtualBox 6.0.0 |
| Keywords: | VMSVGA, frozen RDP | Cc: | |
| Guest type: | all | Host type: | all |
Description
- Create/Select any VM that has the Graphics Controller set to VMSVGA.
- Enable the RDP server.
- Start the VM and connect via an RDP client, MSRDP for OSX or Remmnina will do.
- Connection is successful, but after the first frame comes in, no updates occur.
- Mouse/keyboard input continue to work, so the connection itself is fine.
- The 3D acceleration setting is irrelevant.
- The same exact setup, but with the Graphics Controller set to VBoxVGA works as expected.
- Behavior started with 6.0.0.
- Log files for VBoxVGA/VMSVGA are identical as two drops of water.
Related discussion in the forums: https://forums.virtualbox.org/viewtopic.php?f=3&t=92313
Change History (5)
comment:1 by , 6 years ago
comment:2 by , 6 years ago
| Summary: | VRDPing to a VM with VMSVGA sends only 1 frame, then screen updates stop → RDPing to a VM with VMSVGA sends only 1 frame, then screen updates stop |
|---|
comment:3 by , 6 years ago
| Summary: | RDPing to a VM with VMSVGA sends only 1 frame, then screen updates stop → RDPing to a VM with VMSVGA sends only 1 frame, then screen updates stop -> fixed after 6.0.4 |
|---|
comment:5 by , 6 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
I just realized that the title of the ticket is wrong. Instead of "VRDPing to a VM..." can someone rename that to simply "RDPing to a VM..."? That "V" is superfluous there. TIA.