On 1/31/16 17:14 , Jason Lawrence wrote: > I tried installing Windows 10 (32 bit) in a KVM zone and it appears to > hang immediately after booting from the ISO, indefinitely displaying the > Windows startup logo via VNC for several hours. I see zero disk > activity. The only obvious information I can find relating to KVM is in > the syslog right after starting the VM: > > 2016-01-31T22:25:58.379728+00:00 smarty genunix: [ID 408114 kern.info] > /pseudo/zconsnex@1/zcons@12 (zcons12) online > 2016-01-31T22:25:59.332226+00:00 smarty mac: [ID 469746 kern.info] > NOTICE: vnic1218 registered > 2016-01-31T22:25:59.461815+00:00 smarty kvm: [ID 420667 kern.info] > kvm_lapic_reset: vcpu=ffffff051d031000, id=0, base_msr= fee00100 PRIx64 > base_address=fee00000 > 2016-01-31T22:25:59.461836+00:00 smarty kvm: [ID 710719 kern.info] vmcs > revision_id = 12 > 2016-01-31T22:25:59.462918+00:00 smarty kvm: [ID 420667 kern.info] > kvm_lapic_reset: vcpu=ffffff04ebf3b000, id=1, base_msr= fee00000 PRIx64 > base_address=fee00000 > 2016-01-31T22:25:59.462927+00:00 smarty kvm: [ID 710719 kern.info] vmcs > revision_id = 12 > 2016-01-31T22:26:03.139185+00:00 smarty kvm: [ID 391722 kern.info] > unhandled wrmsr: 0x1010101 data fffffd7fffdfe880 > 2016-01-31T22:26:03.139211+00:00 smarty kvm: [ID 391722 kern.info] > unhandled wrmsr: 0x1010101 data fffffd7fffdfe880 > 2016-01-31T22:26:03.144332+00:00 smarty kvm: [ID 391722 kern.info] > unhandled wrmsr: 0xff30ccec data fffffd7fffdfe850 > 2016-01-31T22:26:03.144407+00:00 smarty kvm: [ID 391722 kern.info] > unhandled wrmsr: 0x0 data 0 > 2016-01-31T22:26:03.144776+00:00 smarty kvm: [ID 391722 kern.info] > unhandled wrmsr: 0x0 data 0 > 2016-01-31T22:26:03.144819+00:00 smarty kvm: [ID 391722 kern.info] > unhandled wrmsr: 0x0 data 0 > 2016-01-31T22:26:03.184712+00:00 smarty kvm: [ID 291337 kern.info] vcpu > 1 received sipi with vector # 10 > 2016-01-31T22:26:03.184722+00:00 smarty kvm: [ID 420667 kern.info] > kvm_lapic_reset: vcpu=ffffff04ebf3b000, id=1, base_msr= fee00800 PRIx64 > base_address=fee00000 > 2016-01-31T22:26:04.387896+00:00 smarty kvm: [ID 391722 kern.info] > unhandled wrmsr: 0x0 data 0 > 2016-01-31T22:26:07.862118+00:00 smarty kvm: [ID 713435 kern.info] > unhandled rdmsr: 0xff295897 > 2016-01-31T22:26:07.862170+00:00 smarty kvm: [ID 391722 kern.info] > unhandled wrmsr: 0x50bff7 data fffffd7ffe9de1c0 > 2016-01-31T22:26:07.867041+00:00 smarty kvm: [ID 713435 kern.info] > unhandled rdmsr: 0xff295897 > 2016-01-31T22:26:07.867059+00:00 smarty kvm: [ID 391722 kern.info] > unhandled wrmsr: 0x50bff7 data fffffd7ffe9de1c0 > 2016-01-31T22:26:07.867357+00:00 smarty kvm: [ID 713435 kern.info] > unhandled rdmsr: 0x3c0003f > 2016-01-31T22:26:07.867376+00:00 smarty kvm: [ID 391722 kern.info] > unhandled wrmsr: 0x0 data 0 > 2016-01-31T22:26:19.488477+00:00 smarty kvm: [ID 713435 kern.info] > unhandled rdmsr: 0x3a > > This means nothing to me, but any suggestions on where I can start looking?
The first thing that I'd look at is the kvmstat output and see if the guest is running and trying to do things or not. Robert ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
