Hi i do have a the following setup config
args: -vnc 0.0.0.0:77
boot: c
bootdisk: scsi0
cores: 30
description: !
localtime: 0
machine: q35
memory: 131072
name: server.domain.com
net0: e1000=00:1d:09:68:2c:f0,bridge=vmbr0,firewall=1
numa: 1
onboot: 1
ostype: l26
scsi0: local-lvm:vm-100-disk-0,cache=writeback,size=700G
scsi1: local-lvm:vm-100-disk-1,cache=writeback,size=1T
scsi2: local-lvm:vm-100-disk-2,size=200G
smbios1: uuid=fa5d5cf5-1623-41bc-b996-677256344
sockets: 2
vga: std
pveversion -v
proxmox-ve: 6.3-1 (running kernel: 5.4.106-1-pve)
pve-manager: 6.4-4 (running version: 6.4-4/337d6701)
pve-kernel-5.4: 6.4-1
pve-kernel-helper: 6.4-1
pve-kernel-5.4.106-1-pve: 5.4.106-1
ceph-fuse: 12.2.11+dfsg1-2.1+deb10u1
corosync: 3.1.2-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.20-pve1
libproxmox-acme-perl: 1.0.8
libproxmox-backup-qemu0: 1.0.3-1
libpve-access-control: 6.4-1
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.4-2
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.2-1
libpve-storage-perl: 6.4-1
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.1.5-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.5-3
pve-cluster: 6.4-1
pve-container: 3.3-5
pve-docs: 6.4-1
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.2-2
pve-ha-manager: 3.1-1
pve-i18n: 2.3-1
pve-qemu-kvm: 5.2.0-6
pve-xtermjs: 4.7.0-3
qemu-server: 6.4-1
smartmontools: 7.2-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 2.0.4-pve1
this is a very old ubuntu 8.04-4 tha unfortunately is a core server that can't be upgraded. we moved from another proxmox version 5.1 and was working fine
as soon as the vm starts originally it had virtio network card but when starts networks works fine for 3 minutes then it stops working (it originally had the virtio drivers installed and working) if we change it to intel it seems to work, but e1000 will crash on kernel panic several times at random times, the only solution is to use virtio but we just get this strange error when vm starts.
we also observed the following errors before the network stops working:
is there a way anyone can help me with this issue.
thanks.
args: -vnc 0.0.0.0:77
boot: c
bootdisk: scsi0
cores: 30
description: !
localtime: 0
machine: q35
memory: 131072
name: server.domain.com
net0: e1000=00:1d:09:68:2c:f0,bridge=vmbr0,firewall=1
numa: 1
onboot: 1
ostype: l26
scsi0: local-lvm:vm-100-disk-0,cache=writeback,size=700G
scsi1: local-lvm:vm-100-disk-1,cache=writeback,size=1T
scsi2: local-lvm:vm-100-disk-2,size=200G
smbios1: uuid=fa5d5cf5-1623-41bc-b996-677256344
sockets: 2
vga: std
pveversion -v
proxmox-ve: 6.3-1 (running kernel: 5.4.106-1-pve)
pve-manager: 6.4-4 (running version: 6.4-4/337d6701)
pve-kernel-5.4: 6.4-1
pve-kernel-helper: 6.4-1
pve-kernel-5.4.106-1-pve: 5.4.106-1
ceph-fuse: 12.2.11+dfsg1-2.1+deb10u1
corosync: 3.1.2-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.20-pve1
libproxmox-acme-perl: 1.0.8
libproxmox-backup-qemu0: 1.0.3-1
libpve-access-control: 6.4-1
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.4-2
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.2-1
libpve-storage-perl: 6.4-1
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.1.5-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.5-3
pve-cluster: 6.4-1
pve-container: 3.3-5
pve-docs: 6.4-1
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.2-2
pve-ha-manager: 3.1-1
pve-i18n: 2.3-1
pve-qemu-kvm: 5.2.0-6
pve-xtermjs: 4.7.0-3
qemu-server: 6.4-1
smartmontools: 7.2-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 2.0.4-pve1
this is a very old ubuntu 8.04-4 tha unfortunately is a core server that can't be upgraded. we moved from another proxmox version 5.1 and was working fine
as soon as the vm starts originally it had virtio network card but when starts networks works fine for 3 minutes then it stops working (it originally had the virtio drivers installed and working) if we change it to intel it seems to work, but e1000 will crash on kernel panic several times at random times, the only solution is to use virtio but we just get this strange error when vm starts.
we also observed the following errors before the network stops working:
| Jan 15 22:18:04 kvm210 pvedaemon[16282]: start VM 100: UPID:kvm210:00003F9A:051E498C:65A61F9C:qmstart:100:root@pam: |
| Jan 15 22:18:04 kvm210 pvedaemon[9414]: <root@pam> starting task UPID:kvm210:00003F9A:051E498C:65A61F9C:qmstart:100:root@pam: |
| Jan 15 22:18:04 kvm210 systemd[1]: Started 100.scope. |
| Jan 15 22:18:05 kvm210 systemd-udevd[16290]: Using default interface naming scheme 'v240'. |
| Jan 15 22:18:05 kvm210 systemd-udevd[16290]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. |
| Jan 15 22:18:05 kvm210 systemd-udevd[16290]: Could not generate persistent MAC address for tap100i0: No such file or directory |
| Jan 15 22:18:06 kvm210 kernel: [858711.325513] device tap100i0 entered promiscuous mode |
| Jan 15 22:18:06 kvm210 systemd-udevd[16290]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. |
| Jan 15 22:18:06 kvm210 systemd-udevd[16290]: Could not generate persistent MAC address for fwbr100i0: No such file or directory |
| Jan 15 22:18:06 kvm210 systemd-udevd[16280]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. |
| Jan 15 22:18:06 kvm210 systemd-udevd[16280]: Using default interface naming scheme 'v240'. |
| Jan 15 22:18:06 kvm210 systemd-udevd[16280]: Could not generate persistent MAC address for fwpr100p0: No such file or directory |
| Jan 15 22:18:06 kvm210 systemd-udevd[16277]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. |
| Jan 15 22:18:06 kvm210 systemd-udevd[16277]: Using default interface naming scheme 'v240'. |
| Jan 15 22:18:06 kvm210 systemd-udevd[16277]: Could not generate persistent MAC address for fwln100i0: No such file or directory |
| Jan 15 22:18:06 kvm210 kernel: [858711.391500] fwbr100i0: port 1(fwln100i0) entered blocking state |
| Jan 15 22:18:06 kvm210 kernel: [858711.391503] fwbr100i0: port 1(fwln100i0) entered disabled state |
| Jan 15 22:18:06 kvm210 kernel: [858711.391680] device fwln100i0 entered promiscuous mode |
| Jan 15 22:18:06 kvm210 kernel: [858711.391774] fwbr100i0: port 1(fwln100i0) entered blocking state |
| Jan 15 22:18:06 kvm210 kernel: [858711.391777] fwbr100i0: port 1(fwln100i0) entered listening state |
| Jan 15 22:18:06 kvm210 kernel: [858711.399797] vmbr0: port 2(fwpr100p0) entered blocking state |
| Jan 15 22:18:06 kvm210 kernel: [858711.399800] vmbr0: port 2(fwpr100p0) entered disabled state |
| Jan 15 22:18:06 kvm210 kernel: [858711.399968] device fwpr100p0 entered promiscuous mode |
| Jan 15 22:18:06 kvm210 kernel: [858711.400509] vmbr0: port 2(fwpr100p0) entered blocking state |
| Jan 15 22:18:06 kvm210 kernel: [858711.400511] vmbr0: port 2(fwpr100p0) entered listening state |
| Jan 15 22:18:06 kvm210 kernel: [858711.541005] fwbr100i0: port 2(tap100i0) entered blocking state |
| Jan 15 22:18:06 kvm210 kernel: [858711.541008] fwbr100i0: port 2(tap100i0) entered disabled state |
| Jan 15 22:18:06 kvm210 kernel: [858711.541227] fwbr100i0: port 2(tap100i0) entered blocking state |
| Jan 15 22:18:06 kvm210 kernel: [858711.541230] fwbr100i0: port 2(tap100i0) entered listening state |
| Jan 15 22:18:07 kvm210 pvedaemon[9468]: <root@pam> successful auth for user 'root@pam' |
| Jan 15 22:18:07 kvm210 pvedaemon[9414]: <root@pam> end task UPID:kvm210:00003F9A:051E498C:65A61F9C:qmstart:100:root@pam: OK |
| Jan 15 22:18:21 kvm210 kernel: [858726.418466] fwbr100i0: port 1(fwln100i0) entered learning state |
| Jan 15 22:18:21 kvm210 kernel: [858726.418520] vmbr0: port 2(fwpr100p0) entered learning state |
| Jan 15 22:18:21 kvm210 kernel: [858726.674505] fwbr100i0: port 2(tap100i0) entered learning state |
is there a way anyone can help me with this issue.
thanks.