Skip to contentSkip to conversation

New: hardware error 0x80000021 on a KVM virtual machine with kernel 3.7

Bug 53191 [email protected] 1 participant 5 messages Jan 29, 2013 – May 20, 2014 KVM

lore
Share & tools
lore
#0 lore raw

https://bugzilla.kernel.org/show_bug.cgi?id=53191

           Summary: hardware error 0x80000021 on a KVM virtual machine
                    with kernel 3.7
           Product: Virtualization
           Version: unspecified
    Kernel Version: 3.7.2
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: kvm
        AssignedTo: [email protected]
        ReportedBy: [email protected]
        Regression: No

Hello,
I faced yesterday the hardware error 0x80000021 which was, I think allready
fixed: https://bugzilla.redhat.com/show_bug.cgi?id=854983

I use a Debian unstable system with a debianized vanilla kernel 3.7.2 (took that kernel from kernel.org and created a debian-package with make-kpkg) My host system is (as I sayed) a debian i686 on a thinkbook x60s with a Intel Core Duo CPU L2400 @ 1.66GHz. One of the first processors with vt, I think. My guest system is a debian-x86 testing as well. I tried to install debian virtual-machine with a net-install-iso-image, but right after the start of the cd it seems to pause (with virt-manager as frontend).

The error dump I got in /var/log/libvirt/qemu/Debian0.log:

2013-01-28 21:53:35.265+0000: starting up

LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin HOME=
/ QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-1.1 -cpu coreduo,+pdcm,+xtpr,+tm2,+e
st,+vmx,+pbe,+tm,+ht,+ss,+acpi,+ds -enable-kvm -m 1024 -smp 1,sockets=1,cores=1,
threads=1 -name Debian0 -uuid e901b56d-1cc9-f983-bd29-9742378004db -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/Debian0.mo nitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=u
tc -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file =/var/lib/libvirt/images/Debian0.img,if=none,id=drive-virtio-disk0,format=raw -d
evice virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=vir tio-disk0,bootindex=1 -drive file=/home/chris/Downloads/public/iso/debian-6.0.6- i386-netinst.iso,if=none,id=drive-ide0-1-0,readonly=on,format=raw -device ide-cd
,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=20,id=hostnet0
,vhost=on,vhostfd=21 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00 :6c:1e:86,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,char
dev=charserial0,id=serial0 -device usb-tablet,id=input0 -vnc 127.0.0.1:0 -vga ci
rrus -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6
char device redirected to /dev/pts/0
KVM: entry failed, hardware error 0x80000021

this problem first occurs only with my custom-kernel. I tested it with the debian-trunk-kernel 3.7 on experimental as well, with the same result!

Signature · 3 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
#1 lore raw

[Bug 53191] hardware error 0x80000021 on a KVM virtual machine with kernel 3.7

https://bugzilla.kernel.org/show_bug.cgi?id=53191

[email protected] changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #1 from [email protected] 2013-01-29 23:35:46 --- 32bit hosts don't get a lot of testing these days. I'd suggest you find the last kernel version that does work and then do a git bisect to figure out where it broke. In the mean time someone will try to find a way to reproduce. Let us know the outcome of your testing.

Signature · 3 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
#2 lore raw

[Bug 53191] hardware error 0x80000021 on a KVM virtual machine with kernel 3.7

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=53191

Gleb <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #2 from Gleb <[email protected]> 2013-01-30 09:51:48 --- Can you try to load kvm-intel module with emulate_invalid_guest_state=0 flag?

Signature · 3 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
#3 lore raw

[Bug 53191] hardware error 0x80000021 on a KVM virtual machine with kernel 3.7

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=53191

George <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #3 from George <[email protected]> 2013-03-25 12:43:55 --- I ran into this issue after upgrading the kernel from 3.5.7 to 3.6.11. Booting 32 bit Windows XP or Debian 6.0.5 on a older Dell D820 laptop (Family:
6 Model: 14 Stepping: 8 T2500 CPU) both failed with the hardware error.

Setting "options kvm_intel emulate_invalid_guest_state=0" in /etc/modprobe.d/kvm_intel.conf appears to have resolved the issue for me.

Signature · 3 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
#4 lore raw

[Bug 53191] hardware error 0x80000021 on a KVM virtual machine with kernel 3.7

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=53191

Jidong Xiao <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #4 from Jidong Xiao <[email protected]> ---
Hi, Gleb, I think your patch "KVM: VMX: mark unusable segment as nonpresent" has already fixed this problem. Your patch was accepted in main kernel in around 3.11, and he was using linux kernel 3.7, so understandably he would face this problem. Right? If so, we can close this ticket, he was just using some obsolete kernel in which we know the bug exists. (In reply to Gleb from comment #2)

Quoted 1 line

Can you try to load kvm-intel module with emulate_invalid_guest_state=0 flag?

Signature · 2 lines
You are receiving this mail because:
You are watching the assignee of the bug.