@TeddyAstie Any idea how to debug this? I'd hoped that enabling VM console output with the following might help: xenstore-write /local/logconsole/@ /tmp/console.%d.log With the xl toolstack and pvshim, you see the shim xen kernel start on the VM serial console before handing over to the PV domU kernel. In XCP-ng, there is no output.

@AtaxyaNetwork I tried the same edits, and I received the same errors btw. After looking at the instructions further, Dell's KVM user guide says there should be two hard drives as part of the VM. First drive is for the OS/Base system, second hard drive is for plugins and any related data. It does say it will boot without the second drive, but basically wont be useable without it. I tried re-doing the instructions but converting the second drive at the same time, and the problem persists. So I think there is a step somewhere after the ko driver install to help it "see" the second drive at all, not really sure how to fix that.

@dinhngtu Hi everyone, Thank you all so much for your help and suggestions. After several tests, I’ve decided to stop troubleshooting and stick with Windows 10 in BIOS mode. UEFI doesn’t work properly for me, whether with Windows 10 or 11, but everything runs fine in BIOS mode. I really appreciate the time and support from this great community!

Looking through the kern.log files I found stuff I thought might be interesting but as I scroll, I see it happening a lot so I then wonder if it's normal. I see sets of three events: Out of memory: Kill process ### Killed process ### oom_reaper: reaped process ### I wonder if it was starving for memory and having to kill off processes to survive then eventually died. I see these 90+ times in one log file and over 200 times in another. Don't know if this is just normal activity or indication of a problem.

@gduperrey I thought I had. I was replying to that thread and the forum software prompted me to click to reload. It continued to show the contents of the thread above as I clicked to post my reply, so if it opened a new thread, I count that as a bug in the forum, not user error

@Denson After enabling HA, the host has to be manually rebooted, which I think you're already aware of. OK, well, that leaves pretty much a network issue. Hmm. The statefile created OK on the shared SR within the pool? The "not found" error message doesn't give you much to go on, unfortunately.

@Andrew, @bvitnik and @DustinB In my tests, I did the following. I did this process twice and it worked. To simulate a hardware failure on the master node, I simply turned it off. If the master pool is down or unresponsive due to a hardware failure, follow these steps to restore operations: Use an SSH client to log in to a slave host in the pool. Run the following command on the slave host to promote it as the new pool master: xe pool-emergency-transition-to-master Confirm the change of the pool master and verify the hosts present in it: xe pool-list xe host-list Even if it is down, the old master node will appear in the listing. Remap the pool in XCP-ng or XO using the IP of the new master node. After resolving the hardware issues on the old master node, start it up. When it finishes booting, it will be recognized as a slave node. In testing, I did not need to run any other commands. However, if the node is not recognized, try typing on it after accessing it via SSH: xe pool-recover-slaves I didn't understand why it worked. It seemed like "magic"!

@bvitnik Thank you -- very useful information!

Confirmed, that works. Thanks!

@nim81 said in Support licensing structure update: but there's no way I can possibly justify the levels of increase being asked here. As Olivier has said, your comparing paying for XOA with no support, to XOA and XCP-ng supported in a package deal. I don't know that the Vates team has specifically cancelled the XOA only package, but that is a bit germane to the conversation. Just use XO from Source, or one of the scripts and move on with your day. If your business grows you can always sign up for support again.

got it @michael.manley . thanks . unchecked that , will monitor and let you know . thanks so much

A powershell SDK? Oh, you just made me a rather happy guy.

@ainsean I am using HPE SN1100Q 16Gb 2P FC HBA

@cds5296 Hi, could you list your hardware specs (server model, CPU model) and post a crashdump?

ok, so I was wrong, the vm boot ! But as you can see I now have a strange space collision, any idea ? [image: 1740412441805-7e80b573-1cc9-4430-b90c-de0b47806ec8-image.png] [image: 1740412567632-e3fb582e-3f25-46b8-a712-f388bab49a80-image.png] when I boot in recovery mode, I can get into linux, so I know it almost work.

It's probably completely unrelated, but feel free to test

@olivierlambert @payback007 @flakpyro I tested my Win11 23H2 setup (on XCP 8.3) and had the same type of problem. Everything was updated and working on 23H2 with XenTools 9.4. Then Windows update ran and downloaded 24H2 and just got stuck after a reboot (windows logo and spinning circle). Force reboot made Win11 revert, so that good. I un-installed the XenTools 9.4 (just from the control panel/uninstall) and then ran windows update again. This time it did update with a few automatic reboots. I then re-installed the XenTools 9.4 and everything is working on Win11 24H2 now. I guess there is some problem between XenTools 9.4 and 24H2 update, not a XCP problem. I did not test the ISO 24H2 update, just the automatic windows update.

@olivierlambert OK. I was guessing something like that. Many thanks for your answer. Best regards, BK