Hi there,
thx for the Info. but this is not really an workaround to shutdown the service .
this solves not the root cause Sfcbd rebounce all the time. also not fitable once doing essentially HW monitoring over cim.
the current solution in my Case i found in an HP pdf.
http://h20195.www2.hpe.com/v2/getpdf.aspx/4AA3-1055ENW.pdf?ver=1.0
thx
max
I've just found that it's no longer working on ESXi 6.0U2 (5572656). I have the latest SMIS provider VIB installed from Avago, but no luck. All I can see is that my MSM is sending SYN packets to the ESXi host on 3071
Has anyone else bumped into this?
i'm having the exact same issue. I was able to use online upgrade process using vfont-d all the way up to ESXi 6.5 Update 1 (Security only) build 5969300 with out a problem.
I'm just 1 version update behind the full 6.5 U1 update.
When you look at the error output, it complains about a non zero exit status on one of the command executions.
Exception: /sbin/partedUtil getptbl /vmfs/devices/disks/mpx.vmhba32:C0:T0:L0 failed to execute: status(255)
Troubleshooting 101 says, attempt to run that execution myself and see what's going on.
[root@VMhost:/dev/disks] /sbin/partedUtil getptbl /vmfs/devices/disks/mpx.vmhba32:C0:T0:L0
Error: The device /dev/disks/mpx.vmhba32:C0:T0:L0 is so small that it cannot possibly store a file system or partition table. Perhaps you selected the wrong device?
Unable to get device /vmfs/devices/disks/mpx.vmhba32:C0:T0:L0
Okay so this is where it choked for sure.
The ESXI installer formats and makes multiple partitions on my USB drive where ESXi is running from which is typical.
Here's the lay out of my USB which is running build 5969300 just fine.
[root@VMhost:/dev/disks] ls -l | grep mpx.vmhba32
-rw------- 1 root root 18302628885633696256 Sep 10 20:11 mpx.vmhba32:C0:T0:L0
-rw------- 1 root root 4161536 Sep 10 20:11 mpx.vmhba32:C0:T0:L0:1
-rw------- 1 root root 262127616 Sep 10 20:11 mpx.vmhba32:C0:T0:L0:5
-rw------- 1 root root 262127616 Sep 10 20:11 mpx.vmhba32:C0:T0:L0:6
-rw------- 1 root root 115326976 Sep 10 20:11 mpx.vmhba32:C0:T0:L0:7
-rw------- 1 root root 299876352 Sep 10 20:11 mpx.vmhba32:C0:T0:L0:8
-rw------- 1 root root 2684354560 Sep 10 20:11 mpx.vmhba32:C0:T0:L0:9
lrwxrwxrwx 1 root root 20 Sep 10 20:11 vml.0000000000766d68626133323a303a30 -> mpx.vmhba32:C0:T0:L0
lrwxrwxrwx 1 root root 22 Sep 10 20:11 vml.0000000000766d68626133323a303a30:1 -> mpx.vmhba32:C0:T0:L0:1
lrwxrwxrwx 1 root root 22 Sep 10 20:11 vml.0000000000766d68626133323a303a30:5 -> mpx.vmhba32:C0:T0:L0:5
lrwxrwxrwx 1 root root 22 Sep 10 20:11 vml.0000000000766d68626133323a303a30:6 -> mpx.vmhba32:C0:T0:L0:6
lrwxrwxrwx 1 root root 22 Sep 10 20:11 vml.0000000000766d68626133323a303a30:7 -> mpx.vmhba32:C0:T0:L0:7
lrwxrwxrwx 1 root root 22 Sep 10 20:11 vml.0000000000766d68626133323a303a30:8 -> mpx.vmhba32:C0:T0:L0:8
lrwxrwxrwx 1 root root 22 Sep 10 20:11 vml.0000000000766d68626133323a303a30:9 -> mpx.vmhba32:C0:T0:L0:9
When it calls the drive with out a specific partition number, it returns no size and an error code as shown above. The individual partitions do however return a result just fine.
[root@VMhost:/dev/disks] /sbin/partedUtil getptbl /vmfs/devices/disks/mpx.vmhba32:C0:T0:L0:5
unknown
31 255 63 511968
[root@VMhost:/dev/disks] /sbin/partedUtil getptbl /vmfs/devices/disks/mpx.vmhba32:C0:T0:L0:6
unknown
31 255 63 511968
[root@VMhost:/dev/disks] /sbin/partedUtil getptbl /vmfs/devices/disks/mpx.vmhba32:C0:T0:L0:1
unknown
0 255 63 8128
This looks like a definitive logic bug to me that needs to be resolved by VMware. Either the version partedUtil getptbl is out of date and doesn't know how to deal with reading the disk with out a partition number or the installation script should be reading the individual partitions and not the disk identifier to get the size. A USB stick being 3GB or 300 GB will have no effect on an error like this so this is not a hardware requirement issue. It could be the USB stick and drive formatting is at fault but I don't think so. I decided to take a USB stick with a different ESXi installation on it and run the same partedUI command against the USB stick with out using the partition number and got the same error. I also got this error before upgrading to build 5969300 and the upgrade installer was able to read and upgrade to my USB stick just fine so i'm nearly positive this is a bug on the VMware side
If anyone knows a workaround to this or where else this should be posted to get the proper attention, I'm all ears.
thanks million parmarr
seems that "esxcli network standard add -v" just created a standard vswitch.
I want to attach/detach these vswitches to guests via ESXi shell. ( after vguests are deployed.)
thank you
Hi All,
After a long night on the phone toe VMware support, the fix was a relatively simple one. Somehow, when creating snapshots, the disk file had moved itself onto the mirror drive (which is where the config file was based) possibly due to a setting that leaves the disks files in the same place as the config file, that may have been set long ago. As such all of the change data since the snapshot had started to accumulate on the mirror drive.
I simply had to power down both VMs, create a new snapshot (to ensure all the snapshot data was captured, in case any snapshots had been deleted in the interim) THEN delete all snapshots which consolidates all the data into the flat files which were in the correct directories.
The key difference was POWERING DOWN the VMs. As if you delete snapshots/consolidate with the VMs POWERED UP you got the repeated error like I did earlier that the drive didn't have enough free space. This is because during the process of deleting/consolidating creates a helper snapshot ONLY when the VMs are POWERED UP, so if they are POWERED DOWN you don't need this extra file and subsequently little or no additional space on the drives, extra space which you get from the RAM of the VMs when they are powered down.
The technician stressed the fact that if you have a lot of snapshot data, the consolidation process can be quite long. You cannot power up the VMs during this consolidation period. The process is quicker based on your hardware and available resources, so luckily for us with new hardware and no other VMs running we had a fair amount of resources to throw at it, so it was relatively quick. He also stressed that if the host was shut down/lost power during the consolidation process, the files could become corrupted. He also mentioned that if the change files are large, the process can appear to get "stuck" at a certain percentage. He linked me a help article to use the SSH to give a better idea of if the process is actually moving along:
Snapshot removal task stops at 99% in ESXi/ESX (1007566) | VMware KB
I hope this information is useful to others, I do not know enough about VMware to say whether or not this might be applicable to you, so take it with a grain of salt.
If you have a support contract, definitely give VMware a buzz if you can, they were very helpful for me!
Thanks for your help,
Daniel
Thanks for your help !
Nope. Ended up ditching the USB tuner, and getting a HDHomeRun network tuner instead. Works like a charm.
One way you can do V2V. or Exporting from v4.0 version & importing to v6.5 after shutdown.
Folks,
Is there a way to configure a virtual HDD connected to the guest via a USB controller?
I have a need to create a virtual device that looks to the guest as a USB connected Mass Storage Device.
It seems like the guest configuration dialogs only allow adding actual USB devices unto a USB controller, but not hard drives. HDDs seem to be connectable via a plethora of controllers (IDE, SATA, SAS etc.) but not USB.
Can this be done in ESXi?
Thanks!
If both ESXi/vCenter hosts are configured Shared Datastore..? If yes. You can unregister VM in 4.0 ESXi/vCenter and register it in 6.5 ESXi/vCenter .
If not a shared Datastore, then you need to do V2V.
Hi ,
If you have shared storage please un-register from 4.0 and register on 6.5 , Take snapshot , upgrade hardware ad update vmware tools
For v2v , you have use vmware converter and i didn't find the version compatible with 6.5 , please find below
VMware Product Interoperability Matrices
still you may try this option on 6.5 else , move to 6.0 then update to 6.5 .
Do I understand this correctly ?
You want to create a normal virtual disk backed up by a VMDK on a standard datastore and configure it in such a way that the guestOS perceives it as a USB-device ?
That is impossible as far as I know.
vCenter Server (5.5.0 Build 4180647) on Network A (192.168.1.10/32)
ESXi HOST (5.5.0 Build 1331820) on Network B (192.168.2.10/32)
vSphere Client 5.5.0 4032365 on Network A to manage vCenter Server and HOSTs
Both networks are behind separate Meraki MX Security Appliances and have a working VPN over WAN (Meraki autoVPN).
Site-to-site VPN ACL (all ports open for troubleshooting purposes).
all traffic from 192.168.1.10/32 to 192.168.2.10/32 is allowed
all traffic from 192.168.2.10/32 to 192.168.1.10/32 is allowed
- vCenter Server receives heartbeat packets from the HOST and stays connected.
- If I "open console" from vCenter Server on any of the virtual machines running on the ESXi HOST on Network B I get "Unable to connect the MKS: Could not connect to pipe \\.\pipe\vmware-authdpipe within retry period".
- If I "open console" from vSphere client directly connected to the HOST it works as expected.
I have tried refreshing the VMX/MKS SSL cache in the virtual machine as explained by this vmware kb article: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2115126
I'm also getting errors from Veeam Backup and Replication:
"Getting VM info from vSphere
Error: NFC storage connection is unavailable. Storage: [stg:datastore-25366,nfchost:host-25365,conn:FQDNvCenterServer]. Storage display name: [DATASTORENAME]. Failed to create NFC download stream. NFC path: [nfc://conn:FQDNvCenterServer,nfchost:host-25365,stg:datastore-25366@FILENAME.vmx]."
Any suggestions would be appreciated.
Regards
Ronny
Hi all,
I would like to ask, if there is any limit for number of local users in case of VMware vSphere 5 Hypervisor, licensed for 1 physical CPU.
We have more users using and managing different VMs in our office. It would be nice if each user will have own vSphere local username with assigned rights to his VMs. But I didn't find any information if there is any limit to this in case of free license. 5 users will be OK for us. We don't share access to our server outside company, we are using it only internally.
Thanks in advance for any comments
... and just a few minutes after posting this I'm able to access the VMs via vCenter Servers "open console". Frustrating...
The last think I tried was connecting directly to the HOST and "opening console" from there. Maybe this had something to do with solving the issue?! Other than that I don't know.
Virtual machine under ESXi 6 shows invalid. I'm not sure how to proceed and this system was setup a while back and I have no record from the previous admin as to the account with VMware. I called support but the woman on the phone wouldn't help me without the purchase order or the account. This VM is only a print server and our update server for ESET antivirus. We are getting ready to upgrade everything to a full VM system and won't need this VM but that will be roughly 3 months away and I would rather not trash this one and redo it if possible. Any help would be appreciated!
Edit: The machine will not boot, all options to edit the VM are gray'd out.
How are you installing VMTools Interactive or automatic? Are you suppressing the drivers like Audio, Filesharing, Sync, Network Introspection ?
Try disabling there drivers and if possible disable VSS driver as well during VMTools re-installation? The above fix which i provided earlier was given by VMware Technical Support, in your case its not so suspecting the above given drivers if not disabled .
NOTE: Network Introspection feature comes with NSX, if not using NSX's this feature disable this driver, i have seen many backup issues due to this as well, its also a VMware Finding.
Check Blow if this can help, usually you can try to re-register VM :
How to register/add a VM to the Inventory in vCenter Server (1006160) | VMware KB
Hello nparas5,
i install /update Tools 10.1.10 interactive. The only disabled option is VMCI-Driver, so no NSX and File Share.
Of course I can disable VSS, but I want the Backup-Snapshot with the VMWARE VSS. And it works.... more often than not with Tools 10.1.10.
I have 2 further Server 2012R2 VM's... Both working great and do not suffer from this "Bug". Maybe its a combination of 2012R2 and Installed Exchange 2013?
But, like i wrote before, with Version 9.10.5 these snapshot Problems do not appear. ( See screenshot some Posts above)