It just happened again. This time I have recorded some new information. netstat shows a costant, non zero Send-Q: @ubuntu:~/WORKS/Programs/apache-jmeter-2.9/bin$ date ; netstat -atn | grep 3389 Wed Jun 5 15:23:24 CEST 2013 tcp 0 7301 192.168.122.1:59458 192.168.122.116:3389 ESTABLISHED @ubuntu:~/WORKS/Programs/apache-jmeter-2.9/bin$ date ; netstat -atn | grep 3389 Wed Jun 5 15:23:27 CEST 2013 tcp 0 7301 192.168.122.1:59458 192.168.122.116:3389 ESTABLISHED @ubuntu:~/WORKS/Programs/apache-jmeter-2.9/bin$ date ; netstat -atn | grep 3389 Wed Jun 5 15:23:47 CEST 2013 tcp 0 7301 192.168.122.1:59458 192.168.122.116:3389 ESTABLISHED @ubuntu:~/WORKS/Programs/apache-jmeter-2.9/bin$ date ; netstat -atn | grep 3389 Wed Jun 5 15:24:34 CEST 2013 tcp 0 7301 192.168.122.1:59458 192.168.122.116:3389 ESTABLISHED Sniffing that connection with tcpdump, I can see that no packets flows back from the VM (port 3389) back to the client: 15:22:03.402659 IP 192.168.122.1.59458 > 192.168.122.116.3389: Flags [P.], seq 2389102186:2389102247, ack 1393955760, win 1968, options [nop,nop,TS val 4537984 ecr 1648164], length 61 15:22:03.402676 IP 192.168.122.1.59458 > 192.168.122.116.3389: Flags [P.], seq 0:61, ack 1, win 1968, options [nop,nop,TS val 4537984 ecr 1648164], length 61 --- 30 seconds here --- 15:24:03.722660 IP 192.168.122.1.59458 > 192.168.122.116.3389: Flags [P.], seq 0:61, ack 1, win 1968, options [nop,nop,TS val 4568064 ecr 1648164], length 61 15:24:03.722675 IP 192.168.122.1.59458 > 192.168.122.116.3389: Flags [P.], seq 0:61, ack 1, win 1968, options [nop,nop,TS val 4568064 ecr 1648164], length 61 Looks like a network issue? On 5 June 2013 15:17, Stefano Doni wrote: > Hi Serge, > > Please find attached the remmina configuration screenshots. > > Yes, when the RDP connection hangs I simply close the RDP client and start > a new one immediately and it works correctly. > > As I mentioned, please consider that this happens also with a completely > different RDP client, so it probably has nothing to do with remmina itself. > > Thank you! > > > On 5 June 2013 14:30, Serge Hallyn wrote: > >> Quoting f3a97 (): >> > Hi Serge, >> > >> > I'm invoking remmina from the Unity shell, not from the terminal. >> >> Could you please tell me, perhaps with some screenshots, exactly what >> boxes you fill in how to start the connection? >> >> > As regard your question: I'm connecting to the VM via RDP, not VNC (it >> is >> > much faster). >> >> IIUC RDP connects to the guest itself over the guest's network. vnc wlil >> connect to the kvm process. So if the problem has to do with the >> guest's networking hanging, then connecting over vnc might let you >> analyze the guest state despite guest network being down. >> >> When the RDP connection hangs, can you simply start a new one >> immediately? >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1180777 >> >> Title: >> Windows 7 VM freeze on Ubuntu 12.04 KVM >> >> Status in “qemu-kvm” package in Ubuntu: >> New >> >> Bug description: >> Hi, >> >> I recently started using KVM over VirtualBox for my Office needs. I >> setup a Windows 7 VM on KVM and started using it through remote >> desktop. >> >> What happens is that, after some hours of usage, the remote desktop >> connection freezes. I thought it was a remmina bug, as the it was >> enough to kill and restart it to successfully connect again to the VM. >> >> However, today I've switched to a different RDP client (2X Client >> chromium app) and the freeze just happened again! >> >> Some information: >> - the host and the VM are completely idle when the freeze occurs >> - I've tried sniffing the network packets toward the RDP port during >> the freeze and found that the client is sending packets but no packet is >> sent back >> >> >> Could this be a KVM issue? How can I further debug this one (I expect >> the freeze to happen again...)? >> >> ProblemType: Bug >> DistroRelease: Ubuntu 12.04 >> Package: kvm 1:84+dfsg-0ubuntu16+1.0+noroms+0ubuntu14.8 >> ProcVersionSignature: Ubuntu 3.2.0-41.66-generic 3.2.42 >> Uname: Linux 3.2.0-41-generic x86_64 >> ApportVersion: 2.0.1-0ubuntu17.2 >> Architecture: amd64 >> Date: Thu May 16 14:12:40 2013 >> MachineType: Hewlett-Packard HP ProBook 4520s >> MarkForUpload: True >> ProcEnviron: >> TERM=xterm >> PATH=(custom, no user) >> LANG=en_US.UTF-8 >> SHELL=/bin/bash >> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-41-generic >> root=UUID=D2E20BC3E20BAAB5 loop=/hostname/disks/root.disk ro quiet splash >> vt.handoff=7 >> SourcePackage: qemu-kvm >> UpgradeStatus: No upgrade log present (probably fresh install) >> dmi.bios.date: 08/26/2010 >> dmi.bios.vendor: Hewlett-Packard >> dmi.bios.version: 68AZZ Ver. F.0A >> dmi.board.name: 1411 >> dmi.board.vendor: Hewlett-Packard >> dmi.board.version: KBC Version 57.30 >> dmi.chassis.type: 10 >> dmi.chassis.vendor: Hewlett-Packard >> dmi.modalias: >> dmi:bvnHewlett-Packard:bvr68AZZVer.F.0A:bd08/26/2010:svnHewlett-Packard:pnHPProBook4520s:pvr:rvnHewlett-Packard:rn1411:rvrKBCVersion57.30:cvnHewlett-Packard:ct10:cvr: >> dmi.product.name: HP ProBook 4520s >> dmi.sys.vendor: Hewlett-Packard >> >> To manage notifications about this bug go to: >> >> https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1180777/+subscriptions >> > >