@Cygace Someone from the community may jump in and help troubleshoot this.
The best approach would be to not modify the Dom0 installation by installing Zabbix via a community post, as you're customizing the installation.
The vates team and XCP-ng specifically need to include these packages to ensure you're able to get support.
Best of luck
@Cygace So you're modifying Dom0... is these instructions from the xcp-ng.org website?
@idar21 said in Xen Orchestra 5.110 V2V not working:
unique configurations slip through the cracks,
In all fairness, edge cases are never tested for until you're building solutions for those edge cases.... It is a bit rough to simply throw the entire thing away because you're on an edge case and a tool built for the masses doesn't work on that edge case...
If you really require uptime of XOA, you could use a public cloud like AWS, setup an EKS cluster across 3 AZ's each having a Site to Site VPN and an EC2 instance which provides a connection so you can access the hosts at a given site.
It's an expensive approach, but the only way I can think of that would ensure XOA was running at all times in the event of an individual outage.
@AtaxyaNetwork said in Unbootable VHD backups:
@Schmidty86 Try to detach the disk and reattach, it should be xvda in order to be bootable
That's what I was thinking as well, but obviously something is off with this VM.
@Schmidty86 is the old host still online? If so you might be able to perform a Live Migration or a replication job to copy it from the old host to the new.
@Schmidty86 That disk appears to be a secondary disk, is this just a "data volume" and not a boot volume (looking at XO where it shows xvdb)?
Hrm as to the fact that it still shows it as a misc disk.... I'm at a loss.
said in Unbootable VHD backups:
@Schmidty86 I dont see your disk at all listed, only PXE (network booting) and then the MISC device (which is the questionable item).
The internal Shell isn't relevant to this conversation.
As a side thought, re-enable the DISK under advanced and then reboot into BIOS and see if the disk is listed.
@Schmidty86 I dont see your disk at all listed, only PXE (network booting) and then the MISC device (which is the questionable item).
The internal Shell isn't relevant to this conversation.
@Schmidty86 Try disabling the boot devices under advanced
https://xcp-ng.org/forum/topic/8357/i-cannot-enter-the-vm-boot-menu/2
then you'll have more time to see what the options are to get into BIOS.
It might even be as simple as tapping the Shift Key while the VM starts.... I don't have to do it often enough to commit to memory, but you can definitely get into BIOS on a VM that "isn't posting". You've technically made it past post, and are failing due to a missing boot device.
@Schmidty86 You might need to go into BIOS and check to see if this now missing device is still listed, and disable it if it is.
@Schmidty86 did this VM previously have a USB device that was passed through on your prior host?
@Schmidty86 The VM template that you created to attach these VHD to, is it configured for BIOS or UEFI?
@Vagrantin What kind of hardware is the XCP-ng host running?
@JCS-RVK You likely need to install the dependencies to use with VDDK.
This is a WIP from the vates team where you can find information regarding it here https://github.com/vatesfr/xen-orchestra/pull/8840
My guess, and I'm still sorting it out for my GH is that you likely need to run sudo apt install libnbd-bin nbdkit nbdkit-plugin-vddk on your XOCE installation, but that is just a guess at this time as the VDDK version number is also in flux (going from 9 to version 8 ) etc.
@ccesario There is a running topic regarding the 2TB limit and removing it with QCOW/2 format https://xcp-ng.org/forum/topic/10308/dedicated-thread-removing-the-2tib-limit-with-qcow2-volumes/156
I've not kept up with it as I don't have this issue, but this is very much a work in progress.
@Forza said in NVMe SSD not found when installing:
We have been using software raid1 for years on Intel hardware for industrial focused computers. However since Intel switched to VMD we started to get very odd problems like blue screens (windows) and spontaneous reboots and hard lockups where the raid volume wouldn't come back unless we did full power cycle. After some months we found a reproducer which we sent to our vendor, who in turn were able to reproduce it on different motherboards of different manufacturers with different chipsets supporting VMD. Until today we have not found a fix.
Yeah this doesn't sound any different from every fakeRAID that has ever existed... it's doing all of the work on the motherboard, writing little to disk and hoping for the best.
@olivierlambert said in NVMe SSD not found when installing:
@DustinB Last time I checked, VMD is a shitty half-baked soft/hard RAID.
@Forza said in NVMe SSD not found when installing:
@olivierlambert said in NVMe SSD not found when installing:
@DustinB Last time I checked, VMD is a shitting half-baked soft/hard RAID.
Indeed. The firmware hides pci devices behind this vmd thing. It is absolutely unstable and unfixable.
Good to know, will steer well clear of it.
@TeddyAstie said in NVMe SSD not found when installing:
Hello,
Make sure Intel VMD is disabled (this is the hardware RAID feature of Intel, and it doesn't currently work on XCP-ng; you probably don't need it unless you are looking to make a RAID). We found some modern platforms enabling by default (which also causes issues with Windows).
Is VMD actually hardware raid or is it some bastardization of Hardware Raid?
