Search results

So after spending the day testing, we're still no further on. Relocated eno2 & eno4 on nodes 2 & 3 to an entirely different freshly configured switch with no success. Speeds are still seemingly throttled. We've also tried changing the bond-lacp-rate to fast, and tested with layer 2 2/3 & 3/4...

Just checked the driver versions if of any help... modinfo i40e | grep ver filename: /lib/modules/6.2.16-10-pve/kernel/drivers/net/ethernet/intel/i40e/i40e.ko description: Intel(R) Ethernet Connection XL710 Network Driver srcversion: F4CBEC026738F03F2EDD1D1 vermagic...

Thanks @jsterr eno2: Identifier : 0x03 (SFP) Extended identifier : 0x04 (GBIC/SFP defined by 2-wire interface ID) Connector : 0x07 (LC) Transceiver codes : 0x10 0x00...

Such a shame I really had high hopes for that working! After applying the configuration and a reboot of all nodes: chris@pve03:~$ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-6.2.16-10-pve root=/dev/mapper/pve-root ro quiet intel_idle.max_cstate=0 intel_iommu=on iommu=pt Yet I'm still really...

After 'failed' migrations I get this when making updates / updates to grub - Generating grub configuration file ... WARNING: VG name ubuntu-vg is used by VGs ydaT6c-EZ7p-ku2w-1etM-k29V-vwBx-J5BUQk and 2TvggJ-6Xok-Zdpw-Gfnc-Pl1n-pJcx-ul7DDg. Fix duplicate VG names with vgrename uuid, a...

We are running Intel, currently configured with only max cstate's - GRUB_DEFAULT=0 GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_idle.max_cstate=0" GRUB_CMDLINE_LINUX="" Thank you - I will give your suggestions a go...

Thanks for your reply. We don't have a /etc/kernel/cmdline file on the nodes. What should be in this file? Ceph config is as below: [global] auth_client_required = cephx auth_cluster_required = cephx auth_service_required = cephx cluster_network = 10.10.50.111/24...

Hi, I've got a three node proxmox cluster with a dedicated Ceph OSD network on a 10GBit link. It's been working great on our providers switching equipment but they've recently had some rack changes and plugged into new switches. During this change, I took the opportunity to update the Proxmox...

Similar situation then. We've run a lot of migrations in Proxmox 6 & 7 and since the 8 update is actually the first time I've ever seen migrations completing with warnings. So I think the might be something introduced with the release of 8. Chris.

Interesting, I have seen those same errors in some other migrations I was making. So in your case did this cause any physical problems or just throwing up some errors? Are you running/have you recently upgraded to Proxmox 8? Chris.

Hi, I'm running a three node hyperconverged cluster. I've been running Proxmox 7 for some time and decided to take the leap to Proxmox 8. Since then, I've noticed some migration issues regarding disks. Below is an example of one of the errors I got when trying to migrate. The migration actually...

Thanks Chris, appreciate the feedback. I'll give it a go!

I'm doing this for a proof of concept. I've got a single Proxmox server with a single NIC, connected to a router. The gateway of the router as an example is 190.150.165.1 and I have access to IP's 190.150.165.35 and 190.150.165.41-45 (all not real IPs). Is it possible to configure a vmbr0...

I'd like to do a live restore (as a new VM alongside the existing) but I don't want the VM to instantly power on. Before booting I want to change the VLAN it's sat on so that it doesn't conflict with the existing machine. Is this possible to achieve? Thanks, Chris.

Just to update for anyone that comes across this thread, despite our fibre passing light tests, and running at full speed when not aggregated, it turns out it was indeed a faulty optic and was fixed by replacing. We're now back to full 20GB/s bonded throughput.

Yep that's fair enough. It breaks autocomplete if it doesn't have access to what you are calling. For me its just personal preference, makes me think twice about the command I'm entering. For example, if I accidentally typed rm -rf / as my user, worse things have happened. Whereas if I...

Only because I'm logged into the box with my own username that has sudoers permissions :) I prefer not to login directly as root... Just in case!

Hi, the new node maintenance mode is a great addition to Proxmox, thank you! Running sudo ha-manager crm-command node-maintenance enable pve01 worked perfectly. However, it'd be really nice to be able to manage maintenance state directly from Datacenter > HA. Is this something that's in the...

Thanks mira, will disable it as it's certainly not needed :) Chris.

I didn't think so but it seems that the NFS module is on: I don't believe it's needed though. Will disabling this resolve the issue?