Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About johnsanc

  • Rank
    Advanced Member
  • Birthday 03/14/1984


  • Gender
  • Location
    Charlotte, NC

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Sounds good, thanks again for all your help with this. I'm glad it was actually something very simple, albeit a little tricky to find.
  2. I found a resolution to the issue I posted here and earlier in this thread if DEBUG is set to "yes" in the domain.cfg then the VMs UI will choke and appears to load forever. Changing this to "no" solved the issue. Still not really sure how that was ever set to "yes" in the first place though... just thought I would share in case anyone else runs into this.
  3. I FIGURED IT OUT!!! For some reason in my domain.cfg I had DEBUG set to "yes" - I have no idea how this even gets set to "yes" since I dont see anything for that in the webUI. I manually changed this to "no" and it worked. Not sure why that debug flag would cause the WebUI to choke, but at least I figured out the issue. Maybe thats something easy to fix with the next update. SERVICE="enable" IMAGE_FILE="/mnt/user/system/libvirt/libvirt.img" IMAGE_SIZE="1" DEBUG="yes" DOMAINDIR="/mnt/user/domains/vm/" MEDIADIR="/mnt/user/domains/iso/" VIRTIOISO="/mnt/user/domains/iso/virtio-win-0.1.160-1.iso" BRNAME="virbr0" VMSTORAGEMODE="auto" DISKDIR="/mnt/" TIMEOUT="60" HOSTSHUTDOWN="shutdown" (Restored my flash backup because the clean install was going to be an even bigger headache...)
  4. I was finally able to get it to work with stock .cfgs that were auto-generated with the exception of the disks cfg. I added that in so I could at least get to the VMs screen. - Although something is wrong with my cache devices. It did not recreate my cache pool properly. I think there is a defect in the VMs portion of the webGUI code. Also, if I start fresh with just the key and super.dat shouldn't it have assigned my cache drives properly? They are both populated as unassigned initially, which is a bit concerning.
  5. Yes its the same issue with all browsers across all devices I have, even in the unraid GUI mode browser. When I removed the .cfgs my cache drives are not included for some reason and so when I start the array the paths do not exist, so I cannot even get to the point where I can startup the VM service. I thought that including just the configs would be a good "bare minimum" - I'm not sure what else I can safely strip out.
  6. Ok, I STILL have the issue with the webUI even with a semi-virgin install. The only things I copied over were: super.dat Pro.key disk.cfg docker.cfg domain.cfg ident.cfg network-rules.cfg network.cfg share.cfg /shares/*.cfg Any thoughts?
  7. Alright, I guess I'll try that. I tried to downgrade then re-upgrade and I still got the same issues.
  8. Thanks, just read through all of it and I think I covered all of the cleanup (and then some) in the process of troubleshooting this issue. Still no luck. At this point I am not sure what else do.
  9. no luck - same issue in safe mode with all plugins disabled.
  10. Trying that now... even though there is no /boot/packages/ folder anyways
  11. Tried safe mode early on and it didn't make any difference it seems. How do I properly comment out package installation when going into safe mode?
  12. Deleted with no ill effects... getting closer, but I still get the WebUI error even after letting it create a new libvirt.img. But now the error is in a different place.
  13. Done... but now its auto-creating and pulling something even OLDER from when I had a windows 8.1 VM. Looks like this one is coming from the virtMan plugin... I assume this can be deleted too? (It would be really nice if Fix Common Problems flagged stuff like this) 2019-05-19 19:13:57.288+0000: 13583: info : libvirt version: 5.1.0 2019-05-19 19:13:57.288+0000: 13583: info : hostname: Tower 2019-05-19 19:13:57.288+0000: 13583: error : virStorageFileReportBrokenChain:4829 : Cannot access storage file '/mnt/disk/appdisk/vm/windows81pro/driver_image/virtio-win-0.1-94.iso': No such file or directory 2019-05-19 19:13:57.330+0000: 13583: error : qemuAutostartDomain:252 : internal error: Failed to autostart VM 'windows81pro': Cannot access storage file '/mnt/disk/appdisk/vm/windows81pro/driver_image/virtio-win-0.1-94.iso': No such file or directory 2019-05-19 19:14:08.780+0000: 13570: error : qemuOpenFileAs:3129 : Failed to open file '/mnt/disk/appdisk/vm/windows81pro/os_image/Win81AIO_With_Update-54in1-x64-en-US-Dec2014.iso': No such file or directory 2019-05-19 19:14:08.781+0000: 13572: error : qemuOpenFileAs:3129 : Failed to open file '/mnt/disk/appdisk/vm/windows81pro/driver_image/virtio-win-0.1-94.iso': No such file or directory 2019-05-19 19:14:08.782+0000: 13572: error : qemuOpenFileAs:3129 : Failed to open file '/mnt/disk/appdisk/vm/windows81pro/windows81pro.qcow2': No such file or directory
  14. I think I may have found the cuprit... I noticed this in the dynamix.kvm.manager plugin. Is this an old img file that is being restored automatically perhaps? I cracked open the domain.img directly and I do see references to those old paths that are no longer used. Is this plugin deprecated? Should I just remove it from the plugins folder? I see another one called dynamix.vm.manager but theres nothing in it.
  15. Also I see a similar issue here, but there was no resolution or explanation for the phantom XML being included immediately when the libvirt.img is created.