qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: yhalperi <yhalperi@redhat.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Windows 7 guest hangs after waking up from S3
Date: Mon, 27 Jun 2011 13:35:05 +0300	[thread overview]
Message-ID: <20110627103505.GN491@redhat.com> (raw)
In-Reply-To: <4E085782.4090605@redhat.com>

On Mon, Jun 27, 2011 at 01:12:18PM +0300, yhalperi wrote:
> On 06/27/2011 11:12 AM, Stefan Hajnoczi wrote:
> >On Mon, Jun 27, 2011 at 8:04 AM, yhalperi<yhalperi@redhat.com>  wrote:
> >>I'm using qemu with qxl (with S3/4 support. patches sent by Alon Levy).
> >>While with Windows xp guest I had no problems, Windows 7 (32 bits) hangs
> >>after S3 (it looks alive for a second, and then it gets stack).It happens
> >>only when using "-net tap"; with "-net user", I didn't encounter a problem.
> >
> >Please post your QEMU command-line.
> >
> >For sanity also please try without the QXL patches.  That way we know
> >whether this issue is related to QXL or not.
> >
> >Stefan
> 
> How can I test S3 without qxl? I tried using cirrus and the Sleep
> option was disabled on windows 7.
> I also tried the older qxl (without the patches that support s3),
> and disabled off-screen surfaces (in order to allow s3 to work), and
> the same problem occured.
> 
"-net tap" vs "-net user" rings the bell for me. There is a known (for
me) problem with Windows S3 resume + networking. It appears that Windows
enables NIC receive interrupt before it registers NIC's interrupt handler
(only on S3 resume! On regular boot the order is different). If interrupt
arrives before NIC's interrupt handler is registered Windows hangs because
interrupt condition is never cleared in the NIC. On real hardware this
is not happening because relatively long time passes between enabling
link and receiving a first packet. With "-net user" guest never receives
unsolicited packet, with "-net tap" there are always enough broadcasts
to trigger the problem. 

> my command line:
> qemu-system-x86_64  -L pc-bios/ -m 1024 -hda <img> -boot c  -vga qxl
> -spice port=5678,disable-ticketing,streaming-video=all -net
> nic,macaddr=00:1a:4a:01:00:e0,model=rtl8139 -net
> tap,ifname=WIN7,script=/local/scripts/lan-ifup -nographic -global
> qxl-vga.debug=1  --enable-kvm -snapshot
> 
> 
> /local/scripts/lan-ifup
> -------------------------
> #!/bin/sh
> switch=sw0
> ifconfig $1 0.0.0.0 up
> brctl addif ${switch} $1

--
			Gleb.

      reply	other threads:[~2011-06-27 10:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-27  7:04 [Qemu-devel] Windows 7 guest hangs after waking up from S3 yhalperi
2011-06-27  8:12 ` Stefan Hajnoczi
2011-06-27 10:12   ` yhalperi
2011-06-27 10:35     ` Gleb Natapov [this message]

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=20110627103505.GN491@redhat.com \
    --to=gleb@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --cc=yhalperi@redhat.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;
as well as URLs for NNTP newsgroup(s).