Search results

Update: the unpredictables crashes appeared on the Gen8 with kernel 6.8.4-3. Newer kernel 6.8.8-1 on the same machine is running stable here for >10 days now.

I'm using Proxmox for years. The upgrade went without any issues (as usual - thanks Proxmox team!) But the latest 6.8 kernel upgrade results in unpredictable crashes (several days) on my HPE Microserver Gen8 (back to 6.5 now and stable) - nothing suspicious in the logs, just bang and reboot. The...

Confirmed. Works with pve-container version 4.4-2. Could someone change the title to solved. Thanks!

Same issue here. One observation: If Firewall on the interface is set to Yes it works for my containers(CentOS, Debian), if set to No --> error as reported above.

Warning is gone with latest Linux pve-2 5.15.39-1-pve Jul 06 12:08:03 pve-2 kernel: Timeout policy base is empty Jul 06 12:08:03 pve-2 kernel: Failed to associated timeout policy `ovs_test_tp'

After some trial and error I found a solution targets='"10.0.20.20:9995"' translates to "targets=\"10.0.20.20:9995\""

Still present in: Linux pve-2 5.15.35-3-pve

No, it is 2-nodes with qdevice.

Hello, since upgrading to Kernel 5.15.35 I have following warning (and a second similar one) during boot: May 15 17:04:57 pve-2 kernel: WARNING: CPU: 0 PID: 1228 at include/net/netfilter/nf_conntrack.h:175 __ovs_ct_lookup+0x907/0xa40 [openvswitch] May 15 17:04:57 pve-2 kernel: Modules linked...

Any update regarding this topic? Do you need further information?

No, doesn't work. Seems that backslash is translated into space. targets=10.0.20.20 :9995

After upgrading to ifupdown to ifupdown2 (as part of PVE7), I have a problem to configure NetFlow with ovs_extra in /etc/network/interfaces. Following statement worked in ifupdown: ovs_extra --id=@nf create NetFlow targets=\"10.0.20.20:9995\" active_timeout=60 -- set Bridge vmbr0 netflow=@nf In...

Default Fedora starts systemd-networkd, but Proxmox uses the former network scripts to set up static IP. Try: systemctl stop systemd-networkd systemctl start network

I did a fresh reinstall of PVE on a separate disk and migrated the VMs. I kept the former zfs-pool as storage. With respect to your question see post #2 of this threat: https://forum.proxmox.com/threads/cant-boot-after-upgrade.32655/#post-160924

One more question. I have recognized that several ZFS packages have been updated (see history.log attached above; e.g. libzfs2:amd64 (0.6.5.8-pve13~bpo80, 0.6.5.8-pve14~bpo80) and then the problems started. But Grub is still from November 30, 2016. Might this be the reason for Grub not...

After "insmod normal" I get the "error: unknown filesystem" again. I still do not understand why I can't access the zfs filesystem from Grub - even Grub from Proxmox Install CD doesn't work. I assume wiping the MTB wouldn't help. Two possibilities: a) install Grub on MicroSD and load...

grub rescue> set cmdpath=(hd0) prefix=(hd0)/ROOT/pve-1@/boot/grub root=hd0

root@pve:~# dpkg --list | grep grub ii grub-common 2.02-pve5 amd64 GRand Unified Bootloader (common files) ii grub-efi-amd64-bin 2.02-pve5 amd64 GRand Unified Bootloader, version 2 (EFI-AMD64 binaries) ii...

There is no result, however if you convert 1d540bdfe4ab7feb (hex) to 2113327181385662443 (dec): root@pve:~# blkid -U 1d540bdfe4ab7feb root@pve:~# blkid -U 2113327181385662443 /dev/sda3 root@pve:~# lsblk -o NAME,FSTYPE,LABEL,UUID /dev/sda3 /dev/sdb3 NAME FSTYPE LABEL UUID sda3 zfs_member...

As requested - appreciate your help! root@pve:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 2.7T 0 disk ├─sda1 8:1 0 1M 0 part ├─sda2 8:2 0 128M 0 part └─sda3 8:3 0 2.7T 0 part sdb 8:16 0 2.7T 0 disk ├─sdb1 8:17 0 1M...