On 2014-08-21 12:16, Mathias Picker wrote:
> On Do, 2014-08-21 at 08:49 -0700, Peter Grehan wrote:
>> Hi Mathias,
>>> twin# ifconfig
>>> igb0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric
>>> 0 mtu 1500
>>>
>>> options=400b8<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO>
>>>          ether 0c:c4:7a:05:81:be
>>>          inet 1yy netmask 0xffffffc0 broadcast 1yy
>>>          inet6 fe80::ec4:7aff:fe05:81be%igb0 prefixlen 64 scopeid 0x1
>>>          inet 1xx netmask 0xfffffff8 broadcast 1
>>>          inet 1xx netmask 0xffffffff broadcast 1
>>>          inet 1xx netmask 0xffffffff broadcast 1
>>
>>   Looks like there might be an error with the IPv4 config of the igb0 
>> interface - those addresses appear to be invalid. Though, that shouldn't 
>> really matter for a bridged config.
>>
> 
> I just edited them a bit...
> 
>>> bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu
>>> 1500
>>>          ether 02:3d:80:23:57:00
>>>          nd6 options=1<PERFORMNUD>
>>>          id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
>>>          maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
>>>          root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
>>>          member: tap8000 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
>>>                  ifmaxaddr 0 port 5 priority 128 path cost 2000000
>>>          member: igb0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
>>>                  ifmaxaddr 0 port 1 priority 128 path cost 20000
>>
>>   That looks Ok.
>>
>>> tap0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
>>>          options=80000<LINKSTATE>
>>>          ether 00:bd:15:8e:4a:00
>>>          nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
>>>          media: Ethernet autoselect
>>>          status: no carrier
>>> tap8000: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST>
>>> metric 0 mtu 1500
>>>          options=80000<LINKSTATE>
>>>          ether 00:bd:76:11:59:40
>>>          nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
>>>          media: Ethernet autoselect
>>>          status: active
>>>          Opened by PID 30817
>>>
>>> bhyve is started like this:
>>>
>>> /usr/sbin/bhyve -c 1 -m 2048 -A -H -W -s 0,hostbridge -s
>>> 2,ahci-hd,/usr/local/vmrc/vm//zimbra-centos-six.five0/zimbra-c
>>> entos-six.five0.img -s 3:0,virtio-net,tap8000 -s 5,lpc -l com1,stdio
>>> zimbra-centos-six.five0
>>>
>>> So, from what I understand, the tap device is created, bridged, and put
>>> correctly in the bhyve incantation.
>>>
>>> So: why do I not have a network card in centos:
>>
>>   Can you try a 'lspci -vv' at the Linux shell prompt ? That will show 
>> if the virtio-net PCI device was at least probed.
> 
> No lspci in the base centos iso I'm afraid... Is there a way to access
> the local (FreeBSD) disk, so I can ship in pciutils?
> 
> 
>>
>>   When you did the initial install, was any networking configured ?
> 
> You mean the centos install? No, nothing.
>>
>> later,
>>
>> Peter.
>>
> 
> 
> _______________________________________________
> freebsd-virtualization@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to 
> "freebsd-virtualization-unsubscr...@freebsd.org"
> 

Try 'ifconfig -a' in the VM

If an interface is not 'up', it might not be listed in 'ifconfig'

-- 
Allan Jude

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to