Hello, I am in need of an answer for a basic question in my opinion, which I somehow haven't been able to find the answer for.
Currently the question is can VM 5.5 export images in the same way that VM 5.1 can, so that Hyper-v can import them? This is because we are thinking of changing from 5.1 to 5.5 but are unsure of whether the previously asked is possible. Many thanks in advance if you can help to answer this question.
Good morning...
This post may seem a little off base, but I am working on a project at my company to compile run books for all systems in our data centers. We found a neat tool that runs against window servers and spew out tons of information about the server including patches, ip addresses, DNS, persistent routes, static routes, etc, etc. I take the results and input into a word document and presto magic I have a "run book" for that windows server. I am now trying to do "run books" for all the zillions of ESXi hosts in our production/dr/lab environments and was wondering if anyone out there in the VMware community knows of a tool for ESX hosts that can do the same magic ..... Any leads and comments would be appreciated...
Have a great day!!!
Hi Friends,
I need clarification regarding VMM responsibility when the Monitor execution mode changes..
The VMM responsibility when Monitor Execution Mode in Software Visualization i.e the Hardware doesn't support the VT and VMM responsibility when Hardware Visualization Mode i.e VT enabled Hardware.
As per my understating in Software Visualization Mode the VMM will running on Ring 0 and perform the Binary Translation but not sure VMM responsibility in Hardware Visualization Mode.
Please clarify in detailed.. Thanks...
Yuvaraj
I receive this error trying to open a console session on a VM on host1 using the Vsphere Client from my computer.
I can do this fine on all the other hosts (which are all ESXi5)
From my computer I also cannot ping host1.
From my virtual center server I can both ping and open a console session just fine.
I am suspecting a firewall issue. What would next steps be?
Thanks
Good morning-
We have two Lenovo RD640 servers running ESXi 5.5 and using the first onboard nic for Management network and an external nic for failover/HA. We have a major issue that the management networks on both servers come up as not working and they won't ping the core switch. Even stopping and restarting management services from the GUI will not kick start the management network and allow it to ping.
Here is how I have to get the management network working after a reboot:
Change the selected management NICS to two other nics, even ones that aren't connected to anything.
Change the IP Address to some random IP address.
Change the management NICS back to the original ones
change the IP Address back to the original correct ones.
Test the management network and it pings the core switch.
This is repeatable after a reboot.
Good afternoon,
It ispossible to makethe resizea virtual disk? The testsI've doneispossible to increaseathindisk,howeverit isnot possible toreduce thisdisk.Does anyone know ifit is possible torealizedownsizingof athindisc?
OK, we are having an odd issue getting our second install of esxi5.5.0 set up.
2 identical UCS devices, first one ran flawless.
2nd one is giving us fits, seems like the weasel python script in the installer is stuck on something.
If I hit F1 for details, or Enter to continue, I get this:
If I peek in the logs, I see some weasel lines, but nothing that makes sense to me.
It works on one box, but not the other. thoughts?
thanks.
Hi
We have a cluster with four nodes with Intel CPU E5-2670 @ 2.60 GHz. Recently we bought a fifth node, same model but with a newer CPU, Intel CPU E5-2697 @ 2.70 GHz v2.
Unfortunately we didn't activated EVC in the cluster and now we have problems to do online migrations.
But what's interesting is that we can migrate 25 of 30 VMs without any problem. How come?
For the other five we got this error:
I do know why, but why does some VMs work but not all? I have compared OS, settings, disks but I cant find any reason why.
Does anyone know?
BR
Hi VMware Gurus,
I ran into a problem installing with custom kickstart script. I began by following William Lam's virtually ghetto blog site on how to create and ESXi ISO with a custom kickstart added into it.
I've modified the boot.cfg.
Before: kernelopt=runweasel
After: kernelopt=ks=file://etc/VMware/weasel/custks.cfg and at the end of the modules I put the tar file into the ranks adding in --- /custks.tgz
I also added the custks.tgz into the main directory of this ISO.
I got two errors when I tried installing.
When booting in EFI mode:
It says "Modules relocation error".
When running in Legacy mode, I get a different error:
It says "Error loading /s.v00 Fatal error: 10 (Out of resources)"
I've digged through this forum but haven't seen anyone run into my first error, but a few with my second error, but their solutions didn't work.
Any suggestions? Thanks for reading.
I still have servers linked to vCenter 4, server_1 and now have vCenter5, server_2 ready.
Will adding the hosts to server_2 while they are linked to server_1 cause>>>>>>>>>>>>>>????
I have 5 ESXi with same hardware 2 of them crashes . Here is the vmkernel-log
2014-08-27T13:47:40.003Z cpu1:108537)World: 14296: VC opID hostd-85e1 maps to vmkernel opID 7c2abc39
2014-08-27T13:48:00.002Z cpu1:108531)World: 14296: VC opID hostd-23a4 maps to vmkernel opID 16c641b3
2014-08-27T13:48:01.033Z cpu0:32957)MCE: 1118: cpu0: MCA error detected via CMCI (Gbl status=0x0): Restart IP: invalid, Error IP: invalid, MCE in progress: no.
2014-08-27T13:48:01.033Z cpu0:32957)MCE: 222: cpu0: bank0: status=0x9000004000010005: (VAL=1, OVFLW=0, UC=0, EN=1, PCC=0, S=0, AR=0), ECC=no, Addr:0x0 (invalid), Misc:0x0 (invalid)
2014-08-27T13:48:01.033Z cpu0:32957)MCE: 231: cpu0: bank0: MCA recoverable error (CE): "Internal Parity Error."
2014-08-27T13:48:01.033Z cpu1:33242)World: 8773: PRDA 0x418040400000 ss 0x0 ds 0x10b es 0x10b fs 0x0 gs 0x13b
2014-08-27T13:48:01.033Z cpu1:33242)World: 8775: TR 0x4020 GDT 0x4123876a1000 (0x402f) IDT 0x418014cf3000 (0xfff)
2014-08-27T13:48:01.033Z cpu1:33242)World: 8776: CR0 0x80010031 CR3 0x11e3e4000 CR4 0x42768
2014-08-27T13:48:01.039Z cpu1:33242)Backtrace for current CPU #1, worldID=33242, ebp=0x4119c0013dd0
2014-08-27T13:48:01.039Z cpu1:33242)0x4119c0013dd0:[0x418014c8cf99]PanicvPanicInt@vmkernel#nover+0x575 stack: 0x8, 0x4119c0013e40, 0x41
2014-08-27T13:48:01.039Z cpu1:33242)0x4119c0013e30:[0x418014c8d1dd]Panic_NoSave@vmkernel#nover+0x49 stack: 0x800000001, 0x5, 0xbe200000
2014-08-27T13:48:01.039Z cpu1:33242)0x4119c0013e90:[0x418014c63e75]IDTReturnPrepare@vmkernel#nover+0x2c5 stack: 0x67374e, 0x6738ce, 0xf
2014-08-27T13:48:01.039Z cpu1:33242)0x4119c0013f20:[0x418014c6475f]Int18_MachineCheck@vmkernel#nover+0x163 stack: 0xff8f3bb8, 0x1196300
2014-08-27T13:48:01.039Z cpu1:33242)0x4119c0013f30:[0x418014cf1064]gate_entry@vmkernel#nover+0x64 stack: 0x0, 0x13b, 0x0, 0x12a7495c, 0
2014-08-27T13:48:01.040Z cpu1:33242) [45m [33;1mVMware ESXi 5.5.0 [Releasebuild-1892794 x86_64] [0m
NOT_REACHED bora/vmkernel/main/idt.c:1165
2014-08-27T13:48:01.040Z cpu1:33242)cr0=0x80010031 cr2=0x12a18be0 cr3=0x11e3e4000 cr4=0x42768
2014-08-27T13:48:01.040Z cpu1:33242)pcpu:0 world:32949 name:"memMapKernel-0" (S)
2014-08-27T13:48:01.040Z cpu1:33242)pcpu:1 world:33242 name:"vobd" (U)
2014-08-27T13:48:01.040Z cpu1:33242)pcpu:2 world:32791 name:"CmdCompl-2" (S)
2014-08-27T13:48:01.040Z cpu1:33242)pcpu:3 world:33210 name:"vmsyslogd" (U)
2014-08-27T13:48:01.040Z cpu1:33242)pcpu:4 world:32783 name:"coalesceWorld-0" (S)
2014-08-27T13:48:01.040Z cpu1:33242)pcpu:5 world:53216 name:"vmm1:Analytics_VM" (V)
2014-08-27T13:48:01.040Z cpu1:33242)pcpu:6 world:33212 name:"vmsyslogd" (U)
2014-08-27T13:48:01.040Z cpu1:33242)pcpu:7 world:32784 name:"netCoalesce2World" (S)
2014-08-27T13:48:01.040Z cpu1:33242)@BlueScreen: NOT_REACHED bora/vmkernel/main/idt.c:1165
2014-08-27T13:48:01.040Z cpu1:33242)Code start: 0x418014c00000 VMK uptime: 2:02:57:31.656
2014-08-27T13:48:01.040Z cpu1:33242)0x4119c0013dd0:[0x418014c8cf99]PanicvPanicInt@vmkernel#nover+0x575 stack: 0x8
2014-08-27T13:48:01.040Z cpu1:33242)0x4119c0013e30:[0x418014c8d1dd]Panic_NoSave@vmkernel#nover+0x49 stack: 0x800000001
2014-08-27T13:48:01.040Z cpu1:33242)0x4119c0013e90:[0x418014c63e75]IDTReturnPrepare@vmkernel#nover+0x2c5 stack: 0x67374e
2014-08-27T13:48:01.040Z cpu1:33242)0x4119c0013f20:[0x418014c6475f]Int18_MachineCheck@vmkernel#nover+0x163 stack: 0xff8f3bb8
2014-08-27T13:48:01.040Z cpu1:33242)0x4119c0013f30:[0x418014cf1064]gate_entry@vmkernel#nover+0x64 stack: 0x0
2014-08-27T13:48:01.042Z cpu1:33242)base fs=0x0 gs=0x418040400000 Kgs=0x0
2014-08-27T13:48:01.042Z cpu1:33242)MC:PCPU0 B:0 S:0x9000004000010005 M:0x0 A:0x0 0
2014-08-27T13:48:01.043Z cpu1:33242)MC:PCPU1 B:8 S:0xbe2000000005110a M:0x9080000086 A:0x118be2600 5
MC:PCPU0: 1 hardware errors seen since boot (1 corrected by hardware)
MC:PCPU1: 1 hardware errors seen since boot (0 corrected by hardware)
2014-08-27T13:48:01.043Z cpu1:33242)PCPU fam:6 model:58 step:9 type:2 name:Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz
2014-08-27T13:48:01.043Z cpu1:33242)vmkernel 0x0 .data 0x0 .bss 0x0
2014-08-27T13:48:01.043Z cpu1:33242)chardevs 0x418015171000 .data 0x417fc0000000 .bss 0x417fc0000400
2014-08-27T13:48:01.043Z cpu1:33242)user 0x418015178000 .data 0x417fc0400000 .bss 0x417fc040e180
2014-08-27T13:48:01.043Z cpu1:33242)vmkapi_mgmt 0x41801522b000 .data 0x417fc0800000 .bss 0x417fc0800140
2014-08-27T13:48:01.043Z cpu1:33242)vprobe 0x418015231000 .data 0x417fc0c00000 .bss 0x417fc0c0b7c0
2014-08-27T13:48:01.043Z cpu1:33242)vmkapi_socket 0x41801526f000 .data 0x417fc1000000 .bss 0x417fc10005c0
2014-08-27T13:48:01.043Z cpu1:33242)vmkapi_v2_0_0_0_vmkernel_shim 0x418015274000 .data 0x417fc1400000 .bss 0x417fc14080c0
2014-08-27T13:48:01.043Z cpu1:33242)vmkapi_v2_1_0_0_vmkernel_shim 0x418015279000 .data 0x417fc1800000 .bss 0x417fc1808840
2014-08-27T13:48:01.043Z cpu1:33242)procfs 0x41801527e000 .data 0x417fc1c00000 .bss 0x417fc1c00240
2014-08-27T13:48:01.043Z cpu1:33242)vfat 0x418015281000 .data 0x417fc2000000 .bss 0x417fc2002600
2014-08-27T13:48:01.043Z cpu1:33242)procMisc 0x41801528b000 .data 0x417fc2400000 .bss 0x417fc2400000
2014-08-27T13:48:01.043Z cpu1:33242)vmci 0x41801528c000 .data 0x417fc2800000 .bss 0x417fc28057c0
2014-08-27T13:48:01.043Z cpu1:33242)iodm 0x4180152af000 .data 0x417fc2c00000 .bss 0x417fc2c00138
2014-08-27T13:48:01.043Z cpu1:33242)vmkplexer 0x4180152b3000 .data 0x417fc3000000 .bss 0x417fc3000260
2014-08-27T13:48:01.043Z cpu1:33242)vmklinux_9 0x4180152b7000 .data 0x417fc3400000 .bss 0x417fc3408e80
2014-08-27T13:48:01.043Z cpu1:33242)vmklinux_9_2_0_0 0x41801533e000 .data 0x417fc3800000 .bss 0x417fc3807e84
2014-08-27T13:48:01.043Z cpu1:33242)vmklinux_9_2_1_0 0x418015341000 .data 0x417fc3c00000 .bss 0x417fc3c07f98
2014-08-27T13:48:01.043Z cpu1:33242)vmklinux_9_2_2_0 0x418015344000 .data 0x417fc4000000 .bss 0x417fc4008838
2014-08-27T13:48:01.043Z cpu1:33242)iscsi_trans 0x418015347000 .data 0x417fc4400000 .bss 0x417fc4401800
2014-08-27T13:48:01.043Z cpu1:33242)iscsi_trans_compat_shim 0x418015352000 .data 0x417fc4800000 .bss 0x417fc480096c
2014-08-27T13:48:01.043Z cpu1:33242)iscsi_trans_incompat_shim 0x418015353000 .data 0x417fc4c00000 .bss 0x417fc4c007e4
2014-08-27T13:48:01.043Z cpu1:33242)etherswitch 0x418015354000 .data 0x417fc5000000 .bss 0x417fc5013a00
2014-08-27T13:48:01.043Z cpu1:33242)netsched 0x418015389000 .data 0x417fc5400000 .bss 0x417fc5404800
2014-08-27T13:48:01.043Z cpu1:33242)cnic_register 0x41801539b000 .data 0x417fc5800000 .bss 0x417fc58001e0
2014-08-27T13:48:01.043Z cpu1:33242)e1000 0x41801539d000 .data 0x417fc5c00000 .bss 0x417fc5c01240
2014-08-27T13:48:01.043Z cpu1:33242)vmkapi_v2_1_0_0_iscsi_shim 0x4180153c3000 .data 0x417fc6000000 .bss 0x417fc6000970
2014-08-27T13:48:01.043Z cpu1:33242)vmkapi_v2_0_0_0_iscsi_shim 0x4180153c4000 .data 0x417fc6400000 .bss 0x417fc6400970
2014-08-27T13:48:01.043Z cpu1:33242)random 0x4180153c5000 .data 0x417fc6800000 .bss 0x417fc6800600
2014-08-27T13:48:01.043Z cpu1:33242)usb 0x4180153c9000 .data 0x417fc6c00000 .bss 0x417fc6c01660
2014-08-27T13:48:01.043Z cpu1:33242)ehci-hcd 0x4180153eb000 .data 0x417fc7000000 .bss 0x417fc70002a0
2014-08-27T13:48:01.043Z cpu1:33242)hid 0x4180153f6000 .data 0x417fc7400000 .bss 0x417fc74004e0
2014-08-27T13:48:01.043Z cpu1:33242)healthchk 0x4180153fb000 .data 0x417fc7800000 .bss 0x417fc7811e00
2014-08-27T13:48:01.043Z cpu1:33242)teamcheck 0x418015411000 .data 0x417fc7c00000 .bss 0x417fc7c12240
2014-08-27T13:48:01.043Z cpu1:33242)vlanmtucheck 0x418015424000 .data 0x417fc8000000 .bss 0x417fc8012000
2014-08-27T13:48:01.043Z cpu1:33242)heartbeat 0x418015439000 .data 0x417fc8400000 .bss 0x417fc8411f00
2014-08-27T13:48:01.043Z cpu1:33242)shaper 0x41801544a000 .data 0x417fc8800000 .bss 0x417fc8813e80
2014-08-27T13:48:01.043Z cpu1:33242)lldp 0x41801545d000 .data 0x417fc8c00000 .bss 0x417fc8c00040
2014-08-27T13:48:01.043Z cpu1:33242)cdp 0x418015462000 .data 0x417fc9000000 .bss 0x417fc9013400
2014-08-27T13:48:01.043Z cpu1:33242)ipfix 0x41801547e000 .data 0x417fc9400000 .bss 0x417fc9412540
2014-08-27T13:48:01.043Z cpu1:33242)tcpip4 0x418015492000 .data 0x417fc9800000 .bss 0x417fc9818180
2014-08-27T13:48:01.043Z cpu1:33242)dvsdev 0x418015598000 .data 0x417fc9c00000 .bss 0x417fc9c00030
2014-08-27T13:48:01.043Z cpu1:33242)dvfilter 0x41801559b000 .data 0x417fca000000 .bss 0x417fca000b00
2014-08-27T13:48:01.043Z cpu1:33242)lacp 0x4180155bd000 .data 0x417fca400000 .bss 0x417fca400160
2014-08-27T13:48:01.043Z cpu1:33242)hbr_filter 0x4180155c7000 .data 0x417fca800000 .bss 0x417fca800300
2014-08-27T13:48:01.043Z cpu1:33242)vmkapi_v2_1_0_0_dvfilter_shim 0x4180155f3000 .data 0x417fcac00000 .bss 0x417fcac009b0
2014-08-27T13:48:01.043Z cpu1:33242)vmkapi_v2_0_0_0_dvfilter_shim 0x4180155f4000 .data 0x417fcb000000 .bss 0x417fcb000930
2014-08-27T13:48:01.043Z cpu1:33242)dvfilter-generic-fastpath 0x4180155f5000 .data 0x417fcb400000 .bss 0x417fcb412380
2014-08-27T13:48:01.043Z cpu1:33242)vmkstatelogger 0x41801560f000 .data 0x417fcb800000 .bss 0x417fcb803a00
2014-08-27T13:48:01.043Z cpu1:33242)esxfw 0x418015633000 .data 0x417fcbc00000 .bss 0x417fcbc12d00
2014-08-27T13:48:01.043Z cpu1:33242)dm 0x418015648000 .data 0x417fcc000000 .bss 0x417fcc000000
2014-08-27T13:48:01.043Z cpu1:33242)nmp 0x41801564a000 .data 0x417fcc400000 .bss 0x417fcc403e50
2014-08-27T13:48:01.043Z cpu1:33242)vmw_satp_local 0x41801566d000 .data 0x417fcc800000 .bss 0x417fcc800028
2014-08-27T13:48:01.043Z cpu1:33242)vmw_satp_default_aa 0x41801566f000 .data 0x417fccc00000 .bss 0x417fccc00000
2014-08-27T13:48:01.043Z cpu1:33242)vmw_psp_lib 0x418015670000 .data 0x417fcd000000 .bss 0x417fcd000290
2014-08-27T13:48:01.043Z cpu1:33242)vmw_psp_fixed 0x418015672000 .data 0x417fcd400000 .bss 0x417fcd400000
2014-08-27T13:48:01.043Z cpu1:33242)vmw_psp_rr 0x418015674000 .data 0x417fcd800000 .bss 0x417fcd800068
2014-08-27T13:48:01.043Z cpu1:33242)vmw_psp_mru 0x418015677000 .data 0x417fcdc00000 .bss 0x417fcdc00000
2014-08-27T13:48:01.043Z cpu1:33242)libata_92 0x418015679000 .data 0x417fce000000 .bss 0x417fce002660
2014-08-27T13:48:01.043Z cpu1:33242)libata_9_2_0_0 0x41801569b000 .data 0x417fce400000 .bss 0x417fce401750
2014-08-27T13:48:01.043Z cpu1:33242)libata_9_2_1_0 0x41801569c000 .data 0x417fce800000 .bss 0x417fce801750
2014-08-27T13:48:01.043Z cpu1:33242)usb-storage 0x41801569d000 .data 0x417fcec00000 .bss 0x417fcec04780
2014-08-27T13:48:01.043Z cpu1:33242)vmkapi_v2_1_0_0_nmp_shim 0x4180156a9000 .data 0x417fcf000000 .bss 0x417fcf000ca8
2014-08-27T13:48:01.043Z cpu1:33242)vmkapi_v2_0_0_0_nmp_shim 0x4180156aa000 .data 0x417fcf400000 .bss 0x417fcf400ca8
2014-08-27T13:48:01.043Z cpu1:33242)svmmirror 0x4180156ab000 .data 0x417fcf800000 .bss 0x417fcf8000c0
2014-08-27T13:48:01.043Z cpu1:33242)cbt 0x4180156b7000 .data 0x417fcfc00000 .bss 0x417fcfc00080
2014-08-27T13:48:01.043Z cpu1:33242)migrate 0x4180156bb000 .data 0x417fd0000000 .bss 0x417fd0004d40
2014-08-27T13:48:01.043Z cpu1:33242)libfc_92 0x41801571a000 .data 0x417fd0400000 .bss 0x417fd0400b80
2014-08-27T13:48:01.043Z cpu1:33242)libfcoe_92 0x418015733000 .data 0x417fd0800000 .bss 0x417fd08001c0
2014-08-27T13:48:01.043Z cpu1:33242)libfc_9_2_0_0 0x418015739000 .data 0x417fd0c00000 .bss 0x417fd0c00868
2014-08-27T13:48:01.043Z cpu1:33242)libfcoe_9_2_0_0 0x41801573a000 .data 0x417fd1000000 .bss 0x417fd10001f4
2014-08-27T13:48:01.043Z cpu1:33242)libfc_9_2_1_0 0x41801573b000 .data 0x417fd1400000 .bss 0x417fd1400868
2014-08-27T13:48:01.043Z cpu1:33242)libfcoe_9_2_1_0 0x41801573c000 .data 0x417fd1800000 .bss 0x417fd18001f4
2014-08-27T13:48:01.043Z cpu1:33242)ahci 0x41801573d000 .data 0x417fd1c00000 .bss 0x417fd1c00420
2014-08-27T13:48:01.043Z cpu1:33242)sunrpc 0x418015744000 .data 0x417fd2000000 .bss 0x417fd2002b80
2014-08-27T13:48:01.043Z cpu1:33242)nfsclient 0x418015753000 .data 0x417fd2400000 .bss 0x417fd2403940
2014-08-27T13:48:01.043Z cpu1:33242)vmkibft 0x41801576c000 .data 0x417fd2800000 .bss 0x417fd28037c0
2014-08-27T13:48:01.043Z cpu1:33242)lvmdriver 0x41801576f000 .data 0x417fd2c00000 .bss 0x417fd2c03380
2014-08-27T13:48:01.043Z cpu1:33242)deltadisk 0x418015783000 .data 0x417fd3000000 .bss 0x417fd3005c00
2014-08-27T13:48:01.043Z cpu1:33242)tracing 0x4180157ae000 .data 0x417fd3400000 .bss 0x417fd3405b40
2014-08-27T13:48:01.043Z cpu1:33242)rdt 0x4180157b5000 .data 0x417fd3800000 .bss 0x417fd3804e00
2014-08-27T13:48:01.043Z cpu1:33242)vsanutil 0x4180157db000 .data 0x417fd3c00000 .bss 0x417fd3c069c0
2014-08-27T13:48:01.043Z cpu1:33242)lsomcommon 0x4180157fa000 .data 0x417fd4000000 .bss 0x417fd4001680
2014-08-27T13:48:01.043Z cpu1:33242)plog 0x41801582e000 .data 0x417fd4400000 .bss 0x417fd44056c0
2014-08-27T13:48:01.043Z cpu1:33242)vmfs3 0x418015871000 .data 0x417fd4800000 .bss 0x417fd4803840
2014-08-27T13:48:01.043Z cpu1:33242)dvfg-igmp 0x4180158d9000 .data 0x417fd5a00000 .bss 0x417fd5a00208
2014-08-27T13:48:01.043Z cpu1:33242)cmmds_net 0x4180158df000 .data 0x417fd5e00000 .bss 0x417fd5e02f40
2014-08-27T13:48:01.043Z cpu1:33242)cmmds 0x4180158ec000 .data 0x417fd6200000 .bss 0x417fd6204d80
2014-08-27T13:48:01.043Z cpu1:33242)cmmds_resolver 0x418015921000 .data 0x417fd6600000 .bss 0x417fd6600140
2014-08-27T13:48:01.043Z cpu1:33242)vsan 0x41801592d000 .data 0x417fd6a00000 .bss 0x417fd6a1c200
2014-08-27T13:48:01.043Z cpu1:33242)vmklink_mpi 0x418015a48000 .data 0x417fd6e00000 .bss 0x417fd6e02400
2014-08-27T13:48:01.043Z cpu1:33242)swapobj 0x418015a4d000 .data 0x417fd7200000 .bss 0x417fd7203010
2014-08-27T13:48:01.043Z cpu1:33242)osfs 0x418015a55000 .data 0x417fd7600000 .bss 0x417fd7603380
2014-08-27T13:48:01.043Z cpu1:33242)vflash 0x418015a63000 .data 0x417fd7a00000 .bss 0x417fd7a03540
2014-08-27T13:48:01.043Z cpu1:33242)vfc 0x418015a6e000 .data 0x417fd7e00000 .bss 0x417fd7e02ac0
Coredump to disk.
2014-08-27T13:48:01.093Z cpu1:33242)Slot 1 of 1.
2014-08-27T13:48:01.093Z cpu1:33242)Dump: 2212: Using dump slot size 2684354560.
Hello!
I am having an issue that is stumping me. I currently have a handful of VM's that are using a high amount of disk space (well, high for these VMs). For example: VMware is reporting used space at close to 2TB.
However, the guest(s) (server 2012, and server 2008) is showing appx 700MB.
The VMs reside across Virtual Disks all on the same LUN, Datastore, and folder structure.
The VM has up to date VM tools
I have run spacesniffer on the VM, and it didnt find any crazy files that was sucking the disk space
I checked for restore points
I am also having the same problem with a couple Server 2008 VM's as well.
Very confusing.
Any guidance would be appreciated!!
Thanks
Hi All,
I have a VM with four HDD
1) OS (VMDK) - Connected to SCSI Controller 1
2)RDM - Connected to SCSI Controller 2
3) RDM - Connected to SCSI Controller 3
4)RDM - Connected to SCSI Controller 4
I have another 3 RDM that needs to be added to this VM.
Because this VM shares disk with other VM (MS Cluster) and VM can have only 4 SCSI Controller how do I go about adding 3 more RDMs.
Thanks....
Hi everyone
I have a question regarding our software iSCSI port binding setup. I honestly got confused after reading this (http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2038869). I would appreciate if you could let me know if the following setup is correct or if you spot anything that should be changed.
vSwitch configuration:
iSCSI software adapter configuration:
The iSCSI datastore I added on the ESXi host lists 4 connected targets, 1 device and 4 paths. I have configured Round Robin (VMware) and storage array type VMW_SATP_ALUA. The following paths are listed:
On the storage side we use two redundant Datacore SANsymphone-V version 9.0 PSP4 servers.
Any feedback would be greatly appreciated! Thank you.
Regards
Paul
Hi,
I'm wondering what would happen in a scenario when all the hosts are in one Cluster but not all the hosts have access to the same storage (see attached).
Is DRS/HA smart enough to only migrate (or start up) a VM to the hosts which have access to the storage it's located on?
I understand this is probably not a supported setup but it's a temporary measure 
Thanks for any help.
Hello,
I would like to increase the vdisk space at one vmachine which runs into the esxi 5.5 (Hypervisor) but I see that the maximum capacity is 55GB and now uses 55GB. They is free space in the datastore and this happens only with this specific vm, if i try to do this on another vmachines I have the option to increase the vm more than 55GB. For example for another vm have the option to increase up to 300GB. I attached one photo which showed the issue.
Any ideas about that? Both vdisks are Thick Provision Lazy Zeroed.
Thanks!
Hello all. First post. Been playing with ESXi for a few months and I'm having an unusual issue. Here's my hardware and VM setup:
Hardware: Supermicro x9scm-f-o with 32GB of ECC RAM and E3-1230v2 CPU
Also included is a M1015 reflashed to IT mode and used as passthrough with VT-d to the FreeNAS VM.
VMs:
FreeNAS 8.3.1 64-bit with 20GB of RAM assigned (3vCPU)
Linux Mint 13 LTS 4GB RAM (3vCPU)
Cyberpower UPS Appliance VM 2GB RAM (1vCPU)
After building the machine a week or two went by, then I lost network connectivity to the entire box(this was when I first realized something might be wrong). I couldn't use the vSphere client or access the guest machines. I attempted to "Restart Management Network" locally but that didn't solve anything. Still no connectivity. I then attempted to shutdown the box but it wouldn't shutdown. Ultimately I power cycled it.
So over the last 2 months at random times I've lost network connectivity. Thanks to reading various sources I've found an error in my syslog that ends up being logged 5-20+ times in a row, and happens randomly at intervals of 2-10 minutes. I get an error that says:
Unknown: out of memory [5880]
I thought it was due to my VMs using a lot of network connections, but never really could find someone else with the error. It's very non-specific and I'm running out of leads to check out the issue, hence I've turned to the community.
Well, today I have decided I want to figure this puzzle out, so I shutdown all of the VMs and that error still continues to show up in the syslog. So clearly I have a configuration problem somewhere. This is odd to me because I've tried to avoid changing settings that I wasn't 100% sure was appropriate for me because Im a newbie to ESXi and I'd rather not break my own installation. The only thing I've done that might be construed as an 'advanced' feature modification is I enabled the RDM function for the Linux Mint installation. It was already on a hard drive and I thought I'd just do RDM passthrough and use it that way if it worked. Well, it has so I left it like that.
I can't find much info on what 5880 might represent, so I assumed its a PID or something. It has changed from one bootup to the next. So here's the output from the CLI:
~ # ps -P | grep 5880
5880 5880 sfcb-vmware_raw 5606 /sbin/sfcbd
5881 5880 sfcb-vmware_raw 5606 /sbin/sfcbd
5882 5880 sfcb-vmware_raw 5606 /sbin/sfcbd
5883 5880 sfcb-vmware_raw 5606 /sbin/sfcbd
5884 5880 sfcb-vmware_raw 5606 /sbin/sfcbd
5885 5880 sfcb-vmware_raw 5606 /sbin/sfcbd
5887 5880 sfcb-vmware_raw 5606 /sbin/sfcbd
5888 5880 sfcb-vmware_raw 5606 /sbin/sfcbd
~ #
Again, I tried searching for sfcbd and it really doesn't give me any clues.
I actually built 2 identical systems. One for me and one for a friend. He uses more RAM for his VMs(and different VMs) but he doesn't have this issue. I'm figuring I've done something to my installation to deserve this since his is flawless, but I am out of leads.
tl;dr: I get the "Unknown: out of memory" error along with a loss of all network connectivity randomly after 1 day to 2 weeks. Sometimes when the server would be idle(such as at night). I don't know if they are related, but I assume they are.
Anyone have ideas to try? This is baffling me and I'm really at a loss to explain the problem let alone how to fix it.
Thanks!
Hi all,
i am running ESXi 5.5 with three NIC:
- Intel I217-V --> vmnic0
- Intel 82574L --> vmnic1
- Intel 82547L --> vmnic2
All Machines on the three Networks were working smooth, yet since two days, all machines on vmnic2 are not avaliable in the network, the host states in the log:
Uplink vmnic2 has recovered from a transient failure due to watchdog timeout
and links to this kb-entry:
VMware KB: Transient failure recovery due to watchdog timeout
This message is in the log every few minutes. The virtual machines are never reachable.
I already deactivated auto-negotiation in the NIC settings on the host.
I don't think it is a driver issue, since vmnic 1 and 2 are the same NIC and use the same driver:
~ # ethtool -i vmnic2
driver: e1000e
version: 2.3.2-NAPI
firmware-version: 1.8-0
bus-info: 0000:03:00.0
~ # ethtool -i vmnic1
driver: e1000e
version: 2.3.2-NAPI
firmware-version: 1.8-0
bus-info: 0000:02:00.0
~ # ethtool -i vmnic0
driver: e1000e
version: 2.3.2-NAPI
firmware-version: 0.12-4
bus-info: 0000:00:19.0
We did not change anything on our infrastructure. It just happend two days ago. Can anyone assit?
Thanks a lot in advance!
The vmkernel.log indicates: (extract)
2014-08-26T01:08:52.166Z cpu1:33280)WARNING: LinNet: netdev_watchdog:3478: NETDEV WATCHDOG: vmnic2: transmit timed out
2014-08-26T01:08:52.166Z cpu1:33280)WARNING: at vmkdrivers/src_92/vmklinux_92/vmware/linux_net.c:3507/netdev_watchdog() (inside vmklinux)
2014-08-26T01:08:52.166Z cpu1:33280)Backtrace for current CPU #1, worldID=33280, ebp=0x41238801de10
2014-08-26T01:08:52.166Z cpu1:33280)0x41238801de10:[0x418025ab8297]watchdog_work_cb@com.vmware.driverAPI#9.2+0x28f stack: 0x410800000d9
2014-08-26T01:08:52.166Z cpu1:33280)0x41238801de90:[0x418025ab8297]watchdog_work_cb@com.vmware.driverAPI#9.2+0x28f stack: 0x41092d8197e
2014-08-26T01:08:52.166Z cpu0:33274)<3>e1000e 0000:03:00.0: vmnic2: Reset adapter unexpectedly
2014-08-26T01:08:52.166Z cpu1:33280)0x41238801df30:[0x418025adf516]vmklnx_workqueue_callout@com.vmware.driverAPI#9.2+0xde stack: 0x0, 0
2014-08-26T01:08:52.166Z cpu1:33280)0x41238801dfd0:[0x41802546138a]helpFunc@vmkernel#nover+0xab6 stack: 0x0, 0x0, 0x0, 0x0, 0x0
2014-08-26T01:08:52.166Z cpu1:33280)0x41238801dff0:[0x418025653242]CpuSched_StartWorld@vmkernel#nover+0xfa stack: 0x0, 0x0, 0x0, 0x0, 0
2014-08-26T01:08:54.735Z cpu1:33283)<6>vmnic2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
2014-08-26T01:08:55.847Z cpu0:32812)NetPort: 1589: disabled port 0x4000002
2014-08-26T01:08:55.847Z cpu0:32812)Uplink: 6530: enabled port 0x4000002 with mac 68:05:ca:28:b5:a5
2014-08-26T01:08:58.178Z cpu1:33281)WARNING: LinNet: netdev_watchdog:3478: NETDEV WATCHDOG: vmnic2: transmit timed out
2014-08-26T01:08:58.178Z cpu1:33281)<3>e1000e 0000:03:00.0: vmnic2: Reset adapter unexpectedly
2014-08-26T01:09:00.780Z cpu0:33279)<6>vmnic2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
2014-08-26T01:09:01.845Z cpu0:32812)NetPort: 1589: disabled port 0x4000002
2014-08-26T01:09:01.845Z cpu0:32812)Uplink: 6530: enabled port 0x4000002 with mac 68:05:ca:28:b5:a5
2014-08-26T01:09:10.191Z cpu2:33271)WARNING: LinNet: netdev_watchdog:3478: NETDEV WATCHDOG: vmnic2: transmit timed out
2014-08-26T01:09:10.191Z cpu1:33278)<3>e1000e 0000:03:00.0: vmnic2: Reset adapter unexpectedly
2014-08-26T01:09:12.750Z cpu0:33277)<6>vmnic2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
2014-08-26T01:09:13.845Z cpu0:32812)NetPort: 1589: disabled port 0x4000002
2014-08-26T01:09:13.845Z cpu0:32812)Uplink: 6530: enabled port 0x4000002 with mac 68:05:ca:28:b5:a5
2014-08-26T01:09:16.199Z cpu0:33277)WARNING: LinNet: netdev_watchdog:3478: NETDEV WATCHDOG: vmnic2: transmit timed out
2014-08-26T01:09:16.199Z cpu0:33277)<3>e1000e 0000:03:00.0: vmnic2: Reset adapter unexpectedly
2014-08-26T01:09:18.766Z cpu1:33274)<6>vmnic2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
2014-08-26T01:09:19.845Z cpu2:32812)NetPort: 1589: disabled port 0x4000002
2014-08-26T01:09:19.845Z cpu2:32812)Uplink: 6530: enabled port 0x4000002 with mac 68:05:ca:28:b5:a5
2014-08-26T01:12:25.466Z cpu0:33273)WARNING: LinNet: netdev_watchdog:3478: NETDEV WATCHDOG: vmnic2: transmit timed out
2014-08-26T01:12:25.466Z cpu0:33273)<3>e1000e 0000:03:00.0: vmnic2: Reset adapter unexpectedly
2014-08-26T01:12:28.038Z cpu0:33277)<6>vmnic2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
2014-08-26T01:12:28.847Z cpu2:32812)NetPort: 1589: disabled port 0x4000002
2014-08-26T01:12:28.847Z cpu2:32812)Uplink: 6530: enabled port 0x4000002 with mac 68:05:ca:28:b5:a5
2014-08-26T01:15:50.773Z cpu0:33278)WARNING: LinNet: netdev_watchdog:3478: NETDEV WATCHDOG: vmnic2: transmit timed out
2014-08-26T01:15:50.773Z cpu1:33269)<3>e1000e 0000:03:00.0: vmnic2: Reset adapter unexpectedly
2014-08-26T01:15:53.457Z cpu0:33277)<6>vmnic2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
2014-08-26T01:15:54.847Z cpu0:32812)NetPort: 1589: disabled port 0x4000002
2014-08-26T01:15:54.847Z cpu0:32812)Uplink: 6530: enabled port 0x4000002 with mac 68:05:ca:28:b5:a5
2014-08-26T01:19:30.071Z cpu3:33275)WARNING: LinNet: netdev_watchdog:3478: NETDEV WATCHDOG: vmnic2: transmit timed out
2014-08-26T01:19:30.071Z cpu3:33275)<3>e1000e 0000:03:00.0: vmnic2: Reset adapter unexpectedly
2014-08-26T01:19:32.603Z cpu1:33284)<6>vmnic2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
2014-08-26T01:19:33.846Z cpu3:32812)NetPort: 1589: disabled port 0x4000002
2014-08-26T01:19:33.846Z cpu3:32812)Uplink: 6530: enabled port 0x4000002 with mac 68:05:ca:28:b5:a5
Hey!
At first, here's my Setup:
VMWare vSphere Web Client: Version 5.5.0 Build 1441077
Client-Integration-Plug-In: Client Support-Version 5.5.0 Build 1279455
Browser: Chrome Version 32.0.1700.77
Flash Player: MAC 12,0,0,41
When I connect to a VM Console on my Mac, using the vSphere Web Client with a German System and a German Keyboard, the Key-Mappings seem to be US. I'm very enthusiastic about using the VMWare vSphere Web Client on my Mac but as I often need Symbols and Characters like Ä,Ü,Ö,ß I have to wait for a fix.
In the following Post the User MikeH_KGH is describing the same Problems on a Swedish system. (Page 4)
Re: vSphere Web Client and Mac OS X
Can you please check the Problem?
Thank you in Advance!
Patrick
Can somebody explain to me what I need to do to download vShpere 5.5 VCenter Server and ESXi iso files for training puproses.
Thank you in advanced!