Call Trace on VM Boot

[CorneliousJD]

I have a very lean Debian 9 VM running just PiHole and I get a call trace on booting it after upgrading to unRAID 6.4.0

 

Anyone able to diagnose what exactly is going on here? 

 

One thing I noticed is I didn't get the common problems alert until I tried to enable IPv4 (Static) + IPv6 (DHCP) - and I now disabled IPv6 entirely but it still shows in the logs below the call trace that IPv6 addresses are being assigned to interface docker0? Not sure if this is related at all, but Pv6 is unRAId settings is turned off again and this still happens.

 

Jan 13 17:23:05 Server kernel: device vnet0 entered promiscuous mode
Jan 13 17:23:05 Server kernel: br0: port 2(vnet0) entered blocking state
Jan 13 17:23:05 Server kernel: br0: port 2(vnet0) entered forwarding state
Jan 13 17:23:05 Server kernel: vmwrite error: reg 810 value 0 (err 0)
Jan 13 17:23:05 Server kernel: CPU: 24 PID: 9174 Comm: CPU 0/KVM Tainted: G W 4.14.13-unRAID #1
Jan 13 17:23:05 Server kernel: Hardware name: Supermicro PIO-617R-TLN4F+-ST031/X9DRi-LN4+/X9DR3-LN4+, BIOS 3.2 03/04/2015
Jan 13 17:23:05 Server kernel: Call Trace:
Jan 13 17:23:05 Server kernel: dump_stack+0x5d/0x79
Jan 13 17:23:05 Server kernel: kvm_lapic_reset+0x278/0x292 [kvm]
Jan 13 17:23:05 Server kernel: kvm_create_lapic+0xa5/0xb2 [kvm]
Jan 13 17:23:05 Server kernel: kvm_arch_vcpu_init+0xd9/0x22d [kvm]
Jan 13 17:23:05 Server kernel: kvm_vcpu_init+0xcd/0xee [kvm]
Jan 13 17:23:05 Server kernel: vmx_create_vcpu+0x54/0xd5c [kvm_intel]
Jan 13 17:23:05 Server kernel: kvm_vm_ioctl+0x13b/0x66c [kvm]
Jan 13 17:23:05 Server kernel: ? free_one_page+0xbe/0x271
Jan 13 17:23:05 Server kernel: vfs_ioctl+0x16/0x23
Jan 13 17:23:05 Server kernel: do_vfs_ioctl+0x4f1/0x504
Jan 13 17:23:05 Server kernel: SyS_ioctl+0x39/0x55
Jan 13 17:23:05 Server kernel: entry_SYSCALL_64_fastpath+0x1e/0x81
Jan 13 17:23:05 Server kernel: RIP: 0033:0x146bdafe1727

Jan 13 17:23:07 Server avahi-daemon[11514]: Joining mDNS multicast group on interface vnet0.IPv6 with address fe80::fc54:ff:fe83:d60e.
Jan 13 17:23:07 Server avahi-daemon[11514]: New relevant interface vnet0.IPv6 for mDNS.
Jan 13 17:23:07 Server avahi-daemon[11514]: Registering new address record for fe80::fc54:ff:fe83:d60e on vnet0.*.
Jan 13 17:23:34 Server root: Starting UniFi
Jan 13 17:23:34 Server kernel: RSP: 002b:0000146bd6cdc228 EFLAGS: 00000246
Jan 13 17:23:34 Server kernel: docker0: port 1(veth28a9d26) entered blocking state
Jan 13 17:23:34 Server kernel: docker0: port 1(veth28a9d26) entered disabled state
Jan 13 17:23:34 Server kernel: device veth28a9d26 entered promiscuous mode
Jan 13 17:23:34 Server kernel: IPv6: ADDRCONF(NETDEV_UP): veth28a9d26: link is not ready
Jan 13 17:23:34 Server kernel: docker0: port 1(veth28a9d26) entered blocking state
Jan 13 17:23:34 Server kernel: docker0: port 1(veth28a9d26) entered forwarding state
Jan 13 17:23:34 Server kernel: docker0: port 1(veth28a9d26) entered disabled state
Jan 13 17:23:35 Server kernel: eth0: renamed from vethedcaed5
Jan 13 17:23:35 Server kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth28a9d26: link becomes ready
Jan 13 17:23:35 Server kernel: docker0: port 1(veth28a9d26) entered blocking state
Jan 13 17:23:35 Server kernel: docker0: port 1(veth28a9d26) entered forwarding state
Jan 13 17:23:35 Server kernel: IPv6: ADDRCONF(NETDEV_CHANGE): docker0: link becomes ready
Jan 13 17:23:35 Server root: CA Docker Autostart Manager Finished
Jan 13 17:23:36 Server avahi-daemon[11514]: Joining mDNS multicast group on interface docker0.IPv6 with address fe80::42:fff:fed8:b8bb.
Jan 13 17:23:36 Server avahi-daemon[11514]: New relevant interface docker0.IPv6 for mDNS.
Jan 13 17:23:36 Server avahi-daemon[11514]: Registering new address record for fe80::42:fff:fed8:b8bb on docker0.*.
Jan 13 17:23:37 Server avahi-daemon[11514]: Joining mDNS multicast group on interface veth28a9d26.IPv6 with address fe80::2c95:a7ff:fef1:d388.
Jan 13 17:23:37 Server avahi-daemon[11514]: New relevant interface veth28a9d26.IPv6 for mDNS.
Jan 13 17:23:37 Server avahi-daemon[11514]: Registering new address record for fe80::2c95:a7ff:fef1:d388 on veth28a9d26.*.

server-diagnostics-20180113-1725.zip

[JorgeB]

On 12/01/2018 at 8:23 PM, limetech said:

Known Issues

• Certain motherboards with on-board Aspeed IPMI graphics adaptors may lose video or switch to different colored text during the boot process. To prevent this, add the nomodeset kernel option to your syslinux append line.

• Some users report vmwrite syslog errors as a result of VM startup. This is a harmless message and can be ignored; however, please report if you see this.

• AMD Ryzen CPU is known to freeze on linux-based distros and unRAID OS is no exception. Disabling C6 state either in your bios or using our zenstates program seems to be the most reliable mitigation for this issue. Maybe some day AMD will fix this.

• AMD Threadripper GPU passthrough to VM's does not work reliably. This is an AMD bug, maybe some day they'll fix it.

 

You should report it in the release thread.

 

 

 

 

[limetech]

1 hour ago, CorneliousJD said:

Jan 13 17:23:05 Server kernel: vmwrite error: reg 810 value 0 (err 0)

 

Right that message and associated stack dump happens for some reason.  VM seems to run ok though and it only happens at VM startup.

[allanp81]

I'm seeing exactly the same, everything appears to be working fine though.