@stevewest15

I believe this issue was resolved when the health check system was changed to detect network connectivity at startup so it did not need to wait for then entire VM to boot. Needs the Xen tools to be installed. I have not had an issue since this change.

@olivierlambert

The server had high memory usage so I expect lots of paging, which could explain the block writes. I've increased the mem and want to see what difference that makes.

@olivierlambert

Results are in...

Four VMs migrated. Three using warm migration and all worked. 4th used straight migration and BSOD but worked after a reboot.

@olivierlambert

Thanks Oliver. We have used GFS with Veeam previously and will be a great addition.

@Danp @DustinB @ph7

This host does not run any VMs, just used for CR

I've increased the dom0 ram to 4GB with no more alarms.

@dinhngtu

Thank you so much. If you want me I'll be at the pub.

@olivierlambert

We have successfully installed using:

rpm -Uvh https://repo.zabbix.com/zabbix/7.0/rhel/7/x86_64/zabbix-release-latest.el7.noarch.rpm
yum install zabbix-agent2 zabbix-agent2-plugin-* --enablerepo=base,updates

@BenjiReis

Worked perfectly. Thanks guys.

@olivierlambert

Thanks Oliver, lots to learn.

p.s. Congrats on the 8.3 launch.

@thomas-dkmt

Our Hyper-V servers have no GUI and the process I use is:

1. RDP to the Hyper-V host
2. Open PowerShell
3. Get a list of the VMs on the host

    Get-VM

4. Stop the VM

    STOP-VM -Name <name of VM>

5. Identify the VM's disk(s) for conversion

    Get-VMHardDiskDrive -VMName <name of VM>

6. Convert the VHDX to VHD (destination file extension sets the type so use ".vhd")

    Convert-VHD -Path <source path> -DestinationPath <destination path> -VHDType Dynamic

To transfer the newly created .vhd files to xcp-ng we use Putty via the cli

@ph7

To automatically update the hosts? I expect, to work, a host reboot would be required however how can this be automated if the host has running VMs?

@Danp @DustinB @ph7

This host does not run any VMs, just used for CR

I've increased the dom0 ram to 4GB with no more alarms.

When I check "Health" in XO everything appears fine but I do see a number of Alarms, problems is I have no idea what they mean. I do not think I have any system performance issues but am sure these should not be ignored.

HST150 is a host for disaster recovery using CR

@olivierlambert

Why did I not do this sooner

I have recently changed our setup to use FreeNAS shared storage for VMs. Now I have shared storage and two hosts I can move running VMs between hosts. This makes it easy to patch & restart a host by moving the VMs off it first.

As opposed to moving the VMs, I could schedule a maint windows and down the VMs then patch and reboot the host. In this scenario, if the host was to fail I expect nothing will be lost as the shared storage is independent. Then I can simple start the VMs on the remaining host, meaning there is no hard link between the host and VM.

Does this sound correct?

@stevewest15

I believe this issue was resolved when the health check system was changed to detect network connectivity at startup so it did not need to wait for then entire VM to boot. Needs the Xen tools to be installed. I have not had an issue since this change.

I have a host with 48 CPUs and 96GB RAM

I understand that the RAM cannot be over allocated to VMs or I get the no hosts available message a startup however I understand CPUs can, so I could allocate all VMs 48 CPUs and they will only utilise what they require. Is this correct and if so is there any reason not to allocate the max CPUs to a VM.

Further to this, if I only allocate the VMs a smaller number of CPUs do they all overlap on the first X CPUs and leave the others unused. i.e. if VM1 has 8 then it will only use the 1st 8 and if VM2 has 4 then it will only use the first 4.

I ask as I currently have multiple VMs using a lesser number of CPUs than the host has however the status only show the first 15 CPUs in use on the host:

@olivierlambert

Here's the new model. We've tried a few combinations and I think with TrueNAS shared storage this will now work well.

For anyone else looking to connect TrueNAS with XCP-NG

https://www.youtube.com/watch?v=mdHmcwWTNWA

In TrueNAS NFS share settings I set this and it now works.