01.10.2013 21:29, Ross Boylan wrote:
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.
Well, 2.6.31 should be "well enough", and indeed it's difficult to
work on a locking vm...
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.
It's unlikely. Guest does not know anything about the host, it
is all converted to reads/writes by qemu, and both stacks works
as you note below.
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.
No. I mean, guest has lots of optimizations for being a "kvm guest".
For example, in this mode it most likely uses another clock, namely
kvmclock, which it does not use on any real hw (obviously) and which
had *lots* of bugs fixed.
Lenny kernel (it is only the guest kernel which matters, nothing more)
had a very preliminary support for all this, which is very very buggy.
But 2.6.31 is not THAT bad.
It'd be nice to try to disable all that completely, but I'm not sure
if that's at all possible, at least not from qemu-kvm command line.
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.
Yes, that too, ofcourse. (It isn't backported because of a different
reason, -- due to other packages migration issues, it can't migrate
from unstable to testing since wheezy release).
Thanks,
/mjt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
