On Fri, Nov 07, 2008 at 02:39:49PM +0100, Pascal A. Dupuis wrote: > Package: qemu > Version: 0.9.1-7 > Severity: important > > I experienced various hangs with qemu. Setup is as follows: > losetup /dev/loop1 hurd.mbr > mdadm --build --level=linear --rounding=4 -n 2 /dev/md0 /dev/loop1 > /dev/hda3 > qemu -m 384 -hda /dev/md0 -net nic -net tap & > > hurd.mbr is a small file emulating a partition table whith the right > parameters; mdadm concatenates this and one partition to appear as a > single bloc device, and qemu uses this device as one single disk. > > guest system is hurd-i486. It boots, I get a login prompt, and > programs run. Network access is through squid acting as proxy server > on the linux side. > > I experienced various hangs with no particular pattern behind them. I > reduced their probability by stopping powernowd (processor is Athlon > XP) and putting the processor at its lowest speed, but still get > somes. When it occurs, system is totally frozen, no messages > whatsoever in the logs or at the console. Only the power switch > permits to bring the computer back on. At this point, there are in > general various errors when fscking the linux partition used inside > md0. Any idea ? How to debug this ? >
If your system is totally frozen, I have doubt it's a qemu bug. Looks like more a hardware or kernel problem. You should send you system logs over the network, so that you can see what happens when the computer crash. -- .''`. Aurelien Jarno | GPG: 1024D/F1BCDB73 : :' : Debian developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `- people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
