Quantcast
Channel: VMware Communities: Message List
Viewing all 229567 articles
Browse latest View live

Re: Move-VM and Set Storage Policy

$
0
0

If I attempt to storage vMotion before changing the storage policy I get this error since the default storage policy is FTT=1:

 

Move-VM : 7/6/2017 2:13:35 PM   Move-VM         The operation for the entity "vmname" failed with the following message: "Cannot complete file creation operation.". Failed to create object. There are currently 1 usable fault domains. The operation requires 2 more usable fault domains.

 

In this scenario, I only have a single fault domain because the other node for the 2 Node VSAN cluster has yet to be upgraded.  It's currently hosting the NFS mount the VMs are running on.  The VMs need to be migrated off of the NFS mount so the host can be upgraded and joined to the VSAN cluster.


Re: Windows 10 guest (on Linux host) *always* loses network connection after dual booting with Windows 10

$
0
0

@wila
I believe it's completely unrelated to Windows now and think the problem is simply to do with rebooting the system and VMWare networking not loading at boot like it used to do (I've noticed that all I have to do is reboot the system and the problem occurs everytime).

 

This issue didn't occur as of a few days ago

 

I forgot that I recently installed a new kernel a few days ago (linux-ck) so immediately I figured that this had to be the issue, so I downgraded back to the stock Linux kernel 4.11.7, deleted VMWare and reinstalled it (just so there was no chance of there being any old configuration being around), but the issue persists.

 

The vmware and vmware-usbarbitrator services load, and vmnet kernel module loads as well.

 

I'm at a loss now as to why networking isn't starting at boot anymore.

Re: Move-VM and Set Storage Policy

$
0
0

I just found that if I change the default storage policy for the target VSAN Datastore I'm able to move the VMs with Move-VM.  The problem with this is I couldn't find how to change the default storage policy with PowerCLI.  Set-SpbmEntityConfiguration would seem to be the correct cmdlet to do this with but it doesn't take a datastore as an entity type.  Initially, I tried using Set-VSANClusterConfiguration -StoragePolicy to apply the FTT=0 policy but apparently this isn't the same as the default storage policy for the VSAN Datastore within the cluster.

Re: Vmware Problem - Issue

$
0
0

If you can find a result today, would you please share it with me?

Re: Can UEM migrate Windows roaming profiles?

$
0
0

Hi iforbes,

 

There's not really a "winner" in that scenario. UEM doesn't care whether the profile settings it saves to a profile archive are coming from a "real" Windows profile, or from an App Volumes writable volume. Similarly, when importing settings from a profile archive, UEM doesn't care whether they end up in a "real" profile or in a writable.

 

Does that help?

Re: get-taskplus failed against standalone host?

$
0
0

thanks LucD, when logged into the standalone host ui and I can see its history tasks, so I am wondering maybe I did not use the api correctly?

Re: VM can’t see the hosts shared folders.

$
0
0

I've updated to the newest version of Workstation on 3 PCs and this is the only one with this issue. I've checked two other Windows 7 hosts and one other Windows 10. They all work but the working Windows 10 is an older version of Windows 10. At some point the Dell Laptop that has the issue updated to the latest version of Windows 10 Preview.

 

I looked and the errors all morning and could find nothing like what I have going on. Disabled all firewalls and enabled all file and print sharing.

 

It's so odd that it is only between the laptops Windows 10 host and it's own VMs.

 

  1. Desktop PC to Laptop share = GOOD
  2. Desktop PC VM toDesktop PC share = GOOD
  3. Laptop toDesktop PC share = GOOD
  4. Laptop VM toDesktop PC share = GOOD
  5. Laptop VM toLaptop share = BAD!

Re: 75 gig of vmdk files in vista guest

$
0
0

In Windows explorer, try taking ownership.

 

Eg. right click the file (or folder vmware-me) you want to delete, properties, security tab page, advanced button, at the top of the  screen that pops up, look at what owner says, if not your account or an account that you control then change it into one.

Once you have ownership, check that the account that owns it has the permissions to delete.

 

If that doesn't work.. attach the disk to another VM as disk "D:"

or... boot from a linux live CD and delete that way.

 

--

Wil


Re: VmwareEsxi上の仮想マシンのシャットダウン、電源OFFの確認について

$
0
0

こんにちは。

 

ログの様子を見ると、VMware Toolsが停止ていていることに関係しそうに見えました。

たとえば、下記のような確認をしてみると、その時の仮想マシンの様子が分かるかもしれません。

  • vSphere Client や Web Client から対象の仮想マシンのイベントやタスクを見て、何か記録が残っていないか。
    ※シャットダウンをしようとしたり、vSphere HAが作動したりしていないか・・・
  • Windows 2012 R2ゲストの中のイベントログなどに、何か記録が残っていないか。
    ※vSphere Client のタスクに記録がなくても、ゲストOSから直接シャットダウンしたような形跡がないか、など・・・

※ESXi はUTC(JSTマイナス9時間)なので、タイムスタンプの読み替えが必要かもしれません。

 

ESXi のサーバ自体の電源をOFFにしたかは、

ESXi のほかのログが同時刻に途切れていないか、ESXi のアップタイムがそのタイミングで途切れていないか、

サーバの管理ボードに、サーバの電源を停止した記録が残っていないか、

といったような確認で見当がつきそうだと思います。

 

以上です。参考になりますでしょうか。

Re: vmware workstation hostd (shared vms) not starting on fresh linux install

$
0
0

Unfortunately it still doesn't appear to be fixed in 12.5.7 build-5813279

Re: VMware Workstation Pro 12.x - Host Memory Allocation

$
0
0

Hi,

 

Well there's another thread here with similar experiences.

VMware Workstation Pro 12 - Host Memory Allocation

no answer there i'm afraid.

 

I tried looking over some of the memory management changes in the linux 4 kernel, but nothing stands out to me.

(see https://kernelnewbies.org/Linux_4 and select one of the kernels from that page)

Caching might be another area that might cause this type of thing.

 

A vmware.log file of a VM might help in diagnosing this.

 

 

FWIW, just looked at one of my linux hosts that has Workstation 12.5.x installed on a 4.8.x kernel and I don't see the VMs take up more as what they should use.

Got two guests running on it, both windows, and they are pretty much using as they have been configured.

Where are you looking how much memory the VMs are using? I just used the top command and looked at the lines that have vmware-vmx as command.

When creating a new VM with 6GB and booting then I do see the VM reserving that memory, but it is all in virtual memory, the actual shared memory that the VM is using is just a few MB. So slow for a bit while the VM is creating that memory backed file, but that isn't strange.

--

Wil

ESXi 6.5.0, USB HID passthrough help

$
0
0

I would like some guidance from someone who understands the vmx config file for usb devices.  I have a situation where we have decided to convert one of our traveling servers who used to run Windows Server 2012 with VMware Workstation Pro into a bare metal ESXi host to take into the field and run demo environments for our potential clients.  Please dont suggest going back to the Windows host and running a Type-2 Hypervisor.  We have no interest in this.  We use this machine for CAD also and need the direct use of the attached Quadro graphics card and display outputs.  We have successfully passed the graphics card through.  This functions great.  We have also been succesful in passing our 3D space navigator through as a USB device.  The last hurdle we face is the HID mouse and keyboard.  I have played around with the config file and even passed through the PCIe adapter that controls the usb bus but no luck.  I believe it is something in the ESXi host preventing the HID device from being recognized as it doesn't ever show up in the available devices list.  I have tried connecting a ps2 mouse and keyboard then booting up the hypervisor.  After Vsphere was up and recognized the PS2 devices maybe it would recognize the second USB devices and let me use them.  No Go.   Below is the config for the VM.

 

I understand the potential pitfall in releasing the keyboard and mouse from the hypervisor and tying them to a VM.  There has to be a way to do this....

 

 

 

Show allHide all

 

     
Apply changes

 

 

pciPassthru1.id00000:001:00.1
pciPassthru1.deviceId0x0e0b
pciPassthru1.vendorId0x10de
pciPassthru1.systemId595bb738-ae78-ee08-311b-0015176a135e
pciPassthru2.id00000:000:15.0
pciPassthru2.deviceId0x402f
pciPassthru2.vendorId0x8086
pciPassthru2.systemId595bb738-ae78-ee08-311b-0015176a135e
usb_xhci.autoConnect.device0vid:046d pid:c626 path:0/5/0/2 autoclean:1
pciPassthru0.id00000:001:00.0
pciPassthru0.deviceId0x11fa
pciPassthru0.vendorId0x10de
pciPassthru0.systemId595bb738-ae78-ee08-311b-0015176a135e
svga.numDisplays2
sched.cpu.latencySensitivitynormal
tools.guest.desktop.autolockFALSE
nvramMRW01.nvram
pciBridge0.presentTRUE
svga.presentTRUE
pciBridge4.presentTRUE
pciBridge4.virtualDevpcieRootPort
pciBridge4.functions8
pciBridge5.presentTRUE
pciBridge5.virtualDevpcieRootPort
pciBridge5.functions8
pciBridge6.presentTRUE
pciBridge6.virtualDevpcieRootPort
pciBridge6.functions8
pciBridge7.presentTRUE
pciBridge7.virtualDevpcieRootPort
pciBridge7.functions8
hpet0.presentTRUE
cpuid.coresPerSocket4
disk.EnableUUIDTRUE
numa.autosize.vcpu.maxPerVirtualNode8
numa.autosize.cookie80001
sched.swap.derivedName/vmfs/volumes/59597523-8aea7fe8-78df-0015176a135e/MRW01.vswp
pciBridge0.pciSlotNumber17
pciBridge4.pciSlotNumber21
pciBridge5.pciSlotNumber22
pciBridge6.pciSlotNumber23
pciBridge7.pciSlotNumber24
scsi0.pciSlotNumber160
sound.pciSlotNumber32
usb_xhci.pciSlotNumber1280
vmci0.pciSlotNumber33
sata0.pciSlotNumber34
scsi0.sasWWID50 05 05 6f c9 03 ab b0
vm.genid1250725909156337573
vm.genidX-7197963755887958834
monitor.phys_bits_used43
vmotion.checkpointFBSize4194304
vmotion.checkpointSVGAPrimarySize4194304
softPowerOffTRUE
acpi.smbiosVersion2.7FALSE
acpi.mouseVMW0003FALSE
ethernet0.pciSlotNumber-1
toolsInstallManager.lastInstallError0
svga.guestBackedPrimaryAwareTRUE
tools.remindInstallTRUE
toolsInstallManager.updateCounter1
sched.mem.pinTRUE
pciPassthru0.pciSlotNumber224
usb_xhci:6.speed2
usb_xhci:6.presentTRUE
usb_xhci:6.deviceTypehub
usb_xhci:6.port6
usb_xhci:6.parent-1
usb_xhci:7.speed4
usb_xhci:7.presentTRUE
usb_xhci:7.deviceTypehub
usb_xhci:7.port7
usb_xhci:7.parent-1
usb.generic.allowHIDTRUE
usb.generic.allowLastHIDTRUE
pciPassthru1.pciSlotNumber256
pciPassthru2.pciSlotNumber1184
usb_xhci:4.presentTRUE
usb_xhci:4.deviceTypehid
usb_xhci:4.port4
usb_xhci:4.parent-1
vmware.tools.internalversion10272
vmware.tools.requiredversion10272
migrate.hostLogStatenone
migrate.migrationId0

 

Vmware Workstation unrecoverable error popup when trying to start virtual machine

$
0
0

Hello, awesome community of VMWare!

I am going to cut straight to the case by mentioning what my problem is. My problem is a message that comes up with with the message as shown: VMware Workstation unrecoverable error: (vcpu-0)

 

vcpu-0:VERIFY

vmcore/vmm/main/physMem_monitor.c:1180

 

A log file is available in "L:\Virtual Machines\macOS

Sierra\vmware.log".

 

You can request support.

 

To collect data to submit to VMware support, choose

"Collect Support Data" from the Help menu.

 

You can also run the "vm-support" script in the

Workstation folder directly.

 

We will respond on the basis of your

entitlement.

 

That message comes up in VMware Workstation and VMware Player, most recent versions of all of them. The guest machine is running macOS Sierra 10.12.1 (At least I think it is 10.12.1). Is there any way to fix this?

Warning: Do not upgrade from 6.5 to 6.5e

$
0
0

I just tried an upgrade using the VAMI, from the online repo, from vSphere 6.5 to 6.5e. The upgrade rebooted my vSphere appliance and neither the VAMI nor vSphere itself came back up. I was able to log into the appliance as root, and was able to observe that no vmware-related processes were running at all. I rebooted the appliance a second time and vSphere started but the VAMI would not start:

 

# systemctl -l status vami-lighttp.service● vami-lighttp.service - LSB: Lightning fast webserver with light system requirements

  Loaded: loaded (/etc/rc.d/init.d/vami-lighttp; bad; vendor preset: enabled)

  Active: failed (Result: exit-code) since Thu 2017-07-06 17:25:25 PDT; 6min ago

    Docs: man:systemd-sysv-generator(8)

  Process: 9551 ExecStart=/etc/rc.d/init.d/vami-lighttp start (code=exited, status=1/FAILURE)

 

<pre>Jul 06 17:25:25 sac-vcenter01.s2prod systemd[1]: Starting LSB: Lightning fast webserver with light system requirements...

Jul 06 17:25:25 sac-vcenter01.s2prod vami-lighttp[9551]: Starting vami-lighttpd:Extracting SSL certificate from VECS

Jul 06 17:25:25 sac-vcenter01.s2prod vami-lighttp[9551]: SSL certificate extracted

Jul 06 17:25:25 sac-vcenter01.s2prod vami-lighttp[9551]: Duplicate config variable in conditional 0 global: server.use-ipv6

Jul 06 17:25:25 sac-vcenter01.s2prod vami-lighttp[9551]: 2017-07-06 17:25:25: (/build/mts/release/bora-4446656/studio/src/vami/apps/lighttpd/1.4.39/src/configfile.c.974) source: /opt/vmware/etc/lighttpd/lighttpd.conf line: 705 pos: 1 parser failed somehow near here: (EOL)

Jul 06 17:25:25 sac-vcenter01.s2prod vami-lighttp[9551]: [FAILED]

Jul 06 17:25:25 sac-vcenter01.s2prod systemd[1]: vami-lighttp.service: Control process exited, code=exited status=1

Jul 06 17:25:25 sac-vcenter01.s2prod systemd[1]: Failed to start LSB: Lightning fast webserver with light system requirements.

Jul 06 17:25:25 sac-vcenter01.s2prod systemd[1]: vami-lighttp.service: Unit entered failed state.

Jul 06 17:25:25 sac-vcenter01.s2prod systemd[1]: vami-lighttp.service: Failed with result 'exit-code'.</pre>

 

After editing that line out of the config file the VAMI would start. My vSphere is still showing the pre-upgrade version (build 5318154) but the VAMI is showing the upgraded version (build 5705665) so my appliance is now in an indeterminate state.

Don't try this upgrade! Even making a snapshot won't save you from some grief unless you know the ESXi host your vSphere is running on, and can fix it from the command line, since it might trash your vSpherem and then you will have no vSphere running....

 

w

Re: Having problems doing a trial install of Horizon 7.1

$
0
0

Add Farm dialog box.png

I see nobody has replied to my original question....   I realized it might make more sense if I included a copy of the actual dialog box and item I'm asking about.

As you can see where I circled it in red, it supposedly prompts for a Host or cluster.  But my actual Horizon 7.1 installation is asking for only a Cluster here, and isn't accepting it when I try to select my single instance of VCenter or the single ESXi server itself.

 

Would this be because I'm using the Enterprise edition instead of Standard?  Or maybe Horizon is simply not the right product for our needs?


Re: Question on Licencing.

$
0
0

Thank you for reply Magneet!!

 

Correct me if I am wrong, if I replace licence key with 500 user, I can still accommodate 800 users?

 

As of now, my ESXi licence is saying, I can create 300 VM's with current licence, I think it mean's I can't accommodate 800 users with out adding new key for 500 VM's?

 

"also currently I am seeing -2 under available VM's in one of the host, under esxi licence detail"

 

lic.PNG

Re: About vRealize Network Insight

$
0
0

Thank you.

There is one doubt.

 

In my environment, the same flow is displayed in "Services in this group" and "External Services Accessed".

 

I do not know why.

 

Re: VMWare Converter: (A file I/O error occurred while accesssing ". )

About the settable maximum value of NSX 6.3

$
0
0

Hello.

 

 

About the settable maximum value of NSX 6.3

 

 

Do you have official information that describes the maximum value that can be set with NSX?

 

 

What I want to know

 

 

1. Maximum number of Logical Switch

         Is it 10000?

 

 

2. Cross-vCenter NSX is how many primary NSX Managers can manage Secandry NSX Manager

 

One primary with max 7 secondary NSX Managers?

Re: Cannot install ESXI 6.5. No Network Adapters found Error.

$
0
0

after using the Powershell script from https://www.v-front.de/p/esxi-customizer-ps.html

with the correct commands, it is loaded succesfully.

Note: PowerCLI need to be installed in PowerShell 5.0 and above

Sample command:

.\ESXi-Customizer-PS-v2.5.ps1 -v65 -vft -load sata-xahci,vmware-esx-dvfilter-maclearn -pkgDir .\bundle -log .\ESXI-6.5.log -nsc

 

in the ./bundle folder make sure only vib or offline-bundle zips are available since it does not perform a recursive check

Viewing all 229567 articles
Browse latest View live