@cmanos No problem, glad I could helped.
As Olivier also pointed above, it's not an issue anymore when using QCOW2 which is currently in beta, so hopefully it's only a short workaround
Yes, they are created either:
on demand for users
when we need in XO 6
Now, XO 6 is becoming the main driver for new endpoint as the UI is providing more and more features.
@carloum70 Disk migration isn't supported by the provider yet. What you can do it's only ignore the changes to the sr_id of a given disk.
For example for the first disk:
lifecycle {
ignore_changes = [
disk[0].sr_id
]
}
You can also manually do the migration in XO and then after edit your HCL to update the sr_id with the new ID. It should do the trick.
Not enough space means not enough space to coalesce, and therefore XO will prevent to continue and fill entirely your storage because of uncoalesced chains.
@tonyp90 I did file a feature suggestion, https://github.com/vatesfr/xen-orchestra/issues/4273 , but not a bug report.
I'm using the xsconsole on the xcp-ng server itself in the few cases where I need to re-attach an SR.
gitterdude created this issue in vatesfr/xen-orchestra
closed
Reattach SR icon is non-obvious
#4273
@olivierlambert Hah, indeed it was! CIFS is totally unstable, but I was able to get NFS working with these configs:
mount -o vers=3,soft,mountproto=tcp [IP]:/share /mnt/nfs_share/backup.xva
@d1rtym0nk3y Thanks for the feedback! This is actually something that we had in mind. It will probably have to wait for the next major version of XO, though.
It's because it's a fake, edited to show how we would like to have it
If you need that, please open an issue in XO bugtracker, only after checking there isn't an existing same request
@dreday said in Cannot see virtual Machine consoles...:
@FPIT I would say to further troubleshoot the limited connectivity issues first...
A few things that jump to mind right away
Does the host have a network gateway address set for the management interface?
Are there any firewalls or switch port ACLs blocking traffic?
This one is the least likely culprit
3) Is you host management configured to use DHCP?(based on the blank console, though it would not explain the connectivity issues unless DHCP is not providing all necessary information for the network)
Option number 3 worked for me. I had initially configured my management console (with public IP) to use DHCP and the other port (with local IP) to use static. When I did reset all connections to use DHCP the consoles came up. Thank you thank you thank you! @DreDay and of course thanks @FPIT for raising the issue. #one
@olivierlambert
Thank you again for the answer!
I was not using the right search criteria to find this part myself
Changed the 'config.toml' file after searching my system (not an XOA but XO CE, so it was in another location then mentioned in the documentation)
Restarted and just as expected the GUI was only available on the specified IP
We are focusing first on getting something correctly integrated from XOA, it doesn't mean it will be exclusive to XOA.
It's just we are first focusing on a completely "known" environment (XOA), but I think at some point we'll be able to provide manual setup for people who want to do it from the sources
@julien-f Backup files check found no problems, so I tried to restore again and it works. No changes or updates in XO, no changes on vhd or json files (same dates and sizes). Only think I did was detach and attach backup repository (settings - remotes) which I tried before with no luck.
In theory, static min is bundled in the template and you shouldn't use less than that. If you still want to do it, consider it as "advanced", and do it with xe
@olivierlambert Dont know why the screenshots were not loading, posting that again
With no snapshots and coalesce completed, very very little space used.
[image: 1606962162989-captura-de-pantalla-233.png]
