Categories

  • All news regarding Xen and XCP-ng ecosystem

    142 Topics
    4k Posts
    R
    Yesterday, from memory: Up-to-date XO (CE) said there were Pool updates available, but the three individual XCP-ng hosts showed nothing available. I went to https://xcp-ng.org/blog/tag/security/ and did not see any new patches published for January, and I feared that the previous updates from October had somehow not been fully installed. I put hosts into Maintenance Mode and rebooted them, and patches were seemingly installed as part of the reboot. I don't recall if I rebooted (and therefore patched) the Master first or not as you are supposed to do. This was a bit unsettling. As of this morning, Central Time US, for our three-node XS 8.4 Pool also managed by the same XO (CE), I see patches available in XO both at the Pool level and at the Host level as expected. (Yesterday, I did not see any patches reported by XO for our XS 8.4 Pool.)

  • Everything related to the virtualization platform

    1k Topics
    14k Posts
    A
    @florent said in vmware vm migration: @acebmxer yes after the first migration, XO knwo that the migration is incomplete and that you may want to finish it later. But if you start this VM direvtly , it will write some data, thus it won't be in sync anymore with the Vmware snapshot. Then XO won't be able to resume You can start a copy of the VM ( XO will handle it for you ) and delete the copy when you're done My advice is to migrate this VM to the right SR and then do the resume. But keep in mind that the V2V tool is intended to target only one SR, so migrate all they disk to the same SR, and select the right one when resuming the V2V. You can change the network after My previous migration was successful with no issues. Previously test vm was fresh install so no vmtools installed. But I did shut the vm down myself prior to starting the migration. VM boots no issues no prompts. This time I decided to follow the steps listed in the documentation as i have been following the changes and updates for the v2v migration. Following the steps as mention XO presented me with that prompt which was not mention in the documentation. As i was typing the post to gather my information it was then i noticed i did not select the proper destination SR and the appropriate nic/vlan for networking. So I noted that in the post. With the assumption i could correct that on the final migration. With that said the I guess the documentation should state - Start vm to test if boots, etc.. When prompted choose "Start a copy". When done shutdown vm and remove.

  • All Xen Orchestra related questions/reports

    3k Topics
    27k Posts
    G
    @john.c I'd say XO-Lite was minimally viable almost a year ago, you could get real work done bouncing between it and the host console (still in XO-Lite). Both are getting better, it's going to be a journey and I'm warming up to some of the features in XO 6. As to the discussion about the third party scripts, maybe if the official method had a script to make it easier/quicker to install we could all be on the same page. I've used both, and failed many times with the official method (several years ago) and it could be easier for people setting up labs to install it. But maybe that's the idea, make it long and tedious. I'm just going to say that things like the new dashboard have grown on me, but needing to flip back to 5 for some things is a pain. Trying to be patient and truthfully I don't spend a lot of time in my system now. Log in to check backups, do some updates once in a while, etc. My system has become fairly stable. That said, I did recently upgrade my lab, and that will get a ton more use in XO when I get back to some testing I'm doing there. Probably going to wipe out my lab and start over, planning that now. and it may or may not be XCP this time so I can learn the basics of a different system.

  • Our hyperconverged storage solution

    40 Topics
    715 Posts
    I
    @ronan-a Thanks

  • Non-English speakers

    31 Topics
    90 Posts
    olivierlambertO
    Yes, account aren't related