SimonF

Check it is not hidden. Click on green padlock top right.
 
Then blue spanner on system part and check not hidden in list that appears.
 

Do you have fastboot enabled if so disable.

Configs are here
 
root@computenode:~# ls /boot/config/wireguard/
peers/  wg0.cfg  wg0.conf  wg1.conf
root@computenode:~# 

Not currently but have made a PR for the next release to fit window.
 
https://github.com/unraid/webgui/pull/1704

You have to create a mount point in the vm and then mount it.
 
i.e.
mkdir /mnt/vmShare
mount -t virtiofs vmShare /mnt/vmShare

I have been able to get this to work.
 
To get socat for 6.12 do, if extra does not exist mkdir /boot/extra
cd /boot/extra wget https://slackware.uk/slackware/slackware64-15.0/slackware64/n/socat-1.7.4.3-x86_64-1.txz installpkg socat-1.7.4.3-x86_64-1.txz  
For next release will need to be 1.8 this version is not compatible with 6.12.
wget https://mirrors.slackware.com/slackware/slackware64-current/slackware64/n/socat-1.8.0.0-x86_64-1.txz  
You only need to install once downloaded. Packages in extra get loaded at boot.
 
This is the XML added to each VM.
 
Debian
    <serial type='unix'>
      <source mode='bind' path='/tmp/foo'/>
      <target type='isa-serial' port='1'>
        <model name='isa-serial'/>
      </target>
      <alias name='serial1'/>
    </serial>
 
Unraid-VM
    <serial type='unix'>
      <source mode='bind' path='/tmp/foo2'/>
      <target type='isa-serial' port='1'>
        <model name='isa-serial'/>
      </target>
      <alias name='serial1'/>
    </serial>
 
Then run -dd is only to give debug data.
 
root@computenode:/usr# socat -dd  UNIX-CLIENT:/tmp/foo  UNIX-CLIENT:/tmp/foo2  
2024/04/13 08:22:30 socat[17649] N successfully connected from local address AF=1 "\0\0\xEE\0\0\xEE\0\0"
2024/04/13 08:22:30 socat[17649] N successfully connected from local address AF=1 "\0\0\xEE\0\0\xEE\0\0\xEE"
2024/04/13 08:22:30 socat[17649] N starting data transfer loop with FDs [5,5] and [6,6]
 
 

Is this your flash drive?
 
Bus 001 Device 005: ID 0951:1666 Kingston Technology DataTraveler 100 G3/G4/SE9 G2/50
 
You have it defined in the JasonVM.
 
mv /usr/local/sbin/qemu /usr/local/sbin/qemu.old
 
This will allow you VM manager and the VMs will not autostart.
 
edit the VM to remove this section.
 
<hostdev mode="subsystem" type="usb" managed="no">
<source startupPolicy="optional">
<vendor id="0x0951"/>
<product id="0x1666"/>
</source>
<address type="usb" bus="0" port="1"/>
</hostdev>
 
mv /usr/local/sbin/qemu.old /usr/local/sbin/qemu
 
Now you should be able to start your VMs.
 
 
 

License is tied to the usb flash boot drive. So you can clear config and move to a different machine.

rename /usr/local/sbin/qemu and the VM will not be able to start. You will be able to remove from the gui. But remember to rename back.

If you are not using PCI passthru you can either leave blank or remove. Changes where made to stop autostart if vfio binding fails as could indicate PCI numbers have chaged due to hardware removal/additions etc. If the VM autostarts and now as the wrong device is allocated to the VM due to PCI number changes it could lookup or crash the host.
 
Before   
07:00.0 VGA Card(Passthru to VM)
08:00.0 Disk Controller(Unraid)
 
After
07:00.0 DIsk Controller(Unraid)
 
If the VM autostarts the diskcontroller would be allocated to the VM and all the Unraid disks would not been seen on the host as a simple example.
 
 

Are you still have issues, You logs are full of these errors. 
Tower winbindd[6662]: set_global_winbindd_state_offline: Offline requested Feb 22 09:34:10 Tower winbindd[6662]: [2024/02/22 09:34:10.370664, 0] ../../source3/winbindd/winbindd_cache.c:3465(set_global_winbindd_state_offline)
 
Can you post current diagnostics if having the issue still.

1024Gb is 1Tb? But it will start as a sparse file so the vdisk on the physical disk will be smaller until data is put into it.

single append line.
 

If you remove the mac address on the NIC it will remove the definition from the guest. You will still be able to access via VNC.

Yes domains is the vm share, appdata is the container path. configs are normally stored in system for both.

Any reason why you are not using host passthru for the CPU? First one is missing the feature lines below are the ones you have on the 2nd working one.
 
<cpu mode='custom' match='exact' check='full'> <model fallback='forbid'>qemu64</model> <topology sockets='1' dies='1' cores='1' threads='1'/> <feature policy='require' name='x2apic'/> <feature policy='require' name='hypervisor'/> <feature policy='require' name='lahf_lm'/> <feature policy='disable' name='svm'/> </cpu>

You need to be careful with this on 6.12 as overlay filesystems are in use which are still using the previous bz files.
 
Doing a 2nd update will cause an issue as it will delete the bz files in previous and move the current. Likely to get a system issue before reboot.

Yes that is correct.

The state of the connections should be as below so looks like it is not connected as serial. Are you able to unplug and reconnect the device?
 

Will auto connect
 
 

Does you vm auto start, maybe hardware has chnaged and pci device is not correct in vm.
 
You can rename the qemu command in /usr/local/sbin to stop it autostarting

yes

Yes plugins would be on flash.
 
search ca for qnap there is a plugin for fan controller

You dont need to login on the console. You can login just from the windows pc

Remove docker.folder.plg - 2023.03.18  (Deprecated)  (Up to date) as it is not compatible with 6.12.x
 
and install