On 22/08/2020 18:20, David White via Users wrote: >> You can actually upload directly via scp to the iso domain, just make >> sure to; >> >> chown -v vdsm: >> /path/to/iso/domain/local_iso_domain/0000000-0000-0000-0000-000000/images/11111111-1111-1111-1111-111111111111/uploaded-file.iso > That worked. Thanks. > I was able to get a VM going. > > Unfortunately, I can't seem to get a 2nd ISO recognized to setup a different > VM. > > I have the following structure: > [root@dev1-centos data]# pwd > /data > [root@dev1-centos data]# ls -la > total 0 > drwxr-xr-x. 4 vdsm kvm 31 Aug 19 20:49 . > dr-xr-xr-x. 19 root root 260 Aug 19 20:28 .. > drwxr-xr-x. 3 vdsm kvm 50 Aug 22 13:10 images > drwxr-xr-x. 5 vdsm kvm 124 Aug 22 13:10 iso > > [root@dev1-centos data]# cd iso/ > [root@dev1-centos iso]# ls -la > total 0 > drwxr-xr-x. 5 vdsm kvm 124 Aug 22 13:10 . > drwxr-xr-x. 4 vdsm kvm 31 Aug 19 20:49 .. > drwxr-xr-x. 3 vdsm kvm 20 Aug 22 09:47 0000000-0000-0000-0000-000000 > drwxr-xr-x. 3 vdsm kvm 20 Aug 22 12:57 0000000-0000-0000-0000-000001 when you create the iso domain, it should have created the path for you, 0000-000-00 was just an example path;
for local iso domain, it should be along the lines of; 1. create top level dir and chown to vdsm: in your case "/data/iso" 2. add iso domain in ui 3. when it added the local iso domain it will setup a bunch of subfolders, in the end folder which is 11111-111-111 you can dump all your iso images in that 1x dir... ie, move the iso file "ubuntu-20.04.1-live-server-amd64.iso" into the same dir as "CentOS-8.2.2004-x86_64-minimal.iso" > > The folder ending in 0 has the original ISO I uploaded (a CentOS 8.2 ISO) - > this is working. > The folder ending in 1 has a Ubuntu 20.04 ISO. - this is not working. > > CentOS path to ISO: > /data/iso/0000000-0000-0000-0000-000000/images/11111111-1111-1111-1111-111111111111/CentOS-8.2.2004-x86_64-minimal.iso > Ubuntu path: > /data/iso/0000000-0000-0000-0000-000001/images/11111111-1111-1111-1111-111111111112/ubuntu-20.04.1-live-server-amd64.iso > > At this point, I have no idea why my CentOS ISO is showing up, but my Ubuntu > ISO is not showing up. > > > Second question: > I left, and came back a while later, and have noticed that when I go to > Storage -> Data Centers, that the Data Center I created (named 'Office') > keeps going from Unresponsive to Activated. It keeps going back and forth, > and I'm not sure why. That seems like an issue. check the engine logs > > > Third Question: > When I go to Compute -> Hosts, and go into the host, under Action Items, I > see: "A new version is available. Upgrade." with a link. > > Yet from the console, when I run `yum update`, nothing is available to update. > I already clicked on that Upgrade link once, and allowed the whole host to > reboot... and that Action Item is still there. > That also seems weird. I would also feel a lot more comfortable about > clicking on "Upgrade" if I had more details - what is it upgrading "from" and > what is it upgrading "to"? yum update will only ensure the packages are installed, however this doesn't mean ovirt has run the upgrade, just upgrade through the ui; 1. put host to maint 2. update host this will trigger ansible which; 1. does yum updates 2. updates the ovirt version to match your latest package you can check what the upgrade is doing as there is a one off log file each time you click update. can't remember the path off the top of my head, just look in /var/log/ovirt* > > > Sent with ProtonMail Secure Email. > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > On Saturday, August 22, 2020 9:37 AM, Michael Jones <[email protected]> > wrote: > >> On 22/08/2020 13:58, David White via Users wrote: >> >>> So, what's the point of all-in-one if you cannot upload ISOs and boot VMs >>> off of ISOs? >>> Is there an alternative way to setup a VM in all-in-one, such as boot from >>> PXE or something? >> You can actually upload directly via scp to the iso domain, just make >> sure to; >> >> chown -v vdsm: >> /path/to/iso/domain/local_iso_domain/0000000-0000-0000-0000-000000/images/11111111-1111-1111-1111-111111111111/uploaded-file.iso >> >> the system will still see it and you can attach to vms at boot; >> >> you can also use pxe, i like the "fai" project for this. >> >>> Regardless, the all-in-one setup was just for learning purposes. >>> I may try a different install approach, and try to get the self-hosted >>> engine working. That said, I'm still unclear on the exact differences >>> between the "self-hosted engine" and the standalone Manager. I'll go >>> re-read earlier responses to my questions on that, as well as the glossary >>> of sorts that Didi was so kind to write in your earlier thread on the >>> imageio issue. >> 4.4 all-in-one is still fully functional par the iso upload and >> download, which i was using for backups. >> >> if you were to go CentOS7+4.3 these features fully work no problem in >> all-in-one. >> >> the alternate to all-in-one would be to choose a different host when >> adding to the standalone manager, or you can have hosted engine, where >> the engine is a vm (dependent on some other stuff re: storage/ips) >> >> Kind Regards, >> >> Mike >> >> Users mailing list -- [email protected] >> To unsubscribe send an email to [email protected] >> Privacy Statement: https://www.ovirt.org/privacy-policy.html >> oVirt Code of Conduct: >> https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: >> https://lists.ovirt.org/archives/list/[email protected]/message/ILLRQN4DUZX5NAFRC44QUJEFJKB7HYNT/ > > _______________________________________________ > Users mailing list -- [email protected] > To unsubscribe send an email to [email protected] > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/[email protected]/message/GU4YPRF3AJLZRGJJZYP4AZYOJTSO3RA4/
_______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/N76EGJVK7QLJXHSTBNHZ6MBJO2PBARIE/
