Re: vmx bug?

Ok, but probably interface renumbering was not checked in those bug. Here is similar topic https://forum.pfsense.org/index.php?topic=95621.0 Here is pciconf: [root@freebsd11-template ~]# pciconf -lv hostb0@pci0:0:0:0: class=0x06 card=0x197615ad chip=0x71908086 rev=0x01 hdr=0x00 vendor

Re: vmx bug?

; ethernet0.pciSlotNumber = "192" ethernet1.pciSlotNumber = "224" ethernet2.pciSlotNumber = "256" ethernet3.pciSlotNumber = "1184" <== vmx0 !!! 2017-05-18 6:52 GMT+03:00 Ryan Stone <ryst...@gmail.com>: > > On Wed, May 17, 2017 at

Re: vmx bug?

2017-05-18 15:43 GMT+03:00 Gary Palmer : > > Out of curiosity, if you install sysutils/dmidecode from ports and > run > > dmidecode -t 41 > > does it help at all? This table is empty on VM: [root@freebsd11-template ~]# dmidecode -t 41 # dmidecode 3.0 Scanning /dev/mem for

vmx bug?

Hi! Recently I found a bug with numbering four (and probably more) vmxnet3 interfaces under ESXi 6.5 (FreeBSD 11.0-RELASE, 10.0-RELEASE and ESXi 5.5U1 reproduced). It seems that this is an old bug https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198406 : > Just reproduced this bug on ESXi