Hi,

After an upgrade from 6.0 to 6.5, and 6.7 (VSphere hosts and VCenter), I'm unable to use Content Libraries.

I'm able to create one, either on local datastores or NFS remote storages. But when I try to display information, I end up with a result like this :

Right now, I'm even able to upload an OVA in the Content Library without error. Unfortunately, as you can imagine, freshly uploaded template remains unable.

What I've tried :

• Use either HTML5 or Flex interface. Same symptom.
• Looked at KB2151085 details. Unfortunately, my content-library service is up and running, and I don't have "ts-config.properties.rpmnew" file.
• Tried as administrator@vsphere.local. Same behaviour.

Any ideas ?

Thanks for your help,

Hi there,

We have recently upgraded our vCenter appliance from 6.5 to 6.5 Update 1.

Since then, the Update Manager Tab in the webclient is not working anymore, we always receive the following error message:

interface com.vmware.vim.binding.integrity.VcIntegrity is not visible from class loader

Many thanks in advance for your help.

Best regards

Reto

Hello

Not making much progress replacing the vCenter self signed certificates - using hybrid method, so only looking to update the ssl cert for web interface..  We are using our own CA.

So method we have used:

1. Used certificate-manager option 1 / option 1 to get a default .csr and .key file.  We did this so vCenter generated the private key.
2. Then used OpenSSL to create the real csr.  We created out own req.config with the cert info and used:
   openssl req -new -key vmca_issued_key.key -out vcenter.csr -config req.conf
3. Took vcenter.csr to our CA and issued a certificate.  NB: This CA has a intermediate certificate.
4. We exported RootCA.cer and IntermediateCA.cer certs and created a full machine chain:
   copy vcenter.cer+IntermediateCA.cer+RootCA.cer machine_chain.cer
5. Back on vCenter used certificate-manager option 1 / option 2 to import new certs:
   custom certificate for machine ssl: machine_chain.cer
   custom key for machine ssl: vmca_issued_key.key
   signing certificate of the machine ssl: RootCA.cer
   
6. This is where we are seeing errors.

error 20 at depth lookup:unable to get local issuer certificate

Error verifying certificate: machine_chain.cer

Googled around and it was suggested that the signing cert needed intermediate and root, so did copy IntermediateCA.cer+RootCA.cer inter_and_root_chain.cer and used this cert for signing certificate of the machine ssl.  This time got a different error:

error 51 at 0 depth lookup:unsupported name constraint type

Error in verifying certificate: machine_chain.cer

Does anyone have any suggestions or come across this?

Thanks

Hi

When I open a console in Vsphere web client 6.5 it opens a new tab and after opens a new vmrc window.

How do I prevent the new tab to be opened (both in firefox and chrome) and only open vmrc?

Best regards

Jorge

Hello

I downloaded vmrc in English but the language it presents is Portuguese Brazil.

How do I change to English?

Best regards

Jorge

I've been looking at stats for years and thought I was pretty good at understanding them, but I had never thought about, or needed to, look at Ready time historically into a specific time frame with vCenter perf charts. 

Lets say I select a time frame between 12noon and 1pm for the prior day?   Would I take the summation values and /200 because the interval is only 1 hour?  Not sure how the stats are presented when you select an historical time slot..

Any ideas?

We are trying to get SSL certs in place in our VMWare environment and while I am making progress its really painful.  In the past I had suggested we have vCenter be a subordinate certificate authority off our root CA like VMWare best practice.  That was shot down.  I am going to reopen that debate. 

One question I have is how does VMware Certificate Authority behave when you have multiple vCenters joined together in Enhanced Link Mode?  Am I going to have make each PSC its own Certificate Authority?

Thanks in advance for any insight

Hi Folks, I am trying to convert a Win7 32 bit physical machine to VM using VMware converter standalone. After around 96% it gives me an error and stops working of :-

Error: An error occurred during reconfiguration.

I fired up the VM and the windows is not loading up, I tried assigning  the the drive letter to physical system disk volume but no luck, Also tried many different things to make it work but unfortunately it is not working.

Any ideas or suggestion would be appreciated. Thanks. Veer.

Message was edited by: Viram Bhutiya

This is very strange:

I just deployed a new vSphere 6.0 VCSA and am using the webclient (currently Firefox on Win 10) to configure the system.  When I create a new object, there are dialog boxes that require me to input data; for example "New Distributed Port Group" prompts me to input the port group name.  The problem is that the web client is not receiving my keystrokes.  The workaround is everytime I run into a dialog box requiring keystrokes (such as inputting an object name, etc.) I have to click the Windows start button (changing focus away from the browser window) then re-click on the input box and begin typing and it works normally.... until the next dialog box is displayed where I have to click away, then return to finish entering data.  I've seen this before on another completely separate system but never chased down the solution.

Anyone else seen this and have a recommendation?

I am new to VMWare.  My question is very similar to Converter 6 -  Partition number must be set for the boot volume but I do have a boot partition.

I used VMWare vCenter Converter 6.20 and ESXi 6.7.0 to remotely convert a CentOS 6.6 (Actually "Schmooze 6.6" -- FreePBX 13 from Sangoma) machine.

There was an error in conversion at 97% -- this is from the log:

2019-01-25T17:29:36.183-05:00 info vmware-converter-server[17492] [Originator@6876 sub=Default] [task,379] [task-6] -- ERROR -- Convert: converter.fault.CloneFault

--> (converter.fault.CloneFault) {

-->    faultCause = (vmodl.MethodFault) null,

-->    description = "Partition number must be set for the boot volume",

-->    msg = ""

--> }

The VM was created so I booted from a CentOS 6.6 install ISO and used the recovery shell.  This is an LVM system. It appears that the boot partition is not being mounted. 

This screenshot is from fdisk -l in the recovery shell, and shows /dev/sda1 as the boot device. https://www.screencast.com/t/ZE6MOJg7Zejp   (Sorry for the screenshot but I can't cut & paste from the VMWare Remote Console.) After #chroot /mnt/sysimage # ls /boot says "0 files".

When I look in BIOS setup on the VM, there are no hard drives listed in boot order -> hard drives.

/sbin/grub-install /dev/sda1 produces "/dev/sda1 does not have any corresponding BIOS drive"

/sbin/grub-install /dev/sda  produces "/dev/sda does not have any corresponding BIOS drive"

/etc/fstab fro the original machine says:

/dev/mapper/VolGroup-lv_root /                       ext4    defaults        1 1

UUID=5a2f524f-6cee-43b2-ad27-3b6ea7f4d3dc /boot                   ext4    defaults        1 2

/dev/mapper/VolGroup-lv_home /home                   ext4    defaults        1 2

/dev/mapper/VolGroup-lv_swap swap                    swap    defaults        0 0

tmpfs                   /dev/shm                tmpfs   defaults        0 0

devpts                  /dev/pts                devpts  gid=5,mode=620  0 0

sysfs                   /sys                    sysfs   defaults        0 0

proc                    /proc                   proc    defaults        0 0

fdisk -l on original machines says:

Disk /dev/sdb: 500.1 GB, 500107862016 bytes

255 heads, 63 sectors/track, 60801 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x00000000

Disk /dev/sda: 500.1 GB, 500107862016 bytes

255 heads, 63 sectors/track, 60801 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x00009c6b

   Device Boot      Start         End      Blocks   Id  System

/dev/sda1   *           1          64      512000   83  Linux

Partition 1 does not end on cylinder boundary.

/dev/sda2              64      121602   976254976   8e  Linux LVM

Disk /dev/sdc: 500.1 GB, 500107862016 bytes

255 heads, 63 sectors/track, 60801 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x00009c6b

   Device Boot      Start         End      Blocks   Id  System

/dev/sdc1   *           1          64      512000   83  Linux

Partition 1 does not end on cylinder boundary.

/dev/sdc2              64      121602   976254976   8e  Linux LVM

Disk /dev/mapper/isw_gcdaibce_Volume0: 1000.2 GB, 1000210432000 bytes

255 heads, 63 sectors/track, 121601 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x00009c6b

                                              Device Boot      Start         End      Blocks   Id  System

/dev/mapper/isw_gcdaibce_Volume0p1   *           1          64      512000   83  Linux

Partition 1 does not end on cylinder boundary.

/dev/mapper/isw_gcdaibce_Volume0p2              64      121602   976254976   8e  Linux LVM

Disk /dev/mapper/isw_gcdaibce_Volume0p1: 524 MB, 524288000 bytes

255 heads, 63 sectors/track, 63 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x00000000

Disk /dev/mapper/isw_gcdaibce_Volume0p2: 999.7 GB, 999685095424 bytes

255 heads, 63 sectors/track, 121538 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x00000000

Disk /dev/mapper/VolGroup-lv_root: 53.7 GB, 53687091200 bytes

255 heads, 63 sectors/track, 6527 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x00000000

Disk /dev/mapper/VolGroup-lv_swap: 12.7 GB, 12666798080 bytes

255 heads, 63 sectors/track, 1539 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x00000000

Disk /dev/mapper/VolGroup-lv_home: 933.3 GB, 933329108992 bytes

255 heads, 63 sectors/track, 113470 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x00000000

It seems some partitions were missed n the conversion?

I can SCP the /boot files from original machine to VM, but I can't seem to mount /dev/sda1 to copy the to copy the files to.

SO, I am now stuck.  Any advice is GREATLY appreciated.

Thanks in advance.

I have logged this as a ticket, but I am in real trouble right now as all backups are failing, so clutching at straws and hoping someone is watching over a weekend.

I think this must have happened on Friday at some point after I left the office, but I only noticed the problem on Saturday as I was checking the progress of a VM that I was working on. The VM in question should have nothing to do with this problem.

The issue I has was that I couldn't access the VM as Vcenter web client was giving me an error (500 error of some sort, but was a proper error page, not just text as it is now). Not sure why, it's never happened before, but a reboot of VCSA seemed like the first port of call.

The reboot took for ever, well over 15 miunutes, and when it finally came up, the error you get now is...

503 Service Unavailable (Failed to connect to endpoint:
[N7Vmacore4Http16LocalServiceSpecE:0x7fdaf26c3c10] _serverNamespace =
/vsphere-client _isRedirect = false _port = 9090)

I can access the console of the VCSA, but if I try and enable SSH and try to login to the VCSA on SSH, it disables SSH as soon as I try the password. This happens over and over so I cannot access the VCSA via SSH to even investigate.

I have since removed the VCSA from inventory on VM2, and imported it on VM3 (shared storage so nothing moved). This is because of a post I saw mentioning USB devices which will be the case on the original VM.

Runing VCSA on VM3 is no different, still a very long wait to load, and same error on webpage. Again, SSH gets disabled as soon as I try to actuall SSH in for some reason.

TIA, Alan

Hi

I am using vmware player in windows 10 for a virtual workstation using ubuntu 18/freesurfer - in order to process MRI-images.

Currently I have a 1920x 12core/24 threads threadripper CPU and have SMT (hyperthreading) enabled.

The VMware player has a max of 16 vCPUs - and I can see from the ressource monitor, that the workstation has access to approximately 2/3 of the cpu-capacity during high load processing.

I was wondering...

If the cpu was upgraded to a 16-core threadripper CPU, SMT was disabled in bios and I gave the VM e.g. 14 vCPUs. Would the VM then have access to 14 full cpu cores instead of the current 8 with SMT?

Hello there.

As far as I know, PNID is still (for 6.7u1 too) the thing, that could not be changed, as well as the FQDN (well, if FQDN was used during deployment of vCenter, then PNID = FQDN). But then what I can change in configuration -> runtime settings?

I guess "vCenter Server unique ID" is some ID that identifies vCenter within SSO-domain. Okay.

vCenter Server managed address??? Documentation says:

In vCenter Server managed address, enter the vCenter Server system address.

The address can be IPv4, IPv6, a fully qualified domain name, an IP address, or another address format.

What the hell? If I want to change the IP, then I would do it via appliance settings (5480). If I want to change "a fully qualified domain name", then... I can't do it.

vCenter Server name??? Documentation says:

In vCenter Server name, enter the name of the vCenter Server system.

If you change the DNS name of the vCenter Server, you can use this text box to modify the vCenter Server name to match.

Again, what the hell?

What are these settings about?

Hello All,

i want to add a user to our vcenter environment which will have access to migrate VMs only from a specific folder.

when i add the user as (vsphere.local) and give permission to the specific folder when the user logins he can see the folder but no vms inside it...

any ideas?

Thanks!!!!

Disclaimer: I have not opened a case with VMware support regarding this issue yet - mostly because I don't think that they will be able to help with this. But on the very slim chance that other people have also experiences a similar issue, I'm trying the community. Maybe I get lucky ... thanks for listening.

After an update of our VCSA to 6.7 U1b we experienced some network issues that we initially did not connect to the vCenter upgrade. There are a number of other VMs on the ESXi hosting the VCSA (mostly Linux VMs). After the upgrade we noticed (for lack of a better description) "an unstable network", resulting in recurring sudden cluster switches of Linux Pacemaker / DRBD clusters due to network reachability issues. We finally could confirm that the VCSA was at least part of the problem, if not the cause.

After moving the vCenter to its own ESXi, we could at least isolate the network issues in such a way that no other of our important VMs are impacted anymore.

The only observable issue regarding this problem is an increasing number of output drops on the switchport that connects to the ESXi with the VCSA (which by now is the only VM on the host). The underlying switch is a Catalyst 6500. The ESXi host is connected with 1Gbps to the switch. Since we never experienced similar network issues in the past, I don't know if these output drops were there before or if they occured only after the upgrade.

So far, we have been able to rule out defective cables, a defective switchport and a defective switch module. The average throughput on that interface is < 2 Mbps combined TX/RX (which is 0.2% of the line speed). Still, we are seeing those output drops which - based on Cisco documentation - are caused by a congested interface: at times the output queue must be full and the switch discards some packets. To the best of my understanding, this must be because of short lived bursty traffic (which we haven't been able to capture yet). What might be the cause of this bursty traffic is still completely unclear to us.

The load on the vCenter is rather small - no discernible CPU or memory issues, a rather low network load (see switch throughput) and no dropped packets on the interface level of the VCSA.

The actual percentage of output drops on the interface is ~ 0.25%. It doesn't seem that high to me, but it does seem to have quite an impact on the stability of Linux DRBD clusters. The "funny" thing is that there is no observable impact on the functionality or performance of the vCenter itself. I would have expected that if other VMs are behaving badly due to those dropped packets that the vCenter might complain as well - but that doesn't seem to be the case.

So here is the question: has anyone else seen this issue with the latest version of vCenter? Is anyone aware of changes made to the vCenter in the latest update that lead to more bursty traffic? And does anyone have an idea on how to further analyze the root cause of this issue?

Thanks a bunch,

-michael

P.S. I can provide more technical information if anyone's interested.

Hi Guys,

Hopefully something you can assist me with to stop me from ripping anymore of my hair out   For the last few days, I have been trying to add our VCSA to our domain so that I can setup the SSO domain.

This is a brand new deployment - 6.0 all around.  We are using the embedded VCSA with an embedded deployment.  When I go to join the domain, I get the following error:

Idm client exception: Error trying to join AD, error code [11], user [Administrator@mydomain], domain [mydomain], orgUnit []

I have replaced our domain name with 'mydomain' above - any ideas?

Good day.

I send in ESXI 6.7 USB Device.After disconnecting this device, I reboot the virtual machine, connect the same USB and the system does not find it.We need to forward again.How to configure so that the virtual machine remembers these devices?

Hello. After rebooting, I could not connect to Vcentr every time I received a 503 error When I start vmware-vpxd manually, I get the following error. What is Stderr = Key not found: vpxd / secureSoapPort? How to fix  and what to do? Help me please! Thank!

service-control --start vmware-vpxd

INFO:root:Service: vmware-vpxd, Action: start

Service: vmware-vpxd, Action: start

2019-01-28T19:29:57.828Z   Running command: ['/sbin/chkconfig', u'vmware-vpxd']

2019-01-28T19:29:57.958Z   Done running command

2019-01-28T19:29:57.958Z   Running command: ['/sbin/service', u'vmware-vpxd', 'status']

2019-01-28T19:29:58.532Z   Done running command

2019-01-28T19:29:58.532Z   Running command: ['/sbin/chkconfig', '--force', u'vmware-vpxd', 'on']

2019-01-28T19:29:58.595Z   Done running command

2019-01-28T19:29:58.595Z   Running command: ['/sbin/service', u'vmware-vpxd', 'start']

2019-01-28T19:30:01.535Z   Done running command

2019-01-28T19:30:01.536Z   Invoked command: ['/sbin/service', u'vmware-vpxd', 'start']

2019-01-28T19:30:01.536Z   RC = 1

Stdout = Key not found: vpxd/secureSoapPort

vmware-vpxd: VC SSL Certificate does not exist, it will be generated by vpxd

Waiting for the embedded database to start up: success

Executing pre-startup scripts...

vmware-vpxd: Starting vpxd by administrative request.

success

vmware-vpxd: Waiting for vpxd to start listening for requests on

Waiting for vpxd to initialize: Usage: wait_for_vpxd.py [options]

wait_for_vpxd.py: error: -p option requires an argument

failed

failed

vmware-vpxd: vpxd failed to initialize in time.

vpxd is already starting up. Aborting the request.

Stderr = Key not found: vpxd/secureSoapPort

2019-01-28T19:30:01.536Z   {

    "resolution": null,

    "detail": [

        {

            "args": [

                "Command: ['/sbin/service', u'vmware-vpxd', 'start']\nStderr: Key not found: vpxd/secureSoapPort\n"

            ],

            "id": "install.ciscommon.command.errinvoke",

            "localized": "An error occurred while invoking external command : 'Сommand: ['/sbin/service', u'vmware-vpxd', 'start']\nStderr: Key not found: vpxd/                                                                      secureSoapPort\n'",

            "translatable": "An error occurred while invoking external command :'%(0)s'"

        }

    ],

    "componentKey": null,

    "problemId": null

}

ERROR:root:Unable to start service vmware-vpxd, Exception: {

    "resolution": null,

    "detail": [

        {

            "args": [

                "vmware-vpxd"

            ],

            "id": "install.ciscommon.service.failstart",

            "localized": "An error occurred while starting service 'vmware-vpxd'                                                                      ",

            "translatable": "An error occurred while starting service '%(0)s'"

        }

    ],

    "componentKey": null,

    "problemId": null

}

Unable to start service vmware-vpxd, Exception: {

    "resolution": null,

    "detail": [

        {

            "args": [

                "vmware-vpxd"

            ],

            "id": "install.ciscommon.service.failstart",

            "localized": "An error occurred while starting service 'vmware-vpxd'                                                                      ",

            "translatable": "An error occurred while starting service '%(0)s'"

        }

    ],

    "componentKey": null,

    "problemId": null

}

Hi, how much exactly vCenter HA need memory? I readed from documentation that it needs 16GB memory. I dont believe this, because now I have vCenter with only 10GB memory and in reality it uses only 1.6GB active memory (ESXi monitoring utilization shows). And also, why witness needs the same amount of memory. So, this sounds bullshit. I have 2 more computers with 8 GB physical memory. I can set cluster VM more amount of memory than physical memory. Anyway it dont use them all. And witness? How much RAM I need exactly and how much for witness?......Or my question is - 16GB for VM or for ESXi? Im tired for searching internet. All articles are just like copy-paste "16GB" , but there is big difference is this requirement for VM or ESXi. And what happens when I have less.