4.2

This configuration (perhaps you'll call it a work-around) took me a while to sort out, so hopefully it will save you some time. The problem: When you bond 2 interfaces and then want to make a "vmbr" (for example vmbr0) over them, you'll find that the moment a VM starts with the same vlan tag as...

After doing a simple `apt-get upgrade` on my older pve 3.4, it didn't come back online due to a kernel panic (can't find /etc/zfs/zfs-functions). Not the end of the world I thought, let's use the opportunity and upgrade to 4.2. After a clean install (again zfs raid 1) and some zpool-hassle, I...

I used to install various versions (since 1.8) of PVE over IPMI to number of servers and everything was fine every time I need that. But this time I need to install PVE 4.2 to some a bit outdated server over IPMI. The problem is that IPMI won't show me the some graphics mode that PVE install...

Hello folks, We are fighting to install PVE 4.2 on a brand new Supermicro with HBA and 5 SAS disks installed on It. Configuration is quite straightforward and all disks are seen at install time. First goal was to configure PVE on 4 disks in RAID 10 ZFS : I selected the four target disks and...

The server has networking, everything appears to be ok on the server's side. But none of our VMs are getting DHCP assignments after the upgrade to v4.2 pveversion -v proxmox-ve: 4.2-48 (running kernel: 4.4.6-1-pve) pve-manager: 4.2-2 (running version: 4.2-2/725d76f0) pve-kernel-4.4.6-1-pve...

Intel DQ77MK board with latest (July 28, 2015) BIOS. Samsung MZVPV128HDGM on PCIe riser card. 4.2 installer on USB drive boots, finds the NVMe disk and happily installs PVE. Reboot, and no bootable devices found. None showing in BIOS. Disabled legacy boot per p.20 of this guide to no effect.

Upgraded 4 of 7 nodes today only to discover than especially two VMs running (Palo Alto - VM200 FWs) use much more CPU than when on pve 4.1 :( Pic 1 here shows VM usage last 24 hour and the jump when migrated onto 4.2.22 around 17:00, the last high jump is me introducing more load on the FW...

I've been having connectivity issues since updating to 4.2 both through a dist-upgrade and after a fresh installation. I first had the issue a few days ago when updating nodes from 4.1 to 4.2 using the no-subscription repository - the first symptom was being unable to connect to any updated...