-
-
Doe the netdata update not actually fix the missing network interfaces or virtual drives?
-
@Biggen I am not aware of this problem. Mine (updated) displays the server's 6 physical eth interfaces and 3 more xapi0 ~ xapi2 and 9 physical drives sda to sdi. I still not have multipath configured in the servers.
-
Perhaps it was fixed. The bug report doesn’t show it: https://github.com/xcp-ng/xcp/issues/379
I uninstalled it back in April and haven’t retested.
-
@Biggen The updated netdata packages display the vm's vbds data (in and out), but nothing for the vm's network interfaces. Not even its presence in the vm's domain.
-
@Biggen said in Updates announcements and testing:
Doe the netdata update not actually fix the missing network interfaces or virtual drives?
No, that bug is not fixed yet.
-
Anyone else who could test the netdata update candidate?
-
I have pushed the netdata update to XCP-ng 8.0 and 8.1's update repository.
-
Several update candidates have been available for some time in our testing repositories without me asking for feedback, so here is the request for tests.
XCP-ng 8.0
Update with:
yum update openvswitch xapi-core xapi-doc xapi-tests xapi-xe xcp-networkd --enablerepo=xcp-ng-testingChanges:
- support for backups with RAM in Xen Orchestra
- openflow support in the SDN controller
- dhcp requests now properly send the hostname to the DHCP server
Aim of the tests:
- no regression after installation and reboot
XCP-ng 8.1
Update with:
yum update xapi-core xapi-doc xapi-tests xapi-xe xcp-networkd --enablerepo=xcp-ng-testingChanges:
- fix compatibility with XenDesktop
- openflow support in the SDN controller
- dhcp requests now properly send the hostname to the DHCP server
Aim of the tests:
- no regression after installation and reboot
Counting on you
-
Simple message to bring the topic on top to increase the chances of feedback.
-
Updated a D54250WYK / i5-4250U / 16GB
XCP-ng 8.1 fully patchedSeems to work without unexpected issues, VMs are running fine.
My USB NIC setup / configuration stopped working, but that was somewhat expected.
I will fix this and report back, if I have an idea why it broke.
Works again after another shutdown / start sequence
-
Updated xcp-ng 8.1 fully patched (Dell R710, dual L5640, 92GB).
no regression to report (but I am not using Xendesktop, SDN, and my dhcp already contains hostname) -
IMPORTANT Security updates!
Calling all stations
Please test it with
yum update qemu --enablerepo=xcp-ng-testing.Might be a bad flaw, so earlier people get feedback, faster we can release it
-
@olivierlambert said in Updates announcements and testing:
qemu
Does this require a reboot or toolstack restart?
-
Good question. If I'm reading this correctly:
Once the hotfix has been applied, the affected guest HVM VMs will need to be restarted or migrated to an updated host to make the remediation effective.
In short, fresh
qemu"fixed" process will be respawn at VM creation/reboot, so no need to reboot the host. -
Updated a D54250WYK / i5-4250U / 16GB
XCP-ng 8.1 fully patched including the update candidates from 11 days agoUpdate ran succesfully (no errors).
Rebooted the host just to be sure.
VMs came up with no problem and seem to work as expected (but I realy just fired them up and poked around a bit, so no real testing) -
Thanks a lot!
-
Updated Dell R620 / XCP-ng 8.1. Rebooting all VMs now, but they appear to be coming up just fine.
-
It's live
Thanks for the feedback! -
New security update candidate for the Xen package in XCP-ng!
Prompt feedback needed
So, a new patch of security patches were released for the Xen hypervisor that is at the core of XCP-ng. Updates candidates are available for XCP-ng 8.1 and in the making for XCP-ng 8.0.
What's being fixed
Mostly flaws allowing privileged guest processes may crash the host under certain conditions.
XCP-ng 8.1
- Update with
yum update xen-dom0-libs xen-dom0-tools xen-hypervisor xen-libs xen-tools --enablerepo=xcp-ng-testing - Reboot.
- Check that your host(s) still work (Spoiler: they will).
- Report here
- Receive our gratitude
XCP-ng 8.0
Coming soon
- Update with
