Installation now went well, no issues noted after the reboot.
Will keep an eye on my system and report back if anything unusual is happening
Best posts made by HeMaN
-
RE: XCP-ng 8.2 updates announcements and testing
-
RE: XCP-ng 8.2 updates announcements and testing
@stormi said in Updates announcements and testing:
yum update bugtool-conn-tests kernel xcp-ng-release xcp-ng-release-config xcp-ng-release-presets xcp-python-libs xen-dom0-libs xen-dom0-tools xen-hypervisor xen-libs xen-tools xenserver-status-report --enablerepo=xcp-ng-testing
Updated both host in the pool (xcp-ng 8.2 fully patched), did my usual stuff and found no anomalities.
Looking good for me! -
RE: XCP-ng 8.2 updates announcements and testing
@stormi installed this new kernel as well and rebooted.
Still no regression issues found till now. -
RE: XCP-ng 8.2 updates announcements and testing
@stormi said in Updates announcements and testing:
Have a installation without any of the fixed bugs, but Installed the updates on my system and did the toolstack restart.
No issues to report this far.
-
RE: XCP-ng 8.2 updates announcements and testing
@stormi
I did not test the updates in the test-repository this time because I wanted to test the Rolling Pool Update function from XO. I recently created a pool of 2 hosts.I noticed the patches were available according to XO on the recently installed host, but not on the host I am using already for a longer time (and used to install the test-patches before). This host is also the pool master.
Only after ayum clean all
and ayum update
the updates were visible on the first host and thus the pool.After fixing that, the Rolling Pool Update went very smooth. I like this feature!
-
RE: XCP-ng 8.2 updates announcements and testing
Update done, rebooting went well, will start to monitor for anomalities.
No news after this message means good news[17:16 xenserver-2 ~]# yum update kernel xen-dom0-libs xen-dom0-tools xen-hyperv isor xen-libs xen-tools xenopsd xenopsd-cli xenopsd-xc --enablerepo=xcp-ng-testi ng Loaded plugins: fastestmirror Determining fastest mirrors Excluding mirror: updates.xcp-ng.org * xcp-ng-base: mirrors.xcp-ng.org Excluding mirror: updates.xcp-ng.org * xcp-ng-testing: mirrors.xcp-ng.org Excluding mirror: updates.xcp-ng.org * xcp-ng-updates: mirrors.xcp-ng.org xcp-ng-base/signature | 473 B 00:00 xcp-ng-base/signature | 3.0 kB 00:00 !!! xcp-ng-testing/signature | 473 B 00:00 xcp-ng-testing/signature | 3.0 kB 00:00 !!! xcp-ng-updates/signature | 473 B 00:00 xcp-ng-updates/signature | 3.0 kB 00:00 !!! (1/3): xcp-ng-updates/primary_db | 21 kB 00:00 (2/3): xcp-ng-base/primary_db | 1.2 MB 00:00 (3/3): xcp-ng-testing/primary_db | 47 kB 00:00 Resolving Dependencies --> Running transaction check ---> Package kernel.x86_64 0:4.19.19-7.0.8.1.xcpng8.2 will be updated ---> Package kernel.x86_64 0:4.19.19-7.0.9.1.xcpng8.2 will be an update ---> Package xen-dom0-libs.x86_64 0:4.13.1-9.7.1.xcpng8.2 will be updated ---> Package xen-dom0-libs.x86_64 0:4.13.1-9.8.2.xcpng8.2 will be an update ---> Package xen-dom0-tools.x86_64 0:4.13.1-9.7.1.xcpng8.2 will be updated ---> Package xen-dom0-tools.x86_64 0:4.13.1-9.8.2.xcpng8.2 will be an update ---> Package xen-hypervisor.x86_64 0:4.13.1-9.7.1.xcpng8.2 will be updated ---> Package xen-hypervisor.x86_64 0:4.13.1-9.8.2.xcpng8.2 will be an update ---> Package xen-libs.x86_64 0:4.13.1-9.7.1.xcpng8.2 will be updated ---> Package xen-libs.x86_64 0:4.13.1-9.8.2.xcpng8.2 will be an update ---> Package xen-tools.x86_64 0:4.13.1-9.7.1.xcpng8.2 will be updated ---> Package xen-tools.x86_64 0:4.13.1-9.8.2.xcpng8.2 will be an update ---> Package xenopsd.x86_64 0:0.150.0-1.2.xcpng8.2 will be updated ---> Package xenopsd.x86_64 0:0.150.2-1.1.xcpng8.2 will be an update ---> Package xenopsd-cli.x86_64 0:0.150.0-1.2.xcpng8.2 will be updated ---> Package xenopsd-cli.x86_64 0:0.150.2-1.1.xcpng8.2 will be an update ---> Package xenopsd-xc.x86_64 0:0.150.0-1.2.xcpng8.2 will be updated ---> Package xenopsd-xc.x86_64 0:0.150.2-1.1.xcpng8.2 will be an update --> Finished Dependency Resolution Dependencies Resolved ================================================================================ Package Arch Version Repository Size ================================================================================ Updating: kernel x86_64 4.19.19-7.0.9.1.xcpng8.2 xcp-ng-testing 30 M xen-dom0-libs x86_64 4.13.1-9.8.2.xcpng8.2 xcp-ng-testing 621 k xen-dom0-tools x86_64 4.13.1-9.8.2.xcpng8.2 xcp-ng-testing 2.4 M xen-hypervisor x86_64 4.13.1-9.8.2.xcpng8.2 xcp-ng-testing 2.3 M xen-libs x86_64 4.13.1-9.8.2.xcpng8.2 xcp-ng-testing 36 k xen-tools x86_64 4.13.1-9.8.2.xcpng8.2 xcp-ng-testing 29 k xenopsd x86_64 0.150.2-1.1.xcpng8.2 xcp-ng-testing 74 k xenopsd-cli x86_64 0.150.2-1.1.xcpng8.2 xcp-ng-testing 1.3 M xenopsd-xc x86_64 0.150.2-1.1.xcpng8.2 xcp-ng-testing 3.9 M Transaction Summary ================================================================================ Upgrade 9 Packages Total download size: 40 M Is this ok [y/d/N]: y Downloading packages: Delta RPMs disabled because /usr/bin/applydeltarpm not installed. (1/9): xen-dom0-libs-4.13.1-9.8.2.xcpng8.2.x86_64.rpm | 621 kB 00:00:00 (2/9): kernel-4.19.19-7.0.9.1.xcpng8.2.x86_64.rpm | 30 MB 00:00:01 (3/9): xen-hypervisor-4.13.1-9.8.2.xcpng8.2.x86_64.rpm | 2.3 MB 00:00:00 (4/9): xen-libs-4.13.1-9.8.2.xcpng8.2.x86_64.rpm | 36 kB 00:00:00 (5/9): xen-tools-4.13.1-9.8.2.xcpng8.2.x86_64.rpm | 29 kB 00:00:00 (6/9): xenopsd-0.150.2-1.1.xcpng8.2.x86_64.rpm | 74 kB 00:00:00 (7/9): xenopsd-cli-0.150.2-1.1.xcpng8.2.x86_64.rpm | 1.3 MB 00:00:00 (8/9): xen-dom0-tools-4.13.1-9.8.2.xcpng8.2.x86_64.rpm | 2.4 MB 00:00:02 (9/9): xenopsd-xc-0.150.2-1.1.xcpng8.2.x86_64.rpm | 3.9 MB 00:00:03 ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Total 6.9 MB/s | 40 MB 00:00:05 Running transaction check Running transaction test Transaction test succeeded Running transaction Updating : xen-hypervisor-4.13.1-9.8.2.xcpng8.2.x86_64 1/18 Updating : xen-dom0-libs-4.13.1-9.8.2.xcpng8.2.x86_64 2/18 Updating : xen-libs-4.13.1-9.8.2.xcpng8.2.x86_64 3/18 Updating : xen-tools-4.13.1-9.8.2.xcpng8.2.x86_64 4/18 Updating : xen-dom0-tools-4.13.1-9.8.2.xcpng8.2.x86_64 5/18 Updating : xenopsd-0.150.2-1.1.xcpng8.2.x86_64 6/18 Updating : xenopsd-cli-0.150.2-1.1.xcpng8.2.x86_64 7/18 Updating : xenopsd-xc-0.150.2-1.1.xcpng8.2.x86_64 8/18 Updating : kernel-4.19.19-7.0.9.1.xcpng8.2.x86_64 9/18 Cleanup : xenopsd-xc-0.150.0-1.2.xcpng8.2.x86_64 10/18 Cleanup : xenopsd-cli-0.150.0-1.2.xcpng8.2.x86_64 11/18 Cleanup : xenopsd-0.150.0-1.2.xcpng8.2.x86_64 12/18 Cleanup : kernel-4.19.19-7.0.8.1.xcpng8.2.x86_64 13/18 Cleanup : xen-dom0-tools-4.13.1-9.7.1.xcpng8.2.x86_64 14/18 Cleanup : xen-tools-4.13.1-9.7.1.xcpng8.2.x86_64 15/18 Cleanup : xen-dom0-libs-4.13.1-9.7.1.xcpng8.2.x86_64 16/18 Cleanup : xen-libs-4.13.1-9.7.1.xcpng8.2.x86_64 17/18 Cleanup : xen-hypervisor-4.13.1-9.7.1.xcpng8.2.x86_64 18/18 Verifying : kernel-4.19.19-7.0.9.1.xcpng8.2.x86_64 1/18 Verifying : xen-libs-4.13.1-9.8.2.xcpng8.2.x86_64 2/18 Verifying : xen-dom0-tools-4.13.1-9.8.2.xcpng8.2.x86_64 3/18 Verifying : xenopsd-0.150.2-1.1.xcpng8.2.x86_64 4/18 Verifying : xen-tools-4.13.1-9.8.2.xcpng8.2.x86_64 5/18 Verifying : xen-hypervisor-4.13.1-9.8.2.xcpng8.2.x86_64 6/18 Verifying : xen-dom0-libs-4.13.1-9.8.2.xcpng8.2.x86_64 7/18 Verifying : xenopsd-cli-0.150.2-1.1.xcpng8.2.x86_64 8/18 Verifying : xenopsd-xc-0.150.2-1.1.xcpng8.2.x86_64 9/18 Verifying : xen-hypervisor-4.13.1-9.7.1.xcpng8.2.x86_64 10/18 Verifying : xen-dom0-libs-4.13.1-9.7.1.xcpng8.2.x86_64 11/18 Verifying : xenopsd-xc-0.150.0-1.2.xcpng8.2.x86_64 12/18 Verifying : xen-tools-4.13.1-9.7.1.xcpng8.2.x86_64 13/18 Verifying : xenopsd-cli-0.150.0-1.2.xcpng8.2.x86_64 14/18 Verifying : xen-libs-4.13.1-9.7.1.xcpng8.2.x86_64 15/18 Verifying : xen-dom0-tools-4.13.1-9.7.1.xcpng8.2.x86_64 16/18 Verifying : kernel-4.19.19-7.0.8.1.xcpng8.2.x86_64 17/18 Verifying : xenopsd-0.150.0-1.2.xcpng8.2.x86_64 18/18 Updated: kernel.x86_64 0:4.19.19-7.0.9.1.xcpng8.2 xen-dom0-libs.x86_64 0:4.13.1-9.8.2.xcpng8.2 xen-dom0-tools.x86_64 0:4.13.1-9.8.2.xcpng8.2 xen-hypervisor.x86_64 0:4.13.1-9.8.2.xcpng8.2 xen-libs.x86_64 0:4.13.1-9.8.2.xcpng8.2 xen-tools.x86_64 0:4.13.1-9.8.2.xcpng8.2 xenopsd.x86_64 0:0.150.2-1.1.xcpng8.2 xenopsd-cli.x86_64 0:0.150.2-1.1.xcpng8.2 xenopsd-xc.x86_64 0:0.150.2-1.1.xcpng8.2 Complete!
-
RE: XCP-ng 8.2 updates announcements and testing
@stormi
Did the update and a reboot just minutes ago.
Dell R710 / dual xeon L5640 / 96GB
XCP-ng 8.1 with latest patches / pool with a single hostSystem is working as expected so far.
If I notice anything during usage I will report back here[20:41 xenserver ~]# yum update Loaded plugins: fastestmirror Determining fastest mirrors Excluding mirror: updates.xcp-ng.org * xcp-ng-base: mirrors.xcp-ng.org Excluding mirror: updates.xcp-ng.org * xcp-ng-updates: mirrors.xcp-ng.org dell-system-update_dependent | 2.3 kB 00:00 dell-system-update_independent | 2.3 kB 00:00 xcp-ng-base/signature | 473 B 00:00 xcp-ng-base/signature | 3.0 kB 00:00 !!! xcp-ng-updates/signature | 473 B 00:00 xcp-ng-updates/signature | 3.0 kB 00:00 !!! No packages marked for update [20:42 xenserver ~]# yum update xen-dom0-libs xen-dom0-tools xen-hypervisor xen-libs xen-tools --enablerepo=xcp-ng-testing Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile Excluding mirror: updates.xcp-ng.org * xcp-ng-base: mirrors.xcp-ng.org Excluding mirror: updates.xcp-ng.org * xcp-ng-testing: mirrors.xcp-ng.org Excluding mirror: updates.xcp-ng.org * xcp-ng-updates: mirrors.xcp-ng.org xcp-ng-testing/signature | 473 B 00:00 xcp-ng-testing/signature | 3.0 kB 00:00 !!! xcp-ng-testing/primary_db | 31 kB 00:00 Resolving Dependencies --> Running transaction check ---> Package xen-dom0-libs.x86_64 0:4.13.0-8.5.1.xcpng8.1 will be updated ---> Package xen-dom0-libs.x86_64 0:4.13.0-8.6.1.xcpng8.1 will be an update ---> Package xen-dom0-tools.x86_64 0:4.13.0-8.5.1.xcpng8.1 will be updated ---> Package xen-dom0-tools.x86_64 0:4.13.0-8.6.1.xcpng8.1 will be an update ---> Package xen-hypervisor.x86_64 0:4.13.0-8.5.1.xcpng8.1 will be updated ---> Package xen-hypervisor.x86_64 0:4.13.0-8.6.1.xcpng8.1 will be an update ---> Package xen-libs.x86_64 0:4.13.0-8.5.1.xcpng8.1 will be updated ---> Package xen-libs.x86_64 0:4.13.0-8.6.1.xcpng8.1 will be an update ---> Package xen-tools.x86_64 0:4.13.0-8.5.1.xcpng8.1 will be updated ---> Package xen-tools.x86_64 0:4.13.0-8.6.1.xcpng8.1 will be an update --> Finished Dependency Resolution Dependencies Resolved ================================================================================ Package Arch Version Repository Size ================================================================================ Updating: xen-dom0-libs x86_64 4.13.0-8.6.1.xcpng8.1 xcp-ng-testing 618 k xen-dom0-tools x86_64 4.13.0-8.6.1.xcpng8.1 xcp-ng-testing 1.7 M xen-hypervisor x86_64 4.13.0-8.6.1.xcpng8.1 xcp-ng-testing 2.3 M xen-libs x86_64 4.13.0-8.6.1.xcpng8.1 xcp-ng-testing 35 k xen-tools x86_64 4.13.0-8.6.1.xcpng8.1 xcp-ng-testing 26 k Transaction Summary ================================================================================ Upgrade 5 Packages Total download size: 4.7 M Is this ok [y/d/N]: y Downloading packages: Delta RPMs disabled because /usr/bin/applydeltarpm not installed. (1/5): xen-dom0-libs-4.13.0-8.6.1.xcpng8.1.x86_64.rpm | 618 kB 00:00 (2/5): xen-dom0-tools-4.13.0-8.6.1.xcpng8.1.x86_64.rpm | 1.7 MB 00:00 (3/5): xen-libs-4.13.0-8.6.1.xcpng8.1.x86_64.rpm | 35 kB 00:00 (4/5): xen-tools-4.13.0-8.6.1.xcpng8.1.x86_64.rpm | 26 kB 00:00 (5/5): xen-hypervisor-4.13.0-8.6.1.xcpng8.1.x86_64.rpm | 2.3 MB 00:01 -------------------------------------------------------------------------------- Total 3.1 MB/s | 4.7 MB 00:01 Running transaction check Running transaction test Transaction test succeeded Running transaction Updating : xen-hypervisor-4.13.0-8.6.1.xcpng8.1.x86_64 1/10 Updating : xen-libs-4.13.0-8.6.1.xcpng8.1.x86_64 2/10 Updating : xen-dom0-libs-4.13.0-8.6.1.xcpng8.1.x86_64 3/10 Updating : xen-tools-4.13.0-8.6.1.xcpng8.1.x86_64 4/10 Updating : xen-dom0-tools-4.13.0-8.6.1.xcpng8.1.x86_64 5/10 Cleanup : xen-dom0-tools-4.13.0-8.5.1.xcpng8.1.x86_64 6/10 Cleanup : xen-tools-4.13.0-8.5.1.xcpng8.1.x86_64 7/10 Cleanup : xen-libs-4.13.0-8.5.1.xcpng8.1.x86_64 8/10 Cleanup : xen-dom0-libs-4.13.0-8.5.1.xcpng8.1.x86_64 9/10 Cleanup : xen-hypervisor-4.13.0-8.5.1.xcpng8.1.x86_64 10/10 Verifying : xen-dom0-libs-4.13.0-8.6.1.xcpng8.1.x86_64 1/10 Verifying : xen-libs-4.13.0-8.6.1.xcpng8.1.x86_64 2/10 Verifying : xen-tools-4.13.0-8.6.1.xcpng8.1.x86_64 3/10 Verifying : xen-hypervisor-4.13.0-8.6.1.xcpng8.1.x86_64 4/10 Verifying : xen-dom0-tools-4.13.0-8.6.1.xcpng8.1.x86_64 5/10 Verifying : xen-dom0-libs-4.13.0-8.5.1.xcpng8.1.x86_64 6/10 Verifying : xen-tools-4.13.0-8.5.1.xcpng8.1.x86_64 7/10 Verifying : xen-dom0-tools-4.13.0-8.5.1.xcpng8.1.x86_64 8/10 Verifying : xen-hypervisor-4.13.0-8.5.1.xcpng8.1.x86_64 9/10 Verifying : xen-libs-4.13.0-8.5.1.xcpng8.1.x86_64 10/10 Updated: xen-dom0-libs.x86_64 0:4.13.0-8.6.1.xcpng8.1 xen-dom0-tools.x86_64 0:4.13.0-8.6.1.xcpng8.1 xen-hypervisor.x86_64 0:4.13.0-8.6.1.xcpng8.1 xen-libs.x86_64 0:4.13.0-8.6.1.xcpng8.1 xen-tools.x86_64 0:4.13.0-8.6.1.xcpng8.1 Complete! [20:42 xenserver ~]# reboot
-
RE: XO Lite: building an embedded UI in XCP-ng
Wget options say
-o logfile,
--output-file=logfile
Log all messages to logfile. The messages are normally reported to standard error.-O file, --output-document=file
The documents are not written to the appropriate files, but all are concatenated together and written to file.So the output of your first wget download was indeed redirected to the xolite.html file you saw in your browser in stead of downloading the file.
The location where you were when you typed the command will have the index.html file that is downloaded as seen in the 'log' file you created
-
RE: XCP-ng 8.2 updates announcements and testing
@stormi
I just installed the updates and have not had any issues this far, will have an eye on the systemfor the next few days and report back if I notice something different.PS you must add
--enablerepo=xcp-ng-testing
to theyum update
command, otherwise it will not install the new packages from the test repo
Latest posts made by HeMaN
-
RE: fatal error while updating XOA (installed from source)
The update of Xen Orchestra from sources (not the same as XOA) is running completely inside the VM and independent of xcp-ng.
If the proces is complaining about missing certificates I would rather suspect the OS of the VM rather than the hypervisor.If you migrate the vm from 8.2 to 8.3 does it also show that error when updating (or use a snapshot)?
-
RE: XO Lite: building an embedded UI in XCP-ng
Wget options say
-o logfile,
--output-file=logfile
Log all messages to logfile. The messages are normally reported to standard error.-O file, --output-document=file
The documents are not written to the appropriate files, but all are concatenated together and written to file.So the output of your first wget download was indeed redirected to the xolite.html file you saw in your browser in stead of downloading the file.
The location where you were when you typed the command will have the index.html file that is downloaded as seen in the 'log' file you created
-
RE: XO Lite: building an embedded UI in XCP-ng
@saneece said in XO Lite: building an embedded UI in XCP-ng:
I've tried to put get this working on both of my hosts but I get the same output when I go to it in Edge and Chrome
Microsoft Edge
Version 121.0.2277.106 (Official build) (64-bit)Google Chrome
Version 121.0.6167.185 (Official Build) (64-bit)Both hosts are on XCP-NG 8.2
Output is of the wget command that should be executed from a shell on the host, but you are talking about edge and chrome.
You did do the wget command in a shell (should save a xolite.html file and not an index.html file) and then with a browser open the xo-lite url on the host it was downloaded on?Otherwise it looks like a typo in the command that made you redirect the screen output of the wget command to a file called xolite.html
-
RE: Google Sign-in stopped working "internal server error" (log attached)
@sluflyer06 if you use it like i do(*), just put a static ip and subnetmask on the storage network adapter and no gateway.
Only put a gateway in the internet connected adapters' network settings
(*) i have a separate vlan for storage with only static ip adresses assigned for that vlan on my hosts and nas, no internet connection, not even dns there.
-
RE: self signed certificate in certificate chain
@techjeff said in self signed certificate in certificate chain:
@stormi @olivierlambert Please see my submitted PR and please provide feedback.
I followed the guides on the site to install my custom certificates (self signed) to my new xcp-ng servers (homelab) and installed the CA cert in XO (from sources).
Came across this post when having issues with deploying self signed certificates and subsequent rrd update errors, and saw there is additional info mentioned in the PR for the Guide section on the website.
Is it correct the PR is not published yet to the website, or am I looking into the wrong places?
-
RE: Remote Backup needs internet to backup, local network. Static ips.
@cookie-eater2000 make sure your Xen Orchestra also has a connection on the 10GB network (IP address on the xo vm)
-
RE: XCP-ng Centre 20.04.01 - VM Autostart on Server Boot not working
@mathiashedberg try, with xo/xoa, toggeling autostart off and then on again for 1 of the vm on the new host so xo will also activate the autostart option at the (new) server if it was not already enabled
-
RE: XO Remote mount.nfs: access denied by server while mounting
@Danp said in XO Remote mount.nfs: access denied by server while mounting:
@daninmanchester said in XO Remote mount.nfs: access denied by server while mounting:
"stderr": "mount.nfs: access denied by server while mounting 192.168.11.60:/Backups",
Would appear to be a rights issue to me.
@tjkreidl verified they can be seen :
Export list for 192.168.11.60:
/export/Backups 192.168.11.0/24
/export/Everyone 192.168.11.0/24
/export 192.168.11.0/24do you need to add "/export" (/export/Backups ) to be able to find the right path?
-
RE: XCP-ng Centre 20.04.01 - VM Autostart on Server Boot not working
@MichaelCropper autostart in xen center is not a bug but a feature
In Xen Center, apart from enabling autostart of a vm you also need to manually (cli) enable the autostart-option on the server.
Xen Orchestra does enable this automatically when not yet enabled on the server when setting autostart for a vm.
-
RE: XCP / XO and Truenas Scale or Core
I have two truenas servers, main server only as a Nas running core and the second server as backup target for main servers' continous replication, cloud backup sync and a little testing and playing around running scale
they work well, and also work fine together.
both are stable and doing their job without issue.
For now the advantage of scale is the slightly better gui display (no more unused nics displayed in dashboard) and maybe more drivers available for more recent or uncommon components.
Core has the advantage of proven functionality and loads of knowledge all over internet