baby0nboardInSg

Hi, I have been reading a lot, but I can't find any document or discussion whether an upgrade from 6.9.2 to 6.11.5 is discouraged. I'm still stuck to not being able to run my windows 10 VM. Would anyone be able to advise if this wiki below: https://wiki.unraid.net/Manual/VM_Management#Step_1:_Preparing_the_disk is necessary for 6.11.5 only? as i did not perform this in 6.9.2, I only followed spaceinvader's guides to make my baremetal into a VM. hoping for anyone to help point into a direction. thanks in advance.

thanks for that, it's really is frustrating. For what it's worth, my IOMMU grouping has been different since I upgraded to 6.11.5. In 6.9.2, my Video card Gtx 1070 was grouped in the same IOMMU for both Graphics and audio, with the acs_override set to both. In 6.11.5, the same video card, the graphics is in 1 group and the audio is in another group, with the acs_override set to both. don't really have anything else here.. hopefully someone can give an advice on how to fix this.

Hi so i decided to create a thread for this as I can't find any working solution. I tried removing the <hyperv> </hyperv> block as some suggested here. I have tried binding my video card to VFIO. Nothing seems to work. This VM was perfectly working in 6.9.2 . attached are my diagnostics. Let me know if I missed anything. "Windows" VM is the 6.9.2 created VM - not working in 6.11.5 "Windows 10" VM is the 6.11.5 created VM - not working hope to hear from you soon.. someone help to point me to a direction unraid-diagnostics-20221125-2235.zip

-device '{"driver":"pcie-root-port","port":12,"chassis":5,"id":"pci.5","bus":"pcie.0","addr":"0x1.0x4"}' \ -device '{"driver":"qemu-xhci","p2":15,"p3":15,"id":"usb","bus":"pcie.0","addr":"0x7"}' \ -device '{"driver":"virtio-serial-pci","id":"virtio-serial0","bus":"pci.2","addr":"0x0"}' \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/virtio-win-0.1.190-1.iso","node-name":"libvirt-3-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-3-format","read-only":true,"driver":"raw","file":"libvirt-3-storage"}' \ -device '{"driver":"ide-cd","bus":"ide.1","drive":"libvirt-3-format","id":"sata0-0-1"}' \ -blockdev '{"driver":"host_device","filename":"/dev/disk/by-id/ata-SanDisk_SDSSDHII480G_153283407122","node-name":"libvirt-2-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-2-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-2-storage"}' \ -device '{"driver":"ide-hd","bus":"ide.2","drive":"libvirt-2-format","id":"sata0-0-2","bootindex":1,"write-cache":"on"}' \ -blockdev '{"driver":"host_device","filename":"/dev/disk/by-id/ata-TOSHIBA_DT01ACA100_46UVA8TNS","node-name":"libvirt-1-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-1-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-1-storage"}' \ -device '{"driver":"ide-hd","bus":"ide.3","drive":"libvirt-1-format","id":"sata0-0-3","write-cache":"on"}' \ -netdev tap,fd=36,id=hostnet0 \ -device '{"driver":"virtio-net","netdev":"hostnet0","id":"net0","mac":"52:54:00:d7:7c:d1","bus":"pci.1","addr":"0x0"}' \ -chardev pty,id=charserial0 \ -device '{"driver":"isa-serial","chardev":"charserial0","id":"serial0","index":0}' \ -chardev socket,id=charchannel0,fd=34,server=on,wait=off \ -device '{"driver":"virtserialport","bus":"virtio-serial0.0","nr":1,"chardev":"charchannel0","id":"channel0","name":"org.qemu.guest_agent.0"}' \ -audiodev '{"id":"audio1","driver":"none"}' \ -device '{"driver":"vfio-pci","host":"0000:07:00.0","id":"hostdev0","bus":"pci.3","multifunction":true,"addr":"0x0","romfile":"/mnt/disk1/software/vbios/GP104.dump"}' \ -device '{"driver":"vfio-pci","host":"0000:07:00.1","id":"hostdev1","bus":"pci.3","addr":"0x0.0x1"}' \ -device '{"driver":"usb-host","hostdevice":"/dev/bus/usb/003/002","id":"hostdev2","bus":"usb.0","port":"1"}' \ -device '{"driver":"usb-host","hostdevice":"/dev/bus/usb/003/004","id":"hostdev3","bus":"usb.0","port":"2"}' \ -device '{"driver":"usb-host","hostdevice":"/dev/bus/usb/003/003","id":"hostdev4","bus":"usb.0","port":"3"}' \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on char device redirected to /dev/pts/4 (label charserial0) 2022-11-25T11:14:44.920286Z qemu-system-x86_64: terminating on signal 15 from pid 6398 (/usr/sbin/libvirtd) 2022-11-25 11:14:46.522+0000: shutting down, reason=destroyed 2022-11-25 11:15:18.800+0000: starting up libvirt version: 8.7.0, qemu version: 7.1.0, kernel: 5.19.17-Unraid, hostname: UNRAID LC_ALL=C \ PATH=/bin:/sbin:/usr/bin:/usr/sbin \ HOME='/var/lib/libvirt/qemu/domain-5-Windows 10' \ XDG_DATA_HOME='/var/lib/libvirt/qemu/domain-5-Windows 10/.local/share' \ XDG_CACHE_HOME='/var/lib/libvirt/qemu/domain-5-Windows 10/.cache' \ XDG_CONFIG_HOME='/var/lib/libvirt/qemu/domain-5-Windows 10/.config' \ /usr/local/sbin/qemu \ -name 'guest=Windows 10,debug-threads=on' \ -S \ -object '{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-5-Windows 10/master-key.aes"}' \ -machine pc-q35-7.1,usb=off,dump-guest-core=off,mem-merge=off,memory-backend=pc.ram \ -accel kvm \ -cpu host,migratable=on,topoext=on,hv-time=on,hv-relaxed=on,hv-vapic=on,hv-spinlocks=0x1fff,hv-vendor-id=none,host-cache-info=on,l3-cache=off \ -m 8192 \ -object '{"qom-type":"memory-backend-ram","id":"pc.ram","size":8589934592}' \ -overcommit mem-lock=off \ -smp 8,sockets=1,dies=1,cores=4,threads=2 \ -uuid abc28570-caf9-0000-0000-000000000000 \ -display none \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=36,server=on,wait=off \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=localtime \ -no-hpet \ -no-shutdown \ -boot strict=on \ -device '{"driver":"pcie-root-port","port":8,"chassis":1,"id":"pci.1","bus":"pcie.0","multifunction":true,"addr":"0x1"}' \ -device '{"driver":"pcie-root-port","port":9,"chassis":2,"id":"pci.2","bus":"pcie.0","addr":"0x1.0x1"}' \ -device '{"driver":"pcie-root-port","port":10,"chassis":3,"id":"pci.3","bus":"pcie.0","addr":"0x1.0x2"}' \ -device '{"driver":"pcie-root-port","port":11,"chassis":4,"id":"pci.4","bus":"pcie.0","addr":"0x1.0x3"}' \ -device '{"driver":"pcie-root-port","port":12,"chassis":5,"id":"pci.5","bus":"pcie.0","addr":"0x1.0x4"}' \ -device '{"driver":"qemu-xhci","p2":15,"p3":15,"id":"usb","bus":"pcie.0","addr":"0x7"}' \ -device '{"driver":"virtio-serial-pci","id":"virtio-serial0","bus":"pci.2","addr":"0x0"}' \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/virtio-win-0.1.190-1.iso","node-name":"libvirt-3-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-3-format","read-only":true,"driver":"raw","file":"libvirt-3-storage"}' \ -device '{"driver":"ide-cd","bus":"ide.1","drive":"libvirt-3-format","id":"sata0-0-1"}' \ -blockdev '{"driver":"host_device","filename":"/dev/disk/by-id/ata-SanDisk_SDSSDHII480G_153283407122","node-name":"libvirt-2-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-2-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-2-storage"}' \ -device '{"driver":"ide-hd","bus":"ide.2","drive":"libvirt-2-format","id":"sata0-0-2","bootindex":1,"write-cache":"on"}' \ -blockdev '{"driver":"host_device","filename":"/dev/disk/by-id/ata-TOSHIBA_DT01ACA100_46UVA8TNS","node-name":"libvirt-1-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-1-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-1-storage"}' \ -device '{"driver":"ide-hd","bus":"ide.3","drive":"libvirt-1-format","id":"sata0-0-3","write-cache":"on"}' \ -netdev tap,fd=37,id=hostnet0 \ -device '{"driver":"virtio-net","netdev":"hostnet0","id":"net0","mac":"52:54:00:d7:7c:d1","bus":"pci.1","addr":"0x0"}' \ -chardev pty,id=charserial0 \ -device '{"driver":"isa-serial","chardev":"charserial0","id":"serial0","index":0}' \ -chardev socket,id=charchannel0,fd=35,server=on,wait=off \ -device '{"driver":"virtserialport","bus":"virtio-serial0.0","nr":1,"chardev":"charchannel0","id":"channel0","name":"org.qemu.guest_agent.0"}' \ -audiodev '{"id":"audio1","driver":"none"}' \ -device '{"driver":"vfio-pci","host":"0000:07:00.0","id":"hostdev0","bus":"pci.3","multifunction":true,"addr":"0x0","romfile":"/mnt/disk1/software/vbios/GP104.dump"}' \ -device '{"driver":"vfio-pci","host":"0000:07:00.1","id":"hostdev1","bus":"pci.3","addr":"0x0.0x1"}' \ -device '{"driver":"usb-host","hostdevice":"/dev/bus/usb/003/002","id":"hostdev2","bus":"usb.0","port":"1"}' \ -device '{"driver":"usb-host","hostdevice":"/dev/bus/usb/003/004","id":"hostdev3","bus":"usb.0","port":"2"}' \ -device '{"driver":"usb-host","hostdevice":"/dev/bus/usb/003/003","id":"hostdev4","bus":"usb.0","port":"3"}' \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on char device redirected to /dev/pts/4 (label charserial0) 2022-11-25T11:19:41.295533Z qemu-system-x86_64: terminating on signal 15 from pid 6398 (/usr/sbin/libvirtd) hi ghost, I don't mean to high jack this thread, but I'm encountering the same issue too.. i was from 6.9.2 then i upgraded to 6.11.5. .. then my Windows VM doesn't have a diplay anymore. and my CPU 4th core is always at 100%. I have attached above VM log. at first my migrated VM was not working so, I thought creating a new windows 10 VM from version 6.11.5, would make things work. but still I'm back to 0, my VM still has no display.

yeah thank you Jorge and trurl.. I did read the more complicated procedure you mention, and as of now.. the data is enough, i'm only using it as backup for photos with nextcloud for helping for auto uploads. thank you and I think my curiosity has been fed.

Hi Jorge, thank you for the reply. did you mean the diagnostics from the disk itself? I've attached the whole diagnostics. unraid-diagnostics-20220827-0346.zip please help to give feedback. Thanks

Hi I'm fairly new to unraid and started using with a 1 parity disk and 1 data disk setup. ( both disk are extras i used for my small home server) After 6 months of no problems, the data disk finally showed some read errors. Since i only have 1 parity and 1 data disk, should following this guide be enough to replace my data disk? https://wiki.unraid.net/Replacing_a_Data_Drive I'm not sure if my parity disk is enough to restore the data disk. I could not search previous discussions so I created one, i just want to make sure before I replace my data disk.

Hi, It's me again, so given that only disk 2 you can use for DSM, will "Disk 2" have something like an "unbounded" storage limit, as it will depend on your shares? or it needs to be fixed storage declared in the VM? do correct me if i have things mixed up, i have no tried doing this yet.

Hi Squid, thanks. I actually tried removing the DROPBOX_SKIP_UPDATE value from the container settings. and made sure set the "Dropbox" share set to Cache setting to "No" and just tried restarting the container, and everything worked already. just circling back to share what was done to make the container work. Edit: for me this is very helpful because i don't have to do any WOL or VPN in the Server to turn on my windows VM. I can just let the kids know what to say to have the Windows VM start. thank you again for the guide.

Hi Squid, I actually used the "Dropbox-otherguy" mgutt's repo for this.. as i can't make the other work. I got into "Syncing..." in the container log but i don't receive my text file inside my share folder. any advise ?

Hi i'm trying out this docker too.. I have 1 text file and 1 sub directory in my dropbox account, but the file is not being synced/sent into the docker container "client". the logs just shows a series of lines of "Syncing... " any advice? EDIT: so i had to remove the value for the last property dropbox_skip_update, and tried the "No" Cache for the dropbox Shares setting, and the logs is now showing "Up to date" and plenty of it. Checking the share directory has reflected my filed already. just circling back for the update

may i ask, if the disk 1 and disk2 will be the "array drives" for the xpenology? i'm new to this and wanted to explore, is there a way to mix the unraid shares with the xpenology VM?

Hi, apologies for multi-posting but i have resolved my issue. what did it for me was disabling the CSM in my bios. Then when I rebooted Unraid, then started my screen is already UP. I don't really have a deep know how on this.. but for AMD SR-IOV needs PCIE-ARI to be enabled to work properly so i thought for those who experience the same issue with mine, you might want to check the BIOS settings for those.

unraid-diagnostics-20220417-2230.zip Attached is another set of diagnostics, i don't really know where i got wrong, i followed the spaceinvader's video about NVIDIA as primary GPU, about the black screen and I did a vbios dump and removing the header. VNC mode graphics works and loads my windows SSD. When i change the graphics to my video card it doesn't work anymore. Tomorrow i will try to roll back my mother bios if it will work hopefully

hi @jugaadkabaap will you be able to describe how to do a nvidia as secondary setup? I don't have any display if i set my video card as direct graphics for my VM, i made unraid as my main OS and my pc as a VM. . Thank you

Hi Community, Can anyone point me to a direction? So i bought unraid basic, to mak e my pc behave as a server and place my windows 10 desktop into a VM, when I set the VM there seems to be no screen/display on my monitor. I have tried the following: - edit VM XML to correct the slot and place the multifunction attribute into the video card hostdev xml block. - made sure i'm using the correct pci slot - re used my SSD as the virtual disk for the VM, using VNC my windows loads, its just when i change the VM into gtx 1070, i did a dump of my video card to place as the "rom" entry into the hostdev block for my graphics card. I really don't have any other direction to proceed, my VM boots, but there is no screen or display i can see on my monitor. Please help to assist. unraid-diagnostics-20220415-1325.zip