RDP traffic freeze on quiet network

[f3a97]

To summarize what I think has been found so far,

  1. The main symptom is that RDP connections hang after some time
  2. This bug affects qemu 1.0 .. 1.6.5
  3. This bug affects at least windows xp and windows 7 guests
  4. Keeping another network connection open, such as vnc, prevents the RDP connection from hanging.

========================================
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

[Serge Hallyn (serge-hallyn)]

Thanks for reporting this bug. Could you please give us more
information on the VM host and the client? What do you mean
by 'kvm over virtualbox'? How exactly did you set it up?
Is the remote desktop running on a windows machine?

My guess is that the answer lies in 'kvm on virtualbox', and
how that is exporting a display to the client.

Marking this incomplete, please feel free to re-mark it new
after replying. Marking low priority as, IF I understand right,
the VM continues to run, making this annoying but with no risk of
data loss.

 status: incomplete
 importance: low

[f3a97 (f3a97)]

Hi Serge,

Thanks for the reply.

What I meant is that I started using KVM for my virtualization needs, while I was previously using VirtualBox. Sorry for not being clear on this point.

Yes the VM continues to run, however it is pretty annoying and can potentially imply that for me Win 7 on KVM is not usable in practice (think about hangs during customer presentations... ).

Thanks.

[Serge Hallyn (serge-hallyn)]

Could you show the exact remmina command you were using to connect to the VM?

If you do 'gvncviewer localhost:0' (from the same machine on which kvm is running), what do you see?

[f3a97 (f3a97)]

Hi Serge,

I'm invoking remmina from the Unity shell, not from the terminal.

As regard your question: I'm connecting to the VM via RDP, not VNC (it is
much faster).

On 5 June 2013 00:07, Serge Hallyn <email address hidden> wrote:

> Could you show the exact remmina command you were using to connect to
> the VM?
>
> If you do 'gvncviewer localhost:0' (from the same machine on which kvm
> is running), what do you see?
>
> --
> 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
>

[Serge Hallyn (serge-hallyn)]

Quoting f3a97 (<email address hidden>):
> 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?

[f3a97 (f3a97)]

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 <email address hidden> wrote:

> Quoting f3a97 (<email address hidden>):
> > 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.ve...

[f3a97 (f3a97)]

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 <email address hidden> 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 <email address hidden> wrote:
>
>> Quoting f3a97 (<email address hidden>):
>> > 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:...

[Serge Hallyn (serge-hallyn)]

Confirmed in raring.

[Serge Hallyn (serge-hallyn)]

Actually no, in my case after I had started up IE and left it sitting, the desktop logged me out, which made windows change its network settings so that RDP was not allowed. I had to log back in over spicy before I could reconnect over RDP.

[Serge Hallyn (serge-hallyn)]

In fact that did not suffice (this is raring, not precise) - windows needed to reboot to reset the model=rtl8139 nic (over tap device).

Could you tell me which network device type you are using?

It looks like I should set up a precise host on which to test.

[f3a97 (f3a97)]

Hi Serge,

Thanks for that.

Please find attached my VM complete xml configuration file (virsh dumpxml).

On 12 June 2013 21:21, Serge Hallyn <email address hidden> wrote:

> In fact that did not suffice (this is raring, not precise) - windows
> needed to reboot to reset the model=rtl8139 nic (over tap device).
>
> Could you tell me which network device type you are using?
>
> It looks like I should set up a precise host on which to test.
>
> --
> 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 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
>

[Serge Hallyn (serge-hallyn)]

Hi,

(You probably knkow this, but to explain my request, the RDP connection goes over the VM's virtual network card to talk directly to the VM. Provided you have only a single VM running, 'gvncviewer localhost:0' (or the equivalent with ssh port forwarding if you can't run X on the host) talks to the kvm process.)

Could you please start the VM, run RDP until it hangs, then connect with vnc and use the windows network admin commands to see what windows thinks is going on? I.e. does it think it is still connected to a network? If not, can you simply reconnect, or do you have to restart the driver, or do you have to restart the VM altogether?

I'm pretty sure htis is a bug in the qemu nic emulation, but am not sure where to begin diagnosing.

[f3a97 (f3a97)]

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)

So it doesn't seem to be a network disconnect issue.

Can you think of anything else?

Thanks!

On 27 June 2013 16:12, Serge Hallyn <email address hidden> wrote:

> Hi,
>
> (You probably knkow this, but to explain my request, the RDP connection
> goes over the VM's virtual network card to talk directly to the VM.
> Provided you have only a single VM running, 'gvncviewer localhost:0' (or
> the equivalent with ssh port forwarding if you can't run X on the host)
> talks to the kvm process.)
>
> Could you please start the VM, run RDP until it hangs, then connect with
> vnc and use the windows network admin commands to see what windows
> thinks is going on? I.e. does it think it is still connected to a
> network? If not, can you simply reconnect, or do you have to restart
> the driver, or do you have to restart the VM altogether?
>
> I'm pretty sure htis is a bug in the qemu nic emulation, but am not sure
> where to begin diagnosing.
>
> --
> 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 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....

[Serge Hallyn (serge-hallyn)]

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).

[f3a97 (f3a97)]

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-Pa...

[Hector Perez (heperez)]

Hi,

I reported the #1212051 (https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1212051) bug with Windows XP, but reading this case i think it could be the same issue.

I connect via RDP to my windows XP VM and after a while it seems to freeze, then, I connect via VNC an without doing anything the communications are restored between the VM and the outside world. So i can connect again with RDP.

Even more, if i leave an open connection with VNC (minimized because is more slow than RDP), connecting via RDP has no trouble and no problem of freeze (lost of communications) occurs.

f3a97, Could you do this test and tell if you have the same experience than i?, If so, my bug is the same of this.
Thanks.

[f3a97 (f3a97)]

Hi Hector,

My network configuration is different than yours - it is not bridged.
Perhaps this might help to diagnose the issue?

I'm now trying to sniff network traffic generated by the VM and see what
happens during RDP hangs: does it still poll outside servers (i.e. google
drive) or will become disconnected?

I'll report the results, stay tuned.

On 19 August 2013 00:42, Hector Perez <email address hidden> wrote:

> Hi,
>
> I reported the #1212051 (https://bugs.launchpad.net/ubuntu/+source/qemu-
> kvm/+bug/1212051) bug with Windows XP, but reading this case i think it
> could be the same issue.
>
> I connect via RDP to my windows XP VM and after a while it seems to
> freeze, then, I connect via VNC an without doing anything the
> communications are restored between the VM and the outside world. So i
> can connect again with RDP.
>
> Even more, if i leave an open connection with VNC (minimized because is
> more slow than RDP), connecting via RDP has no trouble and no problem of
> freeze (lost of communications) occurs.
>
> f3a97, Could you do this test and tell if you have the same experience
> than i?, If so, my bug is the same of this.
> Thanks.
>
> --
> 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:
> New
> 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....

[f3a97 (f3a97)]

Hi,

Eventually I've been able to reproduce the hang.

Just to recap the experiment: I have recorded network traffic during RDP
connection hangs. The result is that the VM has do not experience total
network loss: network traffic continues to flow (tcpdump from the host on
ports other than 3389).

On 5 September 2013 15:22, Stefano Doni <email address hidden> wrote:

> Hi Hector,
>
>
> My network configuration is different than yours - it is not bridged.
> Perhaps this might help to diagnose the issue?
>
>
> I'm now trying to sniff network traffic generated by the VM and see what
> happens during RDP hangs: does it still poll outside servers (i.e. google
> drive) or will become disconnected?
>
>
> I'll report the results, stay tuned.
>
>
> On 19 August 2013 00:42, Hector Perez <email address hidden> wrote:
>
>> Hi,
>>
>> I reported the #1212051 (https://bugs.launchpad.net/ubuntu/+source/qemu-
>> kvm/+bug/1212051<https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1212051>)
>> bug with Windows XP, but reading this case i think it
>> could be the same issue.
>>
>> I connect via RDP to my windows XP VM and after a while it seems to
>> freeze, then, I connect via VNC an without doing anything the
>> communications are restored between the VM and the outside world. So i
>> can connect again with RDP.
>>
>> Even more, if i leave an open connection with VNC (minimized because is
>> more slow than RDP), connecting via RDP has no trouble and no problem of
>> freeze (lost of communications) occurs.
>>
>> f3a97, Could you do this test and tell if you have the same experience
>> than i?, If so, my bug is the same of this.
>> Thanks.
>>
>> --
>> 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:
>> New
>> 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: Tr...

[Vasile Dumitrescu (y-launchpad-vasile)]

I also see these EXACT symptoms, using kvm (VM managed through livirt virsh) on Debian x64 host, guest is Windows 8, RedHat VirtIo network driver.

rgds

[Hector Perez (heperez)]

Hi f3a97, did you tried to connect via VNC when the freeze situation occurs?

This method works as a a workaround to defreeze my windows VM.

[Hector Perez (heperez)]

Since a couple of weeks ago, we started to reboot the VM diary. With this way, the problem occurs very less. We have counted only twice in this period.

[Vasile Dumitrescu (y-launchpad-vasile)]

I added a rtl8139c netcard to the VM and connected through it by RDP - no more freezes.

It looks like kvm does not play well with virtio network cards and RDP.

Red Hat virtio net windows driver version: 62.65.104.6500, 6/19/2013

I left the RH adapter on the VM, I just connect via RDP through the rtl8139c network card.

[f3a97 (f3a97)]

Thanks for the tip Dumitrescu,

I'll rive it a try AMD report here che result.

Regards
 Il 29/set/2013 14:50 "Vasile Dumitrescu" <email address hidden> ha
scritto:

> I added a rtl8139c netcard to the VM and connected through it by RDP -
> no more freezes.
>
> It looks like kvm does not play well with virtio network cards and RDP.
>
> Red Hat virtio net windows driver version: 62.65.104.6500, 6/19/2013
>
> I left the RH adapter on the VM, I just connect via RDP through the
> rtl8139c network card.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1180777
>
> Title:
> RDP traffic freeze on quiet network
>
> Status in QEMU:
> New
> Status in “qemu-kvm” package in Ubuntu:
> Confirmed
> Status in Debian GNU/Linux:
> New
>
> Bug description:
> To summarize what I think has been found so far,
>
> 1. The main symptom is that RDP connections hang after some time
> 2. This bug affects qemu 1.0 .. 1.6.5
> 3. This bug affects at least windows xp and windows 7 guests
> 4. Keeping another network connection open, such as vnc, prevents the
> RDP connection from hanging.
>
> ========================================
> 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...

[Serge Hallyn (serge-hallyn)]

Quoting Vasile Dumitrescu (<email address hidden>):
> I added a rtl8139c netcard to the VM and connected through it by RDP -
> no more freezes.
>
> It looks like kvm does not play well with virtio network cards and RDP.
>
> Red Hat virtio net windows driver version: 62.65.104.6500, 6/19/2013

This makes me wonder if the bug may not actually be in the virtio net driver.
The source for that is at
https://github.com/YanVugenfirer/kvm-guest-drivers-windows .
Something like commit 9b1b81a731f722efa8df24429649b527a17bf433 might
be relevant (assuming the git HEAD has this fixed, which I've not
tested).

[f3a97 (f3a97)]

Hi,

I've double checked my conf, I can confirm I'm not using virtio but
standard Win 7 drivers. (please see my VM conf that I posted some time ago).

So it's not definitely a virtio-specific issue.

On 3 October 2013 16:31, Serge Hallyn <email address hidden> wrote:

> Quoting Vasile Dumitrescu (<email address hidden>):
> > I added a rtl8139c netcard to the VM and connected through it by RDP -
> > no more freezes.
> >
> > It looks like kvm does not play well with virtio network cards and RDP.
> >
> > Red Hat virtio net windows driver version: 62.65.104.6500, 6/19/2013
>
> This makes me wonder if the bug may not actually be in the virtio net
> driver.
> The source for that is at
> https://github.com/YanVugenfirer/kvm-guest-drivers-windows .
> Something like commit 9b1b81a731f722efa8df24429649b527a17bf433 might
> be relevant (assuming the git HEAD has this fixed, which I've not
> tested).
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1180777
>
> Title:
> RDP traffic freeze on quiet network
>
> Status in QEMU:
> New
> Status in “qemu-kvm” package in Ubuntu:
> Confirmed
> Status in Debian GNU/Linux:
> New
>
> Bug description:
> To summarize what I think has been found so far,
>
> 1. The main symptom is that RDP connections hang after some time
> 2. This bug affects qemu 1.0 .. 1.6.5
> 3. This bug affects at least windows xp and windows 7 guests
> 4. Keeping another network connection open, such as vnc, prevents the
> RDP connection from hanging.
>
> ========================================
> 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.bi...

[Thomas Huth (th-huth)]

Triaging old bug tickets... can you still reproduce this issue with the latest version of QEMU? Or could we close this ticket nowadays?

[Launchpad Janitor (janitor)]

[Expired for QEMU because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

[Expired for qemu-kvm (Ubuntu) because there has been no activity for 60 days.]