Re: [OmniOS-discuss] network configuration script
Hi, is there an update for vmware-users? Where in the new downloaded iso I have to place my own config-script or the py-script from Michael? I cannot find any in the iso included files after boot/install... With the old installer there was no problem. Greets Frank Thursday, April 6, 2017, 12:43:25 AM, you wrote: FM> Hello Michael, hello Dan, FM> I find your idea great. FM> Because it´s annoying to do the initial network configuration again FM> and again in my test-installations I had integrated in my own FM> OmniOS-ISO the Solaris-vmware-tools and a shellscript for automated FM> installation. It is not perfect but it works for me... FM> But it is also annoying to implement this in every new FM> release-ISO... FM> It would be great, if you can implement something to ease the setup FM> for the millions of vmware-omnios users. ;-) FM> Also your idea to implement for IPoIB is great - I also use IPoIB in FM> some test-scenarios. FM> Greets FM> Frank FM> Sunday, April 2, 2017, 11:30:33 PM, you wrote: MR>> Hi all, MR>> I think it is not very easy for new users coming to Omnios from various MR>> other distros to make the initial network configuration so I have MR>> written a small tool in Python to remedy this obstacle. The script runs MR>> on all Omnios as of r151014. I have tested on r151014 and bloody MR>> (r151021) MR>> The script is not ment to be the swiss army knife for configuring MR>> networks on Omnios so there is no support for vnic, vlan, and MR>> aggregates. It will only support configuring a single nic given the MR>> user the option for dhcp and static setup. The user is also asked MR>> whether to configure dns in which case the user is asked for an IP. MR>> Currently it will only handle ethernet but IPoIB is on my todo list. I MR>> have attached the script here but if the file is to large it can also MR>> be downloaded here: http://git.datanom.net/netconf.git/ MR>> PS. If I want to have it included in Omnios what license should I use? -- Best regards, Frankmailto:info@gmx.de ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] network configuration script
Hello Michael, hello Dan, I find your idea great. Because it´s annoying to do the initial network configuration again and again in my test-installations I had integrated in my own OmniOS-ISO the Solaris-vmware-tools and a shellscript for automated installation. It is not perfect but it works for me... But it is also annoying to implement this in every new release-ISO... It would be great, if you can implement something to ease the setup for the millions of vmware-omnios users. ;-) Also your idea to implement for IPoIB is great - I also use IPoIB in some test-scenarios. Greets Frank Sunday, April 2, 2017, 11:30:33 PM, you wrote: MR> Hi all, MR> I think it is not very easy for new users coming to Omnios from various MR> other distros to make the initial network configuration so I have MR> written a small tool in Python to remedy this obstacle. The script runs MR> on all Omnios as of r151014. I have tested on r151014 and bloody MR> (r151021) MR> The script is not ment to be the swiss army knife for configuring MR> networks on Omnios so there is no support for vnic, vlan, and MR> aggregates. It will only support configuring a single nic given the MR> user the option for dhcp and static setup. The user is also asked MR> whether to configure dns in which case the user is asked for an IP. MR> Currently it will only handle ethernet but IPoIB is on my todo list. I MR> have attached the script here but if the file is to large it can also MR> be downloaded here: http://git.datanom.net/netconf.git/ MR> PS. If I want to have it included in Omnios what license should I use? -- Best regards, Frankmailto:info@gmx.de ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] Fwd: NVMe in ESXi-Passthrough crashes
Hi, I´ve tested now on another machine (HP DL380 G6). The new bloody OmniOS crashes here too... Frank Sunday, October 23, 2016, 3:11:09 AM, you wrote: >> On Oct 22, 2016, at 9:06 PM, Frank M. <info@gmx.de> wrote: >> >> >> I´ve installed the new bloody as a new test virtual machine. The vm >> crashes whenever there is a access to the nvme device. >> Tests with a "special nvme driver" on the last stable had no problems. >> I tested a Samsung SM951 on ESXi 6.0 U2 on a Supermicro X10DRi-T4+. >> Tomorrow I will test shortly a Samsung SM961 on another Server (HP). >> I hope, you will find a solution until the next stable release... DM> Oddly enough: DM> 1.) r151020 (next stable) is coming soon (November). DM> 2.) Due to some interesting circumstances, the NVMe fixes in DM> bloody & 020 may be backported to LTS (014) and last-stable (018). DM> Dan ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
[OmniOS-discuss] Fwd: NVMe in ESXi-Passthrough crashes
Perhaps my post is here better, because I use OmniOS of course... ...and the next stable OmniOS is in sight... This is a forwarded message From: Frank M. <info@gmx.de> To: Illumos Discussion <disc...@lists.illumos.org> Date: Sunday, October 23, 2016, 2:54:16 AM Subject: NVMe in ESXi-Passthrough crashes ===8<==Original message text=== Hi, I´ve installed the new bloody as a new test virtual machine. The vm crashes whenever there is a access to the nvme device. Tests with a "special nvme driver" on the last stable had no problems. I tested a Samsung SM951 on ESXi 6.0 U2 on a Supermicro X10DRi-T4+. Tomorrow I will test shortly a Samsung SM961 on another Server (HP). I hope, you will find a solution until the next stable release... greets from Germany Frank ===8<===End of original message text=== -- Best regards, Frankmailto:info@gmx.de ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
[OmniOS-discuss] bloody update error pkg
Hi, I wanted to update my 151019-test-installation: root@test-san1:/root# pkg update Checking that pkg(5) is up to date - Errors were encountered while attempting to retrieve package or file data for the requested operation. Details follow: http protocol error: code: 404 reason: Not Found URL: 'http://pkg.omniti.com/omnios/bloody/omnios/manifest/0/package%2Fpkg@0.5.11%2C5.11-0.151019%3A20160824T050133Z' (happened 4 times) Frank --- Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft. https://www.avast.com/antivirus ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] LSI 9300-16i SAS and OmniOS?
Hi, I have an new system with a LSI 9300-16i in slot3 of a X10DRi-T4+ motherboard on a 6G-Backplane. In my short tests with barmetal OmniOS there were no problems. But I would use VMware-virtualized OmniOS with passthrough LSI-HBA. And here I have massive problems... The disks/pools crash after a short time with low load. I testet the HBA in another PCIe-slot - I havn´t seen any problems, but I havn´t looked into the logfile. Supermicro recommended to set jumper JI2C1 and JI2C2 to 2-3 - but they were set to this already. So I set the jumper to 1-2. Now disks/pools crash still earlier. The HBA gets very hot, but I testet it also with "special" airflow - the same I attached the logfile... What does it mean "FastPath": Sep 6 15:07:05 test-san1 scsi: [ID 243001 kern.info] w5000cca24200d4fd FastPath Capable and Enabled Sep 6 15:07:05 test-san1 scsi: [ID 243001 kern.info] w443322110600 FastPath Capable but Disabled Sep 6 15:07:05 test-san1 scsi: [ID 243001 kern.info] w5000cca24200d4c9 FastPath Capable and Enabled Sep 6 15:07:05 test-san1 scsi: [ID 243001 kern.info] w5000cca2426fff85 FastPath Capable and Enabled Sep 6 15:07:05 test-san1 scsi: [ID 243001 kern.info] w5000cca24200d33d FastPath Capable and Enabled Sep 6 15:07:05 test-san1 scsi: [ID 243001 kern.info] w5000cca24200d4c9 FastPath Capable and Enabled and later: Sep 6 15:10:19 test-san1 scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@18/pci1000,3130@0 (mpt_sas19): Sep 6 15:10:19 test-san1 MPT Firmware Fault, code: 5854 Sep 6 15:10:21 test-san1 scsi: [ID 365881 kern.info] /pci@0,0/pci15ad,7a0@18/pci1000,3130@0 (mpt_sas19): Sep 6 15:10:21 test-san1 MPT Firmware version v12.0.0.0 (SAS3008) Sep 6 15:10:21 test-san1 scsi: [ID 365881 kern.info] /pci@0,0/pci15ad,7a0@18/pci1000,3130@0 (mpt_sas19): Sep 6 15:10:21 test-san1 mpt_sas19 SAS 3 Supported Sep 6 15:10:21 test-san1 scsi: [ID 365881 kern.info] /pci@0,0/pci15ad,7a0@18/pci1000,3130@0 (mpt_sas19): Sep 6 15:10:21 test-san1 mpt19: IOC Operational. Sep 6 15:10:28 test-san1 scsi: [ID 243001 kern.info] w44332211 FastPath Capable but Disabled Sep 6 15:10:28 test-san1 last message repeated 1 time Sep 6 15:10:28 test-san1 scsi: [ID 243001 kern.info] w443322110100 FastPath Capable but Disabled Sep 6 15:10:28 test-san1 last message repeated 1 time Sep 6 15:10:29 test-san1 scsi: [ID 243001 kern.info] w443322110200 FastPath Capable but Disabled Sep 6 15:10:29 test-san1 last message repeated 1 time Sep 6 15:10:29 test-san1 scsi: [ID 243001 kern.info] w443322110300 FastPath Capable but Disabled Sep 6 15:10:29 test-san1 last message repeated 1 time Sep 6 15:10:29 test-san1 scsi: [ID 243001 kern.info] w443322110600 FastPath Capable but Disabled Sep 6 15:10:29 test-san1 last message repeated 1 time Sep 6 15:10:29 test-san1 scsi: [ID 243001 kern.info] w443322110700 FastPath Capable but Disabled Sep 6 15:10:29 test-san1 last message repeated 1 time Sep 6 15:10:31 test-san1 scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@18/pci1000,3130@0 (mpt_sas19): Sep 6 15:10:31 test-san1 MPT Firmware Fault, code: 5854 Sep 6 15:10:32 test-san1 scsi: [ID 365881 kern.info] /pci@0,0/pci15ad,7a0@18/pci1000,3130@0 (mpt_sas19): Sep 6 15:10:32 test-san1 MPT Firmware version v12.0.0.0 (SAS3008) Sep 6 15:10:32 test-san1 scsi: [ID 365881 kern.info] /pci@0,0/pci15ad,7a0@18/pci1000,3130@0 (mpt_sas19): Sep 6 15:10:32 test-san1 mpt_sas19 SAS 3 Supported Sep 6 15:10:32 test-san1 scsi: [ID 365881 kern.info] /pci@0,0/pci15ad,7a0@18/pci1000,3130@0 (mpt_sas19): Sep 6 15:10:32 test-san1 mpt19: IOC Operational. Sep 6 15:10:40 test-san1 scsi: [ID 243001 kern.info] w44332211 FastPath Capable but Disabled Sep 6 15:10:40 test-san1 scsi: [ID 243001 kern.info] w443322110100 FastPath Capable but Disabled Sep 6 15:10:40 test-san1 scsi: [ID 243001 kern.info] w443322110200 FastPath Capable but Disabled Sep 6 15:10:40 test-san1 scsi: [ID 243001 kern.info] w443322110300 FastPath Capable but Disabled Sep 6 15:10:41 test-san1 scsi: [ID 243001 kern.info] w443322110600 FastPath Capable but Disabled Sep 6 15:10:41 test-san1 scsi: [ID 243001 kern.info] w443322110700 FastPath Capable but Disabled For information: pool1 6x SATA-SSD Raidz2 pool2 4x SAS-HDD 2 mirrored vdev with SATA-SSD l2arc I hope anybody has any useful hints... PS: Tonight I want to test with only one HDD... Frank Sunday, September 4, 2016, 4:46:45 PM, you wrote: BF> On Sun, 4 Sep 2016, Peter Tribble wrote: >> On Sat, Sep 3, 2016 at 10:42 PM, Bob Friesenhahn < >> bfrie...@simple.dallas.tx.us> wrote: >> >>> Is the LSI 9300-16i SAS support in OmniOS known to be robust? >>> >>> I am planning to use it with the SuperMicro SC836BA-R920B 3U case and >>> Supermicro X10DRi-T4+ motherboard to build a storage server. >>> >>> Is there anything about this HBA
[OmniOS-discuss] nvme-device hangs after power-on - after soft-reboot all is okay
Hi, I have a problem with a NVMe-Device Samsung SM951 in a virtualized Illumos-environment. My default setup is a HP G8 Server (I have tried others) as ESXi6.02-Host and a newest OmniOS-bloody-VM. I´ve learned to setup the nvme from here: https://www.mail-archive.com/smartos-discuss@lists.smartos.org/msg02873.html. Also I have read this: https://www.illumos.org/issues/6908 and other informations on web. The progress of my installation you can read here (if you speak german) - please follow all posts of effemmess: http://www.hardwareluxx.de/community/f101/zfs-stammtisch-570052-272.html#post24644356 The problem in http://www.hardwareluxx.de/community/f101/zfs-stammtisch-570052-272.html#post24660135 is solved -it was a old updated vm, now I use an fresh installed vm... But previosly I thought, there is something with the powerstates of the nvme. Because of that I made these additions to /etc/vmware/passthru.map (info is from here: http://www.vmware.com/pdf/vsp_4_vmdirectpath_host.pdf: # Samsung NVMe 144d a801 d3d0 false 144d a802 d3d0 false These additions are active till now... The actual problem is, that after every cold-boot of the vm the nvme hangs. I test this by running the command "format". I cant see in any logs something interesting. Now I reset the vm via second ssh and the command "reboot -p". Now works the nvme very well for hours. As long as I only reboot the vm all is okay, but if I cold-boot the vm, the nvme hangs again. The whole process is reproducible. Gea says in hardwareluxx-forum, he has also problems with "format" with intel-NVMe. Btw, in all Windows-VMs the NVMe runs promptly after every cold-vm-start. Now I testet it in a freshly installed Openindiana-vm - full updated. Here I have a critical fault after every cold-boot and soft-boot. Also a "fmadm repaired dev:pci@0,0/pci15ad,7a0@15/pci144d,a801@0" doesn't help. In summary, the NVMe runs always very well on bar-metal and on Windows-vm's and after soft-boot also very well in OmniOS. Can anybody help? Best regards, Frank ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
