Opened 14 years ago
Closed 9 years ago
#7631 closed defect (fixed)
VRDP problem
Reported by: | Raveman | Owned by: | |
---|---|---|---|
Component: | RDP | Version: | VirtualBox 3.2.10 |
Keywords: | Cc: | ||
Guest type: | Windows | Host type: | Linux |
Description (last modified by )
Have a problem with the new 3.2.10 when i connect to the guest i see everything but if i click somewhere dont happen anything but if i reconnect i see happened only rdp freezed. So i need to reconnect 100x if i want to work on guest.This is only from 3.2.10 with 3.2.8 and 3.2.10 Guestadd.
Attachments (5)
Change History (14)
comment:1 by , 14 years ago
by , 14 years ago
comment:2 by , 14 years ago
I'm seeing this behavior on two windows 2008 server vm's, ubuntu host, vbox 3.2.8. It started after I moved the VDI's for these guests from direct-attached storage to a NAS device (not sure if it's coincidence, I updated to 3.2.8 around the same time).
I use VRDP/VBoxHeadless exclusively. For me VRDP freezes usually after logging in to the guest: the display doesn't update, keyboard/mouse movements look ineffective. But he vm is active and responding because like the ticket says, you can disconnect and reconnect w/ RDP and see the results of your mouse movements and keyboard input, though the display stays frozen in that state and doesn't update.
comment:3 by , 14 years ago
I think I have the same issue using VRDP.
VirtualBox version is 4.0 running on Ubuntu 10.10 64bit. The virtual machine is running Windows XP Pro 64bit and started with VBoxHeadless "--vrdpon". The remote machine connecting to virtual machine is as well Ubuntu 10.10 64bit and using "rdesktop <targethost>".
When virtual machine is started it usually works but at some point it stops working. I have tried different settings for rdesktop - nothing helps. Also VBoxManage controlvm options seem not to help. Usually I have to force shutdown the virtual machine and it's bad as I have to start every application again. Now I found out a way to continue from VRDP freeze without loosing current work or going the hard way.
To continue working, run "VBoxManage controlvm <host> savestate" to store current state to disk. The VBoxHeadless exits. Then just restart using for example "VBoxHeadless --vrdp on startvm <virtualmachine>". Now when you reconnect using VRDP the virtual machine and VRDP works again.
comment:4 by , 14 years ago
ps. I would attach vbox.log but for some strange reason cannot figure out where it is. It is not in /var/log, not in user's home in .VirtualBox. Maybe it's not enabled as the virtual system was not installed by me.
comment:5 by , 14 years ago
That log file is normally automatically created. Have a look at the main VM selector window, open 'Machine' / 'Show Log...'.
by , 14 years ago
Attachment: | harry-vbox.log added |
---|
The same issue is here, not sure if crashed when this log was generated.
comment:6 by , 14 years ago
I attached the latest log I found. I'm not sure if the problem happened when this log was generated. I will attach new log if use virtualbox and the bug happens.
I also noticed that I stated incorrectly the virtualbox version earlier. I was NOT running latest Virtualbox 4.0.0 but instead older 3.2.10 - the same version that original reporter described to have problems with.
comment:7 by , 14 years ago
I'm running the latest 4.0.2 on Debian and still have the same problem. Every time I have to ctrl-c to break the VBoxHeadless process to restart. I tried to follow harryvbox's instruction to savestate but it does not work for me and the savestate command just freeze. I've attached the relevant VBox.log file.
by , 14 years ago
Attachment: | VBox.log.2 added |
---|
by , 14 years ago
Attachment: | VBox.log.2.2 added |
---|
comment:8 by , 13 years ago
Please try the new extpack. The problem could be fixed there.
For VBox 4.1: this package.
For VBox 4.0: this package.
Thanks.
comment:9 by , 9 years ago
Description: | modified (diff) |
---|---|
Resolution: | → fixed |
Status: | new → closed |
The VBox.log file of such a VM session is missing.