It sounds like you have a device failure if you're getting that message.
↧
Re: could not power on VM
↧
Re: could not power on VM
This is the message the kernel is throwing when trying to open the disk
2017-12-20T02:08:49.060Z| vmx| I125: DISKLIB-VMFS : VmfsExtentCommonOpen: DiskLibIsExtentPathSecure claims extent path "/vmfs/volumes/5a372d98-c11be218-1176-98f2b302b20c/WEN-PC12/WEN-PC12-flat.vmdk" is insecure, failing disk open.
Where is this stored? ESXi seems to think it's on scratch.
Open your ESXi host in the host client and past a screenshot of the Events pane.
↧
↧
Re: could not power on VM
please check.
Liu Wei
↧
Re: could not power on VM
??
↧
ESXi hosts always switch disconnecting and connected to vCenter, and ESXi always report flush firmware configuration
Hello,
I bought a new server HP DL380 Gen9, and installed ESXi5.5 U3 HPE.
Then I met a very strange matter.
I used vclient 5.5 U3 connect to ESXi host and found many tasks. These tasks will happen every minute.
I added this ESXi host in VCenter 6.5, then every some time(it looks like one minute), this host will disconnect from vcenter and display not responding about 2 seconds.
Whatever I change vcenter to 5.5 U3 or move this host into the same LAN with VCenter, this strange problem persists.
Could any one help me? Thanks.
Task Log in vclient:
Configure Storage I/O Control on datastore
Completed
vpxuser
2017/12/20 9:50:02
2017/12/20 9:50:02
2017/12/20 9:50:02
Update vSphere Distributed Switch list
Completed
vpxuser
2017/12/20 9:50:02
2017/12/20 9:50:02
2017/12/20 9:50:02
Select virtual NIC
135.251.69.111
Completed
vpxuser
2017/12/20 9:50:02
2017/12/20 9:50:02
2017/12/20 9:50:02
Flush firmware configuration
Completed
vpxuser
2017/12/20 9:50:01
2017/12/20 9:50:01
2017/12/20 9:50:02
Update management server IP
135.251.69.111
Completed
vpxuser
2017/12/20 9:50:01
2017/12/20 9:50:01
2017/12/20 9:50:01
Update global message
Completed
vpxuser
2017/12/20 9:50:01
2017/12/20 9:50:01
2017/12/20 9:50:01
Event Log in vcenter:
| Description | Type | Date Time | Task | Target | User |
| 有关 135.251.69.111 的警报“主机连接和电源状况”已从红色更改为绿色 | 信息 | 12/20/2017 9:39:15 AM | 135.251.69.111 | ||
| 已建立连接 | 信息 | 12/20/2017 9:39:15 AM | 135.251.69.111 | ||
| 事件 155538“Host 135.251.69.111 in dcn is not responding”触发了 135.251.69.111 上的警报“主机连接故障” | 错误 | 12/20/2017 9:39:15 AM | 135.251.69.111 | ||
| 有关 135.251.69.111 的警报“主机连接和电源状况”已从绿色更改为红色 | 信息 | 12/20/2017 9:39:14 AM | 135.251.69.111 | ||
| 主机无响应 | 错误 | 12/20/2017 9:39:14 AM | 135.251.69.111 | ||
| 有关 135.251.69.111 的警报“主机连接和电源状况”已从红色更改为绿色 | 信息 | 12/20/2017 9:38:15 AM | 135.251.69.111 | ||
| 已建立连接 | 信息 | 12/20/2017 9:38:15 AM | 135.251.69.111 | ||
| 警报“主机连接故障”: 已发送实体 135.251.69.111 的 SNMP 陷阱 | 信息 | 12/20/2017 9:38:15 AM | 135.251.69.111 | ||
| 事件 155531“Host 135.251.69.111 in dcn is not responding”触发了 135.251.69.111 上的警报“主机连接故障” | 错误 | 12/20/2017 9:38:15 AM | 135.251.69.111 | ||
| 有关 135.251.69.111 的警报“主机连接故障”已触发操作 | 信息 | 12/20/2017 9:38:15 AM | 135.251.69.111 |
Best Regards,
Xici
↧
↧
Re: could not power on VM
↧
Re: could not power on VM
↧
Re: could not power on VM
↧
Host Does Not Support Passthrough Configuration
Ok here is my problem...
I am running ESXi 6.0 on a HP ProLiant DL380 G5 (which pretty much looks like this https://www.amazon.com/HP-ProLiant-DL380-G5-Quad-Core/dp/B00CLUIMGQ only thing is I have 2 Xeon 5160 processors at 3 GHz so they won't handle anything higher then ESXi 6.0 not 6.5)
Next I have a Startech PCI expansion bus plugged into the machine...(See link for details PCIe to 4 Slot PCI Expansion System | Slot Conversion | StarTech.com Canada), I know this machine works nicely because it used in so many different PC's. Why I have this box in is because I need to expand my bus into some PCI slots so I can run some NI DAQ hardware that fits to a PCI slot.
Next step....In this expansion box I have the following cards...
- NI PCI-6031 (See link for more details NI PCI-6031E - National Instruments)
- NI PCI-6704 (See link for more details PCI-6704 - National Instruments)
- NI PCI-6509 (See link for more details PCI-6509 - National Instruments)
So, since I have this ProLiant box, you can see that these 3 cards wont fit into the system because there PCI and the HP box doesn't have any PCI slots in them, they are only PCI express.
Now I have a virtual machine setup to take this hardware in. However, when I select this server in vSphere, then click the configuration tab, then select advanced settings, I get "host does not support passthrough configuration"
Could somebody please help me make this hardware show up, so I can pass these 3 cards to the virtual machine I would like to run them on.
Thank you!
↧
↧
Re: Host Does Not Support Passthrough Configuration
The Xeon 5160 CPU does not support Intel Virtualization Technology for Directed I/O (VT-d); so passthrough is not possible at all.
https://ark.intel.com/products/27219/Intel-Xeon-Processor-5160-4M-Cache-3_00-GHz-1333-MHz-FSB
↧
Re: Host Does Not Support Passthrough Configuration
Hi FenrisUltra,
Did you install the VIBs for the PCI cards?
The issue is that the Image from HP or the original Image from ESXi does not have the HP Drivers integrated.
Therefore you have to download the VIBs and then upload them to the ESXi Hosts with WINSCP or with vUM or on the ESXi Host interface.
Whenever you have done it, reboot the ESXi Host, then you will see that they will be recognized.
Whenever you have uploaded the VIBs, if you do it with WINSCP you have to install them by using this command. (Put them in /tmp)
esxcli software vib install -d /tmp/*
* and the path to the VIB.
If you never worked with VIBs before, here is a good article for it:
http://blogs.vmware.com/vsphere/2011/09/whats-in-a-vib.html
Best regards,
Marco
↧
High RAM usage
Hi,
im having some high ram usage on one of my vm's its a "Guest -VM" I have 6 blade servers but even if I move it to a different blade it still uses all 16GB ram im abit confused as the others don't,
ive also tried reinstalling the vm clean but it does the same unless its because its only DDR3 ram not DDR4 I believe its DDR3 1600mhz.
is there something missing orr.
Matt
↧
Re: vSphere Client Console Display Resolution
Thanks a lot, it helped me.
↧
↧
Re: High RAM usage
"Guest -VM"
What do you mean by ""Guest -VM""?
Without knowing what that VM does and looking at specifics including its configuration, you don't provide much to go on.
↧
Re: ESXi hosts always switch disconnecting and connected to vCenter, and ESXi always report flush firmware configuration
Any reason why you'd be installing an old version of ESXi on new hardware? In the past, results have always been mixed when attempting this (and connecting to a new version of vCenter). Do you get the same result if you have ESXi 6.5 installed on this hardware?
↧
Re: Unable to SSH to ESXi after 6.0U2 with PuTTY [SOLVED]
Thanks for posting,
great, it works fine with ESXi 6.5 to
↧
Re: could not power on VM
What type of device is backing DS02? Those USB configuration messages shown in the event log are strange. Is this a USB device?
From a SSH session on your ESXi host, paste the output of df -h
↧
↧
Re: ESXi hosts always switch disconnecting and connected to vCenter, and ESXi always report flush firmware configuration
Thanks for you reply, daphnissov.
Of course, I installed ESXi6.5 on this machine firstly. Then I found this result. So I installed the old version ESXi5.5 on it instead of new version.
I have tried many times of couples between ESXi and vCenter on this machine. I got the same result.
for example:
ESXI 6.5 ->VCenter 6.5
ESXI 5.5 U3 ->VCenter 6.5
ESXI 5.5 U3 ->VCenter 5.5 U3
ESXI 5.5 U3 HPE ->VCenter 6.5
ESXI 5.5 U3 HPE ->VCENTER 5.5 U3
I could not fix this problem.
↧
Re: High RAM usage
Also, what do you mean by "usage" ? Is the memory active or consumed? There's a difference.
Consumed is how much has been allocated to the VM, and active is how much is currently being used. Consumed will remain high until the OS sends the hypervisor a signal saying it can release the RAM, but if you're running a flavor of Linux, this call is never received by the hypervisor, and therefore RAM is never released even if it's not being used.
Is the underlying OS on the VM reporting that it's using all 16Gb? That's the best way to check it.
↧
Re: ESXi hosts always switch disconnecting and connected to vCenter, and ESXi always report flush firmware configuration
First thing I see wrong in your screenshots is you have installed vCenter Server by IP and not name. You always need to use FQDN and ensure forward and reverse DNS lookups are working. Second you've added the host by IP. Again, configure a name and use it when adding to vCenter. DNS must work all around. If you correct these things and install ESXi 6.5 and it's still disconnecting, pull the vpxa log file from the host and attach to see what might be going on.
↧