XCP-ng 7.5.0 Release Candidate
-
yum upgrade
on my testbox went ASAP - As Smooth As Possible -
Congratulations to everyone, impressive work!
I didn't expect ZFS and Ceph support so soon, nice! -
@stormi said in XCP-ng 7.5.0 Release Candidate:
wget https://updates.xcp-ng.org/7/xcp-ng-7.5.repo -O /etc/yum.repos.d/xcp-ng-7.5.repo
yum install xcp-ng-deps
yum update
rebootI was expect, to see 'update' message in new xcp-ng-center, after install repo and deps - but is not show anything.
Anyway, command line update works good.
-
my first host with xcp-ng upgraded successful to 7.5 (Intel NUC) without an error.
thanks for the great job ! -
Progress Report UG to xcp-ng v7.5 from xcp-ng v7.41
Method YUMError
Updating : sm-1.18.0-1.31.x86_64 69/147
Starting sm-multipath (via systemctl): [ OK ]
mv: cannot stat ‘/usr/sbin/lvmetad’: No such file or directoryReboot PASS
Installed v7.5 xcp-ng centre PASS
Test Connection NAS PASSImport VM created on V7.71 xcp-ng PASS
Passthrough USB Device USB3 Bus 001 Device 002: ID 1546:01a8 U-Blox AG FAIL
Passthrough USB Device USB2 Bus 001 Device 004: ID 1546:01a8 U-Blox AG FAIL
Passthrough USB Device USB2 Bus 001 Device 003: ID 051d:0002 American Power Conversion Uninterruptible Power Supply PASS
UPS Test apcupsd service not starting/will not start FAIL
Failed to start apcupsd.service: Unit apcupsd.service failed to load: No such file or directory.note Reboot carried out for each USB U-Blox AG test.
note cold start carried out for USB2 U-Blox AG test.
note USB passthru not working for U-Blox AG (not visible in device list in xcp-ng centre)
note USB passthru working for UPS (visible in device list in xcp-ng centre)Aimee
-
Updated and working so far
-
I'm not sure to get everything you wrote here.
mv: cannot stat ‘/usr/sbin/lvmetad’: No such file or directory
is identified and reported to Citrix. It's not XCP-ng specific.- What do you mean by "test connection"?
- Does USB passthrough worked before on 7.4.1?
- What kind of modification did you do on 7.4.1 before updating? was it "vanilla" or you installed/configured some stuff on it?
apcupsd
doesn't sound coming from vanilla XCP-ng
-
@olivierlambert said in XCP-ng 7.5.0 Release Candidate:
I'm not sure to get everything you wrote here.
mv: cannot stat ‘/usr/sbin/lvmetad’: No such file or directory
is identified and reported to Citrix. It's not XCP-ng specific.
Ok- What do you mean by "test connection"?
The hypervisor successfully connected to the NAS, for the purpose of importing a saved VM. The VM started OK. - Does USB passthrough worked before on 7.4.1?
Only showed the UPS usb device, never the U-Blox AG , this is the same situation with 7.5 (Thread USB Passthrough 20 Jun 2018, 14:13)
Both versions show the device U-Blox AG using the lsusb command. - What kind of modification did you do on 7.4.1 before updating? was it "vanilla" or you installed/configured some stuff on it?
Installed apupsd (Thread Apcupsd UPS support 15 Apr 2018, 17:33)
The upgrade appears to have removed the apcupsd daemon, /usr/sbin/apcupsd, but not the service definition
7.5
service apcupsd status
Redirecting to /bin/systemctl status apcupsd.service
● apcupsd.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
7.4
service apcupsd status
● apcupsd.service - SYSV: apcupsd monitors power and takes action if necessary
Loaded: loaded (/etc/rc.d/init.d/apcupsd)
Active: active (running) since Wed 2018-08-01 14:54:22 BST; 3h 49min ago
Docs: man:systemd-sysv-generator(8)
Process: 2199 ExecStart=/etc/rc.d/init.d/apcupsd start (code=exited, status=0/SUCCESS)
CGroup: /system.slice/apcupsd.service
└─2210 /sbin/apcupsd -f /etc/apcupsd/apcupsd.conf
APC : 001,045,1103
DATE : 2018-08-01 18:44:05 +0100
Citrix did not support apcupsd, but Citrix upgrades in the past did not remove it.
apcupsd
doesn't sound coming from vanilla XCP-ng
No, but ups support is essential for safeguarding the system.
Aimee
-
Yeah but Citrix isn't relying on Yum to upgrade
If you want to be "defensive", then upgrade via the ISO on boot, not on a live system
Problably a dependency thing.
-
I do not quite understand your answer, please can you clarify.
The system was clean installed from 7.4, 7.41 to 7.5, all xcp-ng.
The ony addition was the ups yum , as described in my thread.
Are you suggesting that a clean install will- fix the pass through for the Ublox?
- To get ups support I must repeat my extra ups software install,?
unless xcp-ng is going to provide an alternative package for UPS support?
Thanks
Aimee
-
- Nope
- Yes.
-
This thread is having several discussions in parallel. If nobody minds, I'll move them to separate threads soon.
Update: done.
- Update with HA enabled / or not upgrading master first : https://xcp-ng.org/forum/topic/265/issues-when-upgrading-with-ha-enabled
- USB passthrough: https://xcp-ng.org/forum/topic/266/usb-passthrough-test-reports-in-7-5rc1
-
I pushed several update candidates to the RC in the
updates_testing
repository:- vhd-tool fixing two bugs:
- "VDI import seems broken for large VHD files" https://bugs.xenserver.org/browse/XSO-868
- "VDI export fails with VDI I/O error" https://bugs.xenserver.org/browse/XSO-873
- xen security update
To test:
yum update --enablerepo='xcp-ng-updates_testing*'
and reboot.What we need is to make sure they cause no regressions.
Thanks!
- vhd-tool fixing two bugs:
-
@stormi said in XCP-ng 7.5.0 Release Candidate:
yum update --enablerepo='xcp-ng-updates_testing*'
Is this interfering with the ZFS packages or there is no issue to do it? (especially blktap)
-
@olivierlambert No issue to do it.
-
Great!
-
@christianuhlmann said in XCP-ng 7.5.0 Release Candidate:
my first host with xcp-ng upgraded successful to 7.5 (Intel NUC) without an error.
thanks for the great job !second server has also been updated successfully.
the third server I use pci passthroug for 2 DVB cards.
So far that was excellent under 7.4.1.Since upgrading to 7.5 I get the following error if i want to start the vm with the passthroug pci devices:
vm.start { "id": "40bcca30-d07a-db7c-5744-c134a30af5d1" } { "message": "INTERNAL_ERROR(xenopsd internal error: (Failure \"Error from xenguesthelper: Populate on Demand and PCI Passthrough are mutually exclusive\"))", "stack": "XapiError: INTERNAL_ERROR(xenopsd internal error: (Failure \"Error from xenguesthelper: Populate on Demand and PCI Passthrough are mutually exclusive\")) at wrapError (/home/node/xen-orchestra/packages/xen-api/src/index.js:197:9) at /home/node/xen-orchestra/packages/xen-api/src/index.js:1064:18 at run (/home/node/xen-orchestra/node_modules/core-js/modules/es6.promise.js:75:22) at /home/node/xen-orchestra/node_modules/core-js/modules/es6.promise.js:92:30 at flush (/home/node/xen-orchestra/node_modules/core-js/modules/_microtask.js:18:9) at _combinedTickCallback (internal/process/next_tick.js:131:7) at process._tickCallback (internal/process/next_tick.js:180:9)", "code": "INTERNAL_ERROR", "params": [ "xenopsd internal error: (Failure \"Error from xenguesthelper: Populate on Demand and PCI Passthrough are mutually exclusive\")" ], "method": "VM.start" }
all seem ok
# lspci ..... 02:00.0 Multimedia controller: Digital Devices GmbH Octopus DVB Adapter ...... 08:00.0 Multimedia controller: Digital Devices GmbH Cine V7
# xl pci-assignable-list 0000:02:00.0 0000:08:00.0
# xe vm-param-get uuid=40bcca30-d07a-db7c-5744-c134a30af5d1 param-name=other-config pci: 0/0000:02:00.0,0/0000:08:00.0; base_template_name: Debian Stretch 9.0; import_task: OpaqueRef:83a9253c-f3c0-448f-aba6-df5efa2c1c4a; mac_seed: 1113ba83-5709-4ca5-a292-f8b81a047db4; install-methods: cdrom,nfs,http,ftp; linux_template: true
Does anyone have any idea what that might be?
does anyone have an upgrade to 7.5 with pci passthroug on the run?Thanks and Greetings
Christian
-
@christianuhlmann said in XCP-ng 7.5.0 Release Candidate:
Populate on Demand
Do you know what's this? It seems incompatible to have it enable in parallel with PCI Passthrought.
edit: it seems your dynamix min/max and static max aren't set at the same value.
-
Hi
After a bit of googling on populate on demand I realized.
strange that it worked under 7.4.1.if I understood correctly, it is the dynamic ram assign with min / max.
after I entered a fixed size for ram, the start worked fine.
thank you for the great work
Christian
-
I think ballooning + PCI passthrough can cause some crashes, so that's why there is a check to avoid using both at the same time.