Thanks for your response. On Tue, Oct 01, 2013 at 02:27:16PM +0400, Michael Tokarev wrote: > 28.09.2013 06:18, Ross Boylan wrote: >> Package: qemu-kvm >> Version: 1.1.2+dfsg-6 >> Severity: important >> > [] >> The first time I booted of a virtual CD with the Lenny installer.[] > >> The second time I started the system, did more work, and left it overnight. > > So, the guest you're running in qemu-kvm is lenny? Yes. > > Does the same happen with other guests, or is it lenny-specific? > Does anything changes if you install a more recent kernel in the > lenny guest (iirc, the latest kernel available for lenny was 2.6.30)? I think it was 2.6.31. I think I was running that on my real hardware, so it's natural to try. One issue is that I'm trying to recreate the old system, which means installing a bunch of other stuff first. And it's hard to work on the VM since it keeps locking up.
Since the error seems disk-related, it may be relevant that I'm running a somewhat complicated stack. Inside the guest I have several logical volumes, many of which use encryption. The host provides the disk out of a logical volume on the host. > > Overall, it does not look like a qemu/kvm issue at all, but instead > a guest bug. > I can try those other things. Why do you say it looks like a guest bug? I assume that if lenny had been behaving this way on real hardware someone would have noticed. I thought maybe trying a newer kvm, either building sid from source (unless it's on backports) or getting it upstream, would be the first thing to try. Ross > Thanks, > > /mjt -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
