Hi Serge,

In order to reconnect, I have simply restarted another RDP client without
any further step required (no need to use VNC and ping, it was just a test
to check network connectivity).


On 24 July 2013 15:16, Serge Hallyn <email address hidden> wrote:

> Quoting f3a97 (<email address hidden>):
> > Hi Serge,
> >
> > I performed the experiment you suggested:
> >
> > 1) Connected with RDP client
> > 2) Worked until it hanged
> > 3) Successfully connected to the VM via virt-manager (RDP client still
> > freezed)
> > 4) Verified that Windows is still connected to the network
> > 5) Successfully pinged my host IP from within the VM (ping 192.168.122.1)
>
> Thanks!  So just to be sure, after this did you check whether the RDP
> client worked again?  If not, were you able to re-connect with a new
> RDP client?  If so, then can you also re-connect with a new RDP client
> without first connecting via VNC and pinging the host from the guest?
> (This should tell us whether the problem is the RDP server in windows,
> or the network connection at some layer going stale until we ping).
>
> --
> 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:
>   Confirmed
>
> Bug description:
>   Hi,
>
>   I have recently 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
>