@sshughes

Here is how to do it in KeePass - https://keepass.info/help/base/autotype.html
Here is for KeePassXC- https://keepassxc.org/docs/KeePassXC_UserGuide#_configure_auto_type_sequences

For external copy and paste of text to the console I can suggest using password manager like Keepassxc - it has autotype feature and with little tweaking (like giving it 1-2 seconds before starting the actual typing) it works very good.

Regards

@alexredston What kernel do you use? Can you show the kernel boot parameters (/proc/cmdline) - in our case we used the Debian11 image from their website which had cloud kernel and acpi=on by default. Once we switched to regular kernel and turned off acpi, we saw all the vCPUs in the VM.

Hello,

I saw there is new announcement on Xenbits regarding Zenbleed (https://xenbits.xen.org/xsa/advisory-433.html) - will there be new patch for XCP?

Thanks in advance.

On second thought, I was not clear in the beginning. I don't expect to see 1 socket with 128 vCPU in the VM, but maybe 2 sockets with splitted vCPUs between them if I assign more than 64 to the VM. Initially I had 1 socket with 64 CPU and after turning ACPI off (either in grub or in the VM config itself), secondary socket appeared in the VM with the rest of the CPUs. More funny, turning ACPI off while running the cloud kernel of Debian makes the VM see one CPU only.

@olivierlambert I have a working VM (booted) that shows 2 sockets, 64 cpu each. I am running sysbench with --max-threads=128 and it shows load 128.
I played a bit, with normal acpi in the VM OS and disabled acpi in xe xe vm-param-set platform:acpi=0 results are the same. I am attaching lscpu and dmesg from the second case (acpi is untouched in the VM, but disabled with xe command)

Let me know if anything else is needed.

dmesg1.txt lscpu1.txt

Thanks for the fast reply, is there a documentation/statement about it?

I managed to have more than 64 vCPU with the regular kernel (not the cloud one). I was just curious if anyone has similar experience with the combo AMD/Debian11/cloud kernel.

Hello,

I came across a similar case as described in https://xcp-ng.org/forum/topic/4689/xcp-8-2-vcpus-max-settings
I have server with 2x AMD EPYC 7532. I give 128 vCPUs to Debian11 VM, but it sees only 64 of them. xl vcpu-list shows the upper half of CPUs in paused state. Server is running XCP 8.2, kernel 4.19.19-7.0.14.1 (updated around 4th of December last year).
I managed to fix this by installing "generic" kernel in the VM (linux-image-5.10.0-21-amd64), instead of the usual -cloud (VM comes with 5.10.0-20-cloud-amd64).

When I tried to turn off ACPI as suggested in the post I mentioned, cloud-image sees only one CPU. However, acpi=off in grub is needed for the generic image in order to see all. I haven't played with params on the VM.

I saw few posts here about the vCPU issue, but people are running Intel. Anyone with AMD and similar experience?

Thanks in advance.

Hi,

I am reading https://xen-orchestra.com/blog/virtops1-xen-orchestra-terraform-provider/ and https://registry.terraform.io/providers/terra-farm/xenorchestra/latest/docs, and I can't find information how to set the IP address of the machine in the terraform plan.

Is there a way to do it?

Thanks in advance.

Hi,

Yes, it was installed via the gitbook. I will check again for node.

Regards,