@olivierlambert right, so what is the solution.
Yum update works fine, but I can't install the pool patches yet via Xen Orchestra
G
Latest posts made by gojjily
-
RE: Update XCP NG 8.2 with xen orchestra failedposted in Management
-
RE: Update XCP NG 8.2 with xen orchestra failedposted in Management
Dependencies Resolved =============================================================================================================================== Package Arch Version Repository Size =============================================================================================================================== Updating: forkexecd x86_64 1.18.1-2.1.xcpng8.2 xcp-ng-updates 1.2 M gpumon x86_64 0.18.0-4.3.xcpng8.2 xcp-ng-updates 1.3 M guest-templates-json noarch 1.9.6-1.2.xcpng8.2 xcp-ng-updates 29 k guest-templates-json-data-linux noarch 1.9.6-1.2.xcpng8.2 xcp-ng-updates 19 k guest-templates-json-data-other noarch 1.9.6-1.2.xcpng8.2 xcp-ng-updates 12 k guest-templates-json-data-windows noarch 1.9.6-1.2.xcpng8.2 xcp-ng-updates 14 k kernel x86_64 4.19.19-7.0.15.1.xcpng8.2 xcp-ng-updates 30 M linux-firmware noarch 20190314-8.1.xcpng8.2 xcp-ng-updates 39 M message-switch x86_64 1.23.2-4.1.xcpng8.2 xcp-ng-updates 2.3 M microcode_ctl x86_64 2:2.1-26.xs25.1.xcpng8.2 xcp-ng-updates 6.4 M qemu x86_64 2:4.2.1-4.6.3.1.xcpng8.2 xcp-ng-updates 16 M rrdd-plugins x86_64 1.10.8-5.2.xcpng8.2 xcp-ng-updates 3.8 M sm x86_64 2.30.8-2.1.xcpng8.2 xcp-ng-updates 619 k sm-rawhba x86_64 2.30.8-2.1.xcpng8.2 xcp-ng-updates 32 k sudo x86_64 1.8.23-10.el7_9.3 xcp-ng-updates 843 k varstored-guard x86_64 0.6.2-2.xcpng8.2 xcp-ng-updates 2.2 M xapi-core x86_64 1.249.28-1.2.xcpng8.2 xcp-ng-updates 18 M xapi-tests x86_64 1.249.28-1.2.xcpng8.2 xcp-ng-updates 3.8 M xapi-xe x86_64 1.249.28-1.2.xcpng8.2 xcp-ng-updates 837 k xcp-networkd x86_64 0.56.2-2.xcpng8.2 xcp-ng-updates 3.3 M xcp-ng-release x86_64 8.2.1-9 xcp-ng-updates 104 k xcp-ng-release-config x86_64 8.2.1-9 xcp-ng-updates 108 k xcp-ng-release-presets x86_64 8.2.1-9 xcp-ng-updates 10 k xcp-rrdd x86_64 1.33.2-1.1.xcpng8.2 xcp-ng-updates 1.5 M xen-dom0-libs x86_64 4.13.5-9.35.1.xcpng8.2 xcp-ng-updates 628 k xen-dom0-tools x86_64 4.13.5-9.35.1.xcpng8.2 xcp-ng-updates 2.4 M xen-hypervisor x86_64 4.13.5-9.35.1.xcpng8.2 xcp-ng-updates 2.4 M xen-libs x86_64 4.13.5-9.35.1.xcpng8.2 xcp-ng-updates 39 k xen-tools x86_64 4.13.5-9.35.1.xcpng8.2 xcp-ng-updates 27 k xenopsd x86_64 0.150.14-1.1.xcpng8.2 xcp-ng-updates 79 k xenopsd-cli x86_64 0.150.14-1.1.xcpng8.2 xcp-ng-updates 1.3 M xenopsd-xc x86_64 0.150.14-1.1.xcpng8.2 xcp-ng-updates 4.0 M Transaction Summary =============================================================================================================================== Upgrade 32 Packages Total size: 142 M Total download size: 5.4 M Is this ok [y/d/N]: -
RE: Update XCP NG 8.2 with xen orchestra failedposted in Management
I am having the same issue, and my base repos are not enabled.
How do I resolve this issue? -
RE: Coalesce failed, skipping - corruptedposted in Xen Orchestra
@olivierlambert so I went to restore this VM from backup, and noticed that the monthly backup is currently running on this VM as we speak.
Will restoring from this newest backup fix my issue? Or does it restore the issue back into production?
-
RE: Coalesce failed, skipping - corruptedposted in Xen Orchestra
@olivierlambert I would guess it was a power failure. I had an APC UPS blow up, still working to troubleshoot the UPS issue. APC send a new warranty battery, and now also a new warranty UPS.
-
RE: Coalesce failed, skipping - corruptedposted in Xen Orchestra
right, but what are we saying the options are to fix this?
-
Coalesce failed, skipping - corruptedposted in Xen Orchestra
My Xen orchestra backup is failing for one specific VM with the error below.
How do I fix this?Jul 28 01:28:51 milsrv01 SMGC: [30191] Coalesce candidate: *c5bf9937(350.000G/105.039G) (tree height 6) Jul 28 01:28:51 milsrv01 SMGC: [30191] Coalescing *c5bf9937(350.000G/105.039G) -> *29153ed4(350.000G/214.587G) Jul 28 01:28:51 milsrv01 SMGC: [30191] coalesce: EXCEPTION <class 'util.SMException'>, VHD *c5bf9937(350.000G/105.039G) corrupted Jul 28 01:28:51 milsrv01 SMGC: [30191] File "/opt/xensource/sm/cleanup.py", line 1753, in coalesce Jul 28 01:28:51 milsrv01 SMGC: [30191] self._coalesce(vdi) Jul 28 01:28:51 milsrv01 SMGC: [30191] File "/opt/xensource/sm/cleanup.py", line 1942, in _coalesce Jul 28 01:28:51 milsrv01 SMGC: [30191] vdi._doCoalesce() Jul 28 01:28:51 milsrv01 SMGC: [30191] File "/opt/xensource/sm/cleanup.py", line 764, in _doCoalesce Jul 28 01:28:51 milsrv01 SMGC: [30191] Coalesce failed, skipping -
Best Way to Backup XCP NGposted in Xen Orchestra
Planning to use XOA to create local backups / delta backups of virtual machines. What's the best way to get these remote / offsite?
I want to pull the backups from the remote side so there's no way to access the remote backup from the local network.
Is it a matter of copying the .vhd files to the remote side with whatever preference I have, or is there more stuff we need to use this in case of restoring from backup? I've read about virtual machine meta data. DO we need the .vhd as well as the meta data to restore successfully?
In short, if I make a local backup on a network share, what do I all need to backup to the remote side to successfully restore a VM?