@dinhngtu Thanks for your help.
I solved to install XS Tools uninstalling old XS version 9.0, running XenClean and installing version 9.4.
Also Disk stats now are correct.
Now I get these good performances:
@dinhngtu Thanks for your help.
I solved to install XS Tools uninstalling old XS version 9.0, running XenClean and installing version 9.4.
Also Disk stats now are correct.
Now I get these good performances:
@dinhngtu
In device manager disks are reported as "QEMU NVMe Ctrl".
Now i discover "Citrix Hypervisor PV Tools 9.0.42" are already installed (in App & Features), but in XOA i see "No Xen tools detected".
Should i try to uninstall "Citrix Hypervisor PV Tools 9.0.42" and install 9.4.0 version?
On my xcp-ng 8.3 hosts I've an old Windows server 2019 VM without guest tools installed (Virtualizzation mode is HVM).
Tried to install citrix tools 9.3.3 and 9.4.0 (drivers + management agent).
After tools setup and reboot the VM does not start anymore (stay indefinitely on rotating dots screen).
Am I missing or doing wrong something?
For your knowledge, this VM has also strange "Disk throughput" stats with negative values (all other VMs on the host are ok). I don't know why...
Thanks
Is there an ETA for fully functional deploy (on local storage) with differential backup, live migration, statistics and so on?
Perhaps with 8.3 stable release?
I'm interested mainly because of bit rotting detection of ZFS.
@michael-manley Hi Michael, have you any plan to release a new version working with latest xcp-ng 8.3?
@MathieuRA said in XO - enable PCI devices for pass-through - should it work already or not yet?:
So the error is "normal".
XOA tries to evacuate your host before restarting it, but your host's VMs have "nowhere to go" since you don't have another host.
Are you using XO from sources?
IMHO If there isn't a host where to evacuate the running VMs, the reboot procedure should simply notify the user and shutdown the VMs.
Why a disk/SR/VDI performance graph is not available on stats page for host/VM?
Thanks
I've done some benchmarks with my new servers and want to share results with you.
Server:
fio parameters common to all tests:
--direct=1 --rw=randwrite --filename=/mnt/md0/test.io --size=50G --ioengine=libaio --iodepth=64 --time_based --numjobs=4 --bs=32K --runtime=60 --eta-newline=10
VM Debian: 4 vCPU, 4 GB Memory, tools installed
VM Windows: 2/4 vCPU, 4 GB Memory, tools installed
Results:
Considerations:
I suppose i can install new servers with xcp-ng-8.3.0-beta2-test3.iso and then update to rc/stable release with yum update.
Am i correct?
Regards
Paolo
My new servers will be available in the next week. The full specs are:
Planned setup (KISS):
Questions / your opinion about:
Thanks
Tanks a lot @olivierlambert and @planedrop for your answers.
IMHO with NVMe (PCIe devices) RAID1 / RAID10 configuration the mdadm overhead on the CPU should be negligible, and also reliability should be very good.
Anyway I'll investigate the cost of hardware RAID controller.
I'm planning to buy new servers with NVMe (U.2) based local SR (and install xcp-ng 8.3).
I've some questions:
Thanks
Hi Olivier,
The host is a single host (no other hosts in the pool) with local storage (EXT) only.
I've done some other tests:
Tried to detach disks, re-create VM, re-attach disks: no success
the VM starts if memory is reduced from 16GB to 10GB
I've created a new VM (W2019 template) and the behaviour is the same: with 16GB memory the error is "not enought memory"; with 10GB the VM starts
Starting one of the 10GB memory VM, no other VM can be started (also with only 1 GB memory)
It's like the host has lost 15GB of free memory...
SOLVED: Restarting Toolstack the problem is solved: now i can start 16GB VM and another 9GB VM to use all available memory (25,5 GB).
I'd be curious to know what happened...
[11:40 host1 ~]# xe host-list params=memory-free
memory-free ( RO) : 27513360384
[11:40 host1 ~]# xe vm-compute-maximum-memory uuid=bc3a1a8e-1e64-fd0b-ecc8-ae8e1bd7a6e0 total=`xe host-list params=memory-free --minimal`
27292336128
Thanks for your help...
& Merry Christmas to all XCP-ng community!
@olivierlambert Also from command line the VM cannot be started:
[17:50 host1 ~]# xe vm-start uuid=bc3a1a8e-1e64-fd0b-ecc8-ae8e1bd7a6e0
There are no suitable hosts to start this VM on.
The following table provides per-host reasons for why the VM could not be started:
host1 : Cannot start here [Not enough free memory]
There were no servers available to complete the specified operation.
xcp-ng 8.2
host server total memory: 64 GB
host server available memory: 25.5 GB
Already running VMs: 7
Dom0 memory: 8 GB
Dom0 top info:
KiB Mem : 8110196 total, 5590192 free, 550848 used, 1969156 buff/cache
KiB Swap: 1048572 total, 1048572 free, 0 used. 7355948 avail Mem
VM memory parameters
[11:50 host1 ~]# xe vm-param-list uuid=bc3a1a8e-1e64-fd0b-ecc8-ae8e1bd7a6e0 | grep " memory-"
memory-actual ( RO): 0
memory-target ( RO): 0
memory-overhead ( RO): 140509184
memory-static-max ( RW): 17179869184
memory-dynamic-max ( RW): 17179869184
memory-dynamic-min ( RW): 17179869184
memory-static-min ( RW): 1073741824
When starting this VM with 16GB RAM (fixed) using with XCP-ng Center the following error is displayed:
"not enough server memory is available to perform this operation"
When starting the same VM with XOA the error is NO_HOSTS_AVAILABLE.
I've tried to decrease the VM memory to 8 GB but the error persists.
I think there is a lot of available memory...
What i should check?
Thanks.