Hi all,

I am planning to install 2-node vSAN ROBO for our small office. I will appreciate your help on the networking side for the witness traffic separation.

I am not sure whether I have to separate the witness traffic from management or put the witness traffic on management.

If I can use the management network for witness traffic, it would be easy for me not to bother the network team too much.

I plan to configure the VDS/VSS as below

Management                          192.168.3.11--Will have two 10GB Acrive/Standby

vSAN-Direct Connect            10.10.20.11  -- Server A Port1 Active and Port2 Standby

vMotion-Direct Connect        10.10.30.11  ---Server A Port2 Active and Port1 Standby

Virtual Machines Lan               10.10.1.0/24-- Two 10 GB nic ports

I guess i have to issue the following at each Esxi host at the ROBO site to separate witness traffic to use the management routed netwrok.

esxcli vsan netwrok ip add -I vmk0 -T=Witness

If i am correct with above design,

Should I have to untag vmk1 at the witness appliance and tag it for vmk0 as the vsan traffic or can i put both witness and management at both network and leave vmk1 as the witness port?

Hello averyone

I have a problem

When installing Vmware Horizon Agent on Windows 10 and wWindows Server 2019

"Register with Horizon Connection Server" dialog box Not displayed  And the installation process ends without registering the "Horizon Connection Server" address.

If I do this with the command line, it will still not be registered on the Horizon Connection Serevr !!

Do you have a solution to this problem?

In my new ESXI 7 server I have real customers ans I can not right to try any security experiments because lost control is possible.

But I need to check something. How is possible to do this?

Can I install ESXI 7 as virtual machine? Or this is impossible and I need to install ESXI for security experiments only for free physical computer at home?

And is exist a something standard security tester for ESXI 7?

Hi,

after a clean 7.0.1 install the boot device is up to 128 GB filled with a VFFS and the rest has a VMFS.

I don't need a VMFS on the boot device so i deleted it.

Because i can enable the Host Swap Cache, but i think 112 GB is not very much. And when enabling that for perhaps 96GB i get a alert that the VFFS is nearly full. So when using the additional 128GB and using 128 GB for Host Swap Cache there will still be 112GB free, that sounds good for me...

But in the Virtual Flash Resource Management the free space isn't shown, only a empty disk will be shown.

Is there a way to extend the VFFS to fill up the disk?

Kind regards

Stefan

Hello,

any ideas?

esxcli software profile update -p DEL-ESXi-700_15843807-A01 -d /vmfs/volume

s/ISO/updateFiles/VMware-VMvisor-Installer-7.0.0-15843807.x86_64-DellEMC_Customized-A01.zip --no-hardwa

re-warning

[InstallationError]

Failed to finish bootbank stage: ('/tmp/stagebootbank/imgdb.tgz', 'Error writing tar database: Should have base image when an addon exists.')

      cause = ('/tmp/stagebootbank/imgdb.tgz', 'Error writing tar database: Should have base image when an addon exists.')

I am trying to update ESXI profile but i got theses errors come out.

After google, i can not find any information to solve that.

Please help!

Added an extra HDD to my VM (ruling windows 10) and the OS detects the second HD as a USB. Suggestions how to change this to get the Windows 10 to detect this second HD as a static's HD?

Is exist protection of ESXI 7 server more than simple password? For example 2FA or IP restriction?

Hi there.  I don't expect an easy solution, if any at all, but it seems my Virtual Machine finally crapped out.  I was running a Windows 7 machine so that I could use 3 pretty archaic small apps (one of them which locks you out when you install it on a new computer without deauthorizing it first!).  Since I'm still on Mohave, and was planning to upgrade to Catalina or Big Sur eventually, I figured I might as well upgrade to Fusion 11.  Before doing anything I backed up the whole machine to the cloud, backed up docs and files to multiple HD's and cloud services, had a small snafu where I stupidly deleted the original parent Virtual Disk, but then recovered it from a local backup.  I got the machine up and running again, did all my snapshot cleanups (reducing it from 3 to 2 in the interest of disk space), verified my various backups, and installed Fusion 11.5.  I ran it, it upgraded the compatibility of my VM, booted it just fine.  I tested everything, and I think I may have tried to run some MS Windows software updates that always failed anyway, and they still failed.  So nothing new there, and I shut everything down to get back to work in those apps at a later date.

Ten days later, and Windows 7 won't boot up.  It runs disk repair and cannot repair.  Error is Missing OSLoader.  My 16 yr old wizkid son did a bunch of digging in the terminal, looking through the tree, etc.  He says it's corrupt.  I downloaded the cloud backup of the VM from 10 days ago, tried to run it off an external drive, and same problem.  I tried a fresh copy, downgraded it to hardware v. 12, opened it in Fusion 8.1, and same disk Missing OSLoader failure, no repair possible.  I have a ~1 yr old copy on my regular Time Machine backup, but I don't know if that will give me the same problem and I'm exhausted at this point.

So is this it? Is this machine/HD recoverable in the slightest?  Thank you .

Hello to everyone,

I am running a lab trying to see how Auto Deploy works.

According to the documentation for security reasons, Auto Deploy traffic should be isolated from the management network. But it seems that I can't find any resource/guide with this configuration.

My management network is VLAN 10, 172.16.10.0/24

VCSA, 172.16.10.20

Esxi host 1, 172.16.10.2 (Management NICs, vmnic0, vmnic1)

I created a new VLAN 201 for the Auto Deploy traffic.

TFTP server 172.16.201.20

In my Auto Deploy rule, I have only an image. I don't use host profile for now.

I have a new host that I want to provision. Identical hardware to esxi host 1.

I connect a NIC to VLAN 201.

Esxi host 2 boots and the deployment starts.

According to documentation, host should be added to the Datacenter in Vcenter.

The problem is that when boot is completed, the esxi host 2 has an IP from the range of VLAN 201 and not from VLAN 10. Thus, esxi host 2 is not added to Vcenter.

Any ideas how I can make this work?

Thank you in advance for your help.

I am trying to post a notice with a block of text right after the welcome but before the license agreement.  I have this working as I want using a parameterGroup/infoParameter and using <insertAfter>welcome</insertAfter>, the only problem is that i am reading the textfile from my local filesystem, not from within the installer, so of course it won't work on another system.

How can i set a text variable that can be used by the installer either during the build phase, or access a text file that is part of the distribution well before components are loaded?  This needs to accessed well before the components are selected, before the license agreement is accepted. i don't see any way to add a file out side of the components.    setting an installer variable during the build process doesn't work, since the variable is not still defined when im running the installer.  i could imagine embedding the text in the xml would work, but it is too long and may need to be updated separately, so that i not desirable.  how can this be achieved? 

Okay team – what's going on?

My administrator who uses workstation updated herself to version 16 this morning and installed it and it fell over.

She then tried to put 15.6 back on and that install failed too

This is on a vanilla version of Windows 10 64-bit updated to version 2004

Given there is work to do here what we do next?

Hi,

We published only RDP (remote desktop) App on Horizon 7

Launch RDP App --> Connect to PC - via Horizon client 5.0.0 build-12606690

when user click ALT+TAB (switch windows) is Not work, keyboard Not redirect to remote PC

* If launch Full VDI Desktop  - work correct

** if connect to Terminal without horizon client, via rdp (mstsc),  alt+tab work correct !!!

Try

Set in RDP in settings - Apply Windows key combination: On the remote computer - not help

How to fix ALT+TAB for RDP App published ?

Hello,

I want to migrate a vCenter 6.5 (Windows) to vCenter 6.7 appliance but I have some questions. In vCenter 6.5 I have the vCloud Availabilty to backup some VM's and I would like to maintain all configurations after this upgrade. What cconsideration we need to pay attention to don't lose confs and replications?

Thanks in advance,

It casued 3 times recently,and here is the log I have：

2012-01-04T11:14:21.190Z cpu0:2097642) [45m [33;1mVMware ESXi 6.7.0 [Releasebuild-10764712 x86_64] [0m

#GP Exception 13 in world 2097642:tq:tcpip4 @ 0x41803015d764

2012-01-04T11:14:21.190Z cpu0:2097642)cr0=0x8001003d cr2=0x7ffbb1a9fda4 cr3=0xc8c22000 cr4=0x216c

2012-01-04T11:14:21.190Z cpu0:2097642)frame=0x451a0a09bdf0 ip=0x41803015d764 err=0 rflags=0x10202

2012-01-04T11:14:21.190Z cpu0:2097642)rax=0x1c430940b15040 rbx=0x417fcde20e40 rcx=0x0

2012-01-04T11:14:21.190Z cpu0:2097642)rdx=0x0 rbp=0x4180301af8d8 rsi=0x430940b15040

2012-01-04T11:14:21.190Z cpu0:2097642)rdi=0x417fcde20e40 r8=0x4519c0000de8 r9=0xffffffffffffffff

2012-01-04T11:14:21.190Z cpu0:2097642)r10=0x3fc00000 r11=0x1 r12=0x0

2012-01-04T11:14:21.190Z cpu0:2097642)r13=0x13f0fda r14=0x0 r15=0x4180301af8d8

2012-01-04T11:14:21.190Z cpu0:2097642)pcpu:0 world:2097642 name:"tq:tcpip4" (S)

2012-01-04T11:14:21.190Z cpu0:2097642)pcpu:1 world:2099323 name:"vmx-mks:ros" (U)

2012-01-04T11:14:21.190Z cpu0:2097642)@BlueScreen: #GP Exception 13 in world 2097642:tq:tcpip4 @ 0x41803015d764

2012-01-04T11:14:21.190Z cpu0:2097642)Code start: 0x41802f400000 VMK uptime: 2:10:04:59.424

2012-01-04T11:14:21.190Z cpu0:2097642)0x451a0a09beb0:[0x41803015d764]callout_reset@(tcpip4)#<None>+0x90 stack: 0x16

2012-01-04T11:14:21.191Z cpu0:2097642)0x451a0a09bee0:[0x41803015da09]callout_timer@(tcpip4)#<None>+0x23e stack: 0xffffffffffffffff

2012-01-04T11:14:21.191Z cpu0:2097642)0x451a0a09bf30:[0x41802f43dcbd]VmkTimerQueueWorldFunc@vmkernel#nover+0x27e stack: 0x0

2012-01-04T11:14:21.191Z cpu0:2097642)0x451a0a09bfe0:[0x41802f709112]CpuSched_StartWorld@vmkernel#nover+0x77 stack: 0x0

2012-01-04T11:14:21.193Z cpu0:2097642)base fs=0x0 gs=0x418040000000 Kgs=0x0

2012-01-04T11:14:21.193Z cpu0:2097642)vmkernel             0x0 .data 0x0 .bss 0x0

2012-01-04T11:14:21.193Z cpu0:2097642)chardevs             0x41802fb31000 .data 0x417fc0000000 .bss 0x417fc0000440

2012-01-04T11:14:21.193Z cpu0:2097642)user                 0x41802fb39000 .data 0x417fc0400000 .bss 0x417fc0410a40

2012-01-04T11:14:21.193Z cpu0:2097642)procfs               0x41802fc34000 .data 0x417fc0a00000 .bss 0x417fc0a00240

2012-01-04T11:14:21.193Z cpu0:2097642)lfHelper             0x41802fc37000 .data 0x417fc0e00000 .bss 0x417fc0e03500

2012-01-04T11:14:21.193Z cpu0:2097642)vsanapi              0x41802fc3d000 .data 0x417fc1200000 .bss 0x417fc1203600

2012-01-04T11:14:21.193Z cpu0:2097642)vsanbase             0x41802fc55000 .data 0x417fc1600000 .bss 0x417fc16101a0

2012-01-04T11:14:21.193Z cpu0:2097642)vprobe               0x41802fc6a000 .data 0x417fc1a00000 .bss 0x417fc1a11d00

2012-01-04T11:14:21.193Z cpu0:2097642)vmkapi_mgmt          0x41802fcb7000 .data 0x417fc1e00000 .bss 0x417fc1e00200

2012-01-04T11:14:21.193Z cpu0:2097642)iodm                 0x41802fcbd000 .data 0x417fc2200000 .bss 0x417fc2200128

2012-01-04T11:14:21.193Z cpu0:2097642)vmkapi_v2_4_0_0_mgmt_shim 0x41802fcc2000 .data 0x417fc2600000 .bss 0x417fc26002e8

2012-01-04T11:14:21.193Z cpu0:2097642)vmkapi_v2_3_0_0_mgmt_shim 0x41802fcc3000 .data 0x417fc2a00000 .bss 0x417fc2a00180

2012-01-04T11:14:21.193Z cpu0:2097642)vmkapi_v2_2_0_0_mgmt_shim 0x41802fcc4000 .data 0x417fc2e00000 .bss 0x417fc2e001a0

2012-01-04T11:14:21.193Z cpu0:2097642)vmkapi_v2_2_0_0_vmkernel_shim 0x41802fcc5000 .data 0x417fc3200000 .bss 0x417fc320c9c0

2012-01-04T11:14:21.193Z cpu0:2097642)vmkapi_v2_4_0_0_vmkernel_shim 0x41802fccd000 .data 0x417fc3600000 .bss 0x417fc3612bc0

2012-01-04T11:14:21.193Z cpu0:2097642)vmkapi_v2_3_0_0_vmkernel_shim 0x41802fcd3000 .data 0x417fc3a00000 .bss 0x417fc3a0ff20

2012-01-04T11:14:21.193Z cpu0:2097642)vmkbsd               0x41802fcdc000 .data 0x417fc3e00000 .bss 0x417fc3e07100

2012-01-04T11:14:21.193Z cpu0:2097642)vmkusb               0x41802fd25000 .data 0x417fc4200000 .bss 0x417fc4207a40

2012-01-04T11:14:21.193Z cpu0:2097642)ne1000               0x41802fd9d000 .data 0x417fc4600000 .bss 0x417fc4603100

2012-01-04T11:14:21.193Z cpu0:2097642)vmw_ahci             0x41802fdf2000 .data 0x417fc4a00000 .bss 0x417fc4a005c0

2012-01-04T11:14:21.193Z cpu0:2097642)iscsi_trans          0x41802fe13000 .data 0x417fc4e00000 .bss 0x417fc4e01740

2012-01-04T11:14:21.193Z cpu0:2097642)iscsi_trans_compat_shim 0x41802fe27000 .data 0x417fc5200000 .bss 0x417fc5201148

2012-01-04T11:14:21.193Z cpu0:2097642)vmkapi_v2_3_0_0_vmklinux_shim 0x41802fe28000 .data 0x417fc5600000 .bss 0x417fc56017c4

2012-01-04T11:14:21.193Z cpu0:2097642)vmkplexer            0x41802fe29000 .data 0x417fc5a00000 .bss 0x417fc5a00260

2012-01-04T11:14:21.193Z cpu0:2097642)vmklinux_9           0x41802fe2e000 .data 0x417fc5e00000 .bss 0x417fc5e08f80

2012-01-04T11:14:21.193Z cpu0:2097642)vmkapi_v2_2_0_0_iscsiInc_shim 0x41802fec8000 .data 0x417fc6200000 .bss 0x417fc6200850

2012-01-04T11:14:21.193Z cpu0:2097642)vmkapi_v2_3_0_0_iscsiInc_shim 0x41802fecc000 .data 0x417fc6600000 .bss 0x417fc6600850

2012-01-04T11:14:21.193Z cpu0:2097642)etherswitch          0x41802fed1000 .data 0x417fc6a00000 .bss 0x417fc6a17f80

2012-01-04T11:14:21.193Z cpu0:2097642)portcfg              0x41802ff1f000 .data 0x417fc6e00000 .bss 0x417fc6e16f40

2012-01-04T11:14:21.193Z cpu0:2097642)vswitch              0x41802ff3d000 .data 0x417fc7200000 .bss 0x417fc7200640

2012-01-04T11:14:21.193Z cpu0:2097642)netsched_fifo        0x41802ff8e000 .data 0x417fc7600000 .bss 0x417fc7600060

2012-01-04T11:14:21.193Z cpu0:2097642)netsched_hclk        0x41802ff90000 .data 0x417fc7a00000 .bss 0x417fc7a03ec0

2012-01-04T11:14:21.193Z cpu0:2097642)netioc               0x41802ffa0000 .data 0x417fc7e00000 .bss 0x417fc7e000a0

2012-01-04T11:14:21.193Z cpu0:2097642)lb_netqueue_bal      0x41802ffa7000 .data 0x417fc8200000 .bss 0x417fc8200388

2012-01-04T11:14:21.193Z cpu0:2097642)vmklinux_9_2_3_0     0x41802ffae000 .data 0x417fc8600000 .bss 0x417fc8608ad8

2012-01-04T11:14:21.193Z cpu0:2097642)cnic_register        0x41802ffb1000 .data 0x417fc8a00000 .bss 0x417fc8a001e0

2012-01-04T11:14:21.193Z cpu0:2097642)vmklinux_9_2_2_0     0x41802ffb3000 .data 0x417fc8e00000 .bss 0x417fc8e08798

2012-01-04T11:14:21.193Z cpu0:2097642)r8168                0x41802ffb6000 .data 0x417fc9200000 .bss 0x417fc9200380

2012-01-04T11:14:21.193Z cpu0:2097642)dm                   0x41803000f000 .data 0x417fc9600000 .bss 0x417fc9600000

2012-01-04T11:14:21.193Z cpu0:2097642)nmp                  0x418030012000 .data 0x417fc9a00000 .bss 0x417fc9a04630

2012-01-04T11:14:21.193Z cpu0:2097642)hpp                  0x418030043000 .data 0x417fc9e00000 .bss 0x417fc9e02bf8

2012-01-04T11:14:21.193Z cpu0:2097642)vmw_satp_local       0x41803004d000 .data 0x417fca200000 .bss 0x417fca200020

2012-01-04T11:14:21.193Z cpu0:2097642)vmw_satp_default_aa  0x418030051000 .data 0x417fca600000 .bss 0x417fca600000

2012-01-04T11:14:21.193Z cpu0:2097642)vmw_psp_lib          0x418030053000 .data 0x417fcaa00000 .bss 0x417fcaa00290

2012-01-04T11:14:21.193Z cpu0:2097642)vmw_psp_fixed        0x418030055000 .data 0x417fcae00000 .bss 0x417fcae00000

2012-01-04T11:14:21.193Z cpu0:2097642)vmw_psp_rr           0x418030058000 .data 0x417fcb200000 .bss 0x417fcb200060

2012-01-04T11:14:21.193Z cpu0:2097642)vmw_psp_mru          0x41803005e000 .data 0x417fcb600000 .bss 0x417fcb600000

2012-01-04T11:14:21.193Z cpu0:2097642)vmci                 0x418030060000 .data 0x417fcba00000 .bss 0x417fcba084c0

2012-01-04T11:14:21.193Z cpu0:2097642)healthchk            0x41803008b000 .data 0x417fcbe00000 .bss 0x417fcbe15ca0

2012-01-04T11:14:21.193Z cpu0:2097642)teamcheck            0x4180300a6000 .data 0x417fcc200000 .bss 0x417fcc2161c0

2012-01-04T11:14:21.193Z cpu0:2097642)vlanmtucheck         0x4180300bd000 .data 0x417fcc600000 .bss 0x417fcc616000

2012-01-04T11:14:21.193Z cpu0:2097642)heartbeat            0x4180300d8000 .data 0x417fcca00000 .bss 0x417fcca160c0

2012-01-04T11:14:21.193Z cpu0:2097642)shaper               0x4180300f0000 .data 0x417fcce00000 .bss 0x417fcce17e10

2012-01-04T11:14:21.193Z cpu0:2097642)lldp                 0x418030109000 .data 0x417fcd200000 .bss 0x417fcd200050

2012-01-04T11:14:21.193Z cpu0:2097642)cdp                  0x41803010f000 .data 0x417fcd600000 .bss 0x417fcd617300

2012-01-04T11:14:21.193Z cpu0:2097642)ipfix                0x41803012d000 .data 0x417fcda00000 .bss 0x417fcda16700

2012-01-04T11:14:21.193Z cpu0:2097642)tcpip4               0x41803014d000 .data 0x417fcde00000 .bss 0x417fcde18140

2012-01-04T11:14:21.193Z cpu0:2097642)dvsdev               0x4180302a6000 .data 0x417fce200000 .bss 0x417fce200030

2012-01-04T11:14:21.193Z cpu0:2097642)dvfilter             0x4180302a9000 .data 0x417fce600000 .bss 0x417fce600ac0

2012-01-04T11:14:21.193Z cpu0:2097642)lacp                 0x4180302ce000 .data 0x417fcea00000 .bss 0x417fcea00140

2012-01-04T11:14:21.193Z cpu0:2097642)vmkapi_v2_4_0_0_dvfilter_shim 0x4180302dd000 .data 0x417fcee00000 .bss 0x417fcee009e8

2012-01-04T11:14:21.193Z cpu0:2097642)vmkapi_v2_2_0_0_dvfilter_shim 0x4180302de000 .data 0x417fcf200000 .bss 0x417fcf2009f0

2012-01-04T11:14:21.193Z cpu0:2097642)vmkapi_v2_3_0_0_dvfilter_shim 0x4180302df000 .data 0x417fcf600000 .bss 0x417fcf6009e8

2012-01-04T11:14:21.193Z cpu0:2097642)crypto_fips          0x4180302e0000 .data 0x417fcfa00000 .bss 0x417fcfa019a0

2012-01-04T11:14:21.193Z cpu0:2097642)esxfw                0x41803030e000 .data 0x417fcfe00000 .bss 0x417fcfe16bc0

2012-01-04T11:14:21.193Z cpu0:2097642)dvfilter-generic-fastpath 0x418030329000 .data 0x417fd0200000 .bss 0x417fd02162b0

2012-01-04T11:14:21.193Z cpu0:2097642)vmkibft              0x41803034a000 .data 0x417fd0600000 .bss 0x417fd06039c0

2012-01-04T11:14:21.193Z cpu0:2097642)vmkfbft              0x41803034e000 .data 0x417fd0a00000 .bss 0x417fd0a02b60

2012-01-04T11:14:21.193Z cpu0:2097642)vfat                 0x418030351000 .data 0x417fd0e00000 .bss 0x417fd0e02820

2012-01-04T11:14:21.193Z cpu0:2097642)lvmdriver            0x41803035d000 .data 0x417fd1200000 .bss 0x417fd1203a40

2012-01-04T11:14:21.193Z cpu0:2097642)deltadisk            0x41803037e000 .data 0x417fd1600000 .bss 0x417fd1607ec0

2012-01-04T11:14:21.193Z cpu0:2097642)vdfm                 0x4180303b9000 .data 0x417fd1a00000 .bss 0x417fd1a001c0

2012-01-04T11:14:21.193Z cpu0:2097642)gss                  0x4180303be000 .data 0x417fd1e00000 .bss 0x417fd1e02b18

2012-01-04T11:14:21.193Z cpu0:2097642)vmfs3                0x4180303e6000 .data 0x417fd2200000 .bss 0x417fd2207c40

2012-01-04T11:14:21.193Z cpu0:2097642)sunrpc               0x41803050e000 .data 0x417fd2600000 .bss 0x417fd2603b40

2012-01-04T11:14:21.193Z cpu0:2097642)vmklink_mpi          0x41803052c000 .data 0x417fd2a00000 .bss 0x417fd2a02600

2012-01-04T11:14:21.193Z cpu0:2097642)swapobj              0x418030532000 .data 0x417fd2e00000 .bss 0x417fd2e032f8

2012-01-04T11:14:21.193Z cpu0:2097642)nfsclient            0x41803053c000 .data 0x417fd3200000 .bss 0x417fd3204340

2012-01-04T11:14:21.193Z cpu0:2097642)nfs41client          0x41803055e000 .data 0x417fd3600000 .bss 0x417fd3605700

2012-01-04T11:14:21.193Z cpu0:2097642)pciPassthru          0x4180305ce000 .data 0x417fd3a00000 .bss 0x417fd3a02f00

2012-01-04T11:14:21.193Z cpu0:2097642)vflash               0x4180305de000 .data 0x417fd3e00000 .bss 0x417fd3e03740

2012-01-04T11:14:21.193Z cpu0:2097642)procMisc             0x4180305ea000 .data 0x417fd4200000 .bss 0x417fd4200000

2012-01-04T11:14:21.193Z cpu0:2097642)nrdma                0x4180305eb000 .data 0x417fd4600000 .bss 0x417fd4617e40

2012-01-04T11:14:21.193Z cpu0:2097642)nrdma_vmkapi_shim    0x418030633000 .data 0x417fd4a00000 .bss 0x417fd4a012b8

2012-01-04T11:14:21.193Z cpu0:2097642)vmkapi_v2_4_0_0_rdma_shim 0x418030634000 .data 0x417fd4e00000 .bss 0x417fd4e01370

2012-01-04T11:14:21.193Z cpu0:2097642)vmkapi_v2_3_0_0_rdma_shim 0x418030635000 .data 0x417fd5200000 .bss 0x417fd5200fc0

2012-01-04T11:14:21.193Z cpu0:2097642)vmkapi_v2_3_0_0_nmp_shim 0x418030637000 .data 0x417fd5600000 .bss 0x417fd5600df0

2012-01-04T11:14:21.193Z cpu0:2097642)vmkapi_v2_4_0_0_nmp_shim 0x418030638000 .data 0x417fd5a00000 .bss 0x417fd5a00df0

2012-01-04T11:14:21.193Z cpu0:2097642)vmkapi_v2_2_0_0_nmp_shim 0x418030639000 .data 0x417fd5e00000 .bss 0x417fd5e00d68

2012-01-04T11:14:21.193Z cpu0:2097642)vmkapi_v2_4_0_0_iscsi_shim 0x41803063a000 .data 0x417fd6200000 .bss 0x417fd6201240

2012-01-04T11:14:21.193Z cpu0:2097642)vmkapi_v2_3_0_0_iscsi_shim 0x41803063b000 .data 0x417fd6600000 .bss 0x417fd6600970

2012-01-04T11:14:21.193Z cpu0:2097642)vmkapi_v2_2_0_0_iscsi_shim 0x41803063c000 .data 0x417fd6a00000 .bss 0x417fd6a00970

2012-01-04T11:14:21.193Z cpu0:2097642)vrdma                0x41803063d000 .data 0x417fd6e00000 .bss 0x417fd6e02580

2012-01-04T11:14:21.193Z cpu0:2097642)balloonVMCI          0x41803065e000 .data 0x417fd7200000 .bss 0x417fd7200000

2012-01-04T11:14:21.193Z cpu0:2097642)hbr_filter           0x41803065f000 .data 0x417fd7600000 .bss 0x417fd7600300

2012-01-04T11:14:21.193Z cpu0:2097642)ftcpt                0x418030690000 .data 0x417fd7a00000 .bss 0x417fd7a02fc0

2012-01-04T11:14:21.193Z cpu0:2097642)filtmod              0x4180306dd000 .data 0x417fd7e00000 .bss 0x417fd7e04180

2012-01-04T11:14:21.193Z cpu0:2097642)svmmirror            0x4180306ef000 .data 0x417fd8200000 .bss 0x417fd8200100

2012-01-04T11:14:21.193Z cpu0:2097642)cbt                  0x4180306fc000 .data 0x417fd8600000 .bss 0x417fd86000c0

2012-01-04T11:14:21.193Z cpu0:2097642)migrate              0x4180306ff000 .data 0x417fd8a00000 .bss 0x417fd8a05480

2012-01-04T11:14:21.193Z cpu0:2097642)vfc                  0x41803077f000 .data 0x417fd8e00000 .bss 0x417fd8e02cc0

Coredump to disk.

2012-01-04T11:14:21.243Z cpu0:2097642)Slot 1 of 1 on device t10.ATA_____Netac_SSD_120GB_________________________AA000800080009010575:9.

2012-01-04T11:14:21.243Z cpu0:2097642)Dump: 474: Using dump slot size 2684354560.

2012-01-04T11:14:21.253Z cpu0:2097642)Dump: 2845: Using dump buffer size 98304

search a lot online but still dont understand the reason,hope someone can help me to see if the hardware or software issue.Thanks.

I got a sql server with 128GB memory. in the OS SQL server is using up 110GB of it and 94% utilized

what can i do to resoilve this?

Weird one - I'm trying to remove a folder but the system believes a file is preventing it from proceeding.

[root@ESXi:/vmfs/volumes/5f63db10-27ef5ce4-343a-4ccc6aacf6e7/corrupt-folder] ll

ls: ./vmx-9800-CL-6bbf840bbe070d9eec91181669a3e05c53e050e3-1.vswp: No such file or directory

total 1152

drwxr-xr-x    1 root     root         77824 Oct  9 06:17 .

drwxr-xr-t    1 root     root         77824 Oct 10 14:17 ..

When I try and remove it manually, I get the same roadblock:

[root@ESXi:/vmfs/volumes/5f63db10-27ef5ce4-343a-4ccc6aacf6e7/corrupt-folder] rm vmx-9800-CL-6bbf840bbe070d9eec91

181669a3e05c53e050e3-1.vswp

rm: can't remove 'vmx-9800-CL-6bbf840bbe070d9eec91181669a3e05c53e050e3-1.vswp': No such file or directory

Any ideas?

Hi guys. I built out a pair of identical Windows server 2019 VMs yesterday to serve as an SQL cluster. Followed the instructions I found to the last detail. The servers are running on 2 separate esxi 6.7 HOSTs and backed by a shared, all-flash, Fibre channel connected datastore.

When I start the Failover Cluster validation the disk Failover test step fails and what I notice in the disk management console of the servers is that the validation wizard takes the shared disks offline and does not bring them online again.

The shared disk for the SQL and quorum are thick, eager zeroed.

Does anyone know if this is normal behavior because I'm dreading putting this into a production environment if it's not going to play nice when I really need the cluster to Failover.

Thanks in advance.

Hi,

i just started again with playing around with VVOLs, i installed my VASA appliance on a local small datastore and all is working fine.

Except one thing:

I can't vMotion my VCSA from one host to a other.

In the Web Client the vMotion freezes between 40 and 50%, because the whole vCenter isn't pingable.

If i look on the destination esxi host, in the Web Client the VCSA is on the host but shows switched off, on CLI in the task list the VCSA is running on the destination host. On the source host is nothing. I waited a few minutes but nothing happens. So i killed the vmx task of the VCSA. After that the VCSA disappered from the hosts inventory. Then i used the datastore browser to insert the VM to the inventory and was able to startup the VCSA normally.

So, before i go deepter with my research and creating a case for this problem. Is it supported to run the VCSA on VVOL's?

Kind regards

Stefan

Hi,

i have reinstalled my hosts with 7.0.1 in a vCenter 7.0.1 and i noticed that it is not possible to configure the hosts "Swap File Location" when the host is in a cluster which has configured that the Swap File Location is on a Datastore specified by the host.

The  only way to specify a location on the host is to move the host temporarily out of the cluster.

Looks like "bug" to me.

Kind regards

Stefan