|
本帖最后由 liufanl 于 2023-12-18 16:20 编辑
我在PVE8.0下用LXC运行了一个openwrt。直通了两张网卡,分别是enp1s0,enp3s0。enp1s0用作openwrt WAN口,enp3s0用作openwrt LAN口。每次启动openwrt的时候,系统都会将这两张网卡重命名,enp1s0—>physYPgkhf(这个名称随机)—>eth1(lxc.conf设置的),enp3s0—>phys0TDHej(这个名称随机)—>eth2(lxc.conf设置的),关机或重启时,会重命名回来。但是,eth1—>physYPgkhf—>enp1s0这个过程正常,eth3—>phys0TDHej—>enp3s0这个过程就不能执行完,phys0TDHej—>enp3s0这个过程没有,貌似重启LXC一段时间后该网卡会丢失,失去连接。具体启停日志如下,请问哪位大佬遇见过同样的问题,恳请解答!!
启动LXC openwrt的过程:
2023-12-18T00:03:20.183705+08:00 liufanl kernel: [ 26.056205] EXT4-fs (dm-12): mounted filesystem c23912a6-f52c-4def-9379-e2e3ce7884bd r/w with ordered data mode. Quota mode: none.
2023-12-18T00:03:20.703682+08:00 liufanl kernel: [ 26.577783] kauditd_printk_skb: 12 callbacks suppressed
2023-12-18T00:03:20.703705+08:00 liufanl kernel: [ 26.577787] audit: type=1400 audit(1702829000.699:24): apparmor="STATUS" operation="profile_load" profile="/usr/bin/lxc-start" name="lxc-104_</var/lib/lxc>" pid=1081 comm="apparmor_parser"
2023-12-18T00:03:21.723675+08:00 liufanl kernel: [ 27.596155] vmbr0: port 2(veth104i0) entered blocking state
2023-12-18T00:03:21.723699+08:00 liufanl kernel: [ 27.596164] vmbr0: port 2(veth104i0) entered disabled state
2023-12-18T00:03:21.723701+08:00 liufanl kernel: [ 27.596198] veth104i0: entered allmulticast mode
2023-12-18T00:03:21.723703+08:00 liufanl kernel: [ 27.596319] veth104i0: entered promiscuous mode
2023-12-18T00:03:21.847666+08:00 liufanl kernel: [ 27.719685] igb 0000:01:00.0 physYPgkhf: renamed from enp1s0
2023-12-18T00:03:21.882529+08:00 liufanl kernel: [ 27.755692] igb 0000:03:00.0 phys0TDHej: renamed from enp3s0
2023-12-18T00:03:21.899733+08:00 liufanl kernel: [ 27.772189] eth0: renamed from vethiT4MvH
2023-12-18T00:03:21.915725+08:00 liufanl kernel: [ 27.787855] igb 0000:01:00.0 eth1: renamed from physYPgkhf
2023-12-18T00:03:21.957967+08:00 liufanl kernel: [ 27.833564] igb 0000:03:00.0 eth2: renamed from phys0TDHej
2023-12-18T00:03:22.585972+08:00 liufanl kernel: [ 28.460815] vmbr0: port 2(veth104i0) entered blocking state
2023-12-18T00:03:22.586006+08:00 liufanl kernel: [ 28.460829] vmbr0: port 2(veth104i0) entered forwarding state
关闭LXC openwrt的过程:
2023-12-18T00:04:25.471676+08:00 liufanl kernel: [ 91.502006] br-lan: port 2(eth2) entered disabled state
2023-12-18T00:04:25.471705+08:00 liufanl kernel: [ 91.502038] br-lan: port 1(eth0) entered disabled state
2023-12-18T00:04:25.471707+08:00 liufanl kernel: [ 91.503639] eth0: left allmulticast mode
2023-12-18T00:04:25.471710+08:00 liufanl kernel: [ 91.503646] eth0: left promiscuous mode
2023-12-18T00:04:25.471711+08:00 liufanl kernel: [ 91.503666] br-lan: port 1(eth0) entered disabled state
2023-12-18T00:04:25.485695+08:00 liufanl kernel: [ 91.518094] vmbr0: port 2(veth104i0) entered disabled state
2023-12-18T00:04:25.485720+08:00 liufanl kernel: [ 91.518378] igb 0000:03:00.0 eth2: left allmulticast mode
2023-12-18T00:04:25.485723+08:00 liufanl kernel: [ 91.518402] igb 0000:03:00.0 eth2: left promiscuous mode
2023-12-18T00:04:25.485725+08:00 liufanl kernel: [ 91.518817] br-lan: port 2(eth2) entered disabled state
2023-12-18T00:04:29.739316+08:00 liufanl kernel: [ 95.774565] igb 0000:01:00.0 physYPgkhf: renamed from eth1
2023-12-18T00:04:29.779732+08:00 liufanl kernel: [ 95.814454] igb 0000:03:00.0 phys0TDHej: renamed from eth2
2023-12-18T00:04:29.822689+08:00 liufanl kernel: [ 95.860802] vmbr0: port 2(veth104i0) entered disabled state
2023-12-18T00:04:29.823774+08:00 liufanl kernel: [ 95.861108] veth104i0 (unregistering): left allmulticast mode
2023-12-18T00:04:29.823808+08:00 liufanl kernel: [ 95.861119] veth104i0 (unregistering): left promiscuous mode
2023-12-18T00:04:29.823811+08:00 liufanl kernel: [ 95.861127] vmbr0: port 2(veth104i0) entered disabled state
2023-12-18T00:04:29.879831+08:00 liufanl kernel: [ 95.915372] igb 0000:01:00.0 enp1s0: renamed from physYPgkhf
这个位置缺少enp3s0网卡的重命名
2023-12-18T00:04:30.359789+08:00 liufanl kernel: [ 96.398064] audit: type=1400 audit(1702829070.352:30): apparmor="STATUS" operation="profile_remove" profile="/usr/bin/lxc-start" name="lxc-104_</var/lib/lxc>" pid=11417 comm="apparmor_parser"
2023-12-18T00:04:31.252447+08:00 liufanl pvestatd[1013]: unable to get PID for CT 104 (not running?)
2023-12-18T00:04:31.473470+08:00 liufanl pvestatd[1013]: unable to get PID for CT 104 (not running?)
2023-12-18T00:04:31.550231+08:00 liufanl pvedaemon[1040]: unable to get PID for CT 104 (not running?)
|
|