Search results

  1. [SOLVED] After upgrading to 7.2-14 on starting VM's error dev tap104i0 master static' failed: exit code 255 when OVS is used

    Confirmed. Works with pve-container version 4.4-2. Could someone change the title to solved. Thanks!
  2. [SOLVED] After upgrading to 7.2-14 on starting VM's error dev tap104i0 master static' failed: exit code 255 when OVS is used

    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.
  3. [SOLVED] WARNING: CPU: 0 PID: ... [openvswitch]

    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'
  4. [SOLVED] ifupdown2: ovs_extra parameter

    After some trial and error I found a solution targets='""' translates to "targets=\"\""
  5. [SOLVED] WARNING: CPU: 0 PID: ... [openvswitch]

    Still present in: Linux pve-2 5.15.35-3-pve
  6. [SOLVED] WARNING: CPU: 0 PID: ... [openvswitch]

    No, it is 2-nodes with qdevice.
  7. [SOLVED] WARNING: CPU: 0 PID: ... [openvswitch]

    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...
  8. [SOLVED] ifupdown2: ovs_extra parameter

    Any update regarding this topic? Do you need further information?
  9. [SOLVED] ifupdown2: ovs_extra parameter

    No, doesn't work. Seems that backslash is translated into space. targets= :9995
  10. [SOLVED] ifupdown2: ovs_extra parameter

    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=\"\" active_timeout=60 -- set Bridge vmbr0 netflow=@nf In...
  11. Can't set static IP to Fedora 27 (or 26) lxc container

    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
  12. Can't boot after upgrade

    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:
  13. Can't boot after upgrade

    One more question. I have recognized that several ZFS packages have been updated (see history.log attached above; e.g. libzfs2:amd64 (, and then the problems started. But Grub is still from November 30, 2016. Might this be the reason for Grub not...
  14. Can't boot after upgrade

    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...
  15. Can't boot after upgrade

    grub rescue> set cmdpath=(hd0) prefix=(hd0)/ROOT/pve-1@/boot/grub root=hd0
  16. Can't boot after upgrade

    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...
  17. Can't boot after upgrade

    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...
  18. Can't boot after upgrade

    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...
  19. Can't boot after upgrade

    "update-grub" and "grub-install /dev/sda" (see attachment) went fine. Key question is still why: a) Grub bootloader on /dev/sda can't load subsequent modules from /dev/sda3 b) Grub on Proxmox 4.4 install disk can't access kernel/initrd from zfs pool on /dev/sda3. Thanks for your support!
  20. Can't boot after upgrade

    Here we go: root@pve:~# zpool get all rpool NAME PROPERTY VALUE SOURCE rpool size 2.72T - rpool capacity 43% - rpool altroot -...


The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!