Yes - the inability to start networking occurs the first time the suspend2
kernel starts (before I have even created a suspend image or added the
resume parameter to the boot line.

I will try enabling the debug as you suggest and will see what I get.

Thanks

Simon

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Behalf Of John Coiner
Sent: 19 October 2005 20:52
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] FW: QEMU and suspend2



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


**********************************************************************
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: [EMAIL PROTECTED]

For further information http://www.sungard.com/vivista


_______________________________________________
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel

Reply via email to