shalarice

Hey look an active thread. lol

@Mr. Traxson Just in case you could not find the answer. You can indeed use the gui under Settings ---> Network: There you can find the IP settings such as the address, netmask, gateway, dns server. Take note that you need to stop the VM and Docker Service before doing so. It might also be useful to know that you need to make sure that you change the IP for the right interface if you have more than one nic in your system. Alternatively you could change these settings via ssh. https://www.freebsd.org/doc/handbook/config-network-setup.html Hope that helps a bit more than "take a look" regards

Hello, Sorry for broken english I just bought a license for UNRAID and have been setting it up on my machine. I am currently having 2 major issues at the moment. I have been going through threads but could not find anything on here or on external media. VMS are gone after a reboot. (I don't know much but I feel like it has something to do with the libvirt.img and the xml which contains the meta data of the vms being wrong or corrupted or missing? . I was not able to locate the said XML but I found related posts that mentioned it. I have been recreating the VM multiple times to try and fix the issue number 1 and have experienced wildly different behavior when doing so. Behavior varies from the vm not booting at all, taking 20 minutes to start. Sometimes the graphics card drivers are missing sometimes not. Troubleshooting steps are atrociously long. At the moment. The one VM is created but will not start or take 10 minutes to boot - Output comes up after 2 3 minutes but then nothing. I haven't changed anything since the last time I have attached the diagnostic files but here a little bit more info on my scenario: Hardware: Asus X99-A II fully updated bios CPU: I7-6800k RAM: Corsair Dominator 4 x 8 GB 3200mhz (XMP Profile disabled) GPU: Asus Strix GTX 970. Drives: 3TB WD RED - Parity 3TB WD RED - Array Disk 1 2TB WD RED - Array Disk 2 1TB WD RED - Array Disk 3 1TB WD RED - Array Disk 4 500GB Seagate RED - Array Disk5 128GB Adata SSD - Cache Drive 400GB Nvme Intel 750 Series : Passthrough for the One VM at fault. At the moment I only have one VM and no Docker container as I was trying to build my Server step by step: The VM is a Windows 10 Machine and I was able to, at some point, to have it working but as mentioned I feel like it is 1 step forward and 2 millions step back. The windows 10 was an existing windows 10 installation. I have set up a passthrough to my NVME 400 GB drive while building it and realized it was working, so I left it alone. At the moment the vms is setup that way: (I wish I had an xml I could send you guys but I can't find any). CPU Mode: Host Passthrough Logical CPUS (all 12 threads) Initial - Max Memory : 24 / 24 GB Machine: Q35-4.2 ( As suggested in guides and threads I have been reading) Bios: SeaBIOS (Again, as suggested in guides and threads) Hyper-V: No USB: Tried all of them and did not change anything but at the moment set to 3.0 (nec XHCI) Os Install media: NONE Primary vDisk Location: /dev/disk/by-id/nvme-INTEL_SSDPEDMW400G4_CVCQ54360060400AGN Primary vDisk Bus: *SATA as Virtio was not working Graphics Card: NVIDIA GeForce GTX 970 (01:00.0) Graphics Card ROM: Custom Rom where I edited the HASH from a tech republic ROM file that matched my GPU where I removed few lines as per community guide on youtube as there is nothing about that on yoru forum, or wiki (why?). that seems to work ok for * this is the log that I was getting when trying to set it to VIRTIO: 2020-03-29 16:22:58.019+0000: 3738: info : libvirt version: 5.10.0 2020-03-29 16:22:58.019+0000: 3738: info : hostname: GarbageUnraid 2020-03-29 16:22:58.019+0000: 3738: warning : qemuDomainObjTaint:9301 : Domain id=1 name='Windows 10' uuid=8d31c940-f54b-d742-9cae-b6295634b63c is tainted: high-privileges 2020-03-29 16:22:58.019+0000: 3738: warning : qemuDomainObjTaint:9301 : Domain id=1 name='Windows 10' uuid=8d31c940-f54b-d742-9cae-b6295634b63c is tainted: host-cpu 2020-03-29 16:40:15.997+0000: 3746: error : virProcessRunInFork:1159 : internal error: child reported (status=125): 2020-03-29 16:40:15.997+0000: 3746: warning : qemuBlockRemoveImageMetadata:2604 : Unable to remove disk metadata on vm Windows 10 from /dev/disk/by-id/nvme-INTEL_SSDPEDMW400G4_CVCQ54360060400AGN (disk target hdc) 2020-03-29 16:40:19.404+0000: 3740: warning : qemuDomainObjTaint:9301 : Domain id=2 name='Windows 10' uuid=8d31c940-f54b-d742-9cae-b6295634b63c is tainted: high-privileges 2020-03-29 16:40:19.404+0000: 3740: warning : qemuDomainObjTaint:9301 : Domain id=2 name='Windows 10' uuid=8d31c940-f54b-d742-9cae-b6295634b63c is tainted: host-cpu 2020-03-29 16:46:39.621+0000: 3738: error : virProcessRunInFork:1159 : internal error: child reported (status=125): 2020-03-29 16:46:39.621+0000: 3738: warning : qemuBlockRemoveImageMetadata:2604 : Unable to remove disk metadata on vm Windows 10 from /dev/disk/by-id/nvme-INTEL_SSDPEDMW400G4_CVCQ54360060400AGN (disk target hdc) 2020-03-29 16:48:17.504+0000: 10538: info : libvirt version: 5.10.0 2020-03-29 16:48:17.504+0000: 10538: info : hostname: Studio 2020-03-29 16:48:17.504+0000: 10538: warning : qemuDomainObjTaint:9301 : Domain id=1 name='Windows 10' uuid=8d31c940-f54b-d742-9cae-b6295634b63c is tainted: high-privileges 2020-03-29 16:48:17.504+0000: 10538: warning : qemuDomainObjTaint:9301 : Domain id=1 name='Windows 10' uuid=8d31c940-f54b-d742-9cae-b6295634b63c is tainted: host-cpu 2020-03-29 16:54:06.853+0000: 10535: error : qemuMonitorIO:619 : internal error: End of file from qemu monitor 2020-03-29 16:54:08.083+0000: 11636: error : virProcessRunInFork:1159 : internal error: child reported (status=125): internal error: End of file from qemu monitor 2020-03-29 16:54:08.083+0000: 11636: warning : qemuBlockRemoveImageMetadata:2604 : Unable to remove disk metadata on vm Windows 10 from /dev/disk/by-id/nvme-INTEL_SSDPEDMW400G4_CVCQ54360060400AGN (disk target hdc) 2020-03-29 17:05:44.448+0000: 10539: warning : qemuDomainObjTaint:9301 : Domain id=2 name='Windows 10' uuid=8d31c940-f54b-d742-9cae-b6295634b63c is tainted: high-privileges 2020-03-29 17:05:44.448+0000: 10539: warning : qemuDomainObjTaint:9301 : Domain id=2 name='Windows 10' uuid=8d31c940-f54b-d742-9cae-b6295634b63c is tainted: host-cpu 2020-03-29 17:17:20.463+0000: 10542: error : virProcessRunInFork:1159 : internal error: child reported (status=125): 2020-03-29 17:17:20.463+0000: 10542: warning : qemuBlockRemoveImageMetadata:2604 : Unable to remove disk metadata on vm Windows 10 from /dev/disk/by-id/nvme-INTEL_SSDPEDMW400G4_CVCQ54360060400AGN (disk target hdc) 2020-03-29 17:17:39.293+0000: 10536: warning : qemuDomainObjTaint:9301 : Domain id=3 name='Windows 10' uuid=8d31c940-f54b-d742-9cae-b6295634b63c is tainted: high-privileges 2020-03-29 17:17:39.293+0000: 10536: warning : qemuDomainObjTaint:9301 : Domain id=3 name='Windows 10' uuid=8d31c940-f54b-d742-9cae-b6295634b63c is tainted: host-cpu Last update: after booting for 12 minutes: this is the logs for the VM It is currently up and running. -cpu host,host-cache-info=on,l3-cache=off \ -m 24064 \ -overcommit mem-lock=off \ -smp 12,sockets=1,cores=6,threads=2 \ -uuid 8d31c940-f54b-d742-9cae-b6295634b63c \ -display none \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=34,server,nowait \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=localtime,driftfix=slew \ -global kvm-pit.lost_tick_policy=delay \ -no-hpet \ -no-shutdown \ -boot strict=on \ -device pcie-root-port,port=0x8,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x1 \ -device pcie-root-port,port=0x9,chassis=2,id=pci.2,bus=pcie.0,addr=0x1.0x1 \ -device pcie-root-port,port=0xa,chassis=3,id=pci.3,bus=pcie.0,addr=0x1.0x2 \ -device pcie-root-port,port=0xb,chassis=4,id=pci.4,bus=pcie.0,addr=0x1.0x3 \ -device pcie-root-port,port=0xc,chassis=5,id=pci.5,bus=pcie.0,addr=0x1.0x4 \ -device nec-usb-xhci,p2=15,p3=15,id=usb,bus=pcie.0,addr=0x7 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.2,addr=0x0 \ -blockdev '{"driver":"host_device","filename":"/dev/disk/by-id/nvme-INTEL_SSDPEDMW400G4_CVCQ54360060400AGN","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 ide-hd,bus=ide.2,drive=libvirt-1-format,id=sata0-0-2,bootindex=1,write-cache=on \ -netdev tap,fd=36,id=hostnet0,vhost=on,vhostfd=38 \ -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:c1:b1:f2,bus=pci.1,addr=0x0 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0 \ -chardev socket,id=charchannel0,fd=37,server,nowait \ -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ -device vfio-pci,host=0000:01:00.0,id=hostdev0,x-vga=on,bus=pci.3,addr=0x0,romfile=/mnt/user/system/ROMS/970.rom \ -device usb-host,hostbus=3,hostaddr=3,id=hostdev1,bus=usb.0,port=1 \ -device usb-host,hostbus=3,hostaddr=5,id=hostdev2,bus=usb.0,port=2 \ -device usb-host,hostbus=5,hostaddr=2,id=hostdev3,bus=usb.0,port=3 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on 2020-03-29 17:17:39.293+0000: Domain id=3 is tainted: high-privileges 2020-03-29 17:17:39.293+0000: Domain id=3 is tainted: host-cpu char device redirected to /dev/pts/1 (label charserial0) Before I finish this thread here are the result of a reboot: Before reboot: And the VM Manager setup ok so now for the reboot of the host. Oh well. It appears the vm is there now.... Which is not really what I was looking for as there is nothing I have done this time different than the last time I rebooted. However even though the machine is set to auto start. It did not. Its one after another. I guess I am too dumb to use UNRAID. I will post anyway as I am really not comfortable to use it as "production setup". thanks studio-diagnostics-20200329-1248.zip