Posts made by stormi

@robert-wild I'm not sure about that. See this comment https://github.com/xcp-ng/xcp/issues/104#issuecomment-449381556

jaroslaw-freus created this issue in xcp-ng/xcp

closed XCP-ng 7.6 /run/lvm/lvmetad.socket: connect failed #104

If the question was about the XCP-ng Center, then we aren't working on it: its maintenance depends entirely on the community.

@tuxen There's no permission that I'm aware of. Maybe github has some rule that requires users to wait for a few hours before they are allowed to make edits. Was there an error message? What do you mean with "was flagged"?

By "without creating an account" I meant that many people already have an account so they don't need to create yet another account to edit the wiki. In your case, since you did not already have a github account, this isn't true.

github's wiki is not my preferred solution, but it's the most straightforward to let people contribute without first creating an account. In my opinion, that wiki is decent enough and what matters most for now is the contents that is present or missing.

I think the main missing piece in current docs is a quickstart guide, as discussed here https://xcp-ng.org/forum/topic/2427/what-to-do-after-install

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 haven't heard of it until now.

Update published: https://xcp-ng.org/blog/2019/12/16/xen-and-intel-microcode-security-updates/

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).

stormi created this issue in xcp-ng/xcp

closed Xen and microcode security update (December 12th) #319

Yes, as long as they are clearly identified as third party videos, I think they would be a useful addition.

Maybe "Releases and support" (with spaces between words... Not everyone is German :P)

Logs from the server showing that error message and several lines before and after may help (after testing in XO).

I have already seen this error message when I was doing live migration tests from older XenServer to recent XCP-ng. Unfortunately I did not keep notes. I think it was related to a bug in the sender (XenServer) that manifested in some cases and that we can't fix on our side as the receiver, but I don't guarantee that my memory is right here. Were the XS 7.0 hosts fully updated?

Thanks, I've updated it. I'm thinking of a better page title because to me release plan is about future releases, not exactly about support.

You can check what amount of CPU usage netdata uses in htop... or in netdata.

Note that netdata runs with a very low priority so in theory the overhead should not slow your important tasks down.

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 of netdata for all hosts into a single interface. See the blog post.

If xcp-ng-xapi-plugins is 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.

Note: the patch only fixes migration for VMs without any network interface. Was that the case for you?

Edit: looks like this patch could be a fix for https://github.com/xcp-ng/xcp/issues/269

elialum created this issue in xcp-ng/xcp

open live migration failed - Xenops_interface.Does_not_exist #269

Did the patch fix migrations that were failing before, for the same VMs? Else we're not sure that the issue you had previously was fixed by it.

Your error message was
Caught Xenops_interface.Xenopsd_error([S(Storage_backend_error);[S(SR_BACKEND_FAILURE_46);[S();S(The VDI is not available [opterr=VDI e3222f55-10ce-4d85-b6a8-a7c81f1a5a1d not detached cleanly]);S()]]])

In the commit message the error message that the patch fixes is:
Caught Xs_protocol.Enoent("directory")

I've built xenopsd with that patch.

You can download the xenopsd and xenopsd-xc packages (both need to be updated) there:

• https://koji.xcp-ng.org/kojifiles/work/tasks/362/10362/xenopsd-0.101.0-2.0.1.xcpng8.0.x86_64.rpm
• https://koji.xcp-ng.org/kojifiles/work/tasks/362/10362/xenopsd-xc-0.101.0-2.0.1.xcpng8.0.x86_64.rpm

I believe a toolstack restart is enough afterwards.