Quantcast
Channel: VMware Communities: Message List - ESXi
Viewing all 28826 articles
Browse latest View live
↧

Tiny 2 Host Environment - Configuration

June 3, 2019, 7:50 pm
$
0
0

Hi all,

 

I have a very small, 2 host ESXi setup (vCenter Essentials Plus 6.7) and each host as 4 x 1Gbit NIC's (HP DL380 Gen10)

My question is, is this considered typical in terms of security?:

 

2 x NIC teamed for production, (static channel group on switch, no LACP due to licencing)

1 x NIC for management / vmk0 (physically separate to switch) different VLAN

1 x NIC for vMotion / vmk1 *

 

* for vMotion I have connected the two hosts ports with a single patch cable (no switch) and I'm using link-local addresses for vMotion.

I don't intend ever to have more than 2 hosts (unless migration upgrading), is this ok do to? It works as expected.

 

Throughput/Performance not an issue, I don't have 10Gb switches yet.

 

Cheers all,

 

Matt

↧
Search

Re: Tiny 2 Host Environment - Configuration

June 4, 2019, 3:56 am
$
0
0

Hi StixNZ,

 

Looks okay however I would consider having both Management and VMotion portgroups on the same vSwitch. Then make one of the NICs active Management network with the other in Standby. Do the reverse for the VMotion portgroup.

 

This will give Management and VMotion networks redundancy as well.

 

Kind regards.

↧
↧

New Datastore Error

June 4, 2019, 4:33 am
$
0
0

Hi community,

 

its probably a simple fix but im having trouble trying to create a datastore on two hosts that were previously used?

 

when i try and create a datastore it shows this error (Either the selected disk already has a VMFS datastore or the host cannot perform a partition table conversion. Select another disk)

 

when i try to delete the exsisting partitions it just shows an error and wont delete them.

 

i have tried deleting the disk in the server raid controller i have it set up as "2x SSD's in a RAID 1"

 

 

Matto

↧

Re: New Datastore Error

June 4, 2019, 4:53 am
↧

Re: New Datastore Error

June 4, 2019, 4:56 am
$
0
0

Matto,

The easiest solution would probably be to login to the command line of the esxi host and use partedutil to delete the existing partitions before you can add them in a normal way (like you've already tried to).

 

Lars

↧
↧

Re: New Datastore Error

June 4, 2019, 5:11 am
$
0
0

try to rescan the vmfs volumes and than try

↧

Re: New Datastore Error

June 4, 2019, 5:28 am
$
0
0

HI LARS,

 

what is the process of the command line ? what do i have to type in to delete the partitions?

i tried following that other article but none of the options are displayed what it says.

 

matto

↧

Re: New Datastore Error

June 4, 2019, 5:28 am
$
0
0

hi danand84,

 

i tried that a few times to rescan the volmes.

 

matto

↧
Search

Re: New Datastore Error

June 4, 2019, 5:57 am
$
0
0

Matto,

It should be something like this:

[root@qaesx01:/dev/disks] ls /vmfs/devices/disks/

mpx.vmhba32:C0:T0:L0                    vml.0000000000766d68626133323a303a30

mpx.vmhba32:C0:T0:L0:1                  vml.0000000000766d68626133323a303a30:1

mpx.vmhba32:C0:T0:L0:5                  vml.0000000000766d68626133323a303a30:5

mpx.vmhba32:C0:T0:L0:6                  vml.0000000000766d68626133323a303a30:6

mpx.vmhba32:C0:T0:L0:7                  vml.0000000000766d68626133323a303a30:7

mpx.vmhba32:C0:T0:L0:8                  vml.0000000000766d68626133323a303a30:8

mpx.vmhba32:C0:T0:L0:9                  vml.0000000000766d68626133323a303a30:9

Above you can see I have two disks that each have quite a few partitions.

 

[root@qaesx01:/dev/disks] partedUtil get vml.0000000000766d68626133323a303a30

1947 255 63 31293440

1 64 8191 0 128

5 8224 520191 0 0

6 520224 1032191 0 0

7 1032224 1257471 0 0

8 1257504 1843199 0 0

9 1843200 7086079 0 0

[root@qaesx01:/dev/disks]

 

partedUtil delete "/vmfs/devices/disks/diskname partitionnumber"

 

In the last command you will need to replace the diskname and partitionnumber with the info found by the ls command.

 

Lars

↧
↧

Re: How to automatically suspend VMs during power outage? (ESXi 6.7 / HPE ProLiant / APC Smart UPS)

June 4, 2019, 6:05 am
↧

Re: The Small Footprint CIM Broker Daemon (SFCBD) is running, but no data has been reported. You may need to install a CIM provider for your storage adapter.

June 4, 2019, 11:29 pm
$
0
0

has anybody fixed this issue?

 

I'm running esxi 6.5 on Dell R640 platform and under same issue which on storage monitoring tab.

 

who does can support me? dell or vmware?

↧

Re: Migration to new datastore (rebuilding the old one)

June 5, 2019, 5:03 am
$
0
0

Hi Andre,

 

Thanks for your reply and additional insight.

 

This ESXi instance is installed on this very same RAID0... Will be there any way to migrate then?

 

Or the only way would be the following:

1. Migrate all VMs to temporary disk,

2. Break RAID0 (decommission one disk)

3. Rebuild RAID0

4. Install ESXi in RAID-0 and hopefully migrate VMs from temporary disk to RAID0 back.

↧

Re: ESXi 6.7 Windows 2016/2019 freeze

June 5, 2019, 6:39 am
$
0
0

Hello Bernhad

 

I have a similar issue with Windows 10 1809 clients. We did an inplace upgrade from build 1709 and 1803 to Windows 1809.

 

After a few days the VMs are also unresponsible and hang. Logs are clean and only a reset helps.

 

2019-05-27T17:30:02.594Z| vmx| I125: GuestRpc: Got error for channel 1 connection 1111: Remote disconnected

2019-05-27T21:27:39.396Z| vmx| I125: GuestRpcSendTimedOut: message to toolbox timed out.

2019-05-27T21:27:46.225Z| vmx| I125: GuestRpcSendTimedOut: message to vdiagent timed out.

2019-05-27T21:27:46.225Z| vmx| I125: ToolsGetAppGenericName: vdiagent status not set

2019-05-27T21:27:53.295Z| vcpu-0| I125: Tools: Tools heartbeat timeout.

2019-05-27T21:27:53.295Z| vcpu-0| I125: Tools: Running status rpc handler: 1 => 0.

2019-05-27T21:27:53.295Z| vcpu-0| I125: Tools: Changing running status: 1 => 0.

2019-05-27T21:27:59.399Z| vmx| I125: GuestRpcSendTimedOut: message to toolbox timed out.

2019-05-27T21:27:59.399Z| vmx| I125: GuestRpc: app toolbox's second ping timeout; assuming app is down

2019-05-27T21:27:59.400Z| vmx| I125: GuestRpc: Reinitializing Channel 0(toolbox)

2019-05-27T21:27:59.400Z| vmx| I125: GuestMsg: Channel 0, Cannot unpost because the previous post is already completed

2019-05-27T21:28:06.229Z| vmx| I125: GuestRpcSendTimedOut: message to vdiagent timed out.

2019-05-27T21:28:06.229Z| vmx| I125: GuestRpc: app vdiagent's second ping timeout; assuming app is down

2019-05-27T21:28:06.229Z| vmx| I125: ToolsGetAppGenericName: vdiagent status not set

2019-05-27T21:28:06.229Z| vmx| I125: GuestRpc: Reinitializing Channel 1(vdiagent)

2019-05-27T21:28:06.229Z| vmx| I125: GuestMsg: Channel 1, Cannot unpost because the previous post is already completed

2019-05-27T21:28:06.229Z| vmx| I125: ToolsGetAppGenericName: vdiagent status not set

2019-05-27T21:28:58.295Z| vcpu-0| I125: Tools: Running status rpc handler: 0 => 1.

2019-05-27T21:28:58.295Z| vcpu-0| I125: Tools: Changing running status: 0 => 1.

2019-05-27T21:29:19.295Z| vcpu-0| I125: Tools: Tools heartbeat timeout.

 

We are on VMware ESXi, 6.5.0, 9298722.

 

Did you find a solution to your problem?

 

 

thanks

↧
↧

Help with psod

June 5, 2019, 7:13 am
$
0
0

Hello all, after when i`m add a new wirtual mashine i recived psod. I have new desctop hardware. Thanks all!

6.7.0

8169922

Log

2019-06-05T10:16:07.202Z cpu12:2099602)@BlueScreen: #PF Exception 14 in world 2099602:vmm1:UFS IP 0x418006e8063f addr 0x436083938028

PTEs:0x1004ce023;0x0;

2019-06-05T10:16:07.202Z cpu12:2099602)Code start: 0x418006e00000 VMK uptime: 0:02:01:08.016

2019-06-05T10:16:07.203Z cpu12:2099602)0x451a1cf1bad8:[0x418006e8063f]CPUTopology_AreRelated@vmkernel#nover+0x2b stack: 0x0

2019-06-05T10:16:07.203Z cpu12:2099602)0x451a1cf1bae0:[0x418007113771]CpuSchedRebalance_StickySysCyclesAdd@vmkernel#nover+0x42 stack: 0x43006a0d04b0

2019-06-05T10:16:07.203Z cpu12:2099602)0x451a1cf1bb10:[0x418006eedbac]IntrCookie_DoInterrupt@vmkernel#nover+0x1ed stack: 0x7780

2019-06-05T10:16:07.204Z cpu12:2099602)0x451a1cf1bbc0:[0x418006eee0f1]IntrCookie_VmkernelInterrupt@vmkernel#nover+0x3a stack: 0xffffffffffffffef

2019-06-05T10:16:07.204Z cpu12:2099602)0x451a1cf1bbe0:[0x418006f442ec]IDT_IntrHandler@vmkernel#nover+0x9d stack: 0x0

2019-06-05T10:16:07.204Z cpu12:2099602)0x451a1cf1bc00:[0x418006f5e066]gate_entry@vmkernel#nover+0x67 stack: 0x0

2019-06-05T10:16:07.204Z cpu12:2099602)0x451a1cf1bcc0:[0x418006e9ac48]Power_ArchSetCState@vmkernel#nover+0x15c stack: 0x0

2019-06-05T10:16:07.205Z cpu12:2099602)0x451a1cf1bcf0:[0x418007103302]CpuSchedIdleLoopInt@vmkernel#nover+0x333 stack: 0x450184afa000

2019-06-05T10:16:07.205Z cpu12:2099602)0x451a1cf1bd60:[0x418007105fd5]CpuSchedDispatch@vmkernel#nover+0x12aa stack: 0x451a00000001

2019-06-05T10:16:07.205Z cpu12:2099602)0x451a1cf1beb0:[0x4180071074bb]CpuSchedWait@vmkernel#nover+0x2f4 stack: 0x450100000000

2019-06-05T10:16:07.205Z cpu12:2099602)0x451a1cf1bf40:[0x418007107c34]CpuSched_VcpuHalt@vmkernel#nover+0x12d stack: 0x0

2019-06-05T10:16:07.206Z cpu12:2099602)0x451a1cf1bfa0:[0x418006f335a6]VMMVMKCall_Call@vmkernel#nover+0xf7 stack: 0x0

2019-06-05T10:16:07.206Z cpu12:2099602)0x451a1cf1bfe0:[0x418006f57cdd]VMKVMM_ArchEnterVMKernel@vmkernel#nover+0xe stack: 0x0

2019-06-05T10:16:07.208Z cpu12:2099602)base fs=0x0 gs=0x418043000000 Kgs=0x0

2019-06-05T10:16:07.208Z cpu12:2099602)vmkernel             0x0 .data 0x0 .bss 0x0

2019-06-05T10:16:07.208Z cpu12:2099602)chardevs             0x418007528000 .data 0x417fc0000000 .bss 0x417fc0000440

2019-06-05T10:16:07.208Z cpu12:2099602)user                 0x418007530000 .data 0x417fc0400000 .bss 0x417fc0410a00

2019-06-05T10:16:07.208Z cpu12:2099602)procfs               0x41800762a000 .data 0x417fc0a00000 .bss 0x417fc0a00240

↧

Re: Help with psod

June 5, 2019, 7:36 am
$
0
0

ESXi is not meant to be installed on desktop hardware. Your PSOD may be a result of incompatible hardware.

↧
Search

Re: Help with psod

June 5, 2019, 7:39 am
$
0
0

I know, but it work 6 month without problem. i want more exact answer

↧

Re: Help with psod

June 5, 2019, 7:50 am
$
0
0

If you want an exact answer you can open an SR with VMware...except you don't have support and aren't using supported hardware.

↧
↧

Re: Help with psod

June 5, 2019, 7:55 am
$
0
0

I suggest getting VMware workstation and install a nested ESXi server, yes its a little slower and the os and workstation takes extra resources, but it's more likely to work.

↧

Re: Don't send the combination ctrl/ alt/ suppr

June 5, 2019, 8:20 am
$
0
0

if it is the same issue as me.

It was not working in the web browser for 2012r2 2016 server

I find out a workaround

I donwloaded the external console (the app) then sending it key command from the app is working

unlike the web browser

↧

Upgrading ESXi 6.0 to 6.5 U2 on HP Server

June 5, 2019, 11:07 am
$
0
0

Hi,

I am trying to update HPE Microserver with ESXi 6.0 U2 to ESXi 6.5 U2 - I am using HPE custom image (VMware-ESXi-6.5.0-Update2-9298722-HPE-preGen9-650.U2.9.6.8.3-Sep2018.iso)

 

During the update process I am getting OSError [Errno 39] Directory not empty: '/vmfs/volumes/<something>System Volume Information'

 

I was checking for state.xxx folders in /bootbank and /newbank but nothing is there

 

This is contents of /altbootbank

total 257

drwxr-xr-x    1 root     root           512 Jun  5 18:05 ..

drwxr-xr-x    1 root     root             8 Jun  5 12:15 System Volume Information

-rwx------    1 root     root           184 Jun  5 17:45 imgdb.tgz

 

Here is the upgrade log:

2019-06-05T17:28:49Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/bootOption', '-rp']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-06-05T17:28:49Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/bootOption', '-ro']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-06-05T17:28:49Z esxupdate: imageprofile: INFO: Adding VIB VMware_locker_tools-light_6.0.0-2.34.3620759 to ImageProfile (Updated) HPE-ESXi-6.0.0-Update2-iso-600.9.6.0.49

2019-06-05T17:28:49Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/esxcfg-advcfg', '-U', 'host-acceptance-level', '-G']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-06-05T17:28:49Z esxupdate: root: DEBUG: Finished execution of command = profile.setacceptance

2019-06-05T17:28:49Z esxupdate: root: DEBUG: Completed esxcli output, going to exit esxcli-softwareinternal

2019-06-05T17:45:28Z esxupdate: root: INFO: Command = profile.setacceptance

2019-06-05T17:45:28Z esxupdate: root: INFO: Options = {}

2019-06-05T17:45:28Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/bootOption', '-rp']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-06-05T17:45:28Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/bootOption', '-ro']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-06-05T17:45:28Z esxupdate: imageprofile: INFO: Adding VIB VMware_locker_tools-light_6.0.0-2.34.3620759 to ImageProfile (Updated) HPE-ESXi-6.0.0-Update2-iso-600.9.6.0.49

2019-06-05T17:45:28Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/esxcfg-advcfg', '-U', 'host-acceptance-level', '-G']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-06-05T17:45:28Z esxupdate: root: DEBUG: Finished execution of command = profile.setacceptance

2019-06-05T17:45:28Z esxupdate: root: DEBUG: Completed esxcli output, going to exit esxcli-softwareinternal

 

Any idea how to fix this?

Thanx,

D

↧
Viewing all 28826 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>