We've identified that the following commit resolved the issue
commit 47113ab6b8c5659ad94c69aacca572f731ebb0ac
Author: Wen Congyang we...@cn.fujitsu.com
Date: Fri Nov 4 10:45:58 2011 +0800
reenable vm_clock when resuming all vcpus
We disable vm_clock when pausing all vcpus,
** Attachment added: screenshot showing nw initialization failure
https://bugs.launchpad.net/bugs/886255/+attachment/2585413/+files/vm1_2011-11-04_00-45-19.jpg
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
We are currently investigating the failure. One of our suspects is that
on kvm autotest, each new qemu process instance might have a new NIC mac
address, and that might be triggering some condition in qemu in
conjunction to the guest init scripts.
It is important to note that this problem does
I can't reproduce this with an Ubuntu guest. I suspect it has
something to do with how you're configuring networking.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/886255
Title:
Qemu master
A little more investigation shows that empty ssh keys are being
generated on the first boot, so now it doesn't look like a network
problem anymore. now we are trying to figure out just on qemu this
phenomenon is happening.
--
You received this bug notification because you are a member of qemu-
