softfeet

Hmm. Still seeing some weirdness. I have another gpu of the exact same type in the unraid host. When I load the second vm (ubuntu 16.04) with the second gpu. it crashed the system. unraid offline. network packet storm. after reboot. the ubuntu vm wont boot at all. even after switching back to the regular vnc video. so strange. Could be due to board bios type that is being emulated. but i cant imagine that as the reason. I also checked the sylog file. nothing informative.

Figured out how it can work. setup the listener and the server in the sections listed. so that it is sending to the ip of itself... (unraid server)... Took about 3 minutes to push a few buttons and test after looking back into it. creates a file in the listed directory. having tcp and tcp set to the same is important... udp/tcp failed. lol.

I still need to do the ddu step. though I will give this phase an hour or two and see if it survives. then if it knocks itself out, i'll try the ddu. going to backup the xml too. I recall having that setting a while back ... but so many edits. like you say. they get lost depending on the mode. Thanks!

of note, that makes the VM sound a lot better. . seems faster on the network too. I have the same network profile up prior to loading the vm so that things will hopefully break/not break in the same environment.

<hostdev mode='subsystem' type='pci' managed='yes' xvga='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <rom file='/mnt/user/windows_share/desktop/MSI.GTX1070.dump'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x1'/> </hostdev>

Is this section critical?

Clearing the drivers and installing them. I don't know these steps all that well. The drivers were originally auto loaded from windows 10. I was amazed. I'm not sure what to do in the reload the drivers scenario.

edit rom file: yes. This was a lot easier on a windows machine. cleared old drivers: not yet. something to try. new vm method: I presume this would be just the regular emulated video hardware. the resolution is terrible. worth a shot to have it running as a clone to start and restart every few hours. pcie_no_flr in place, yes it is still in place.

This says that It should be logging syslog here... but it is a complete lie or misdirection. As far as I can tell.

I can't figure out why this is so unstable. my win10 vm is using seabios. was unable to get the install to work any other way. goes to that black startup screen if you use the non-seabios option.

Just had the unraid system lock up again. Was logged into win10 machine via parsec. Hit the shutdown button from the start menu. Entire network came to a grinding halt. network usage: two cifs connections open to two osx computers. (share mounted, not utilized for stream or transfer) smb mount in vm of linux. active data being transferred from wan to smb mount. nfs4 connection from above linux vm2. with active file transfer from wan. the win10 vm up. has a smb connected share to unraid. iscsi vm running with network share to linux vm. Everything works fine until the win10 vm is shut off. then unraid goes into network hell and the entire network grinds to a halt. packet blender. This is with the dumped rom file for the video card. I don't get it. This makes no sense. I would look at logs... but dont know exactly what to look for in a usb based system. .

I just went through the rom/dump procedure in the vm that crashes (the only windows machine i got :D) I am now runing the .dump file and the system looks stable. I'll try and get it to crash on shut down some time in the next few days. Unsure what causes the crash specifically, but this looks like a step in the right direction. Thanks for the explanation and tips. I'll check back in after a few days(or sooner if it blows up ) with updates if I use the ddu.

researching and reading about:

DDU: https://www.guru3d.com/files-details/display-driver-uninstaller-download.html unsure what the workflow for this would be though.

I had tried space invader's video on a first go through. It didn't work for me though. I dumped, found a bios file online. But found that just passing through worked... to a point. per the thread. I am not familiar with DDU. Can you explain why the options you are mentioning would help with my specific problem? I dont want to spend a lot of time trying something if it does not have a rational for being a solution. That is, I dont want to spend hours testing other people's theories unless I am sure that it is a guess and check session.