On 27/06/2015 12:08, Graham Stephens wrote:
On 26/06/2015 19:42, John D Groenveld wrote:
In message <[email protected]>, Graham Stephens
writes:
Does anyone else here have problems trying to start a kvm due to vnics
not initializing properly? It seems to me that the more vnics you add,
the more likely the problem is to occur.
No.
What's your reproducable configuration?
What version OmniOS?
How many VMs and VNICs?
What's your KVM invocations?
John
[email protected]
-------------------
I also get these messages in the global log, but only AFTER the kvm has
managed to start:
Jun 27 09:13:19 eppigw01 genunix: [ID 420667 kern.info] kvm_lapic_reset:
vcpu=ffffff04ffa6d000, id=0, base_msr= fee00100 PRIx64
base_address=fee00000
Jun 27 09:13:19 eppigw01 genunix: [ID 710719 kern.info] vmcs revision_id
= f
Jun 27 09:13:19 eppigw01 genunix: [ID 420667 kern.info] kvm_lapic_reset:
vcpu=ffffff04ffa65000, id=1, base_msr= fee00000 PRIx64
base_address=fee00000
Jun 27 09:13:19 eppigw01 genunix: [ID 710719 kern.info] vmcs revision_id
= f
Jun 27 09:13:21 eppigw01 genunix: [ID 391722 kern.info] unhandled wrmsr:
0xfed8c25b data 53
Jun 27 09:13:21 eppigw01 last message repeated 1 time
Jun 27 09:13:21 eppigw01 genunix: [ID 391722 kern.info] unhandled wrmsr:
0xff3fd4a0 data fffffd7fffdfea70
Jun 27 09:13:21 eppigw01 last message repeated 1 time
Jun 27 09:13:21 eppigw01 genunix: [ID 391722 kern.info] unhandled wrmsr:
0xffdff078 data fffffd7fffdfe900
Jun 27 09:13:21 eppigw01 last message repeated 1 time
Jun 27 09:13:21 eppigw01 genunix: [ID 291337 kern.info] vcpu 1 received
sipi with vector # 10
Jun 27 09:13:21 eppigw01 genunix: [ID 420667 kern.info] kvm_lapic_reset:
vcpu=ffffff04ffa65000, id=1, base_msr= fee00800 PRIx64
base_address=fee00000
Jun 27 09:13:37 eppigw01 genunix: [ID 713435 kern.info] unhandled rdmsr:
0x756e6547
Jun 27 09:13:37 eppigw01 genunix: [ID 391722 kern.info] unhandled wrmsr:
0x0 data 0
Jun 27 09:13:44 eppigw01 genunix: [ID 291337 kern.info] vcpu 1 received
sipi with vector # 10
Jun 27 09:13:44 eppigw01 genunix: [ID 420667 kern.info] kvm_lapic_reset:
vcpu=ffffff04ffa65000, id=1, base_msr= fee00800 PRIx64
base_address=fee00000
Jun 27 09:13:44 eppigw01 genunix: [ID 713435 kern.info] unhandled rdmsr:
0x756e6547
Jun 27 09:13:44 eppigw01 genunix: [ID 391722 kern.info] unhandled wrmsr:
0x0 data 0
Jun 27 09:13:44 eppigw01 genunix: [ID 713435 kern.info] unhandled rdmsr:
0x756e6547
Jun 27 09:13:44 eppigw01 genunix: [ID 391722 kern.info] unhandled wrmsr:
0x0 data 0
(sorry for the email client formatting)
---------------------------------------------------------
An update to tell tales of weirdness...
One of two things did "something":
1) pkg update in the non-global zone for Openssl & ntp
2) I attempted to turn off the new CPUID feature in the bios (new from
2008!) as I didn't know what it was for, with a resultant OmniOS crash
at startup. So I changed it back. ;)
One of these two things appears to have helped with kvm startup. Early
days, sure, but I have restarted three or four times without issue. I'll
let you know if it decides not to play nice again.
----------------------------------------------------------
I spoke too soon - I added another vnic and it took half a dozen
attempts to start. :(
_______________________________________________
OmniOS-discuss mailing list
[email protected]
http://lists.omniti.com/mailman/listinfo/omnios-discuss
