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.

Hi, Please provide more details. Which XCP-ng version? What PV driver version?

@foreverska witch one do you find with XCP?

I have the same problem with xcp-ng-8.2. I'm trying to start with mxgpu with HPE ML380p Gen8 E5-2620V2. Inserting pci=realloc pci=assign-busses the server cannot boot. Below the point of boot where it crashes. The log in images seems to recall a known bug --> "choose an explicit smt=(bool) setting. See XSA-297" It's the pci=assign-busses that cannot permit to boot but without it "modprobe gim" has not inserted. Also using usb disk avoiding PCI disk system crashs during startup. Firmware bios is really recent ( 2019 ) , the last one. Someone has resolved this issue ?[image: 1615626649154-crash-assign-busses-resized.jpg]

@olivierlambert Strange, that 32bit windows was from the 32bit Windows 10 template. I installed Windows10 but it seems I installed the 64bit.

@jedimarcus Okay - and once again. Thanks for your help.

If you have decent perf with your apps on it, I would say it's fine. 64KHz seems a display bug more than a real number to me. On my Dell R620 I have Avg freq 2473030 KHz.

Hello, On a new server where I migrated about 15 VMs, same problem suddenly! Thanks for the tip, the Restarting Toolstack worked! (XCP-NG 8.2 / XCP-ng Center 20.04.01)

@ascar Maybe this helps: https://forum.netgate.com/topic/97553/pfsense-2-3-on-xen-server/5 Also, dont forget to disable offloading.

Okay. Please remember to NOT tinker with dom0 because this will cause you this kind of issues