brendanpg's Posts

The XML files in this directory: /var/db/esximg/vibs Have a list of files the packages contain. Example: /var/db/esximg/vibs # cat  vmware-esx-MegaCli-8.07.07--1938763172.xml <vib v... See more...
The XML files in this directory: /var/db/esximg/vibs Have a list of files the packages contain. Example: /var/db/esximg/vibs # cat  vmware-esx-MegaCli-8.07.07--1938763172.xml <vib version="5.0"><type>bootbank</type><name>vmware-esx-MegaCli-8.07.07</name><version>8.07.07-01</version><vendor>LSI</vendor><summary>MegaRAID Command Line Tool for ESX Server</summary><description>MegaRAID Command Line Tool for ESX Server</description><release-date>2012-12-19T15:56:09.224245+00:00</release-date><urls><url key="General info">http://www.lsi.com</url></urls><relationships><depends/><conflicts/><replaces/><provides/><compatibleWith/></relationships><software-tags/><installdate>2015-05-19T10:05:19.933253+00:00</installdate><system-requires><maintenance-mode>false</maintenance-mode></system-requires><file-list><file>opt/lsi/MegaCLI/MegaCli</file><file>opt/lsi/MegaCLI/libstorelib.so</file></file-list><acceptance-level>partner</acceptance-level><live-install-allowed>true</live-install-allowed><live-remove-allowed>true</live-remove-allowed><cimom-restart>false</cimom-restart><stateless-ready>true</stateless-ready><overlay>false</overlay><payloads><payload name="vmware-esx-Mega" type="vgz" size="750181"><checksum checksum-type="sha-256">124e47800bbede149019547cf791f7e902702775be21c2e0211dde00d50b6d45</checksum><checksum checksum-type="sha-1" verify-process="gunzip">385b7360134241da9f1ac9b88361fd72452dcb40</checksum></payload></payloads></vib> Then you can go to this site: http://www.utilities-online.info/xmltojson/ And convert xml to json which is a bit easier to read when scanning for files. output: <snip>         "etc/cim/lsi/lsi_mr.conf",         "etc/cim/lsi/providerTraceLog.properties",         "etc/cim/lsi/resource_default.properties",         "etc/cim/lsi/resource_en.properties",         "etc/cim/lsi/sas_mib.ini",         "etc/cim/openwsman/lsi.conf",         "usr/lib/cim/libint13cmpi.so",         "usr/lib/cim/libstorelib.so",         "usr/lib/cim/libstorelibir-2.so",         "usr/lib/cim/libstorelibir-3.so",         "usr/lib/cim/libstorelibir.so",         "var/lib/sfcb/registration/repository/lsiprovider-500.04.V0.55-0006/lsi/lsimr13/classSchemas",         "var/lib/sfcb/registration/repository/lsiprovider-500.04.V0.55-0006/lsi/lsimr13/qualifiers",         "var/lib/sfcb/registration/repository/lsiprovider-500.04.V0.55-0006/lsi/lsimr13/qualifiers.idx",         "var/lib/sfcb/registration/repository/lsiprovider-500.04.V0.55-0006/root/interop/classSchemas",         "var/lib/sfcb/registration/repository/lsiprovider-500.04.V0.55-0006/root/interop/qualifiers",         "var/lib/sfcb/registration/repository/lsiprovider-500.04.V0.55-0006/root/interop/qualifiers.idx",         "var/lib/sfcb/registration/vmw_lsiprovider-providerRegister" </snip> This could be done with various python utilities but this is a quick and dirty way to do it one the host itself.
Hi jmattson ; I ran into the same problem on a physical Realtek with an injected VIB for ESXi 5.5.U1. Basically link is up, ethtool works on vmnic0 and all offloads are disabled, tcpdump show... See more...
Hi jmattson ; I ran into the same problem on a physical Realtek with an injected VIB for ESXi 5.5.U1. Basically link is up, ethtool works on vmnic0 and all offloads are disabled, tcpdump shows truncated IP, and DHCP addresses dont work and static addresses dont work. I get an error 49 cant unset IP, and then I get a no-router warning from ipv6. So whats interesting is the virtual e1000 from qemu, the realtek from qemu and the 8168 realtek in physical are having the same issues - truncated IP, no DHCP, etc.
They were truncated packets. I have to revive the setup for getting the actual packet data. What would happen would be a few successful pings (sometimes it would ping, sometimes it would not) and... See more...
They were truncated packets. I have to revive the setup for getting the actual packet data. What would happen would be a few successful pings (sometimes it would ping, sometimes it would not) and then the packets would be truncated and anything larger than a minimum sized packet would be truncated. . With ping it would say on the ESXi side "20 bytes missing" or something of this nature when dumping vmk.
Hi, I got everything but networking working with 5.5rollup1 so far on KVM (kernel 3.12.6, libvirt 1.2.0, QEMU 1.7.0, plus the Qemu piix patch from above), plus the following kvm flags: modp... See more...
Hi, I got everything but networking working with 5.5rollup1 so far on KVM (kernel 3.12.6, libvirt 1.2.0, QEMU 1.7.0, plus the Qemu piix patch from above), plus the following kvm flags: modprobe.d]# cat kvm.conf options kvm ignore_msrs=1 modprobe.d]# cat kvm-intel.conf options kvm-intel nested=y ept=y The last piece I am stuck on is the networking. I tried Realtek, e1000 and vmxnet on the kvm side. None of these work with ESXi 5.5, and I cant figure out why. I see some packets, ping will work in some cases - I see truncated packets and larger packets simply dont work. Any ideas on what I can do to get any basic networking - the test harness doesnt need super-high performance.