@olivierlambert said in ISO Importing Results in .img Files:
take the name but create an UUID directl
I can try a different connection method I'm currently using.
NFS v4 and DNS names to connect to backend storage.
I can test with a lower NFS version or switch over to ISCSI targets to see if I can replicate it.
@planedrop Good morning,
Thanks for the input I have renamed my ISO's directly, and now I can easily track each iso on my NAS.
Here is what I mean when checking my VMs.
Example:
For my test lab, the display name for XO-CE is XO-CE_urene when creating the VM. However, when viewing the VM on my NAS, the Guid appears:
I was expecting to see (XO-CE_urene) as the .vhd and thought this might be the same thing going on with the ISO files.
I'm still learning the system and don't know what the expected behavior is. 
So far, I'm still learning the product. I have the lab with Xen Orchestra and XOA appliance, and I am testing configurations and stability before loading up my VMS.
I build mini clones of my corporate domain to test AD automation—prototype working demos to automate HRIS and AD for onboarding projects. Firewall SDN testing and staging demo websites to clients as needed.
It is better to play in the lab before modifying production Active Directory
Load testing XOSTOR at the moment, getting pretty good IOPS so far:
Intel
i7-10810U 6 Core / 12 Thread at 1.1 GHz (Turbo up to 4.9 GHz)
The device has a max power consumption of 55W
Im experiencing this behavior up loading iso, one post mentions we can safely rename the iso after import.
Is this the recommended workaround?
Also i notice the same thing is happening with my vms. Can. I simply rename the vm as well?
I just rebuilt my VMware home lab with XO-CE and XCP-NG, and the installation and hardware compatibility have been excellent. Performance is great. Four small industrial machines live inside a small IT closet at my home.
Hosts:
64gb ram
2tb nvme
4tb SSDs
6 2.5gbe nics
Snynology
8 1tb SSDs
Hello,
I have a question regarding importing ISOs into a Shared ISO storage on my Synology.
I've uploaded two test ISOs into my lab, and they import and are viewable in the Xen Orchestra as follows:
windows server 2023.iso
ubuntu-22.04.3-live-server-amd64.iso
However, when I check the Synology ISO share, they appear to be converted .img files and have random file names,
2e9970ef-9d18-4f24-a6ab-af09751583af.img
d96f93ac-abcc-4b9b-b824-52aa7432093b.img
Is this expected behavior? Or am I importing ISO incorrectly?
The .img files work in the Xen Orchestra when creating VMs. However, I'd like the files to be identifiable on my Synology for local administration.
Thanks for the input, I'm going to disable this integration and deploy a similar solution.
Happy new year,
I was able to, figure out the issue, I created two empty .pem files and needed to open port 80 on UFW firewall per the directions above.
/etc/ssl/certs/xo.cert.pem
/etc/ssl/private/xo.key.pem
after restarting services I was able to receive a let's encrypt certificate. However, the certificate appears untrusted, what is the expected outcome, should this certificate be trusted automatically? or do I need to install a certificate chain on my systems?
Apologies for the stupid questions it's my first time working with these technologies.
Hello all, I'm new to xen orchestra and xcp-ng. setting up my first lab, attempting to replace vmware. Any pointers on this would be appreciated.
I've built an ubuntu XO Community edition server, everything seems to be working however when attempting to follow the directions found here: https://github.com/vatesfr/xen-orchestra/blob/master/%40xen-orchestra/mixins/docs/SslCertificate.md?ref=xen-orchestra.com
I don't seem to get a lets encrypt certificate.
here are the relevant config file settings:
redirectToHttps = true
port = 443
autoCert = true
acmeCa = 'zerossl/production'
acmeDomain = 'xo-ce.mydomain.com'
acmeEmail = 'myemail@mydomain.com'
cert = '/etc/ssl/certs/certificate.pem'
key = '/etc/ssl/private/key.pem'
note, do I create empty .pem files? inorder for this to work?