Recent content by mram

Reboot the ESXi host. I had better luck rebooting vs just restarting the services.

On ESXi 7 it was set to 0 which I assumed meant disabled, but that doesn't work on ESXi 6.x. I guess the hunt for the best setting continues.

I did see one example with maxSessionCount as high as 50,000. Not sure if you went that high. It's worth a shot.

The changes to vpxa.cfg and config.xml should work. During my research 6.5 was listed as applicable in the documentation.

Something is not right there. I am importing a 32GB test VM in 12 minutes over a 1Gig connection in the lab.

When editing with vi, save with ESC : w! which will write it anyway.

I have 2 settings I am testing now. After reboot the hostd file change was not enough. I will post again after another reboot and import test in about 30 minutes. Added: Here is what I am testing [root@localhost:~] grep -wns '<soap>' /etc/vmware/hostd/config.xml -A 4 323: <soap> 324-...

I believe I have the fix for the 6.5/6.7 users. I am now able to successfully import on 6.7. SSH into your ESXi server and run this: sed -i 's,</soap>, <maxSessionCount>0</maxSessionCount>\n </soap>,' /etc/vmware/hostd/config.xml && /etc/init.d/hostd restart You can check the hostd config...

Not seeing Config.HostAgent.vmacore.soap.maxSessionCount on 6.7 Update 2 either. But if that 500 is in seconds (8.3 minutes) then that is exactly how long mine runs until it times out. Mar 28 15:55:22 Mar 28 16:03:14 node-a root@pam VM 100 - Create Error: unable to create VM 1... Added: I...

My R730xd servers loaded 8.02 fine. It was the odd QCT nodes that failed to boot for me. Reloading with 7.4 and upgrading worked fine.

Having the same issue with a clean reload on some nodes with 8.0-2.

I have seen the same issue as OP on Toshiba SAS drives only. My Hitachi SAS drives are correct. The WWN number returned by /dev/disk/by-id/ and smartctl is 1 higher than what is printed on the label. Note the serial number matches. # smartctl -i /dev/disk/by-id/wwn-0x500003992892bdf1 smartctl...

Nope. That's a default looking fstab file.

I would get something like that when other mount points in my /etc/fstab changed. Not sure if that will help in your situation.

I want to thank the Proxmox team for yet another amazing update with v5. This post is just for information for anyone out there running a ZFS cluster with no shared storage. It is possible to live migrate QEMU VMs but you cannot use the GUI (yet). If you attempt to migrate a running VM using ZFS...