Date: Thu, 18 May 2017 13:43:11 +0100 From: Gary Palmer <gpalmer@freebsd.org> To: Andrew Vylegzhanin <avv314@gmail.com> Cc: Ryan Stone <rysto32@gmail.com>, freebsd-net <freebsd-net@freebsd.org>, freebsd-virtualization@freebsd.org Subject: Re: vmx bug? Message-ID: <20170518124311.GB89273@in-addr.com> In-Reply-To: <CA%2BBi_YgQWMz83bxJtU9dFLXZv=M%2BcTegsB6KgVnawGft7J0WwQ@mail.gmail.com> References: <CA%2BBi_Ygn89Tg5DVG=x%2B0-NLQxCk_BTQj4dK2jBN63nUGc5%2BU5w@mail.gmail.com> <CAFMmRNw2HUwMMHeDcXejLejMTxGf0cz5iEnY4ZTHaGq2P%2Bh-mA@mail.gmail.com> <CA%2BBi_Yh5-JgxafxXjF=xwd4sZM91vrbU5xOVsx%2Bq9KFJQLM_pA@mail.gmail.com> <CAFMmRNzCGiERmeKr1_A21vX_FRdZxoH%2BYLn=7Y9Tox3jzGD6jw@mail.gmail.com> <CA%2BBi_YgQWMz83bxJtU9dFLXZv=M%2BcTegsB6KgVnawGft7J0WwQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, May 18, 2017 at 08:39:24AM +0300, Andrew Vylegzhanin wrote: > I will test this VM with Linux tomorrow. > > Just for information, here is part of .vmx file with pci related conifg: > > pciBridge0.present = "TRUE" > > pciBridge4.present = "TRUE" > pciBridge4.virtualDev = "pcieRootPort" > pciBridge4.functions = "8" > pciBridge5.present = "TRUE" > pciBridge5.virtualDev = "pcieRootPort" > pciBridge5.functions = "8" > pciBridge6.present = "TRUE" > pciBridge6.virtualDev = "pcieRootPort" > pciBridge6.functions = "8" > pciBridge7.present = "TRUE" > pciBridge7.virtualDev = "pcieRootPort" > pciBridge7.functions = "8" > pciBridge0.pciSlotNumber = "17" > pciBridge4.pciSlotNumber = "21" > pciBridge5.pciSlotNumber = "22" > pciBridge6.pciSlotNumber = "23" > pciBridge7.pciSlotNumber = "24" > vmci0.pciSlotNumber = "33" > ethernet0.pciSlotNumber = "192" > ethernet1.pciSlotNumber = "224" > ethernet2.pciSlotNumber = "256" > ethernet3.pciSlotNumber = "1184" <== vmx0 !!! Out of curiosity, if you install sysutils/dmidecode from ports and run dmidecode -t 41 does it help at all? Some PC vendors have taken to doing odd things with their PCI layout which produce unexpected results with device naming (so port 1 on the back of the server is not the first interface in the OS) and introduced DMI type 41 as a "fix" e.g. see https://linux.dell.com/files/whitepapers/consistent_network_device_naming_in_linux.pdf Regards, Gary > 2017-05-18 6:52 GMT+03:00 Ryan Stone <rysto32@gmail.com>: > > > > On Wed, May 17, 2017 at 7:32 PM, Andrew Vylegzhanin <avv314@gmail.com> > wrote: > >> > >> > >> vmx0@pci0:4:0:0: class=0x020000 card=0x07b015ad chip=0x07b015ad rev=0x01 > hdr=0x00 > >> > >> vendor = 'VMware' > >> > >> device = 'VMXNET3 Ethernet Controller' > >> > >> class = network > >> > >> subclass = ethernet > >> > >> vmx1@pci0:11:0:0: class=0x020000 card=0x07b015ad chip=0x07b015ad > rev=0x01 hdr=0x00 > >> > >> vendor = 'VMware' > >> > >> device = 'VMXNET3 Ethernet Controller' > >> > >> class = network > >> > >> subclass = ethernet > >> > >> vmx2@pci0:19:0:0: class=0x020000 card=0x07b015ad chip=0x07b015ad > rev=0x01 hdr=0x00 > >> > >> vendor = 'VMware' > >> > >> device = 'VMXNET3 Ethernet Controller' > >> > >> class = network > >> > >> subclass = ethernet > >> > >> vmx3@pci0:27:0:0: class=0x020000 card=0x07b015ad chip=0x07b015ad > rev=0x01 hdr=0x00 > >> > >> vendor = 'VMware' > >> > >> device = 'VMXNET3 Ethernet Controller' > >> > >> class = network > >> > >> subclass = ethernet > > > > > > Everything appears to be enumerated in the proper order. Do other OSes, > say Linux, somehow enumerate in a different order? > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170518124311.GB89273>