OpenIndiana(illumos):重新启动时丢失 vmxnet3 接口

OpenIndiana(illumos):重新启动时丢失 vmxnet3 接口

我希望我的 VMware vmxnet3 接口在启动时使用 DHCP。我可以使用以下命令手动配置 NIC:

# ifconfig vmxnet3s0 plumb
# ipadm create-addr -T dhcp vmxnet3s0/v4dhcp

但创建/etc/dhcp.vmxnet3s0并重新启动后,接口关闭,日志显示:

Aug 13 09:34:15 neumann vmxnet3s: [ID 654879 kern.notice] vmxnet3s:0: getcapab(0x200000) -> no
Aug 13 09:34:15 neumann vmxnet3s: [ID 715698 kern.notice] vmxnet3s:0: stop()
Aug 13 09:34:17 neumann vmxnet3s: [ID 654879 kern.notice] vmxnet3s:0: getcapab(0x200000) -> no
Aug 13 09:34:17 neumann vmxnet3s: [ID 920500 kern.notice] vmxnet3s:0: start()
Aug 13 09:34:17 neumann vmxnet3s: [ID 778983 kern.notice] vmxnet3s:0: getprop(TxRingSize) -> 256
Aug 13 09:34:17 neumann vmxnet3s: [ID 778983 kern.notice] vmxnet3s:0: getprop(RxRingSize) -> 256
Aug 13 09:34:17 neumann vmxnet3s: [ID 778983 kern.notice] vmxnet3s:0: getprop(RxBufPoolLimit) -> 512
Aug 13 09:34:17 neumann nwamd[491]: [ID 605049 daemon.error] 1: nwamd_set_unset_link_properties: dladm_set_linkprop failed: operation not supported
Aug 13 09:34:17 neumann vmxnet3s: [ID 654879 kern.notice] vmxnet3s:0: getcapab(0x20000) -> no
Aug 13 09:34:17 neumann nwamd[491]: [ID 751932 daemon.error] 1: nwamd_down_interface: ipadm_delete_addr failed on vmxnet3s0: Object not found
Aug 13 09:34:17 neumann nwamd[491]: [ID 819019 daemon.error] 1: nwamd_plumb_unplumb_interface: plumb IPv4 failed for vmxnet3s0: Operation not supported on disabled object
Aug 13 09:34:17 neumann nwamd[491]: [ID 160156 daemon.error] 1: nwamd_plumb_unplumb_interface: plumb IPv6 failed for vmxnet3s0: Operation not supported on disabled object
Aug 13 09:34:17 neumann nwamd[491]: [ID 771489 daemon.error] 1: add_ip_address: ipadm_create_addr failed on vmxnet3s0: Operation not supported on disabled object
Aug 13 09:34:17 neumann nwamd[491]: [ID 405346 daemon.error] 9: start_dhcp: ipadm_create_addr failed for vmxnet3s0: Operation not supported on disabled object

然后我尝试禁用network/physical:nwamnetwork/physical:default这有效,接口已启动但physical:default失败并且我的网络服务(例如 NFS)拒绝启动。

# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
    inet 127.0.0.1 netmask ff000000 
vmxnet3s0: flags=1004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 9000 index 2
    inet 192.168.178.248 netmask ffffff00 broadcast 192.168.178.255
vmxnet3s0:1: flags=1004842<BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 9000 index 2
    inet 192.168.178.248 netmask ffffff00 broadcast 192.168.178.255
vmxnet3s0:2: flags=1004842<BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 9000 index 2
    inet 192.168.178.248 netmask ffffff00 broadcast 192.168.178.255
vmxnet3s0:3: flags=1004842<BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 9000 index 2
    inet 192.168.178.248 netmask ffffff00 broadcast 192.168.178.255
vmxnet3s0:4: flags=1004842<BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 9000 index 2
    inet 192.168.178.248 netmask ffffff00 broadcast 192.168.178.255
vmxnet3s0:5: flags=1004842<BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 9000 index 2
    inet 192.168.178.248 netmask ffffff00 broadcast 192.168.178.255
vmxnet3s0:6: flags=1004842<BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 9000 index 2
    inet 192.168.178.248 netmask ffffff00 broadcast 192.168.178.255
vmxnet3s0:7: flags=1004842<BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 9000 index 2
    inet 192.168.178.248 netmask ffffff00 broadcast 192.168.178.255
vmxnet3s0:8: flags=1004842<BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 9000 index 2
    inet 192.168.178.248 netmask ffffff00 broadcast 192.168.178.255
lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252 index 1
    inet6 ::1/128 
vmxnet3s0: flags=20002000840<RUNNING,MULTICAST,IPv6> mtu 9000 index 2
    inet6 ::/0

# cat /var/svc/log/network-physical\:default.log
[ Aug 16 09:46:39 Enabled. ]
[ Aug 16 09:46:41 Executing start method ("/lib/svc/method/net-physical"). ]
[ Aug 16 09:46:41 Timeout override by svc.startd.  Using infinite timeout. ]
starting DHCP on primary interface vmxnet3s0
ifconfig: vmxnet3s0: DHCP is already running
[ Aug 16 09:46:43 Method "start" exited with status 96. ]

NFS server not running:

# svcs -xv network/nfs/server
svc:/network/nfs/server:default (NFS server)
State: offline since August 16, 2012 09:46:40 AM UTC
Reason: Service svc:/network/physical:default
        is not running because a method failed.
   See: http://illumos.org/msg/SMF-8000-GE
  Path: svc:/network/nfs/server:default
          svc:/milestone/network:default
            svc:/network/physical:default
Reason: Service svc:/network/physical:nwam is disabled.
   See: http://illumos.org/msg/SMF-8000-GE
  Path: svc:/network/nfs/server:default
          svc:/milestone/network:default
            svc:/network/physical:nwam
Reason: Service svc:/network/nfs/nlockmgr:default is disabled.
   See: http://illumos.org/msg/SMF-8000-GE
  Path: svc:/network/nfs/server:default
          svc:/network/nfs/nlockmgr:default
   See: man -M /usr/share/man -s 1M nfsd
Impact: This service is not running.

我是 Solaris 世界的新手,因此任何帮助我解决问题的办法都将不胜感激。谢谢!

答案1

不要使用 ifconfig 来检测接口的使用情况ipadm create-if。您还成功配置了 9 次适配器,所有适配器都配置为使用 DHCP。您应该ipadm delete-addr在所有 9 次适配器上运行,甚至可能运行ipadm delete-if vmxnet3

完成此操作后,您还应该停止在虚拟机配置中使用 vmxnet3 接口,而改用 e1000 接口,我对这些接口的运气更好。

更多信息:ifconfig 与 ipadm 比较在 OmniOS 中使用 dladm 和 ipadm 设置网络的示例(也适用于其他 Illumos 衍生产品,如 OpenIndiana)。

相关内容