Search results

Cheers Thomas, can verify that at least backup creation works on Fedora 36 as well :)

Nice work Thomas! Seems the Cargo.toml file changed a bit between 2.3.1 and 2.3.3, sections updated a bit for deps/workspace.dependencies etc. Are you still updating your repo?

Hi! For some reason the guest VMs stopped accepting hot plug. First I thought it was because of all PCI slots being full but it doesn't look that way. Long-shot but the VMs without issues haven't been rebooted with +pcid cpu flag yet. Anyone solved this one? Mar 8 11:20:09 xxxxxx kernel...

If the kernel for your UCS system has backported PCID support, then it might have less of a performance impact with PCID on in proxmox.

I'm not affiliated with proxmox, but pulling stuff in from testing repo to a production server should be avoided. We might have to wait for upstream fixes which should be available on monday then wait a day or so for Proxmox to pull it in and test...

No, PCID is a CPU feature from 2010 that hasn't really been used until linux kernel 4.14. Now with meltdown it's actually useable to counteract some of the performance loss. However, I haven't done any benchmarking but if you're going to reboot your Guests anyway, then make sure to add PCID...

There's a spectre variant 1 PoC around that lets you read the RAM of the host from a KVM guest. You should at least grab the latest PVE kernel with the fix for that PoC. Also, there's microcode available already from intel for spectre, but we still need to wait for the kernel updates as well...

Well - I wouldn't recommend running with cpu type: host if you are running a cluster of several proxmox servers since they might differ in CPU architecture. That might lead to live migration difficulty (when migrating from a node with flags not available in newer node). The way we do it is that...

Did you log in to a proxmox host webgui with an updated pve-manager?If you log on to one with old pve-manager you wont see it anywhere (had the same issue where i just updated one host, but logged in through another and didnt see it)

Oh, intel just updated their site today with microcode updates: https://downloadcenter.intel.com/download/27431/Linux-Processor-Microcode-Data-File?v=t

You should at the very least patch Meltdown, as it is the easiest one to "use". So that means patching guest, rebooting it. Spectre needs microcode update, intel has release some already to certain companies like HP, Dell, Supermicro and they've created bios updates for some cpus / servers. It...

https://www.qemu.org/2018/01/04/spectre/ https://lists.nongnu.org/archive/html/qemu-devel/2018-01/msg01386.html

I'd say it depends on what you're running on those KVM guests. Unpatched meltdown might mean that they can read VM guest RAM on the machine they're on, so if you're running several users or applications that might have vulnerabilities they might be exploited to run meltdown code and read the...

Hi, So, has anyone been using drbd9 with redundancy 3 in a production environment? Any issues so far or things to consider?

Hi! We're running Proxmox 3.2-2 and we'd like to upgrade it to 3.4. Is it possible to keep ceph packages (both librados and osd/mon packages) on the version they're at now but still update the rest of pve? Can we just hold those packages through apt/dpkg or will there be dependency issues?

Hi 1nerdyguy - did you install CoreOS from ISO or did you successfully manage to use their kvm/qemu ISO from coreos site? In that case, how do you manage to start import it?

Tried to disable intel_pstate and reboot the hosts but that didn't work out (although now cpuinfo reports a stable frequency). However the solution was to change clocksource in the GUEST from kvm_clock to tsc. Now we're able to live migrate CentOS / CloudLinux guests. It seems to be a bug in...

I apologize about leaving that out. I've tried with the standard kernels as well 2.6.32 and 3.10, that's why I didn't mention it. But you're right, I should have mentioned it.

Ah you may be right there, I see that intel_pstate is set as the scaling driver (we're using backport kernel 3.13 due to some issues with LACP with 2.6.32 and 3.10). I actually left it running for 15 minutes or more and it was still stuck, but maybe I'll try and reboot with the old scaling...

Hi, I'm running a VE 3.2 cluster with Ceph Dumpling. All works very well except a few hickups - one of the mayor issues is with Online Migration of VMs between the same hardware/software (exactly the same CPU). What is interesting is that Online Migration works perfectly if the VM was recently...