SOLVED UBUNTU 20.04 Virtual Machine suddenly stops after a few days running (SOLVED)

[Dennis Lovelady]

I was impressed how easily I could set up a Virtual Machine on FreeNAS. Currently running FreeNAS-11.3-U2. My VM runs great for a few days and then suddenly it is (apparently) powered off (by FreeNAS?). There is nothing in the VM's logs that helps identify the issue. For example, it "went away" between 4:00AM and 4:05AM yesterday. Here are the /var/log/syslog from before the DOWN until the startup. Nothing here to indicate it's about to crash.
````
Mar 17 03:58:45 www20 kernel: [ 18.984898] Initializing XFRM netlink socket
Mar 17 03:58:45 www20 systemd-udevd[392]: ethtool: autonegotiation is unset or enabled, the speed an
d duplex are not writable.
Mar 17 03:58:45 www20 systemd-networkd[620]: rtnl: received neighbor for link '3' we don't know abou
t, ignoring.
Mar 17 03:58:45 www20 systemd-networkd[620]: message repeated 3 times: [ rtnl: received neighbor for
link '3' we don't know about, ignoring.]
Mar 17 03:58:45 www20 systemd-timesyncd[569]: Network configuration changed, trying to establish con
nection.
Mar 17 03:58:45 www20 networkd-dispatcher[676]: WARNING:Unknown index 3 seen, reloading interface li
st
Mar 17 07:58:46 www20 systemd[1]: Starting Daily apt upgrade and clean activities...
Mar 17 07:58:46 www20 systemd[1]: Starting Clean php session files...
````

Similarly, here's the output from "last -x"
````
dennis pts/1 10.158.54.6 Wed Mar 17 08:00 still logged in
dennis pts/0 10.158.54.6 Wed Mar 17 08:00 still logged in
runlevel (to lvl 5) 5.4.0-66-generic Wed Mar 17 07:58 still running
reboot system boot 5.4.0-66-generic Wed Mar 17 03:58 still running
dennis pts/2 10.158.54.6 Sat Mar 13 19:59 - crash (3+06:59)
dennis pts/2 10.158.54.6 Fri Mar 12 23:16 - 23:17 (00:01)
dennis pts/1 10.158.54.6 Fri Mar 12 20:45 - crash (4+06:13)
````
While I admit there's somethin indicating a crash on Saturday, there is nothing at all about the shutdown last night.

Because this was going on, I put together a process that writes basically a "still alive" message to a MySQL database every five minutes. An entry was written at 4AM, on the 16th, the last entry before this morning. I do know for sure that the process never runs early so I can take it to the bank that it was alive at 04:00:01 on 16-March, and not alive at 04:05:02.

All the above for this: How can I tell from FreeNAS logs what its perception of that VM is? Or if FreeNAS took some sort of drastic action? I have several servers running in this network, some physical, some running on EXSI, and have never seen such a "neat" (<--wildly inappropriate choice of words here) shutdown of a system.

Can you help?

 

[sretalla]

What you have shared so far points me in the direction of asking about your hardware (in particular the network).

What are you running FreeNAS on and how is the network (host and VM) set up?

 

[Dennis Lovelady]

Running on a 64GB Xeon E7/V4. Hardware list below.

VM NIC:
nic_attach: igb1
mac: 00:a0:98:4f:ce:59
type: E1000



Here's the pciconvf -lv output:

> pciconf -lv
none0@pci0:255:11:0: class=0x088000 card=0x6f818086 chip=0x6f818086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link 0/1'
class = base peripheral
none1@pci0:255:11:1: class=0x110100 card=0x6f368086 chip=0x6f368086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link 0/1'
class = dasp
subclass = performance counters
none2@pci0:255:11:2: class=0x110100 card=0x6f378086 chip=0x6f378086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link 0/1'
class = dasp
subclass = performance counters
none3@pci0:255:11:3: class=0x088000 card=0x00000000 chip=0x6f768086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link Debug'
class = base peripheral
none4@pci0:255:12:0: class=0x088000 card=0x6fe08086 chip=0x6fe08086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent'
class = base peripheral
none5@pci0:255:12:1: class=0x088000 card=0x6fe18086 chip=0x6fe18086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent'
class = base peripheral
none6@pci0:255:12:2: class=0x088000 card=0x6fe28086 chip=0x6fe28086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent'
class = base peripheral
none7@pci0:255:12:3: class=0x088000 card=0x6fe38086 chip=0x6fe38086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent'
class = base peripheral
none8@pci0:255:12:4: class=0x088000 card=0x6fe48086 chip=0x6fe48086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent'
class = base peripheral
none9@pci0:255:12:5: class=0x088000 card=0x6fe58086 chip=0x6fe58086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent'
class = base peripheral
none10@pci0:255:12:6: class=0x088000 card=0x6fe68086 chip=0x6fe68086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent'
class = base peripheral
none11@pci0:255:12:7: class=0x088000 card=0x6fe78086 chip=0x6fe78086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent'
class = base peripheral
none12@pci0:255:15:0: class=0x088000 card=0x6ff88086 chip=0x6ff88086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent'
class = base peripheral
none13@pci0:255:15:4: class=0x088000 card=0x6fe08086 chip=0x6ffc8086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent'
class = base peripheral
none14@pci0:255:15:5: class=0x088000 card=0x6fe08086 chip=0x6ffd8086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent'
class = base peripheral
none15@pci0:255:15:6: class=0x088000 card=0x6fe08086 chip=0x6ffe8086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent'
class = base peripheral
none16@pci0:255:16:0: class=0x088000 card=0x6f1d8086 chip=0x6f1d8086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R2PCIe Agent'
class = base peripheral
none17@pci0:255:16:1: class=0x110100 card=0x6f348086 chip=0x6f348086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R2PCIe Agent'
class = dasp
subclass = performance counters
none18@pci0:255:16:5: class=0x088000 card=0x6f1e8086 chip=0x6f1e8086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Ubox'
class = base peripheral
none19@pci0:255:16:6: class=0x110100 card=0x6f7d8086 chip=0x6f7d8086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Ubox'
class = dasp
subclass = performance counters
none20@pci0:255:16:7: class=0x088000 card=0x6f1f8086 chip=0x6f1f8086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Ubox'
class = base peripheral
none21@pci0:255:18:0: class=0x088000 card=0x6fa08086 chip=0x6fa08086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Home Agent 0'
class = base peripheral
none22@pci0:255:18:1: class=0x110100 card=0x6f308086 chip=0x6f308086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Home Agent 0'
class = dasp
subclass = performance counters
none23@pci0:255:19:0: class=0x088000 card=0x6fa88086 chip=0x6fa88086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Target Address/Thermal/RAS'
class = base peripheral
none24@pci0:255:19:1: class=0x088000 card=0x6f718086 chip=0x6f718086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Target Address/Thermal/RAS'
class = base peripheral
none25@pci0:255:19:2: class=0x088000 card=0x6faa8086 chip=0x6faa8086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel Target Address Decoder'
class = base peripheral
none26@pci0:255:19:3: class=0x088000 card=0x6fab8086 chip=0x6fab8086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel Target Address Decoder'
class = base peripheral
none27@pci0:255:19:4: class=0x088000 card=0x6fac8086 chip=0x6fac8086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel Target Address Decoder'
class = base peripheral
none28@pci0:255:19:5: class=0x088000 card=0x6fad8086 chip=0x6fad8086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel Target Address Decoder'
class = base peripheral
none29@pci0:255:19:6: class=0x088000 card=0x00000000 chip=0x6fae8086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Broadcast'
class = base peripheral
none30@pci0:255:19:7: class=0x088000 card=0x00000000 chip=0x6faf8086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Global Broadcast'
class = base peripheral
none31@pci0:255:20:0: class=0x088000 card=0x6fb08086 chip=0x6fb08086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 0 Thermal Control'
class = base peripheral
none32@pci0:255:20:1: class=0x088000 card=0x6fb18086 chip=0x6fb18086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 1 Thermal Control'
class = base peripheral
none33@pci0:255:20:2: class=0x088000 card=0x6fb28086 chip=0x6fb28086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 0 Error'
class = base peripheral
none34@pci0:255:20:3: class=0x088000 card=0x6fb38086 chip=0x6fb38086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 1 Error'
class = base peripheral
none35@pci0:255:20:4: class=0x088000 card=0x00000000 chip=0x6fbc8086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Interface'
class = base peripheral
none36@pci0:255:20:5: class=0x088000 card=0x00000000 chip=0x6fbd8086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Interface'
class = base peripheral
none37@pci0:255:20:6: class=0x088000 card=0x00000000 chip=0x6fbe8086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Interface'
class = base peripheral
none38@pci0:255:20:7: class=0x088000 card=0x00000000 chip=0x6fbf8086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Interface'
class = base peripheral
none39@pci0:255:21:0: class=0x088000 card=0x6fb48086 chip=0x6fb48086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 2 Thermal Control'
class = base peripheral
none40@pci0:255:21:1: class=0x088000 card=0x6fb58086 chip=0x6fb58086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 3 Thermal Control'
class = base peripheral
none41@pci0:255:21:2: class=0x088000 card=0x6fb68086 chip=0x6fb68086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 2 Error'
class = base peripheral
none42@pci0:255:21:3: class=0x088000 card=0x6fb78086 chip=0x6fb78086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 3 Error'
class = base peripheral
none43@pci0:255:30:0: class=0x088000 card=0x6f988086 chip=0x6f988086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit'
class = base peripheral
none44@pci0:255:30:1: class=0x088000 card=0x6f998086 chip=0x6f998086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit'
class = base peripheral
none45@pci0:255:30:2: class=0x088000 card=0x6f9a8086 chip=0x6f9a8086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit'
class = base peripheral
none46@pci0:255:30:3: class=0x088000 card=0x6fc08086 chip=0x6fc08086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit'
class = base peripheral
none47@pci0:255:30:4: class=0x088000 card=0x6f9c8086 chip=0x6f9c8086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit'
class = base peripheral
none48@pci0:255:31:0: class=0x088000 card=0x00000000 chip=0x6f888086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit'
class = base peripheral
none49@pci0:255:31:2: class=0x088000 card=0x00000000 chip=0x6f8a8086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit'
class = base peripheral
hostb0@pci0:0:0:0: class=0x060000 card=0x086d15d9 chip=0x6f008086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DMI2'
class = bridge
subclass = HOST-PCI
pcib2@pci0:0:1:0: class=0x060400 card=0x086d15d9 chip=0x6f028086 rev=0x03 hdr=0x01
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 1'
class = bridge
subclass = PCI-PCI
pcib3@pci0:0:2:0: class=0x060400 card=0x086d15d9 chip=0x6f048086 rev=0x03 hdr=0x01
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 2'
class = bridge
subclass = PCI-PCI
pcib4@pci0:0:2:2: class=0x060400 card=0x086d15d9 chip=0x6f068086 rev=0x03 hdr=0x01
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 2'
class = bridge
subclass = PCI-PCI
pcib5@pci0:0:3:0: class=0x060400 card=0x086d15d9 chip=0x6f088086 rev=0x03 hdr=0x01
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 3'
class = bridge
subclass = PCI-PCI
none50@pci0:0:5:0: class=0x088000 card=0x086d15d9 chip=0x6f288086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Map/VTd_Misc/System Management'
class = base peripheral
none51@pci0:0:5:1: class=0x088000 card=0x086d15d9 chip=0x6f298086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D IIO Hot Plug'
class = base peripheral
none52@pci0:0:5:2: class=0x088000 card=0x086d15d9 chip=0x6f2a8086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D IIO RAS/Control Status/Global Errors'
class = base peripheral
xhci0@pci0:0:20:0: class=0x0c0330 card=0x086d15d9 chip=0x8c318086 rev=0x05 hdr=0x00
vendor = 'Intel Corporation'
device = '8 Series/C220 Series Chipset Family USB xHCI'
class = serial bus
subclass = USB
none53@pci0:0:22:0: class=0x078000 card=0x086d15d9 chip=0x8c3a8086 rev=0x04 hdr=0x00
vendor = 'Intel Corporation'
device = '8 Series/C220 Series Chipset Family MEI Controller'
class = simple comms
none54@pci0:0:22:1: class=0x078000 card=0x086d15d9 chip=0x8c3b8086 rev=0x04 hdr=0x00
vendor = 'Intel Corporation'
device = '8 Series/C220 Series Chipset Family MEI Controller'
class = simple comms
ehci0@pci0:0:26:0: class=0x0c0320 card=0x086d15d9 chip=0x8c2d8086 rev=0x05 hdr=0x00
vendor = 'Intel Corporation'
device = '8 Series/C220 Series Chipset Family USB EHCI'
class = serial bus
subclass = USB
pcib6@pci0:0:28:0: class=0x060400 card=0x086d15d9 chip=0x8c108086 rev=0xd5 hdr=0x01
vendor = 'Intel Corporation'
device = '8 Series/C220 Series Chipset Family PCI Express Root Port'
class = bridge
subclass = PCI-PCI
pcib7@pci0:0:28:4: class=0x060400 card=0x086d15d9 chip=0x8c188086 rev=0xd5 hdr=0x01
vendor = 'Intel Corporation'
device = '8 Series/C220 Series Chipset Family PCI Express Root Port'
class = bridge
subclass = PCI-PCI
ehci1@pci0:0:29:0: class=0x0c0320 card=0x086d15d9 chip=0x8c268086 rev=0x05 hdr=0x00
vendor = 'Intel Corporation'
device = '8 Series/C220 Series Chipset Family USB EHCI'
class = serial bus
subclass = USB
isab0@pci0:0:31:0: class=0x060100 card=0x086d15d9 chip=0x8c548086 rev=0x05 hdr=0x00
vendor = 'Intel Corporation'
device = 'C224 Series Chipset Family Server Standard SKU LPC Controller'
class = bridge
subclass = PCI-ISA
ahci1@pci0:0:31:2: class=0x010601 card=0x086d15d9 chip=0x8c028086 rev=0x05 hdr=0x00
vendor = 'Intel Corporation'
device = '8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode]'
class = mass storage
subclass = SATA
none55@pci0:0:31:3: class=0x0c0500 card=0x086d15d9 chip=0x8c228086 rev=0x05 hdr=0x00
vendor = 'Intel Corporation'
device = '8 Series/C220 Series Chipset Family SMBus Controller'
class = serial bus
subclass = SMBus
none56@pci0:0:31:6: class=0x118000 card=0x086d15d9 chip=0x8c248086 rev=0x05 hdr=0x00
vendor = 'Intel Corporation'
device = '8 Series Chipset Family Thermal Management Controller'
class = dasp
none57@pci0:2:0:0: class=0x088000 card=0x086d15d9 chip=0x6f508086 rev=0x00 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon Processor D Family QuickData Technology Register DMA Channel 0'
class = base peripheral
none58@pci0:2:0:1: class=0x088000 card=0x086d15d9 chip=0x6f518086 rev=0x00 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon Processor D Family QuickData Technology Register DMA Channel 1'
class = base peripheral
none59@pci0:2:0:2: class=0x088000 card=0x086d15d9 chip=0x6f528086 rev=0x00 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon Processor D Family QuickData Technology Register DMA Channel 2'
class = base peripheral
none60@pci0:2:0:3: class=0x088000 card=0x086d15d9 chip=0x6f538086 rev=0x00 hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon Processor D Family QuickData Technology Register DMA Channel 3'
class = base peripheral
ix0@pci0:3:0:0: class=0x020000 card=0x15ad15d9 chip=0x15ad8086 rev=0x00 hdr=0x00
vendor = 'Intel Corporation'
device = 'Ethernet Connection X552/X557-AT 10GBASE-T'
class = network
subclass = ethernet
ix1@pci0:3:0:1: class=0x020000 card=0x15ad15d9 chip=0x15ad8086 rev=0x00 hdr=0x00
vendor = 'Intel Corporation'
device = 'Ethernet Connection X552/X557-AT 10GBASE-T'
class = network
subclass = ethernet
ahci0@pci0:4:0:0: class=0x010601 card=0x92151b4b chip=0x92151b4b rev=0x11 hdr=0x00
vendor = 'Marvell Technology Group Ltd.'
class = mass storage
subclass = SATA
igb0@pci0:5:0:0: class=0x020000 card=0x152115d9 chip=0x15218086 rev=0x01 hdr=0x00
vendor = 'Intel Corporation'
device = 'I350 Gigabit Network Connection'
class = network
subclass = ethernet
igb1@pci0:5:0:1: class=0x020000 card=0x152115d9 chip=0x15218086 rev=0x01 hdr=0x00
vendor = 'Intel Corporation'
device = 'I350 Gigabit Network Connection'
class = network
subclass = ethernet
pcib8@pci0:6:0:0: class=0x060400 card=0x086d15d9 chip=0x11501a03 rev=0x03 hdr=0x01
vendor = 'ASPEED Technology, Inc.'
device = 'AST1150 PCI-to-PCI Bridge'
class = bridge
subclass = PCI-PCI
vgapci0@pci0:7:0:0: class=0x030000 card=0x086d15d9 chip=0x20001a03 rev=0x30 hdr=0x00
vendor = 'ASPEED Technology, Inc.'
device = 'ASPEED Graphics Family'
class = display
subclass = VGA

 

[sretalla]

type: E1000

For a linux VM, you should probably be using VirtIO rather than E1000. Have you tried that?

 

[Dennis Lovelady]

Before I start changing things that seem to otherwise work, and hope I accidentally stumble on what might be wrong, I'd rather understand the problem and eliminate it intelligently. I don't only want it to go away, I want to understand it and diagnose. I'll restate:

All the above for this: How can I tell from FreeNAS logs what its perception of that VM is? Or if FreeNAS took some sort of drastic action? I have several servers running in this network, some physical, some running on EXSI, and have never seen such a "neat" (<--wildly inappropriate choice of words here) shutdown of a system.

 

[morganL]

FreeNAS integrates bhyve as the hypervisor for VMs. Typically FreeNAS is responsible for the set-up of the VM. However, once it is running, bhyve is responsible for operating the VM. The stability of bhyve is a function of the guest OS and drivers.

Unless, you want to debug old versions of bhyve, I'd suggest updating to 11.3-U5 to make sure you have the most stable version. If a wizened sage recommends virtio, its probably because of experience and finding that there were fewer bugs with this driver option. After those issues are eliminated, they you can make a call on whether bhyve is reliable enough for this VM.

One of the main reasons for the introduction of TrueNAS SCALE is that it supports KVM hypervisor. This is significantly more battle tested and supports a much wider range of guest OSes reliably. It's still early for use of that, but that option is being rolled out.

 

[Basil Hendroff]

I'd suggest updating to 11.3-U5 to make sure you have the most stable version.

@Dennis Lovelady I'm running Ubuntu 20.04 in an 11.3-U5 and it's as stable as a rock.

 

[Dennis Lovelady]

FreeNAS integrates bhyve as the hypervisor for VMs. Typically FreeNAS is responsible for the set-up of the VM. However, once it is running, bhyve is responsible for operating the VM. The stability of bhyve is a function of the guest OS and drivers.

Unless, you want to debug old versions of bhyve, I'd suggest updating to 11.3-U5 to make sure you have the most stable version. If a wizened sage recommends virtio, its probably because of experience and finding that there were fewer bugs with this driver option. After those issues are eliminated, they you can make a call on whether bhyve is reliable enough for this VM.

One of the main reasons for the introduction of TrueNAS SCALE is that it supports KVM hypervisor. This is significantly more battle tested and supports a much wider range of guest OSes reliably. It's still early for use of that, but that option is being rolled out.

Thank you, this is good information. I will update the version of FreeNAS (didn't realize it'd gotten backlevel).

On the Wizened Sage: there was no basis or justification for making the change. "You should probably" has never gotten me much success in the past. "... because..." would have been a welcomed addition. Especially in light of the fact that a poor choice (if it is that) for network selection should never bring a system down. AND because - again - I am looking for logs. Reasons. Explanations. Not quick fixes.

 

[Dennis Lovelady]

I will consider ths solved (by upgrading from -U2 to -U5.

i still hold that there should have been logs indicating what went wrong (and when), but I suppose the point is moot now.