ISO's do not download. Is this a folder permission issue?
srslol opened this issue · comments
Hello. When I add from Updates/Media or Updates/Domains, it stays at a zero percent (0%) download and just spins. I tried doing a direct ISO download from Ubuntu and Centos, but it just spins. I've rebuilt twice now and don't want to do that again. Hoping somebody else has solved this in the past.
I've checked DNS and any networking problems, but no issues. Is there a folder I can just dump ISO's into with a specific permission set?
I just keep getting spinning for hours.
First of all, thank you to use IsardVDI.
From Domains of Updates section you are downloading desktops, not ISOs.
Please, could you see what say the logs?
docker-compose logs and /opt/isard-local/logs/*/*.log
Yeah buddy, the concept is amazing. Attached are the logs. Let me know what you think I should do. I can start over from scratch if necessary.
yeah , I have the same problem , can not download any desktop from IsardVDI .
and I also can not download ISO in media.
is there any news about this issue ?
I find something error in log.
downloads - INFO - download_changes - waiting an hypervisor online to launch downloading actions
so I check the status in admin console , find out that hypervisor is not enabled .
and docker logs of hypervisor
chchang@hqdc039:~/docker/isard$ docker logs isard-hypervisor
Generating selfsigned certs for spice client...
Starting libvirt daemon...
2021-01-07 09:43:12.644+0000: 25: info : libvirt version: 5.9.0
2021-01-07 09:43:12.644+0000: 25: info : hostname: 24c18237e71d
2021-01-07 09:43:12.644+0000: 25: error : virDBusGetSystemBus:108 : internal error: Unable to get DBus system bus connection: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
2021-01-07 09:43:12.644+0000: 25: warning : networkStateInitialize:822 : DBus not available, disabling firewalld support in bridge_network_driver: internal error: Unable to get DBus system bus connection: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
2021-01-07 09:43:12.782+0000: 25: error : qemuProcessQMPLaunch:8593 : internal error: Failed to start QEMU binary /usr/local/bin/qemu-system-x86_64 for probing: libvirt: error : cannot execute binary /usr/local/bin/qemu-system-x86_64: Permission denied
2021-01-07 09:43:12.782+0000: 25: warning : virQEMUCapsLogProbeFailure:4629 : Failed to probe capabilities for /usr/local/bin/qemu-system-x86_64: internal error: Failed to start QEMU binary /usr/local/bin/qemu-system-x86_64 for probing: libvirt: error : cannot execute binary /usr/local/bin/qemu-system-x86_64: Permission denied
2021-01-07 09:43:12.785+0000: 25: error : qemuProcessQMPLaunch:8593 : internal error: Failed to start QEMU binary /usr/local/bin/qemu-system-x86_64 for probing: libvirt: error : cannot execute binary /usr/local/bin/qemu-system-x86_64: Permission denied
2021-01-07 09:43:12.785+0000: 25: warning : virQEMUCapsLogProbeFailure:4629 : Failed to probe capabilities for /usr/local/bin/qemu-system-x86_64: internal error: Failed to start QEMU binary /usr/local/bin/qemu-system-x86_64 for probing: libvirt: error : cannot execute binary /usr/local/bin/qemu-system-x86_64: Permission denied
Activating network: default
Network default started
Network default marked as autostarted
Activating network: private1
Network private1 started
Network private1 marked as autostarted
Activating network: private2
Network private2 started
Network private2 marked as autostarted
Activating network: private3
Network private3 started
Network private3 marked as autostarted
Activating network: private4
Network private4 started
Network private4 marked as autostarted
Activating network: private5
Network private5 started
Network private5 marked as autostarted
Activating network: shared
Network shared started
Network shared marked as autostarted
Checking hypervisor...
[1/1] basic domain start...
2021-01-07 09:43:16.590+0000: 11: error : qemuProcessQMPLaunch:8593 : internal error: Failed to start QEMU binary /usr/local/bin/qemu-system-x86_64 for probing: libvirt: error : cannot execute binary /usr/local/bin/qemu-system-x86_64: Permission denied
2021-01-07 09:43:16.590+0000: 11: warning : virQEMUCapsLogProbeFailure:4629 : Failed to probe capabilities for /usr/local/bin/qemu-system-x86_64: internal error: Failed to start QEMU binary /usr/local/bin/qemu-system-x86_64 for probing: libvirt: error : cannot execute binary /usr/local/bin/qemu-system-x86_64: Permission denied
2021-01-07 09:43:16.593+0000: 11: error : qemuProcessQMPLaunch:8593 : internal error: Failed to start QEMU binary /usr/local/bin/qemu-system-x86_64 for probing: libvirt: error : cannot execute binary /usr/local/bin/qemu-system-x86_64: Permission denied
2021-01-07 09:43:16.593+0000: 11: warning : virQEMUCapsLogProbeFailure:4629 : Failed to probe capabilities for /usr/local/bin/qemu-system-x86_64: internal error: Failed to start QEMU binary /usr/local/bin/qemu-system-x86_64 for probing: libvirt: error : cannot execute binary /usr/local/bin/qemu-system-x86_64: Permission denied
2021-01-07 09:43:16.593+0000: 11: error : virCapabilitiesDomainDataLookupInternal:738 : invalid argument: could not find capabilities for arch=x86_64 domaintype=kvm
error: Failed to create domain from checks/domain.xml
error: invalid argument: could not find capabilities for arch=x86_64 domaintype=kvm
error: failed to get domain 'domain'
Server listening on 0.0.0.0 port 22.
Server listening on :: port 22.
Accepted publickey for root from 172.29.0.14 port 36102 ssh2: RSA SHA256:vq9cf3CqSRmfV5yydz0P00Yocl6OVEt64Mc5wwMWIaI
kex_exchange_identification: Connection closed by remote host
Accepted publickey for root from 172.29.0.14 port 36116 ssh2: RSA SHA256:vq9cf3CqSRmfV5yydz0P00Yocl6OVEt64Mc5wwMWIaI
Accepted publickey for root from 172.29.0.14 port 36118 ssh2: RSA SHA256:vq9cf3CqSRmfV5yydz0P00Yocl6OVEt64Mc5wwMWIaI
Accepted publickey for root from 172.29.0.14 port 36122 ssh2: RSA SHA256:vq9cf3CqSRmfV5yydz0P00Yocl6OVEt64Mc5wwMWIaI
2021-01-07 09:43:19.199+0000: 15: error : qemuProcessQMPLaunch:8593 : internal error: Failed to start QEMU binary /usr/local/bin/qemu-system-x86_64 for probing: libvirt: error : cannot execute binary /usr/local/bin/qemu-system-x86_64: Permission denied
2021-01-07 09:43:19.199+0000: 15: warning : virQEMUCapsLogProbeFailure:4629 : Failed to probe capabilities for /usr/local/bin/qemu-system-x86_64: internal error: Failed to start QEMU binary /usr/local/bin/qemu-system-x86_64 for probing: libvirt: error : cannot execute binary /usr/local/bin/qemu-system-x86_64: Permission denied
2021-01-07 09:43:19.202+0000: 15: error : qemuProcessQMPLaunch:8593 : internal error: Failed to start QEMU binary /usr/local/bin/qemu-system-x86_64 for probing: libvirt: error : cannot execute binary /usr/local/bin/qemu-system-x86_64: Permission denied
2021-01-07 09:43:19.202+0000: 15: warning : virQEMUCapsLogProbeFailure:4629 : Failed to probe capabilities for /usr/local/bin/qemu-system-x86_64: internal error: Failed to start QEMU binary /usr/local/bin/qemu-system-x86_64 for probing: libvirt: error : cannot execute binary /usr/local/bin/qemu-system-x86_64: Permission denied
2021-01-07 09:43:19.202+0000: 15: error : virCapabilitiesDomainDataLookupInternal:738 : invalid argument: could not find capabilities for arch=x86_64 domaintype=qemu
2021-01-07 09:43:19.202+0000: 15: error : virQEMUCapsGetDefaultVersion:1497 : internal error: Cannot find suitable emulator for x86_64
Received disconnect from 172.29.0.14 port 36118:11: disconnected by user
Disconnected from user root 172.29.0.14 port 36118
What could I do now ??
Your host doesn't seem to have virtualization enabled. If it is a bare metal check in BIOS. If it is a virtualized host then check you have nested virtualization enabled.
Other possibility is that you have selinux (redhat/centos/fedora) active or apparmor (debian/ubuntu) blocking at host level.
Also check that you don't have libvirt service running in your host.
@jvinolas thanks for the hint . after stopping libvirtd service
sudo service libvirtd stop
chang@hq39:~/git/webrtc-remote-screen$ sudo service libvirtd stop
Warning: Stopping libvirtd.service, but it can still be activated by:
libvirtd.socket
libvirtd-admin.socket
libvirtd-ro.socket
and remove from apparmor
sudo ln -s /etc/apparmor.d/usr.sbin.libvirtd /etc/apparmor.d/disable/libvirtd
sudo apparmor_parser -R /etc/apparmor.d/disable/usr.sbin.libvirtd
the hypervisor works and start to download ISO files !
maybe it's a good idea to put this issue in FAQ ?
Oh wow. I have it running on ESXi. I'll check the nested virt and selinux settings!!!