Is anybody else using qemu-2.4.0 and seeing their machine variously locking up or oopsing ? I say oops because the keyboard LEDs flash, but nothing ever gets to either the host or guest logs.
This all started around last Thursday or Friday, when I began building systems in qemu to test current versions and to (eventually) explore trying to put qt-5.5.0 in /usr (that part failed, even on real hardware). I was running qemu-2.4.0 on my AMD phenom (yeah, these phenoms seem to have "a bad day" from time to time, but not *that* often), and using a 4.2-rc kernel (-rc5, I think - that kernel had been rock solid when I didn't run qemu). And several times the host locked up. On at least one occasion the keyboard LEDs were flashing. But another time the guest build started to fail a minute or two before things ground to a halt: I was building Xorg, and had got to the protocols - when I resumed, I eventually discovered that although several of these had created a "stamp" file to signify the package had been installed, these stamps were empty (normally: package's name/version, time, SBU, yadda, yadda) and later packages failed because one or other of the protocols was missing). After fixing that up, and getting to a suitable place to leave it, I rebooted into memtest86+ and left that running for more than 10 hours : no problems. After that, when I resumed I first built a 4.1 kernel, and then went back to qemu-2.3.0. Over a few days, that combination was ok, so I then installed a 4.2-rc7 kernel : still seemed ok. This evening, I reinstalled qemu-2.4.0 and again the box oopsed after an hour or two of running qemu. ĸen, going back to 2.3.0, again :-( -- This one goes up to eleven: but only on a clear day, with the wind in the right direction. -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
