spravtek's Posts

Ah yes, LUN sizing, sorry, should drink more coffee first ... Doesn't the size depend on the amount of linked clones, there's an example of how to calculate this in the document I referenced to in my previous post. Don't know of any other recommendations really ...

I think the consensus is RAID10, but some people choose RAID5 for added storage and being it all SSD, IOPs is mostly a non-issue, unless you really need very high IOPs... But as most of the time, your mileage may vary ... Just for reference: http://www.vmware.com/files/pdf/view_storage_considerations.pdf

Just my 2c. ... I've seen a lot of environments, using all kinds of storage, ranging from NFS to Fiber, iSCSI ... And so on ... Most of the environments never had any issues with shared storage, doesn't matter what technology was used. The environment that did have issues are plenty too, but there was always some reason for it, wrong configuration, hardware or software problems, network issues, something. It all comes down to really hunt for the cause, sometimes it's very difficult, sometimes it can be something like firmware of a hba not being up to date, conflicting ip-addresses or whatever. For some cases it took days if not weeks before the issue was found, depending on how frequent the issues occured or just how much resources were available to research the problem. In short, I don't really have a preference, and all technologies have their own challenges when it comes to troubleshooting. ymmv...

Sorry, was away ... The only thing I can think of now is maybe permission errors on the keys, but then it should also fail when not in lockdown mode, did you run ssh -vvv root@192..., anything in your logs (local station)?

Woops, read right over that, sorry ... Still saw these errors (dev "mpx.vmhba32:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x26 0x1.) ... So yeah... Since I don't have an LSI I can't test things, I'll have a talk with some friends, see if any of them have LSI.

Hi, Can you check this KB please: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1030265 It relates to your IO device as well (LSI1064E). Might help the stability and who knows, the passthrough as well...

The hidden devices can have something to do with it if it is a converted machine yes, check this article: http://support.microsoft.com/kb/315539 See if you can find some hidden network devices that can cause issues ...

It will be difficult to troubleshoot without actually seeing what is going on or how it is configured, if possible post some screenshots of the network settings of the VM and maybe an ipconfig /all ... Do you have any other VM's installed on this ESXi host? No hidden devices in the devmgr? (eg hidden nic) Is the VM deployed from a template, newly deployed or ??? We'll need all the info we can get.

Hi, Could you answer some questions to give us a better picture of the issue? What's the OS? VMware Tools installed? Can you ping something (eg Gateway) from "inside" the VM? Did you try changing the nic type (e1000, VMXNET3)? What troubleshooting steps did you already try? Thanks,

Hey, The /etc/hosts should look something like this: "127.0.0.1  localhost.x.x.domain localhost localhost.localdomain" I never had to actually put in the kickstart, nor really had to play too much with the /etc/hosts on esxi hosts, but it might help solve the issues you're having, it sure is acting a little weird though.

dGeorgey's suggestion is worth a try ... The firstboot logs could be saved to persistent storage using something like this: # copy %firstboot logs to persisted datastore cp /var/log/hostd.log "/vmfs/volumes/$(hostname -s)_datastore1/firstboot-hostd.log" cp /var/log/esxi_install.log "/vmfs/volumes/$(hostname -s)_datastore1/firstboot-esxi_install.log"

Hi, According to the installation-setup guide, the Belgian keyboard should still be available, I haven't tested it myself since I'm not fond of Azerty so can't verify (Page 147 of http://pubs.vmware.com/vsphere-55/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-55-installation-setup-guide.pdf) If you run the command for enabling the ssh after the installation (if it is succesful), do you get any errors, or do you get/see any errors during the deployment regarding this?

Hi, What OS/Application is the VM running? Maybe you could check the VSS of the VM, if VSS is used of course, check: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1031298 Test if the backup works without quiescing... The KB mentions the disabling of the feature. If the machine is producing too much IO during the backup, the quiescing can fail.