Search results

Would be very nice if you could post this in the devel list [1] or at the very least post a feature request in bugzilla [2] to get this compiled by default, as it is a nice feature and this kind of modifications will be overwritten on updates and are quite hard to maintain at scale. Thanks...

L40S seems to be supported by current driver version 18, so it should work. You can use it without licenses, i.e. to try if it works for you, but performance will be limited by the driver unless a Nvidia license is activated [1] [1]...

AFAIK, you need a different, non-gaming, card to use Nvidia vGPU feature: https://docs.nvidia.com/vgpu/gpus-supported-by-vgpu.html

XY problem... IMHO you should ask / investigate why it you are suffering from that load from pvestatd instead of asking how to disable it, which can't be done while keeping PVE working as expected. First time I've heard about this issue, so can't really help much without details about the...

Ceph cluster network is used for replication traffic only. All traffic from clients, MON, MDS, OSD flows through the public network. I would bond both 2.5 nics in an LACP LAG to two stacked/MLAG switches and set both public and cluster networks as vlans through the bond. That would get you the...

Why would anyone want to stop an essential PVE service?

What exactly happend on the network and pve hosts when the VM did not move to another host in the cluster? Remember that PVE HA will only try to restart VMs configured for HA if the host loses quorum, and for that all corosync links have to fail. It will not move a VM if just "a network" fails...

It's fine! I somehow understood that you where to install vCenter in the same host of PVE, not in a VM. Sorry, seems I had a shortcircuit in my brain.

Had no idea about that. I used good old BIOS for the PVE VM I used to install ESXi. I strongly advise against installing anything in the PVE host itself. Use another VM to get vCenter running.

That depends on your corosync configuration and which interfaces are used for corosync and Ceph. Corosync networks are completely different thing than Ceph networks. In fact, you may even have quorum in PVE and not in Ceph and vice versa. Also remember that Ceph public network is used for all...

Only the PCI device. Remember that any passed through device can't be used in the host once the VM has started, don't pass through the one that you used for your vmbr0 or vmbr1!

Use MLAG with both F5 switches and configure LACP 802.3ad LAG both in PVE and in the switches and you will get both links in an active/active setup with failover/failback times tipically under 400ms. Remember to add the LAG to the Ceph vlan. You will lose Ceph quorum because no monitor will...

This is surprising, given the added instructions of v3 and v4 over v2 or v2-AES. Here [1] is the definition of each x86-64 CPU type. Maybe you could try using a custom CPU and manually add each flag and bench your workload to try to find out which one is introducing the performance loss that you...

IMHO something is off with that measurement: it's simply impossible that mechanical disks provide a 8 minute GC for a 2TB datastore, no matter the filesystem. Maybe it's using some cache? I do have some 2-4TB datastores using either single drives + EXT4 or ZFS mirrors and all take way more than...

Does the network of the VMs running inside ESXi work correctly for you?

Yes, you need to disable CSO offloading inside ESXi. Don't really know why just yet, found it after 2 days of trial and error and browsing online docs. The idea came from here [1] and the fact that tcpdump shows lots of crc errors typically related to misbehaving offloading in the drivers...

Sorry, I'm not the OP ;). I too think that something isn't correctly configured in Corosync, host lost quorum and HA made them reboot, hence I asked for the configuration files and other details.

Essentially it's the same procedure as with a major version upgrade, like you posted [1]. Install packages in all nodes, set noout, restart one by one mons, managers, OSD, MDS, while waiting for Ceph status to be ok before restarting the next daemon. Finally, remove the noout flag. PVE webUI...

QEMU guest agent does not keep time in sync like i.e. VMWare tools do. It only syncs time on VM start, after suspend/resume and after a snapshot is taken, either a manual one or from a backup. You need some ntp/sntp client to keep time synced. Most OS do come with some configured by default.

What does happen exactly when you try to access the webUI of ESXi ?