[OmniOS-discuss] r151014 KVM crash

Mon Apr 6 08:20:56 UTC 2015

Hi!

I switched one of my development  machines over to r151014. On that machine I got a few KVM VM's.

One of them is a Linux terminal server, and when I wanted to update/upgrade it, both the general OS and the chroot environments I got in it, it crashed. I tried several times, and every time I did it, it crashed. It seems to run without problems when I don't do any heavy work on it, but with this update/upgrade, it runs for about ~5 min, then it crashes. It can't get started again, until I reboot the server.

The following msg is from /var/adm/messages:

40b0000, id=1, base_msr= fee00000 PRIx64 base_address=fee00000
Apr  4 20:45:45 omni2 kvm: [ID 710719 kern.info] vmcs revision_id = f
Apr  4 20:45:45 omni2 kvm: [ID 420667 kern.info] kvm_lapic_reset: vcpu=ffffff06140a8000
, id=2, base_msr= fee00000 PRIx64 base_address=fee00000
Apr  4 20:45:45 omni2 kvm: [ID 710719 kern.info] vmcs revision_id = f
Apr  4 20:45:45 omni2 kvm: [ID 420667 kern.info] kvm_lapic_reset: vcpu=ffffff0614236000
, id=3, base_msr= fee00000 PRIx64 base_address=fee00000
Apr  4 20:45:45 omni2 kvm: [ID 710719 kern.info] vmcs revision_id = f
Apr  4 20:45:52 omni2 kvm: [ID 391722 kern.info] unhandled wrmsr: 0x1010101 data fffffd
7fffdfe8e0
Apr  4 20:45:52 omni2 last message repeated 3 times
Apr  4 20:45:52 omni2 kvm: [ID 391722 kern.info] unhandled wrmsr: 0xff3d0f9c data fffff
d7fffdfe8b0
Apr  4 20:45:52 omni2 kvm: [ID 391722 kern.info] unhandled wrmsr: 0x0 data 0
Apr  4 20:45:52 omni2 last message repeated 6 times
Apr  4 20:45:52 omni2 kvm: [ID 291337 kern.info] vcpu 1 received sipi with vector # 10
Apr  4 20:45:52 omni2 kvm: [ID 291337 kern.info] vcpu 2 received sipi with vector # 10
Apr  4 20:45:52 omni2 kvm: [ID 291337 kern.info] vcpu 3 received sipi with vector # 10
Apr  4 20:45:52 omni2 kvm: [ID 420667 kern.info] kvm_lapic_reset: vcpu=ffffff06140b0000
, id=1, base_msr= fee00800 PRIx64 base_address=fee00000
Apr  4 20:45:52 omni2 kvm: [ID 420667 kern.info] kvm_lapic_reset: vcpu=ffffff06140a8000
, id=2, base_msr= fee00800 PRIx64 base_address=fee00000

Then it goes on like this:

Apr  4 20:46:25 omni2 kvm: [ID 713435 kern.info] unhandled rdmsr: 0xff311c4c
Apr  4 20:46:25 omni2 kvm: [ID 391722 kern.info] unhandled wrmsr: 0x525f2f data 8000000
01
Apr  4 20:46:25 omni2 kvm: [ID 713435 kern.info] unhandled rdmsr: 0xff311c4c
Apr  4 20:46:25 omni2 kvm: [ID 391722 kern.info] unhandled wrmsr: 0x525f2f data 8000000
01
Apr  4 20:46:25 omni2 kvm: [ID 713435 kern.info] unhandled rdmsr: 0xff311c4c
Apr  4 20:46:25 omni2 kvm: [ID 391722 kern.info] unhandled wrmsr: 0x525f2f data 8000000
01
Apr  4 20:46:25 omni2 kvm: [ID 713435 kern.info] unhandled rdmsr: 0xff311c4c
Apr  4 20:46:25 omni2 kvm: [ID 391722 kern.info] unhandled wrmsr: 0x525f2f data 8000000
01
Apr  4 20:46:25 omni2 kvm: [ID 713435 kern.info] unhandled rdmsr: 0xff311c4c
Apr  4 20:46:25 omni2 kvm: [ID 391722 kern.info] unhandled wrmsr: 0x525f2f data 8000000
01
Apr  4 20:46:25 omni2 kvm: [ID 713435 kern.info] unhandled rdmsr: 0xff311c4c
Apr  4 20:46:25 omni2 kvm: [ID 391722 kern.info] unhandled wrmsr: 0x525f2f data 8000000
01
Apr  4 20:46:34 omni2 kvm: [ID 713435 kern.info] unhandled rdmsr: 0xff311c4c
Apr  4 20:46:34 omni2 kvm: [ID 391722 kern.info] unhandled wrmsr: 0x525f2f data 2000000
001
Apr  4 20:46:34 omni2 kvm: [ID 713435 kern.info] unhandled rdmsr: 0xff311c4c
Apr  4 20:46:34 omni2 kvm: [ID 391722 kern.info] unhandled wrmsr: 0x525f2f data 2000000
001
Apr  4 20:46:34 omni2 kvm: [ID 713435 kern.info] unhandled rdmsr: 0xff311c4c
Apr  4 20:46:34 omni2 kvm: [ID 391722 kern.info] unhandled wrmsr: 0x525f2f data 2000000
001
Apr  4 20:46:34 omni2 kvm: [ID 713435 kern.info] unhandled rdmsr: 0xff311c4c
Apr  4 20:46:34 omni2 kvm: [ID 391722 kern.info] unhandled wrmsr: 0x525f2f data 2000000
001
Apr  4 20:46:34 omni2 kvm: [ID 713435 kern.info] unhandled rdmsr: 0xff311c4c
Apr  4 20:46:34 omni2 kvm: [ID 391722 kern.info] unhandled wrmsr: 0x525f2f data 2000000
001
Apr  4 20:46:34 omni2 kvm: [ID 713435 kern.info] unhandled rdmsr: 0xff311c4c
Apr  4 20:46:34 omni2 kvm: [ID 391722 kern.info] unhandled wrmsr: 0x525f2f data 2000000

And like this:

Apr  4 20:50:45 omni2 kvm: [ID 713435 kern.info] unhandled rdmsr: 0xff311c4c
Apr  4 20:50:45 omni2 kvm: [ID 391722 kern.info] unhandled wrmsr: 0x526835 data 8
Apr  4 20:50:45 omni2 kvm: [ID 713435 kern.info] unhandled rdmsr: 0xff311c4c
Apr  4 20:50:45 omni2 kvm: [ID 391722 kern.info] unhandled wrmsr: 0x526835 data 8
Apr  4 20:50:45 omni2 kvm: [ID 713435 kern.info] unhandled rdmsr: 0xff311c4c
Apr  4 20:50:45 omni2 kvm: [ID 391722 kern.info] unhandled wrmsr: 0x526835 data 8
Apr  4 20:50:45 omni2 kvm: [ID 713435 kern.info] unhandled rdmsr: 0xff311c4c
Apr  4 20:50:45 omni2 kvm: [ID 391722 kern.info] unhandled wrmsr: 0x526835 data 8
Apr  4 20:50:45 omni2 kvm: [ID 713435 kern.info] unhandled rdmsr: 0xff311c4c
Apr  4 20:50:45 omni2 kvm: [ID 391722 kern.info] unhandled wrmsr: 0x526835 data 8
Apr  4 20:50:45 omni2 kvm: [ID 713435 kern.info] unhandled rdmsr: 0xff311c4c
Apr  4 20:50:45 omni2 kvm: [ID 391722 kern.info] unhandled wrmsr: 0x526835 data 10
Apr  4 20:50:45 omni2 kvm: [ID 713435 kern.info] unhandled rdmsr: 0xff311c4c
Apr  4 20:50:45 omni2 kvm: [ID 391722 kern.info] unhandled wrmsr: 0x526835 data 10
Apr  4 20:50:45 omni2 kvm: [ID 713435 kern.info] unhandled rdmsr: 0xff311c4c
Apr  4 20:50:45 omni2 kvm: [ID 391722 kern.info] unhandled wrmsr: 0x526835 data 10
Apr  4 20:50:45 omni2 kvm: [ID 713435 kern.info] unhandled rdmsr: 0xff311c4c
Apr  4 20:50:45 omni2 kvm: [ID 391722 kern.info] unhandled wrmsr: 0x526835 data 10
Apr  4 20:50:45 omni2 kvm: [ID 713435 kern.info] unhandled rdmsr: 0xff311c4c
Apr  4 20:50:45 omni2 kvm: [ID 391722 kern.info] unhandled wrmsr: 0x526835 data 10
Apr  4 20:50:45 omni2 kvm: [ID 713435 kern.info] unhandled rdmsr: 0xff311c4c
Apr  4 20:50:45 omni2 kvm: [ID 391722 kern.info] unhandled wrmsr: 0x526835 data 10
Apr

I switched back to r151012, and there everything is working fine...

I do a rollback of the volumes I used for the chroots in the VM, because they've been messed up of the repetedly interupted upgrade attemts, so I run new updates/upgrades on the chroots, and even build new ones, and no problems here in r151012.

So the problem seem to be exclusively in r151014.

I got some messages on the omnios console after the VM crashes that I didn't record, unfortunatly. What I remember was that it was complaining about a bus, and it was also complains about either ps or pthread as well.

I will go back to r151014 again, and run more tests like this, to get this clarified, and record the exact msg on the consol.

Any suggestion?

Best regards from/Med vänliga hälsningar från

Johan Kragsterman

Capvert