-
@stormi Thank you!
I'll be applying and validating the patch. -
@stormi the update actually solves the problem of zombies process, but the coalesce, all disks after backup/snapshot (removal) still continue with a 1 disk stuck in the leaf chain.
I am also testing the update made available in https://support.citrix.com/article/CTX265619 in an XS 7.1 pool.
-
I'm interested in the results because it's the same patch!
-
@stormi The perception I have is as follows in XCP8:
- After backup, all the disks were left with 1 disk frozen in the leaf tree.
- Even pausing the VM and rescanning disk, the coalesce process does not start.
For CH7.1 with the XS71ECU2020 update, the coalesce process completed 100% by pausing the VMs. We will now re-back it up and see if the coalesce runs again 100%.
I used standard times in LIVE_LEAF_COALESCE_TIMEOUT=10.
The new test will be with LIVE_LEAF_COALESCE_TIMEOUT=300. -
@stormi The strange thing is, I had to turn off the VMs, rescan disk and then turn on again.
The coalesce process began with the linked VMs (in production) and successfully completed. The following values have been changed at /opt/xensource/sm/cleanup.py :
LIVE_LEAF_COALESCE_MAX_SIZE = 1024 * 1024 * 1024 # bytes LIVE_LEAF_COALESCE_TIMEOUT = 300 # secondsWell, apparently everything ok... we will see in our next backup if it will be necessary to turn off the VMs for the coalesce to start and complete correctly.
-
@stormi After the informed change, the backup occurred with 100% success, on no disk in the coalesce chain.
We're migrating another cluster to XCP-ng 8!
Thanks for the support, quick return and attention. -
A new update just pushed for XCP-ng 8.0:
xcp-ng-xapi-plugins. It adds a plugin that the latest version of Xen Orchestra (just released) needs in order to offer a new feature: integration ofnetdatafor all hosts into a single interface. See the blog post.If
xcp-ng-xapi-pluginsis the only update available for your hosts, then no need to reboot after installing. A toolstack restart is enough.If you don't need the new feature, you can skip this update until the next batch.
-
New security update candidate for testing in XCP-ng 8.0 and 7.6.
Fixes security issues in Xen. Also provides updated microcode for some Intel
Details and discussion on https://github.com/xcp-ng/xcp/issues/319
Please test (we simply need people to install them and check that they do not see obvious regressions).
-
-
This post is deleted! -
This post is deleted! -
Hi
I've a problem with freezing Windows VMs after applaying latest updates - do You know anything about it? Those vms have guest tools from citrix.
-
I haven't heard of it until now.
-
@akurzawa I also experienced an issue after the update as well. After the host rebooted and I tried turning on a Windows 10 VM it hung on the Windows boot screen.
-
I eventually force rebooted
-
Force shutdown + Change CPU and RAM (not sure if the resource adjustments helped of not)
-
Start VM and it came up in Windows recovery mode
In the windows recovery mode I just exited and it continued the boot process. This time it booted successfully but I was greeted with the below message upon login.
I had to use XCP-ng center to use keyboard shortcuts to select yes on the dialog box as mouse input was not working. After the restart everything is working as usual again.
I also have the Windows Updates based guest tools enabled on this VM.
@stormi I think this has to do with the new version of guest tools Citrix has pushed from their release of CH8.1. Checking the services they now show major version 9. Not sure if @akurzawa is facing the exact same issue or a variant of it?
-
-
This smells like windows pv drivers upgrades. Had similiar effects on various VMs.
-
FYI: https://support.citrix.com/article/CTX235404
"Important: Updating to this version of the driver removes the quiesced snapshots capability of the VM. If you are using quiesced snapshots and wish to retain this functionality, do not adopt these 9.0.0.x drivers."
They do not tell about crashing VMs though
-
Citrix also has a long history of problematic VM guest-tools. Race conditions with broken drivers, unbootable VMs, broken agents... It's a pain in the a**.
If you like your VMs: Always make a snapshot of every VM before updating the tools.Is known why they remove the VSS-functionality? I don't get why they remove features (again).
-
@stormi said in Updates announcements and testing:
FYI: https://support.citrix.com/article/CTX235404
"Important: Updating to this version of the driver removes the quiesced snapshots capability of the VM. If you are using quiesced snapshots and wish to retain this functionality, do not adopt these 9.0.0.x drivers."
They do not tell about crashing VMs though
I read the support article hoping for more details on how to "...retain this functionality, do not adopt these 9.0.0.x drivers." but the article does not mention that either.
I did not opt to install the new guest tools at any point. I only shutdown the VM to complete the host patches.
Also see the image below, unless it installs guest tools through a side channel that does not show in the Windows updates history.
Would simply disabling the "Windows Update tools" advanced option in XOA/XO stop it from adopting the new guest tools?
-
I have pushed an update to the
netdataandnetdata-uipackages.No need to reboot after installing it even if XO tells you so.
It fixes an upstream issue where in some cases the cache size on disk grows indefinitely without respecting the 256M default limit (reproduced only internally but I don't want to take a risk). Only
netdata-uiis concerned. If you are using netdata through XO, then there's no risk for your hosts. Now netdata will only store 1h of data in RAM, nothing on disk. -
I have pushed an updated
bnxt_endriver asbroadcom-bnxt-en-altfor 8.0 and 8.1. It is inxcp-ng-testingfor 8.0. If fixes a very specific issue from what I can see in the code diff, so no need to install it if everything is already OK for you.
