Search results

It's very active! https://xcp-ng.org/blog/2024/07/12/xcp-ng-8-3-release-candidate-1/

No, I'm trying XCP-ng for this deployment. To my surprise, it seems to be working really well. I have other smaller issues, but I think those will be easier to work out than this issue was.

Thank you for asking. We never got it. Between this and some other issues (in another thread), we had to change strategies completely.

As I mentioned above, I have been searching for weeks and haven't found any solutions yet. It's been like this since Proxmox 7.0 so I don't think it's qemu/kernel version specific.

Nothing. I started with Default and have tried each of the settings there. I also moved the hdd to a 36x HDD ZFS System on 10G with excellent IOPS and low latency with the identical result. It's like the VM is underwater. Even Terminal takes like 8 seconds to open.

Yes, that’s what I did. It’s why I started this thread. I can’t get replication between nodes working with local storage. Shared storage is also not an option due to latency.

CEPH performs way too slow for our needs. We need lightning fast response times. RAID0 local seems to work the best in our testing.

Thanks for the reply! Yes, the machine has 72x cores, but I did try 8x just to test NUMA issues and it's exactly the same. It's a RAID0 ZFS with 2x fast SSDs They are set to 9000. I tried 1500 with the same result. Makes my VMs crash (rarely), so I stopped using host.

Yep, I've gone through all of these. I think I just have a tough use case.

Hi there, I've been searching for a week and can't find the answer. Why is my Windows 11 VM so slow?? I'm simply testing the UI via RDP between several machines (2x VMs and 2x bare metal computers). The 2x bare metal computers are snappy and HIGHLY responsive. The 2x VMs struggle just...

I see. Thank you for this. I guess it's time to move back to VMWare.

I have 8 nodes with properly working HA, local ZFS on each (identical), and replication. When I reboot a host, a FRESH replication occurs instead of making a delta and it takes forever. Anyone have any ideas why it doesn't use the existing data as a base?

I'll be happy to pay a $100 bounty to the first person that solves this issue for me. Please DM me or post here. I'm happy to run a Zoom meeting so you can see clearly where I'm having trouble with this platform.

Am I the only person that needs to do updates to Proxmox hosts? How are you guys managing these things?

I'm still having this issue. Can anyone help with replication not working (as expected)? Again, the goal is just to have replication jobs running and successful so that we when we reboot a server, the VM migrates QUICKLY without needing to send a full replication at that moment. This is...

Error. "2024-03-11 08:54:04 110-0: volume 'rpool/data/vm-110-disk-0' already exists" I just went to Replication under Datacenter and configured each one there. Then the replication will be happy and the next time I need to failover, it will error again.

Ceph is too slow for our needs.

Hi, I've configured HA and replication, but when I actually reboot a server, the failover fails stating that the volume already exists at the target node. Some helpful info: I have 8x nodes my goal is to have replications every 15m when there's an event that causes a failover, either a quick...

The PERSONAL tabs!! Thank you so much. It was in crontab-e.

Thank you, again. Yep, Cluster = corosync in my mind. I’ll set it for speed.