Hi,
I'll have Vsphere 6.0 update 2 and when I try to add a new ESXi node I'll have the following error:
A general system error occurred: Unable to get signed certificate for host: xxx.xxx.xxx.xxx. Error: The Root CA certificate is missing or failed to initialize (70000)
Apparently is a certificate issue.
I'll appreciate any help on this.
Best regards.
I am running Converter on Windows 7 ans trying to make a virtual machine of the current installation to upgrade to Windows 10.
Whenever I start to use the converter I get this error message "Unable to complete Converter agent installation on Dell-9020. Another version of this product is already installed.
I have looked around the machine and the only one I can find is the current installation.
Anyone any ideas. Thanks
2-3 times a day VMWare Workstation crashes with Unrecoverable Error vthread-8.
This seems to be a Workstation UI crash because the services are still running; I can even suspend my VM, reboot my computer and restore the VM where I was working before.
Looking through similar posts this seems to be a fairly common problem without an answer... though I did notice that a few recent posts were using a similar series motherboard to mine: ASUS MAXIMUS VIII
Though not unworkable this problem is very annoying!
Can anyone please help?
Thought I would share these with the VMware community.
I was playing around with virtualisation and connecting to legacy hardware via USB and Serial Ports so decided to make a video tutorial and guide.
The written guide may be found here:
Hi there,
i am using VMware Workstation 12 Player for embedded SW development. Thus, i have some USB devices attached to my virtual machine. Unfortunately, i happens from time to time, that the player crashes when i connect/disconnect USB devices: Runtime Error R6025 pure virtual function call.
I am using Windows 8.1 x64 as host, Windows 7 Pro x64 as guest on a Dell Latitude E7450. VMware® Workstation 12 Player 12.1.1 build-3770994
Interestingly, the vm will load immediately, if i start it again after a crash.
Any ideas? Help would be much appreciated.
Regards,
Alex
Hi
I currently have a six node san cluster and a vcenter server and I would like to evaluate vsan. My plan is to create a new vsan cluster and move 3 hosts to it and run the eval. E.g one vsan eval cluster and the old one (now consisting of 3 nodes) on the same vcenter.
possible and if so how? I'm unable to download any keys just a link to download vcenter and esxi again
regards
İ want to use my Machines configured on vSphere Client on my Website for Lab Access... it doesnt matter, if theres a login on the beginning for the machines or in the machines as local users...
But how to configure that? When i want to access my Machine, i just can access it trough localip/ui/#/console/1 and console in VMware ESXİ Web Client or vSphere Client, is there a possiblity to access VM remotely with an ip? i tought, its NAT but i dont know how to configure it...
The end product should look nearly like this:
That means:
when someone access my website, should be go to login, enter his credentials and all my VM should appear there.... example: mydomain.com/login - username - password, choose your VM...
or
when someone access my website, can go to login and VM appears there, but he has to login to his local user account: example: mydomain.com/machines - windows 10 - hisusername - password (like the windows server 2012 photo, which is above in the middle)
Hi,
I want to shrink a thin provisioned vmdk file, because in the affected virtual machine OS there are many GBs free, but the thin provisioned disk is nearly the same size like a thick provisioned disk.
Regarding the VMware KB2004155, a SVMotion process to another datastore does not shrink the vmdk file.
I have a vSphere 6 environment with VMFS5 datastores only. So (I think) only a block size of 1MB is possible. Maybe this KB article is a little bit confusing.
Maybe somebody has a good ides how I can shrink a thin provisioned disk?
Thanks and Best Regards,
Andre
Hi guys,
Hope someone can help please.
i have two VM (VM1 in ESX1 and VM2 in ESX2 )
VM1 and VM2 are both on the same VLAN 610.
Ping from VM1 two VM2 experience many times out:
30 packets transmitted, 25 received, 16% packet loss, time 29992ms Thu Jul 28 20:13:01 CEST 2016
30 packets transmitted, 9 received, 70% packet loss, time 34324ms Thu Jul 28 20:14:01 CEST 2016
30 packets transmitted, 22 received, 26% packet loss, time 30004ms Thu Jul 28 20:15:01 CEST 2016
I checked the network. there is no errors nor drops
I Tried a ping from a VM3 in ESX3 which is in a different vlan 680 toward VM1 in ESX1. and its works perferctly. there is no timeout.
I am confiused.
Can any one help please ?
Many thanks
i have 2X10 gbit embeded network adaptor and 2 x10 gbit pci network adaptor. and i have 2 vswitch on vcenter . managemet-vmotion and virtual machine' network. i will create one backup network . what is best practives for backup network. i must connect to management network or virtual machine' network
Hi Forum, My host experience purple screen MCE. I took a screen pic and collected zdump however I am not able to interpret the root cause because of my limited understanding of troubleshooting techniques. I have attached the pic and extracted log file. Requesting you help to understand the root cause. Adding some portion of the log below.
2016-09-04T10:45:22.687Z cpu3:33122)<6>hub 2-0:1.0: suspended
2016-09-04T10:46:17.228Z cpu0:32782)World: 9740: PRDA 0x418040000000 ss 0x0 ds 0x4018 es 0x4018 fs 0x0 gs 0x0
2016-09-04T10:46:17.228Z cpu1:33079)World: 9740: PRDA 0x418040400000 ss 0x0 ds 0x4018 es 0x4018 fs 0x0 gs 0x0
2016-09-04T10:46:17.228Z cpu2:32781)World: 9740: PRDA 0x418040800000 ss 0x0 ds 0x4018 es 0x4018 fs 0x0 gs 0x0
2016-09-04T10:46:17.228Z cpu3:35426)World: 9740: PRDA 0x418040c00000 ss 0x4018 ds 0x4018 es 0x4018 fs 0x0 gs 0x0
2016-09-04T10:46:17.228Z cpu1:33079)World: 9742: TR 0x4000 GDT 0xfffffffffc60a000 (0xffff) IDT 0xfffffffffc608000 (0xffff)
2016-09-04T10:46:17.228Z cpu0:32782)World: 9742: TR 0x4000 GDT 0xfffffffffc60a000 (0xffff) IDT 0xfffffffffc608000 (0xffff)
2016-09-04T10:46:17.228Z cpu2:32781)World: 9742: TR 0x4000 GDT 0xfffffffffc60a000 (0xffff) IDT 0xfffffffffc608000 (0xffff)
2016-09-04T10:46:17.228Z cpu1:33079)World: 9743: CR0 0x80050031 CR3 0x17b6bb000 CR4 0x42668
2016-09-04T10:46:17.228Z cpu0:32782)World: 9743: CR0 0x80050031 CR3 0x17ba56000 CR4 0x42668
2016-09-04T10:46:17.228Z cpu3:35426)World: 9742: TR 0x4000 GDT 0xfffffffffc60a000 (0xffff) IDT 0xfffffffffc608000 (0xffff)
2016-09-04T10:46:17.228Z cpu2:32781)World: 9743: CR0 0x80050031 CR3 0x16908a000 CR4 0x42668
2016-09-04T10:46:17.228Z cpu3:35426)World: 9743: CR0 0x80050031 CR3 0x17c0e3000 CR4 0x42668
2016-09-04T10:46:17.259Z cpu1:33079)Panic: 634: Panic from another CPU (cpu 1, world 33079): ip=0x418011c780a0 randomOff=0x11c00000:
Machine Check Exception: Fatal (unrecoverable) MCE on PCPU1 in world 33079:helper39-3
System has encountered a Hardware Error - Please contact the hardware vendor
2016-09-04T10:46:17.259Z cpu1:33079)Backtrace for current CPU #1, worldID=33079, rbp=0x410014740008
2016-09-04T10:46:17.259Z cpu1:33079)0x4390c9b9ba80:[0x41801246093b]e1000_intr@<None>#<None>+0x77 stack: 0x0, 0x41801231005d, 0x101c, 0x
2016-09-04T10:46:17.259Z cpu1:33079)0x4390c9b9baa0:[0x41801231005d]Linux_IRQHandler@com.vmware.driverAPI#9.2+0x25 stack: 0x418012310054
2016-09-04T10:46:17.259Z cpu1:33079)0x4390c9b9bad0:[0x418011c5a3d6]IntrCookie_DoInterrupt@vmkernel#nover+0x41e stack: 0x780, 0x0, 0x430
2016-09-04T10:46:17.259Z cpu1:33079)0x4390c9b9bb80:[0x418011c56940]IDT_IntrHandler@vmkernel#nover+0x104 stack: 0x0, 0x418040400200, 0x0
2016-09-04T10:46:17.259Z cpu1:33079)0x4390c9b9bbb0:[0x418011cc7044]gate_entry_@vmkernel#nover+0x0 stack: 0x0, 0x0, 0x0, 0x0, 0x41804040
2016-09-04T10:46:17.259Z cpu1:33079)0x4390c9b9bc70:[0x418011f0263a]Power_HaltPCPU@vmkernel#nover+0x1f2 stack: 0x417fd1e83ea0, 0x4180405
2016-09-04T10:46:17.259Z cpu1:33079)0x4390c9b9bcc0:[0x418011e0fc68]CpuSchedIdleLoopInt@vmkernel#nover+0x2f8 stack: 0x27f2159ff62b, 0x10
2016-09-04T10:46:17.259Z cpu1:33079)0x4390c9b9bd40:[0x418011e133bd]CpuSchedDispatch@vmkernel#nover+0x16b5 stack: 0xffffffffffffffff, 0x
2016-09-04T10:46:17.259Z cpu1:33079)0x4390c9b9be60:[0x418011e13f84]CpuSchedWait@vmkernel#nover+0x240 stack: 0x0, 0x43054b304240, 0x5d01
2016-09-04T10:46:17.259Z cpu1:33079)0x4390c9b9bee0:[0x418011e141be]CpuSched_TimedWaitIRQ@vmkernel#nover+0x7e stack: 0x43054b304240, 0x4
2016-09-04T10:46:17.259Z cpu1:33079)0x4390c9b9bf30:[0x418011c503ce]helpFunc@vmkernel#nover+0x5f2 stack: 0x0, 0x43054b3037e0, 0x27, 0x0,
2016-09-04T10:46:17.259Z cpu1:33079)0x4390c9b9bfd0:[0x418011e14c1e]CpuSched_StartWorld@vmkernel#nover+0xa2 stack: 0x0, 0x0, 0x0, 0x0, 0
2016-09-04T10:46:17.259Z cpu1:33079)Panic: 769: Halting PCPU 1.
2016-09-04T10:46:17.290Z cpu3:35426)Panic: 634: Panic from another CPU (cpu 3, world 35426): ip=0x418011c780a0 randomOff=0x11c00000:
Machine Check Exception: Fatal (unrecoverable) MCE on PCPU3 in world 35426:vmm0:win7
System has encountered a Hardware Error - Please contact the hardware vendor
2016-09-04T10:46:17.290Z cpu3:35426)Backtrace for current CPU #3, worldID=35426, rbp=0x0
2016-09-04T10:46:17.290Z cpu3:35426)0x43911311bcf8:[0x418011f0263a]Power_HaltPCPU@vmkernel#nover+0x1f2 stack: 0x417fd1e83ea0, 0x418040d
2016-09-04T10:46:17.290Z cpu3:35426)0x43911311bd48:[0x418011e0fc68]CpuSchedIdleLoopInt@vmkernel#nover+0x2f8 stack: 0x27f2159b4ea2, 0x10
2016-09-04T10:46:17.290Z cpu3:35426)0x43911311bdc8:[0x418011e133bd]CpuSchedDispatch@vmkernel#nover+0x16b5 stack: 0x4391135a7b00, 0x4391
2016-09-04T10:46:17.290Z cpu3:35426)0x43911311bee8:[0x418011e13f84]CpuSchedWait@vmkernel#nover+0x240 stack: 0x410014a2cde0, 0x0, 0xa000
2016-09-04T10:46:17.290Z cpu3:35426)0x43911311bf68:[0x418011e140da]CpuSched_VcpuHalt@vmkernel#nover+0x11e stack: 0xffffffff00002001, 0x
2016-09-04T10:46:17.290Z cpu3:35426)0x43911311bfb8:[0x418011cabe39]VMMVMKCall_Call@vmkernel#nover+0x139 stack: 0x418011cab988, 0x0, 0x4
2016-09-04T10:46:17.290Z cpu3:35426)Panic: 769: Halting PCPU 3.
2016-09-04T10:46:17.352Z cpu2:32781)Panic: 634: Panic from another CPU (cpu 2, world 32781): ip=0x418011c780a0 randomOff=0x11c00000:
Machine Check Exception: Fatal (unrecoverable) MCE on PCPU2 in world 32781:coalesceWorl
System has encountered a Hardware Error - Please contact the hardware vendor
2016-09-04T10:46:17.352Z cpu2:32781)Backtrace for current CPU #2, worldID=32781, rbp=0x0
2016-09-04T10:46:17.352Z cpu2:32781)0x4390c069bbe0:[0x418011f0263a]Power_HaltPCPU@vmkernel#nover+0x1f2 stack: 0x417fd1e83ea0, 0x4180409
2016-09-04T10:46:17.352Z cpu2:32781)0x4390c069bc30:[0x418011e0fc68]CpuSchedIdleLoopInt@vmkernel#nover+0x2f8 stack: 0x27f2159b79d1, 0x10
2016-09-04T10:46:17.352Z cpu2:32781)0x4390c069bcb0:[0x418011e133bd]CpuSchedDispatch@vmkernel#nover+0x16b5 stack: 0xef, 0x439080d04001,
2016-09-04T10:46:17.352Z cpu2:32781)0x4390c069bdd0:[0x418011e13f84]CpuSchedWait@vmkernel#nover+0x240 stack: 0x0, 0x0, 0x80069be78, 0x0,
2016-09-04T10:46:17.352Z cpu2:32781)0x4390c069be50:[0x418011e144bf]CpuSched_SleepUntilTC@vmkernel#nover+0x8f stack: 0x400002001, 0x4390
2016-09-04T10:46:17.352Z cpu2:32781)0x4390c069beb0:[0x418011db9b64]NetCoalesceDefaultWorldCB@vmkernel#nover+0x190 stack: 0x0, 0x0, 0x0,
2016-09-04T10:46:17.352Z cpu2:32781)0x4390c069bfd0:[0x418011e14c1e]CpuSched_StartWorld@vmkernel#nover+0xa2 stack: 0x0, 0x0, 0x0, 0x0, 0
2016-09-04T10:46:17.352Z cpu2:32781)Panic: 769: Halting PCPU 2.
2016-09-04T10:46:17.383Z cpu0:32782)Backtrace for current CPU #0, worldID=32782, rbp=0x0
2016-09-04T10:46:17.383Z cpu0:32782)0x4390c071bcd0:[0x418011f0263a]Power_HaltPCPU@vmkernel#nover+0x1f2 stack: 0x417fd1e83ea0, 0x4180401
2016-09-04T10:46:17.383Z cpu0:32782)0x4390c071bd20:[0x418011e0fc68]CpuSchedIdleLoopInt@vmkernel#nover+0x2f8 stack: 0x27f2159bc891, 0x10
2016-09-04T10:46:17.383Z cpu0:32782)0x4390c071bda0:[0x418011e133bd]CpuSchedDispatch@vmkernel#nover+0x16b5 stack: 0x43018bafc634, 0x4180
2016-09-04T10:46:17.383Z cpu0:32782)0x4390c071bec0:[0x418011e13f84]CpuSchedWait@vmkernel#nover+0x240 stack: 0x0, 0x0, 0x80071bf68, 0x0,
2016-09-04T10:46:17.383Z cpu0:32782)0x4390c071bf40:[0x418011e144bf]CpuSched_SleepUntilTC@vmkernel#nover+0x8f stack: 0x20c49ba500002001,
2016-09-04T10:46:17.383Z cpu0:32782)0x4390c071bfa0:[0x418011dbd5ba]NetCoalesce2WorldCB@vmkernel#nover+0xde stack: 0x4390c00a7100, 0x439
2016-09-04T10:46:17.383Z cpu0:32782)0x4390c071bfd0:[0x418011e14c1e]CpuSched_StartWorld@vmkernel#nover+0xa2 stack: 0x0, 0x0, 0x0, 0x0, 0
2016-09-04T10:46:17.413Z cpu0:32782) [45m [33;1mVMware ESXi 6.0.0 [Releasebuild-4192238 x86_64] [0m
Machine Check Exception: Fatal (unrecoverable) MCE on PCPU0 in world 32782:netCoalesce2
System has encountered a Hardware Error - Please contact the hardware vendor
2016-09-04T10:46:17.416Z cpu0:32782)cr0=0x8001003d cr2=0x1bc1ef78 cr3=0x8001b000 cr4=0x216c
2016-09-04T10:46:17.416Z cpu0:32782)Last branch from 0x418011f02533 to 0x418011f025eb
2016-09-04T10:46:17.417Z cpu0:32782)frame=0x4390c071bc10 ip=0x418011f0263a err=18 rflags=0x10202
2016-09-04T10:46:17.418Z cpu0:32782)rax=0x0 rbx=0x418040000000 rcx=0x0
2016-09-04T10:46:17.418Z cpu0:32782)rdx=0x0 rbp=0x0 rsi=0x27f2159bb9c6
2016-09-04T10:46:17.418Z cpu0:32782)rdi=0x43004d0f51f0 r8=0x15 r9=0x0
2016-09-04T10:46:17.419Z cpu0:32782)r10=0x0 r11=0x43004d0c8438 r12=0x418040000200
2016-09-04T10:46:17.419Z cpu0:32782)r13=0x0 r14=0x40 r15=0x0
2016-09-04T10:46:17.419Z cpu0:32782)pcpu:0 world:32782 name:"netCoalesce2World" (S)
2016-09-04T10:46:17.420Z cpu0:32782)pcpu:1 world:33079 name:"helper39-3" (SH)
2016-09-04T10:46:17.420Z cpu0:32782)pcpu:2 world:32781 name:"coalesceWorld-0" (S)
2016-09-04T10:46:17.420Z cpu0:32782)pcpu:3 world:35426 name:"vmm0:win7" (V)
2016-09-04T10:46:17.420Z cpu0:32782)@BlueScreen: Machine Check Exception: Fatal (unrecoverable) MCE on PCPU0 in world 32782:netCoalesce2
System has encountered a Hardware Error - Please contact the hardware vendor
2016-09-04T10:46:17.420Z cpu0:32782)Code start: 0x418011c00000 VMK uptime: 0:04:53:32.503
2016-09-04T10:46:17.421Z cpu0:32782)0x4390c071bcd0:[0x418011f0263a]Power_HaltPCPU@vmkernel#nover+0x1f2 stack: 0x417fd1e83ea0
2016-09-04T10:46:17.422Z cpu0:32782)0x4390c071bd20:[0x418011e0fc68]CpuSchedIdleLoopInt@vmkernel#nover+0x2f8 stack: 0x27f2159bc891
2016-09-04T10:46:17.423Z cpu0:32782)0x4390c071bda0:[0x418011e133bd]CpuSchedDispatch@vmkernel#nover+0x16b5 stack: 0x43018bafc634
2016-09-04T10:46:17.424Z cpu0:32782)0x4390c071bec0:[0x418011e13f84]CpuSchedWait@vmkernel#nover+0x240 stack: 0x0
2016-09-04T10:46:17.425Z cpu0:32782)0x4390c071bf40:[0x418011e144bf]CpuSched_SleepUntilTC@vmkernel#nover+0x8f stack: 0x20c49ba500002001
2016-09-04T10:46:17.426Z cpu0:32782)0x4390c071bfa0:[0x418011dbd5ba]NetCoalesce2WorldCB@vmkernel#nover+0xde stack: 0x4390c00a7100
2016-09-04T10:46:17.427Z cpu0:32782)0x4390c071bfd0:[0x418011e14c1e]CpuSched_StartWorld@vmkernel#nover+0xa2 stack: 0x0
2016-09-04T10:46:17.435Z cpu0:32782)base fs=0x0 gs=0x418040000000 Kgs=0x0
2016-09-04T10:46:17.435Z cpu0:32782)3 other PCPUs are in panic.
2016-09-04T10:46:17.228Z cpu3:35426)MC:PCPU3 B:5 S:0xb200000080200e0f M:0x0 A:0x0 5
2016-09-04T10:46:17.228Z cpu0:32782)MC:PCPU0 B:5 S:0xb200001044100e0f M:0x0 A:0x0 4
2016-09-04T10:46:17.228Z cpu2:32781)MC:PCPU2 B:5 S:0xb200000084200e0f M:0x0 A:0x0 5
2016-09-04T10:46:17.228Z cpu1:33079)MC:PCPU1 B:5 S:0xb200001040100e0f M:0x0 A:0x0 4
Thanks in advance!!
Hello Team,
I am trying to install iSCSI Software adapter in my lab machine. But every time in task status Change software internet SCSCI status completed successfully. But when i check in Storage Adapter respective adapter is not visible (vmbha33 is not visible) in storage.
Can anybody please suggest me how to resolve this issue. Without this option am unable to continue my lab to add iSCSI/NFS disk in my lab.
I attached herewith respective screen shot, i think these information are sufficient to help me.
Regards
GaneshSS
Hello everybody,
I have a question about the vCenter Update Manager. I have successfully integrated the VIBs from HPE (https://vibsdepot.hpe.com/index.xml). When I now create a new host baseline as host extension I get a list of HPE VIBs that I can now tick and then deploy to my hosts.
My problem is that I don't know which VIBs I need?
I deployed my hosts with the custom VMware image from HPE. Now I only want to update all HPE driver and software parts. I don't want to install new ones that I don't need.
How do I only get the VIBs that just need an update and nothing more?
Regards Wolfgang
So in my lab, I have auto deploy working with host profiles. However about every 3 (randomly) boot on the same VM it the auto deploy hangs on the "Loading VMware ESXi" Screen.
Loading /vmw/cache/38/6fetc etc etc. The bar always fills to about 90% and them 1 out of 3 times hangs forever and never finishes.
The VC auto deploy screen says only 330mb of 2gb cache is used.
I have downloaded the Auto Deploy Logs, and there is nothing that has Error just Debug/Info. (no idea what exactly to look for)
What is causing this? What else can I check?
Hi i have just installed WSX and when i browse to the portal i dont get the window that displays the shared VM's. All i get is a button to add a server.
I have ensured sharing is enabled and have cloned a machine for testing.
Appreciate if someone could point me in the correct direction.
Thanks.
Hi guys
I have been installed VMware workstation pro 12 and Vmware WSX 1.0.2 on a sever now I want to connect to my VMs remotely.when I enter the (ServerIP:8888) a web page is open and ask me for login to VMware WSX, after login to server a new page will apear that contain a link to Shared VMs. (localhost) when I click on it, a menue will appear that ask me to login to localhost and when I enter my username and password again I will receive this error :
[Errno 8] _ssl.c:480: EOF occurred in violation of protocol
can anyone help me?
VMWare Workstation 12 Pro officially ends life in January 2017. Is this product dead or is there a future product version? Need to decide if I need to more these processes to another provider soon.
Thanks for the insight.
Ken
Okay, this is really annoying. Using Workstation player 12.1.1, the latest, on a Linux Mint 18 Host OS, with a Windows 7 VM. Occasionally the mouse cursor gets offset somehow, and I have to click somewhere in the vicinity of the item that I'm aiming at. This is really intolerable, so I re-install vmware-tools (which I've had to do several times already because of this) yet again, and it corrects the problem after a VM reboot. Then this same thing happens again.
I'm about ready to throw this thing out, both the player and the VM are more trouble than they're worth at this point...before I did that, thought I'd ask if there's anyone else experiencing this, and if there's some sort of workaround or something that I can do to keep this from happening?
Thanks!
Hey there,
we got the same problem two weeks ago. One of our Datastores was suddenly unavailable.
Back then there where machines running on that Datastore.
We rebooted the server, the Datastore was back on but we had serious problems with locked files (which still isn't resolved).
See the Thread here: http://communities.vmware.com/thread/319421?tstart=150
We now are in fear that there might be more locked files or some more trouble when rebooting the server.
We also would like to know the cause of that Datastore beeing unavailable.
We already tried "vmkfstools -V" and looking at the problem with esxcfg-scsidevs -l / -a / -m (see output below!)
I was deleting some old backups of machines when the Datastore vanished (deleting some machines via the Console/SSH on the same Datastore worked a few minutes before).
I include the Console output at the time the Datastore was gone (see below).
Maybe someone has some useful tips on how to remount the Datastore / get it back online or can indentify the source of the problem!
Thanks in advance for replies, asgaroth
/vmfs/volumes/4bd88e21-e8b0d6ea-6c1a-003048c30e8c # rm -rf serverxyz.subdomain.domain rm: cannot remove 'serverxyz.subdomain.domain/serverxyz.subdomain.domain-flat.vmdk': Resource temporarily unavailable rm: cannot stat 'serverxyz.subdomain.domain/serverxyz.subdomain.domain.vmdk': Device or resource busy rm: cannot stat 'serverxyz.subdomain.domain/serverxyz.subdomain.domain.nvram': Device or resource busy rm: cannot stat 'serverxyz.subdomain.domain/vmware-37.log': Device or resource busy rm: cannot stat 'serverxyz.subdomain.domain/vmware-38.log': Device or resource busy rm: cannot stat 'serverxyz.subdomain.domain/vmware-39.log': Device or resource busy rm: cannot stat 'serverxyz.subdomain.domain/serverxyz.subdomain.domain-c1309193.hlog': Device or resource busy rm: cannot stat 'serverxyz.subdomain.domain/vmware-42.log': Device or resource busy rm: cannot stat 'serverxyz.subdomain.domain/vmware-41.log': Device or resource busy rm: cannot stat 'serverxyz.subdomain.domain/vmware-40.log': Device or resource busy rm: cannot stat 'serverxyz.subdomain.domain/vmware.log': Device or resource busy rm: cannot remove 'serverxyz.subdomain.domain': Device or resource busy ash: getcwd: Device or resource busy (unknown) # ls -al ls: .: Input/output error ash: getcwd: Input/output error (unknown) # cd / ~ # ls -al /vmfs/volumes/ ls: /vmfs/volumes/4bd88e21-e8b0d6ea-6c1a-003048c30e8c: Input/output error drwxr-xr-x 1 root root 512 Jul 12 13:37 . drwxr-xr-x 1 root root 512 Jun 28 15:57 .. drwxr-xr-x 1 root root 8 Jan 1 1970 386a41e4-ff1587ba-1385-2feaeed494ad drwxr-xr-t 1 root root 1960 Jul 12 12:56 4bc8414f-3206fe54-f06e-003048c30e8c drwxr-xr-t 1 root root 3500 Jul 8 22:30 4bd88e99-c67ad631-6c62-003048c30e8c drwxr-xr-t 1 root root 980 May 21 14:43 4dd7cf77-c3e57835-e9ef-003048c30e8c drwxr-xr-x 1 root root 8 Jan 1 1970 8c7e2fe8-f4c58d9f-34d3-8553ffee79a0 lrwxr-xr-x 1 root root 35 Jul 12 13:37 Datastore1 -> 4bc8414f-3206fe54-f06e-003048c30e8c lrwxr-xr-x 1 root root 35 Jul 12 13:37 Datastore2 -> 4bd88e21-e8b0d6ea-6c1a-003048c30e8c lrwxr-xr-x 1 root root 35 Jul 12 13:37 Datastore3 -> 4bd88e99-c67ad631-6c62-003048c30e8c lrwxr-xr-x 1 root root 35 Jul 12 13:37 Datastore4 -> 4dd7cf77-c3e57835-e9ef-003048c30e8c lrwxr-xr-x 1 root root 35 Jul 12 13:37 Hypervisor1 -> 386a41e4-ff1587ba-1385-2feaeed494ad lrwxr-xr-x 1 root root 35 Jul 12 13:37 Hypervisor2 -> 8c7e2fe8-f4c58d9f-34d3-8553ffee79a0 lrwxr-xr-x 1 root root 35 Jul 12 13:37 Hypervisor3 -> e00f98e1-2bcc0c91-e7a2-3487611c1557 drwxr-xr-x 1 root root 8 Jan 1 1970 e00f98e1-2bcc0c91-e7a2-3487611c1557 ~ # ls -al /vmfs/volumes/Datastore2 lrwxr-xr-x 1 root root 35 Jul 12 13:38 /vmfs/volumes/Datastore2 -> 4bd88e21-e8b0d6ea-6c1a-003048c30e8c ~ # ls -al /vmfs/volumes/Datastore2/ ls: /vmfs/volumes/Datastore2/: Input/output error ~ # df Filesystem 1k-blocks Used Available Use% Mounted on visorfs 1338636 267996 1070640 20% / vmfs3 488112128 328402944 159709184 67% /vmfs/volumes/4bc8414f-3206fe54-f06e-003048c30e8c nfs 315829740 135465900 180363840 43% /vmfs/volumes/0d6becf5-2ea0d633 nfs 1175588244 230332944 945255300 20% /vmfs/volumes/fa828cd2-adbc3d72 vmfs3 976486400 578560 975907840 0% /vmfs/volumes/4dd7cf77-c3e57835-e9ef-003048c30e8c vfat 292752 139328 153424 48% /vmfs/volumes/e00f98e1-2bcc0c91-e7a2-3487611c1557 vfat 255716 90204 165512 35% /vmfs/volumes/8c7e2fe8-f4c58d9f-34d3-8553ffee79a0 vfat 255716 61804 193912 24% /vmfs/volumes/386a41e4-ff1587ba-1385-2feaeed494ad ~ # vmkfstools -V ~ # ls /vmfs/volumes/ 0d6becf5-2ea0d633 4dd7cf77-c3e57835-e9ef-003048c30e8c Datastore4 e00f98e1-2bcc0c91-e7a2-3487611c1557 386a41e4-ff1587ba-1385-2feaeed494ad 8c7e2fe8-f4c58d9f-34d3-8553ffee79a0 Hypervisor1 fa828cd2-adbc3d72 4bc8414f-3206fe54-f06e-003048c30e8c Datastore1 Hypervisor2 nfs-vmds1 4bd88e99-c67ad631-6c62-003048c30e8c Datastore3 Hypervisor3 nfs-vmds2 ~ # ls -l /vmfs/volumes/ drwxr-x--- 1 root root 4096 Jun 30 12:47 0d6becf5-2ea0d633 drwxr-xr-x 1 root root 8 Jan 1 1970 386a41e4-ff1587ba-1385-2feaeed494ad drwxr-xr-t 1 root root 1960 Jul 12 12:56 4bc8414f-3206fe54-f06e-003048c30e8c drwxr-xr-t 1 root root 3500 Jul 8 22:30 4bd88e99-c67ad631-6c62-003048c30e8c drwxr-xr-t 1 root root 980 May 21 14:43 4dd7cf77-c3e57835-e9ef-003048c30e8c drwxr-xr-x 1 root root 8 Jan 1 1970 8c7e2fe8-f4c58d9f-34d3-8553ffee79a0 lrwxr-xr-x 1 root root 35 Jul 12 13:59 Datastore1 -> 4bc8414f-3206fe54-f06e-003048c30e8c lrwxr-xr-x 1 root root 35 Jul 12 13:59 Datastore3 -> 4bd88e99-c67ad631-6c62-003048c30e8c lrwxr-xr-x 1 root root 35 Jul 12 13:59 Datastore4 -> 4dd7cf77-c3e57835-e9ef-003048c30e8c lrwxr-xr-x 1 root root 35 Jul 12 13:59 Hypervisor1 -> 386a41e4-ff1587ba-1385-2feaeed494ad lrwxr-xr-x 1 root root 35 Jul 12 13:59 Hypervisor2 -> 8c7e2fe8-f4c58d9f-34d3-8553ffee79a0 lrwxr-xr-x 1 root root 35 Jul 12 13:59 Hypervisor3 -> e00f98e1-2bcc0c91-e7a2-3487611c1557 drwxr-xr-x 1 root root 8 Jan 1 1970 e00f98e1-2bcc0c91-e7a2-3487611c1557 drwxr-x--- 1 root root 4096 Jun 30 12:36 fa828cd2-adbc3d72 lrwxr-xr-x 1 root root 17 Jul 12 13:59 nfs-vmds1 -> 0d6becf5-2ea0d633 lrwxr-xr-x 1 root root 17 Jul 12 13:59 nfs-vmds2 -> fa828cd2-adbc3d72 ~ # esxcfg-scsidevs -l mpx.vmhba0:C0:T0:L0 Device Type: CD-ROM Size: 0 MB Display Name: Local TSSTcorp CD-ROM (mpx.vmhba0:C0:T0:L0) Multipath Plugin: NMP Console Device: /vmfs/devices/cdrom/mpx.vmhba0:C0:T0:L0 Devfs Path: /vmfs/devices/cdrom/mpx.vmhba0:C0:T0:L0 Vendor: TSSTcorp Model: CDDVDW SH-S202N Revis: SB01 SCSI Level: 5 Is Pseudo: false Status: on Is RDM Capable: false Is Removable: true Is Local: true Other Names: vml.0005000000766d686261303a303a30 VAAI Status: unknown mpx.vmhba32:C0:T0:L0 Device Type: Direct-Access Size: 998 MB Display Name: Local USB Direct-Access (mpx.vmhba32:C0:T0:L0) Multipath Plugin: NMP Console Device: /vmfs/devices/disks/mpx.vmhba32:C0:T0:L0 Devfs Path: /vmfs/devices/disks/mpx.vmhba32:C0:T0:L0 Vendor: TinyDisk Model: 2005-03-10 Revis: 2.00 SCSI Level: 2 Is Pseudo: false Status: on Is RDM Capable: false Is Removable: true Is Local: true Other Names: vml.0000000000766d68626133323a303a30 VAAI Status: unknown naa.600050e0d7beda002095000037530000 Device Type: Direct-Access Size: 953664 MB Display Name: Local AMCC Disk (naa.600050e0d7beda002095000037530000) Multipath Plugin: NMP Console Device: /vmfs/devices/disks/naa.600050e0d7beda002095000037530000 Devfs Path: /vmfs/devices/disks/naa.600050e0d7beda002095000037530000 Vendor: AMCC Model: 9650SE-8LP DISK Revis: 4.10 SCSI Level: 5 Is Pseudo: false Status: on Is RDM Capable: false Is Removable: false Is Local: true Other Names: vml.0200000000600050e0d7beda002095000037530000393635305345 VAAI Status: unknown t10.AMCC____9QJ0ZCFYD87EFE007FC4 Device Type: Direct-Access Size: 953664 MB Display Name: Local AMCC Disk (t10.AMCC____9QJ0ZCFYD87EFE007FC4) Multipath Plugin: NMP Console Device: /vmfs/devices/disks/t10.AMCC____9QJ0ZCFYD87EFE007FC4 Devfs Path: /vmfs/devices/disks/t10.AMCC____9QJ0ZCFYD87EFE007FC4 Vendor: AMCC Model: 9650SE-8LP DISK Revis: 4.10 SCSI Level: 5 Is Pseudo: false Status: on Is RDM Capable: false Is Removable: false Is Local: true Other Names: vml.010000000039514a305a434659443837454645303037464334393635305345 VAAI Status: unknown t10.AMCC____9QJ16PFCD87EFE00CB5E Device Type: Direct-Access Size: 953664 MB Display Name: Local AMCC Disk (t10.AMCC____9QJ16PFCD87EFE00CB5E) Multipath Plugin: NMP Console Device: /vmfs/devices/disks/t10.AMCC____9QJ16PFCD87EFE00CB5E Devfs Path: /vmfs/devices/disks/t10.AMCC____9QJ16PFCD87EFE00CB5E Vendor: AMCC Model: 9650SE-8LP DISK Revis: 4.10 SCSI Level: 5 Is Pseudo: false Status: on Is RDM Capable: false Is Removable: false Is Local: true Other Names: vml.010000000039514a3136504643443837454645303043423545393635305345 VAAI Status: unknown t10.AMCC____U34961226AEF5C004A68 Device Type: Direct-Access Size: 476827 MB Display Name: Local AMCC Disk (t10.AMCC____U34961226AEF5C004A68) Multipath Plugin: NMP Console Device: /vmfs/devices/disks/t10.AMCC____U34961226AEF5C004A68 Devfs Path: /vmfs/devices/disks/t10.AMCC____U34961226AEF5C004A68 Vendor: AMCC Model: 9650SE-8LP DISK Revis: 4.10 SCSI Level: 5 Is Pseudo: false Status: on Is RDM Capable: false Is Removable: false Is Local: true Other Names: vml.01000000005533343936313232364145463543303034413638393635305345 VAAI Status: unknown ~ # esxcfg-scsidevs -a vmhba0 ata_piix link-n/a ide.vmhba0 (0:0:31.1) Intel Corporation 631xESB/632xESB IDE Controller vmhba1 3w-9xxx link-n/a unknown.vmhba1 (0:1:0.0) 3ware Inc 3ware 9650SE vmhba32 usb-storage link-n/a usb.vmhba32 () USB vmhba33 ata_piix link-n/a ide.vmhba33 (0:0:31.1) Intel Corporation 631xESB/632xESB IDE Controller ~ # esxcfg-scsidevs -m t10.AMCC____U34961226AEF5C004A68:1 /vmfs/devices/disks/t10.AMCC____U34961226AEF5C004A68:1 4bc8414f-3206fe54-f06e-003048c30e8c 0 Datastore1 naa.600050e0d7beda002095000037530000:1 /vmfs/devices/disks/naa.600050e0d7beda002095000037530000:1 4dd7cf77-c3e57835-e9ef-003048c30e8c 0 Datastore4 t10.AMCC____9QJ16PFCD87EFE00CB5E:1 /vmfs/devices/disks/t10.AMCC____9QJ16PFCD87EFE00CB5E:1 4bd88e99-c67ad631-
So, I've downloaded the UCS adapter .pak file and installed it. When I go to configure it, I cannot seem to get the credentials correct for registering the UCS domain. I get the error attached in the screenshot below. I've tried multiple authentication formats, but get the same error. All credentials have been confirmed separately. I've got two separate UCS domains to register, but both provide the same error.
With the UCS and vRealize credentials combined in this one registration step, its unclear where the problem lies (screenshot attached). I get the feeling that the formats I've tried are incorrect.
Google has been little help with this particular problem. Has anyone else had this problem and have a good place to look for a failure log of some kind? Or do you know for sure what format the credentials need to be provided in?
If it matters:
vROPS 6.2
UCS 2.2(2c)