timg11

Update after I thought more about this issue for a couple of days....
I told Gemini that 1) The Matrox installer did not recognize the card and refused to run; and 2) when I manually installed extracted drivers from Device Manager Update Driver, it sort of worked but the image was compressed in the upper half of the display.

Gemini thought those symptoms meant the QEMU was not properly initializing the Matrox, and went off on a rabbit trail of VBIOS, and various other attempts, finally leading to suggesting kernel changes for Unraid. At that point I realized it was off track and stopped.

I thought I'd go back to the manually installed drivers and do some testing with different DisplayPort to HDMI adapters on the two DIsplayPort outputs of the G550.
I re-installed the drivers, and the G550 was recognized and looked normal in Device Manager. Still had the 1/2 display on the HDMI monitor. The only other monitor I had in reach was a VGA analog. I had an adapter, so I plugged it in to the other port. Perfect video. I moved it to the first port. Perfect video. Then I borrowed another HDMI monitor and plugged it in the adapter and port I'd been testing with. Perfect video. So the 1/2 screen issue was a compatibility issue with a specific monitor.

So that HDMI incompatibility is still a mystery, but the Matrox card pass through into the Windows VM is solved.

I finally got this working.
I have the passthrough set up to bind to vfio in system devices, checked the [102b:0536] 03:00.0 VGA compatible controller in IOMMU Group 20.

I disabled the VGA and restarted. This succeeded without crashing Unraid. Then I enabled the VGA and it was detected as Microsoft Basic Adapter.
That seemed to work, but only supported one mode 1200x800, which apparently the connected monitor does not support so there was no display.

I then installed the Dell Matrox drivers for the VGA instead of the Basic Adapter drivers, and re-started the VM.
Then I was able to set the resolution for the physical VGA and have an image on the monitor, along with the QXL virtual display for VNC.

I think I figured it out. The uid was incorrect.
This line in fstab appears to work:

//T440.local/linux /mnt/linux cifs rw,credentials=/etc/samba/servershare.conf,uid=1000 0 0


Using UID=0 means root, which does not seem to allow R/W.
UID=1000 is the first user on the Debian system, which then shows files on the share as:

-rwxr-xr-x 1 debianuser root 6 May 24 11:36 test1.txt

Edit - I was getting my SSH sessions confused between the Unraid OS and the Debian 12 OS running in a VM under Unraid.
 
For the Unraid OS, I can log in SSH as root. I don't need to log in as other users. (the other users are for file shares on the array)
 
For Debian 12, I can log in as tim, but not as root. However I can use su to become root, so there is no issue.
 
 
 
 

@bmartino1 thank you! In my case with the SG200, it is very similar, but some of the names are different. For anyone else with a Cisco SG200 or similar:
From Port Management / Link Aggregation / LAG Management: Select the LAG you want to use (1 to 4), click Edit. Add the ports from the Port List to the LAG Members list with the > arrow button. Be sure to check the "LACP Enable" box. I chose IP/MAC address for load balance. Give the LAG a name. Click Apply and Close.
From Port Management / Link Aggregation / LAG Settings: Additional settings are available - I didn't need to change any of them.
 
From switch saved configuration:
interface gigabitethernet25 description "T440 Server Eth1 Bonded" channel-group 1 mode auto ! interface gigabitethernet26 description "T440 Server Eth2 Bonded" channel-group 1 mode auto ! interface Port-channel1 flowcontrol auto description T440-LAG !  
In Unraid, Ethernet: Enable Bonding Yes, Bonding Mode 802.3ad(4), bonding members eth0, eth1, Enable bridging Yes
 
To verify, I ran two instances of iperf3 server in Unraid from SSH shell sessions. (Use an alternate port for the second one)
Run iperf3 clients to the unraid server's IP (different ports) from two different computers at the same time.
On the Unraid dashboard for interface bond0, you should see an inbound number over 1 Gbps. I saw 1.9 Gbps with both iperf clients running.
 

Finally solved this. A helpful person @CwF on the Debian forum noticed the minimum RAM in the Template was 1G. I changed the minimum RAM to 8G, and the installer completed normally. I had the maximum RAM set at 24G, incorrectly thinking that the VM would allocate what was required up to that limit.

My error was to use the "Template" for a Debian VM provided in the Unraid "New VM" list of templates. That template has the 1G memory. Being new to Unraid, I was trying to minimize making changes to settings, incorrectly believing the Template was appropriate for a Debian VM.
 
Ironically, the libvirt logs look exactly the same for a successful install compared to a install that apparently failed due to lack of RAM:
2025-04-23 21:03:43.109+0000: 2110453: warning : qemuDomainObjTaintMsg:7164 : Domain id=5 name='Debian' uuid=6b84f376-fdc0-6c7a-2b13-637dc7bf562a is tainted: high-privileges  

Finally solved this. A helpful person @CwF on the Debian forum noticed the minimum RAM in the Template was 1G. I changed the minimum RAM to 8G, and the installer completed normally. I had the maximum RAM set at 24G, incorrectly thinking that the VM would allocate what was required up to that limit.

My error was to use the "Template" for a Debian VM provided in the Unraid "New VM" list of templates. That template has the 1G memory. Being new to Unraid, I was trying to minimize making changes to settings, incorrectly believing the Template was appropriate for a Debian VM.