From: John Coiner <jcoiner@stanfordalumni.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] FW: QEMU and suspend2
Date: Wed, 19 Oct 2005 15:51:44 -0400 [thread overview]
Message-ID: <4356A3D0.10206@stanfordalumni.org> (raw)
In-Reply-To: <E671455BAF0BFC43B8B31A6455348E7F09877136@srvmeth10.sis.co.uk>
Simon,
There's a known issue with using suspend2 on a QEMU host, described here:
http://people.brandeis.edu/~jcoiner/qemu_idedma/qemu_dma_patch.html#suspend
But, it sounds like you have trouble with a suspend2-capable guest
kernel, and that the trouble starts as soon as you boot (ie before you
actually use the suspend2 feature.) Is that right?
You might try uncommenting the "#define DEBUG_NE2000" line in
hw/ne2000.c, recompiling, and then comparing the debug log from a
vanilla guest kernel against the debug log from a suspend2 guest kernel.
Good luck.
-- john
Simon Guerrero wrote:
> I'm figuring that nobody has an answer for this. Can anyone suggest an
> idea as to what files I need to look at in the Qemu sources to see if
> suspend2 has "polluted" the networking ability?
> -----Original Message-----
> *From:* Simon Guerrero
> *Sent:* 17 October 2005 11:36
> *To:* 'qemu-devel@nongnu.org'
> *Subject:* QEMU and suspend2
>
> Hi
>
> I am developing a custom kernel using Qemu. I have an amd64 system,
> running an ia32 chroot in which I build 32 bit kernels and run Qemu to
> test them. My kernel is a bare minimum 2.6 and worked just fine until I
> added the suspend2 (software suspend) patch and rebuilt.
>
> Now when qemu starts up, everything works fine except networking (I am
> using user-net). It claims it can't identify the network hardware and as
> a consequence, eth0 isn't created.
>
> When I compare the two .config files for the kernel (before and after
> the suspend2 patch), there is nothing changed that should affect
> networking - only some new definitions for suspend2 and switching on LZF
> compression, etc.
>
> Is there a known issue with suspend2 and qemu?
>
> Any help appreciated.
>
> Thanks
>
> Simon
>
>
> **********************************************************************
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they
> are addressed. If you have received this email in error please notify
> the system manager.
>
> This footnote also confirms that this email message has been swept by
> MIMEsweeper for the presence of computer viruses.
>
> www.mimesweeper.com
> **********************************************************************
>
> _____________________________________________________________________
>
> This message has been checked for all known viruses on behalf of Sungard
> Vivista by MessageLabs.
>
> http://www.messagelabs.com or Email: mailsweeper.info@vivista.co.uk
>
> For further information http://www.sungard.com/vivista
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
prev parent reply other threads:[~2005-10-19 19:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-19 8:13 [Qemu-devel] FW: QEMU and suspend2 Simon Guerrero
2005-10-19 19:51 ` John Coiner [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=4356A3D0.10206@stanfordalumni.org \
--to=jcoiner@stanfordalumni.org \
--cc=qemu-devel@nongnu.org \
/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).