public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: "Thomas Løcke" <thomas.granvej6@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: 2.6.35.11 + qemu-kvm 0.14.0 + Windows XP RDP access = unstable
Date: Tue, 08 Mar 2011 12:19:00 +0200	[thread overview]
Message-ID: <4D760294.9020109@redhat.com> (raw)
In-Reply-To: <AANLkTims3e3Gmcp5SAfL6X0tLk27PA43cB0SiS0HEFRN@mail.gmail.com>

On 03/08/2011 08:43 AM, Thomas Løcke wrote:
> Hey all,
>
> I have 9 Windows XP guests running on a KVM host. The host is
> Slackware 13.1 x86_64 with kernel 2.6.35.11.
>
> All the guests are being accessed using the built-in RDP server in
> Windows XP. This worked perfectly with qemu-kvm 0.13.0, but with
> 0.14.0 the connection is dropped every 5-10 minutes.
>
> This is the command used to start the guests:
>
> /opt/qemu-0.13.0/bin/qemu-system-x86_64 -name fdacs1sa1_15,
> process=fdacs1sa1_15 \
>      -pidfile /var/run/kvm/15.pid \
>      -drive file=/storage_slow_one/fd_acs2_sa2.raw,snapshot=off,if=virtio,media=disk,cache=none,format=raw,boot=on
> \
>      -monitor unix:/var/run/kvm/15.monitor,server,nowait \
>      -cpu qemu64 \
>      -smp 1 \
>      -m 512 \
>      -k da \
>      -vnc :15 \
>      -rtc base=localtime,clock=host \
>      -tdf \
>      -net nic,macaddr=de:ad:be:ef:00:15,model=virtio \
>      -net tap,ifname=tap_15,script=no,downscript=no \
>      -runas kvm \
>      -daemonize \
>      -usbdevice tablet
>
> The virtio drivers used are virtio-win-1.1.16.
>
> Access via the qemu-kvm VNC interface does not experience these
> connection drops. There are no visible errors in the Windows XP
> guests.
>
> Now, since I don't have any issues with qemu-kvm 0.13.0, it is not a
> problem for me to go back to using this version instead of the new
> 0.14.0.
>
> So:
>      2.6.35.11 + 0.13.0 = Flawless operation. It just hums along.
>      2.6.35.11 + 0.14.0 = The connection to the internal Windows XP RDP
> server breaks every 5-10 minutes.
>
> Anybody else who've experienced something similar?

You might try logging the connection with wireshark (start on the, 
perhaps later also in the guest) to see what's the cause.  If you run it 
on both guest and host, you can see if packets are lost or corrupted.

-- 
error compiling committee.c: too many arguments to function


  parent reply	other threads:[~2011-03-08 10:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-08  6:43 2.6.35.11 + qemu-kvm 0.14.0 + Windows XP RDP access = unstable Thomas Løcke
2011-03-08  7:22 ` Michael Tokarev
2011-03-08  8:08   ` Thomas Løcke
2011-03-08  8:42     ` Michael Tokarev
2011-03-08  8:44       ` Thomas Løcke
2011-03-08  9:40 ` Michael Tokarev
2011-03-08  9:47   ` Thomas Løcke
2011-03-08 10:19 ` Avi Kivity [this message]
2011-03-09  8:37   ` Thomas Løcke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D760294.9020109@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=thomas.granvej6@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox