Most recent kernel where this bug did not occur: unknown Distribution: Gentoo Hardware Environment: Athlon 64 X2 Software Environment: kvm-35, win98 VM Problem Description: This problem was first reported on http://bugs.gentoo.org/show_bug.cgi?id=187812 With kernel 2.6.23_rc2 (and 2.6.22.1) loading a win98 virtual machine with kvm-35 (and kvm-31) results in the VM hanging with a black screen during startup (after scandisk, but before the desktop appears if that's of any help). The VM works fine if KVM is disabled (either with -no-kvm or /dev/kvm not being available). When the VM hangs, top reports 100% "sys" cpu usage (but that would be normal with a win98 VM). Unfortunately I haven't been able to reproduce this problem with a freely available VM so far (freedos and linux VMs from http://fabrice.bellard.free.fr/qemu/download.html booted fine with KVM enabled). Please let me know if you need further information or want me to test anything specific.
Marius, Have you tested this since with new kernel/KVM? and have you filed your bug on the KVM mailing list https://lists.sourceforge.net/lists/listinfo/kvm-devel/ ? If not, I can forward the bug to this list. Thanks.
(In reply to comment #1) > Marius, > Have you tested this since with new kernel/KVM? and have you filed your bug > on > the KVM mailing list https://lists.sourceforge.net/lists/listinfo/kvm-devel/ > ? > If not, I can forward the bug to this list. Still reproducible here with kernel 2.6.24 and kvm-59 (with modules from kernel and kvm), except that the black screen is replaced by the windows boot splashscreen in the kvm+kvm combination (but it still hangs indefinitely). One thing I forgot to mention in the first comment is that the mentioned kvm versions refer only the the userspace parts, the modules came from the mentioned kernel versions. One more thing is that booting to the DOS prompt in the same VM works fine with KVM, but failsafe mode does not (don't know if that information is useful). Forwarding the bug to the right people would be nice, thanks.
Is this still the case with 2.6.28 ?