Hi folks,

I'm scratching my head over SmartOS on a DL360g6 which I've been trying to 
piece together for deployment in a remote datacenter (DR and DNS service), so 
it's smaller / less capable than the machines that I usually run.

Some time ago I tried running SmartOS on these machines with an HP P410i RAID 
controller.  The disk performance at the time was generally unsatisfactory, but 
there's a new driver for that controller family effective late last year ( 
https://smartos.org/bugview/OS-5564 ) so I figured I'd give it a try.

I'm running 20170608T172228Z on all the other machines around here so I figured 
I'd give it a go on this one as well.  Booted fine from the USB, zpool was a 
ZFS mirror of two drives on the HP controller configured as singles.  
Everything seemed to come up OK, disk performace was adequate but nothing to 
write home about...  but creating a VM timed out waiting for the VM to become 
ready...  vmadm list showed the VM in provisioning status...  and it eventually 
went to "running".

Odd.  Well, maybe 6g was not enough ram for it to be truly happy.  I upped the 
memory to 24g.  No dice same deal.

OK, must be the disk subsystem right?  Picked up some HP H220s (SAS2308 aka 
9207s) and reflashed to IT mode.  System boots but throws an odd error in the 
middle of booting:  "warning: KCS error: ff" - Google tells me little except 
that maybe bmc is weird about the card.  Disabled the built-in SmartArray just 
in case.

Disk array faster for copy across the network (getting 110-112 MByte/sec on 
gigabit ethernet vs. 75-80 before).  zpool scrub operates as expected -  "37.6G 
scanned out of 102G at 134M/s, 0h8m to go".  And still, vmadm create runs out 
the clock:

[root@00-23-7d-e8-af-38 /zones/rs]# time vmadm create -f test29.json 
first of 1 error: timed out waiting for zone to transition to running

real    0m57.031s
user    0m2.322s
sys     0m1.847s
[root@00-23-7d-e8-af-38 /zones/rs]# 

Maybe it's the hard drives?  HP 146g 10k SAS drives shouldn't be slow right?  
Tried upgrading to 600g 10k WD Velociraptor SATA drives.  Same deal.  And still 
the KCS error.

I'm kind of puzzled at this point.  I've run SmartOS on things far less capable 
than a single die (4 core) L5520, so reasonably sure it's not CPU.  Anyone have 
ideas?  Thoughts on tracing?  Sysinfo output is below.

-r

[root@00-23-7d-e8-af-38 ~]# sysinfo
{
  "Live Image": "20170608T172228Z",
  "System Type": "SunOS",
  "Boot Time": "1503016030",
  "SDC Version": "7.0",
  "Manufacturer": "HP",
  "Product": "ProLiant DL360 G6",
  "Serial Number": "MXQ91704UG",
  "SKU Number": "504636-001",
  "HW Version": "",
  "HW Family": "ProLiant",
  "Setup": "false",
  "VM Capable": true,
  "CPU Type": "Intel(R) Xeon(R) CPU L5520 @ 2.27GHz",
  "CPU Virtualization": "vmx",
  "CPU Physical Cores": 2,
  "UUID": "35303436-3336-4d58-5139-313730345547",
  "Hostname": "00-23-7d-e8-af-38",
  "CPU Total Cores": 8,
  "MiB of Memory": "24565",
  "Zpool": "zones",
  "Zpool Disks": "c0t50014EE657986649d0,c0t50014EE6ACEDBAE8d0",
  "Zpool Profile": "mirror",
  "Zpool Creation": 1503015684,
  "Zpool Size in GiB": 538,
  "Disks": {
    "c0t50014EE657986649d0": {"Size in GB": 600},
    "c0t50014EE6ACEDBAE8d0": {"Size in GB": 600}
  },
  "Boot Parameters": {
    "console": "vga",
    "vga_mode": "115200,8,n,1,-",
    "root_shadow": "xxxxxx",
    "smartos": "true",
    "boot_args": "",
    "bootargs": ""
  },
  "Network Interfaces": {
    "bnx0": {"MAC Address": "00:23:7d:e8:af:38", "ip4addr": "172.30.251.93", 
"Link Status": "up", "NIC Names": ["admin"]},
    "bnx1": {"MAC Address": "00:23:7d:e8:af:3a", "ip4addr": "", "Link Status": 
"down", "NIC Names": []}
  },
  "Virtual Network Interfaces": {
  },
  "Link Aggregations": {
  }
}
[root@00-23-7d-e8-af-38 ~]# 






-------------------------------------------
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Reply via email to