Hello ,
Channel is latest and Current version: 5.95.0 - XOA build: 20240401
I red but couldn't see some feature like extend k8s cluster , upgrade or something.
I was expected that after creation k8s cluster it will appear under recipes and i will manage it.
Also like Hub also K8s installed on Debian 11
And LINBIT
released the Kubernetes CSI plugin for LINSTOR, then if we use XOSTOR K8s installation support this CSI ?
Regards
VM
Hello ,
We couldn't understand hot add feature for ram and vcpu.
if we have 4 vcpu and if os support i can reduce and re-adjust it to 4 vcpu again but if i want 6 cpu then i couldn't, need restart.
To have this feature run properly for our customers we will set max cpu and set min or like that to customer can increase it later ?
Also dmc, we set max 64 but 32 gb min, server have 56 Gb free memory.
When we started VM expected it consume 32 and if need more and place to grow increase but it allocate 53 gb of ram
Thanks for help
Regards
VM
@Danp Did you have different recommendation for 2019 ? Because also 2019 still used by our customers ....
Hi , We are installing windows 2022 and want to install management tool and pv drivers.
Documentations said that XenServer or Xen-ng ones could be used ...
When i check https://github.com/xcp-ng/win-pv-drivers/releases/tag/v8.2.2.200-RC1 its quite old ....
When check XenServer web page https://www.xenserver.com/downloads its younger then Xen-ng ...
XenServer VM Tools for Windows 9.3.2 --> November 27, 2023
Which one is the best ?
Xen-ng stop development agent for Windows ?
Could you pls show the way ?
Regards
VM
@nikade yes same, they are running on same broadcast domain
@nikade No storage migration , they are all sit in shared storage
increasing memory of Dom0 did not effect ...
increasing vCPU of Dom0 did not effect (actually not all vcpu already used for it but i just want to try )
I run stress*ng for load vms memory but did not effect
No pinning or numa config need because single cpu and shared L3 cache for all cores
Also MTU size is not effecting its working same with 1500 and 9000 MTU
I saw and change tcp_limit_output_bytes but did not help me
Only what effect is changing the hardware
My Intel servers are Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz --> 0.9 Gbit/s per migration
My AMD servers are AMD EPYC 7502P 32-Core Processor --> 1.76 Gbit/s per migration
Do you have any advise ?
@nikade @tjkreidl
increasing memory of Dom0 did not effect ...
increasing vCPU of Dom0 did not effect (actually not all vcpu already used for it but i just want to try )
I run stress*ng for load vms memory but did not effect
No pinning or numa config need because single cpu and shared L3 cache for all cores
Also MTU size is not effecting its working same with 1500 and 9000 MTU
I saw and change tcp_limit_output_bytes but did not help me
Only what effect is changing the hardware
My Intel servers are Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz --> 0.9 Gbit/s per migration
My AMD servers are AMD EPYC 7502P 32-Core Processor --> 1.76 Gbit/s per migration
Do you have any advise ?
@Danp No of course i can disable it , okay i will not struggle with it
After disable HA , i could delete it , thanks
@Danp if this is the rule , what i can say.
I will try one thing more because to create xostore step by step I shutdown servers and add disks after that i could delete the network