@olivierlambert Thanks. I tried that right now, booting with mitigations=off and saw no improvements unfortunately. Before: [09:06 VIRTUAL33 ~]# grep . /sys/devices/system/cpu/vulnerabilities/* /sys/devices/system/cpu/vulnerabilities/itlb_multihit:Not affected /sys/devices/system/cpu/vulnerabilities/l1tf:Not affected /sys/devices/system/cpu/vulnerabilities/mds:Not affected /sys/devices/system/cpu/vulnerabilities/meltdown:Not affected /sys/devices/system/cpu/vulnerabilities/spec_store_bypass:Vulnerable /sys/devices/system/cpu/vulnerabilities/spectre_v1:Mitigation: usercopy/swapgs barriers and __user pointer sanitization /sys/devices/system/cpu/vulnerabilities/spectre_v2:Mitigation: Full AMD retpoline, IBPB: conditional, STIBP: disabled, RSB filling /sys/devices/system/cpu/vulnerabilities/srbds:Not affected /sys/devices/system/cpu/vulnerabilities/tsx_async_abort:Not affected After: [12:18 VIRTUAL33 ~]# grep . /sys/devices/system/cpu/vulnerabilities/* /sys/devices/system/cpu/vulnerabilities/l1tf:Not affected /sys/devices/system/cpu/vulnerabilities/meltdown:Not affected /sys/devices/system/cpu/vulnerabilities/spec_store_bypass:Vulnerable /sys/devices/system/cpu/vulnerabilities/spectre_v1:Mitigation: __user pointer sanitization /sys/devices/system/cpu/vulnerabilities/spectre_v2:Mitigation: Full AMD retpoline, IBPB: conditional, STIBP: disabled, RSB filling

@olivierlambert Just a update, I have moved from the Single Socket Server to the Dell R710 with 128GB of RAM successfully all VMs are working I have also updated to 8.2

@sapcode Found a description here: https://linux.die.net/man/1/xm But no idea why it starts some CPUs in the pause state.... Will do some testing with C states and govenor performance.... STATES The State field lists 6 states for a Xen Domain, and which ones the current Domain is in. r - running      The domain is currently running on a CPU b - blocked     The domain is blocked, and not running or runnable. This can be caused because the domain is waiting on IO (a traditional wait state) or has gone to sleep because there was nothing else for it to do. p - paused       The domain has been paused, usually occurring through the administrator running xm pause. When in a paused state the domain will still consume allocated resources like memory, but will not be eligible for scheduling by the Xen hypervisor. s - shutdown   The guest has requested to be shutdown, rebooted or suspended, and the domain is in the process of being destroyed in response. c - crashed      The domain has crashed, which is always a violent ending. Usually this state can only occur if the domain has been configured not to restart on crash. See xmdomain.cfg for more info. d - dying         The domain is in process of dying, but hasn't completely shutdown or crashed.

Any thoughts on this topic? I noticed that Alpine from XO HUB didn't use irqbalance by default.

This means your XAPI is down for some reasons. Try a xe-toolstack-restart or check the logs as explained in our documentation: https://xcp-ng.org/docs/troubleshooting.html

@jmccoy555 got it. Thank you for being with me during this amazing journey

I am just curious in why this will not work on XCP-NG but will work on Proxmox when installing the drivers on the VM...

@olivierlambert said in Debian 10 cloud-init - VM encryption: You should ask the cloudinit community about this Thank you, I will do

So when you live migrate a VM, Xen will decrease memory dynamically to the minimum. If you didn't plan correctly dynamic min to a value that's OK for your system, you might have memory problems for your operating system (eg if you system can't survive with less than 4GiB RAM and the dynamic min is set to 3GiB, this will cause problems!). So planning is important. There's some edge cases also in migration when you have to tell Xen about memory management when you grow/reduce amount of RAM. But it works generally OK if you took care of dynamic min as I said.

Okay so maybe a typo in the key the first time you entered it

@ddelnano said in Terraform VM Deployment: es running it on the xcp-ng host would work, Hi @ddelnano, Thank you very much for your valuable advice. I will never run any third party application directly in xcp-ng. I meant inside a VM that will run on the xcp-ng hypervisor, like Xen Orchestra is. So, I need to create a VM and set the correct network and then run nmap -sT -P0 -p 443 xo-domain to test the connection. I'll give this a go. Thank you

IIRC, it will be permanent until there's another Grub update that will regenerate the menu. So it's not really permanent and it's better to use XO/CLI/whatever supported client to modify the value.

@danp I am getting this error You attempted an operation on a VM that was not in an appropriate power state at the time; for example, you attempted to start a VM that was already running. The parameters returned are the VM's handle, and the expected and actual VM state at the time of the call. vm: 2fc2b09b-2249-164a-9f60-e408d9c3db82 (Cert test-host_2021-04-07T16:19:20.356Z) expected: running actual: halted the last portion states that I can only do this command on a running vm Edit: I created a new vm using terraform and changed ran the suggested command. The result is that the vm operates normally. The issue now is what is causing this to happen? I don't believe this was an issue for me before. Thanks for your help.

@s-pam I can't look at the dmesg today as I'm home with a cold... I hope you get well soon I did experiment with xl cpupool-numa-split but this did not generate good results for multithreaded workloads. I believe this is because VMs get locked to use only as many cores as there are in each NUMA domain. Indeed, a VM in a pool get locked to use only the cores of the pool and its max amount of VCPU being the number of core in the pool. It is useful if you have the need to isolate completely the VM. You need to be careful when benching these things because the memory allocation of a running VM is not moved but the VCPU will still run on the pinned node. I don't remember exactly if cpu-pool did have a different behavior than simple pinning in that case though. I remember that hard pinning a guest VCPU were not definitely not moving its memory. You could only modify this before booting.

@olivierlambert That is wonderful news. We actually will be closer to a 1.2:1 or 1.1:1 ratio of vCPU's per physical core - our hosts are old beasts, but we don't work them hard. We had some 10 or 12 VMs on one while it was running VMware (DURING our migration, so a it was running more than it normally did) and it was consuming maaaaaaybe 30% of the available CPU power. There really aren't that many of us. We are probably not going to purchase XCP-ng Pro Support, but we absolutely WILL be purchasing a Xen Orchestra subscription at the Starter tier. I think it hits all the features we need, it gives us a real support contract for our virtualization solution, and it is our great honor to support an open-source project! Thanks for answering my question. Hopefully it's helpful in answering someone else's out there on the internet.

Yes, more explanation here: https://support.citrix.com/article/CTX246466

@jedimarcus said in Export/Import VM between 8.1 and 7.5 versions: There is certainly another way, but XOA is your golden hammer, use that one, instead of the rusty shovel next to it. It will make your life so much easier. Okay. I'll try to do this way. thank you

Nested is really complicated and not very well tested (both from hardware and software perspective). So I'm not surprised about your various experience depending on the hardware.

@chrisarzu You're very welcome. My solution to the similar problem I'd had was to set up a couple of internal systems as NTP servers so that I always had something with the right time and static IP addresses and pointed everything needing NTP at them.