Change of hardware, network drops when starting VM

[reggierat]

I have just swapped my motherboard, CPU and memory.

 

I have kept the same Intel NIC

 

Since swapping the hardware everytime i start my windows VM i lose network access to the unraid Host

update: seems a bit random, sometimes doing it before starting the array etc

 

I have verified this several times booting into GUI mode

 

Any help would be greatly appreciated

 

I have deleted both my network config file and the vfio-bind config file

 

 

unraid-diagnostics-20220402-1400.zip

Edited April 2, 2022 by reggierat

[MrGrey]

Just the Windows VM, or others as well?

 

[reggierat]

5 minutes ago, MrGrey said:

Just the Windows VM, or others as well?

 

Sorry if i wasn't clear , the unraid Host

[JorgeB]

Apr  2 13:59:49 unRaid kernel: dmar_fault: 2 callbacks suppressed
Apr  2 13:59:49 unRaid kernel: DMAR: DRHD: handling fault status reg 3
Apr  2 13:59:49 unRaid kernel: DMAR: [DMA Read] Request device [05:00.0] PASID ffffffff fault addr fff8b000 [fault reason 06] PTE Read access is not set
Apr  2 13:59:49 unRaid kernel: DMAR: DRHD: handling fault status reg 3
Apr  2 13:59:49 unRaid kernel: DMAR: [DMA Read] Request device [05:00.0] PASID ffffffff fault addr ffcb6000 [fault reason 06] PTE Read access is not set
Apr  2 13:59:49 unRaid kernel: DMAR: DRHD: handling fault status reg 2
Apr  2 13:59:49 unRaid kernel: DMAR: [DMA Read] Request device [05:00.0] PASID ffffffff fault addr ff740000 [fault reason 06] PTE Read access is not set
Apr  2 13:59:49 unRaid kernel: DMAR: DRHD: handling fault status reg 2

 

There's this constant issue with the NIC, later resulting in a hang:

 

Apr  2 13:59:51 unRaid kernel: e1000 0000:05:00.0 eth0: Detected Tx Unit Hang
Apr  2 13:59:51 unRaid kernel:  Tx Queue             <0>
Apr  2 13:59:51 unRaid kernel:  TDH                  <6b>
Apr  2 13:59:51 unRaid kernel:  TDT                  <7d>
Apr  2 13:59:51 unRaid kernel:  next_to_use          <7d>
Apr  2 13:59:51 unRaid kernel:  next_to_clean        <68>
Apr  2 13:59:51 unRaid kernel: buffer_info[next_to_clean]
Apr  2 13:59:51 unRaid kernel:  time_stamp           <fffe78a5>
Apr  2 13:59:51 unRaid kernel:  next_to_watch        <6c>
Apr  2 13:59:51 unRaid kernel:  jiffies              <fffe7f80>
Apr  2 13:59:51 unRaid kernel:  next_to_watch.status <0>
Apr  2 13:59:53 unRaid kernel: e1000 0000:05:00.0 eth0: Detected Tx Unit Hang
Apr  2 13:59:53 unRaid kernel:  Tx Queue             <0>
Apr  2 13:59:53 unRaid kernel:  TDH                  <6b>
Apr  2 13:59:53 unRaid kernel:  TDT                  <7d>
Apr  2 13:59:53 unRaid kernel:  next_to_use          <7d>
Apr  2 13:59:53 unRaid kernel:  next_to_clean        <68>
Apr  2 13:59:53 unRaid kernel: buffer_info[next_to_clean]
Apr  2 13:59:53 unRaid kernel:  time_stamp           <fffe78a5>
Apr  2 13:59:53 unRaid kernel:  next_to_watch        <6c>
Apr  2 13:59:53 unRaid kernel:  jiffies              <fffe8780>
Apr  2 13:59:53 unRaid kernel:  next_to_watch.status <0>
Apr  2 13:59:55 unRaid kernel: e1000 0000:05:00.0 eth0: Detected Tx Unit Hang
Apr  2 13:59:55 unRaid kernel:  Tx Queue             <0>
Apr  2 13:59:55 unRaid kernel:  TDH                  <6b>
Apr  2 13:59:55 unRaid kernel:  TDT                  <7d>
Apr  2 13:59:55 unRaid kernel:  next_to_use          <7d>
Apr  2 13:59:55 unRaid kernel:  next_to_clean        <68>
Apr  2 13:59:55 unRaid kernel: buffer_info[next_to_clean]
Apr  2 13:59:55 unRaid kernel:  time_stamp           <fffe78a5>
Apr  2 13:59:55 unRaid kernel:  next_to_watch        <6c>
Apr  2 13:59:55 unRaid kernel:  jiffies              <fffe8f80>
Apr  2 13:59:55 unRaid kernel:  next_to_watch.status <0>
Apr  2 13:59:56 unRaid kernel: ------------[ cut here ]------------

 

Try installing the NIC in a different PCIe slot if available.

[reggierat]

Thanks for taking a look. I've concluded the NIC has been damaged somehow in the changeover.  Rolled up a trial version of unraid on a fresh USB and had the same issue. Have switched over to the onboard NIC and all seems to be fine