Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

4 Neutral

About Fiservedpi

  • Rank
    Advanced Member
  • Birthday July 17


  • Location

Recent Profile Visitors

592 profile views
  1. Same RC 5 10 Dockers 4 vms br0 for all, ever since rc5 I've noticed one of my br0 Dockers would "stall out" become unreachable, I'm assuming this issue is why. Error does not appear until a VM is started tower-diagnostics-20191108-1356.zip
  2. After installing the container and trying to stop the array I'm now greeted with the server unable to spin down disk 1 anyone know how I can resolve this `````Oct 28 18:19:20 Tower root: umount: /mnt/disk1: target is busy. Oct 28 18:19:20 Tower emhttpd: shcmd (683): exit status: 32 Oct 28 18:19:20 Tower emhttpd: Retry unmounting disk share(s)... Oct 28 18:19:25 Tower emhttpd: Unmounting disks... Oct 28 18:19:25 Tower emhttpd: shcmd (684): umount /mnt/disk1 Oct 28 18:19:25 Tower root: umount: /mnt/disk1: target is busy. Oct 28 18:19:25 Tower emhttpd: shcmd (684): exit status: 32 Oct 28 18:19:25 Tower emhttpd: Retry unmounting disk share```
  3. Ok thanks @Squid That's what I thought my setup is currently 100% reliable so I'll just leave it as is I'll toss the nic in an pfsense scraps box I'm saving
  4. I recently picked up an Intel Pro 1000 PT dual nic would I benefit by using this over the built nic on my Mobo? Asus 310 Prime A
  5. I believe i got it there was an issue with my .iso
  6. Switch to sata cleared up a few errors now just this one
  7. After creating a new VM and clicking VNCRemote I'm presented with this screen can anyone assist, what is it telling me? And what should I do?
  8. after upgrading my gpu im now getting this error in the picture. Attached vm log as well, everything was running before and 10 min after but has stopped working -cpu host,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_vendor_id=none \ -drive file=/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd,if=pflash,format=raw,unit=0,readonly=on \ -drive file=/etc/libvirt/qemu/nvram/347d621d-20a1-54f8-c6ec-4bcc2f308186_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 \ -m 4608 \ -realtime mlock=off \ -smp 3,sockets=1,cores=3,threads=1 \ -uuid 347d621d-20a1-54f8-c6ec-4bcc2f308186 \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=24,server,nowait \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=localtime \ -no-hpet \ -no-shutdown \ -boot strict=on \ -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x7.0x7 \ -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x7 \ -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x7.0x1 \ -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x7.0x2 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 \ -drive 'file=/mnt/user/domains/Windows 10.3/vdisk1.img,format=raw,if=none,id=drive-virtio-disk2,cache=writeback' \ -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk2,id=virtio-disk2,bootindex=1,write-cache=on \ -drive file=/mnt/user/isos/virtio-win-0.1.160-1.iso,format=raw,if=none,id=drive-ide0-0-1,readonly=on \ -device ide-cd,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1 \ -netdev tap,fd=27,id=hostnet0,vhost=on,vhostfd=28 \ -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:30:69:2f,bus=pci.0,addr=0x3 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0 \ -chardev socket,id=charchannel0,fd=29,server,nowait \ -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ -device usb-tablet,id=input0,bus=usb.0,port=1 \ -vnc,websocket=5700 \ -k en-us \ -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2 \ -device vfio-pci,host=01:00.0,id=hostdev0,bus=pci.0,addr=0x6 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on 2019-09-14 14:16:36.253+0000: Domain id=2 is tainted: high-privileges 2019-09-14 14:16:36.253+0000: Domain id=2 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial
  9. so i've got the plugin up and running WITHIN my network but it doesn't work outside my network i've forwarded the correct port but am lost on how to have this set so i can connect when I'm not on my network
  10. And swing and a miss number 2 traded up from a 760 to 960 gtx but same issue "no Cuda enabled devices found" as well as rm-init-adapter failed does this mean these cards can not do transcoding? I've passed it through to the VM successfully (off during testing though)
  11. All of a sudden the plug-in is not actually updating the Dockers all my settings are the same but I have to hit the apply update button manually
  12. meehh slap a putty tunnel on that sum b%#$ch call it a dayy