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

Re: Can I move a VM to the same partition as the host ?

$
0
0

I noticed your response indicated to COPY the VM rather than to MOVE it.

My big fear was that a change to the MAC address or the UUID would cause great anger with the windows licensing gods.

It actually doesn't matter, whether you move, or copy the VM's folder from one location to another. What counts is the answer to the question that you will see when you power on the copied/moved VM for the first time. I recommended copying the VM to have the original VM still available in case you need to go back to it.

Please note that you will need to remove the original VM from VMware Workstation's inventory/library, before you add the copied one. Otherwise it may prevent you from keeping the UUID, and MAC address.

 

The second part that you are worried about is about accessing the host's drive/partition directly from within the guest OS, which I think is not the case here.


André


Re: Not enough space on local standard disk in VMWare Player for Linux

$
0
0

I didn't watch the entire video, but the presentation seems to be a bit confused about whether it will be using a "live" installation of CentOS or installing it onto a hard disk.

 

You will either need to:

 

1. Download and use a "Live" image (see the "LiveGNOME" filename shown next to the Installer disc image file in the screenshot, as described at 10:55), in which case you do not need a large virtual hard disk drive (explanation at 11:30);

 

or


2. Download and use a "full" DVD image which you will install onto the virtual hard disk, in which case you will need to ensure that the virtual disk's size is adequate... Later in the presentation, in the section for VMware Fusion at 13:43, the presenter recommends at least 10 GBytes for the virtual hard disk.

 

It will not be possible to use a "full" DVD image and install it into a tiny (100 MByte) virtual hard disk... that is what CentOS is complaining about in the screenshot you provided.

 

Unless the distinction between those two approaches is explained in part of the presentation that I skipped past, you might need to get that clarified by the presenter.

 

Thanks,

--

Darius

Re: NMI on Host System

$
0
0

I tried these things.

 

1) I upgraded the BIOS.

2) Erased the computer completely, and installed a fresh new Windows Server 2019 with all patches.

3) Installed the latest VMWare 15.5.2

4) Created a new fresh VM from scratch of Windows Server 2019

5) NMI during the install process.

6) WIndows system log indicates HAL.dll was the failure point, but sometime in another system file, but almost always hal.dll

 

The weird thing is, If I turn on VMWare logging it will NOT cause an NMI.   Figure that one out and I think you will solve the problem.

 

Going to try ESXi7 next, but it doesn't support my onboard Raid controller, so I will be loosing some capability.

Re: Not enough space on local standard disk in VMWare Player for Linux

$
0
0

Hi dariusd!

 

Thanks for your reply!

 

Sorry, the video is quite lengthy. So I will be referring to your step 1 because I am on Windows OS (Surface Pro).

At 9:30 (as a reference image), the author is talking about grabbing a .iso file (I'm not sure what it means exactly. Author mentions it'll boot a 'clean' version of the OS for the virtual machine)

from a mirror link on this site: redsiege.com/ca/centos8 and I simply clicked the first link (but maybe I shouldn't have?)

 

So now I have this file: CentOS-8.1.1911-x86_64-boot.iso and that's where (10:55) I browsed and selected this iso file I downloaded from the mirror link. And I followed the Author's instruction until 15:55 where I got stuck.

 

So dariusd, do I perhaps have the wrong '"Live" image'? I'm not sure.

 

Kind regards,

vmware toolsが自動的に停止する事象

$
0
0

ご質問させていただきます。

 

ESXi6.0の基板(3台)上に仮想マシンを構築しております。

その仮想マシンのバックアップを取得しようとした際に、1台だけ取得できない事象が発生しました。

バックアップメーカに確認したところ、手動でのスナップショット(静止ゲストファイルシステム(VMwareToolsのインストールが必要)のパターン)が

取得できるか確認されたため、手動で実行したところ、取得できました。

 

ただし、スナップショット取得後、vmwae toolsが停止する事象が発生し、2度目以降は取得できない状況となりました。

仮想マシンのOS(Windows2012R2)上のサービスは起動しているように見えるのですが、vCenter上では認識されないようです。

OS上のサービスを再起動すると、vCenter上にも起動したように反映されるのですが、約30秒後にvCenter上で「(vmware toolsが)実行されていません」と

表示されてしまいます。(数回繰り返しましたが、同様の事象が発生いたします)

 

vmware toolsをアンインストールして、再インストールすると起動したままになるのですが、一度上記スナップショットを取得すると同じ現象が再発いたします。

 

vCenterはアプライアンスの6.7を利用しております。

vmware toolsを常時正常起動させておくにはどのように対応したらよいのでしょうか?

 

よろしくお願いいたします。

Assign IP Public for VMs on ESXi

$
0
0

Hi all,

 

I have a topo networks:

1.jpg

- i have 01 IP publi: 124.45.67.89

How can I:

- assign IP Public 124.45.67.89 for VMs

- management host from VM ip: 192.168.100.100

Re: Single host in cluster with error log on non-persistent storage

$
0
0

Correct. However folder name should be like this if all hosts logs save in same datastore.

/vmfs/volumes/5735f199-20b5a43a-0498-a0369fa17999/.locker-hostname

VMware Fusion for Mac - I was not able to export a windows virtual machine

$
0
0

HI gurus,

I'm new with MacBook and i have installed and configured a windows virtual machine on vmware fusion (free trial for the moment)

For backup purposes i tried the following command:

 

./ovftool ~/Virtual\ Machines.localized/vm.vmwarevm/vm.vmx archive.ovf

 

The message i got is:

Opening VMX source: /Users/nicoladonatiello/Virtual Machines.localized/vm.vmwarevm/vm.vmx

Opening OVF target: archive.ovf

Writing OVF package: archive.ovf

Transfer Failed                      

Error: System error: (std::exception)

Completed with errors

 

 

What is wrong?

 

Thank you

Nicola


Re: Power on VM and Node Status goes to "down" and Edge Transport Node status goes to "Degraded"

$
0
0

Hi Gleed,

I have same issue. But it has not been resolved. Have you dealt with it yet ?

Re: VMware Fusion for Mac - I was not able to export a windows virtual machine

$
0
0

I have tried to generate a log file using the following command:

./ovftool --X:logFile=log.txt  ~/Virtual\ Machines.localized/vm.vmwarevm/vm.vmx archive.ovf

 

i got the error message:

Error: Permission denied for file  : log.txt

Completed with errors

 

Thank you

Re: Assign IP Public for VMs on ESXi

$
0
0
  1. Create a VM Portgroup called "Internet" on that vSwitches where NIC1 is assigned as an Uplink or when NIC1 isnt in use yet create a new vSwitch.
  2. Add a 2n.d vNIC to VM1 and configure it to be connected on the new created Portgroup "Internet"
  3. Configure the IP Adress for the new Interface within the GuestOS

 

Keep notice that you only can use your Internet IP for  one VM and not more. Question: Are you sure that your Internet IP isnt already in use on your Model/Router?

 

Regards,

Joerg

Re: Single host in cluster with error log on non-persistent storage

$
0
0

ScratchConfig.CurrentScratchLocation   /tmp/scratch

 

Thats the unmodified default value. I assume that on your 8 hosts someone just enable to suppress the warning about the logs on non persistent storage instead of solving the problem.

 

Keep in mind than you need a every hosts need it own directory

mkdir  .locker-hostname1 and .locker-hostname2 and .locker-hostname3 and .locker-hostname4 ....

 

Regards,
Joerg

Invalid operation for device '0' vcloud director v10 VM while try to extend the virtual disk

$
0
0

Hi All,

 

We recently did P2V.It has been successfully converted to VMware and the VM is currently running on top of VCD.

 

vSphere version is 6.7 U1

vcloud director v10

Windows 2012 version

 

The Windows 2012 has 2 disks with LSI parallel SCSI controller.

C--> 100 GB space--> Tried to extend the space(from tenant VDC) via online with another 50 GB it got successful.

D--> 760 GB space --->Tried to extend the space(from tenant VDC) with another 450 GB it was not successful.Tried with lower space also 10 GB,50 GB etc..Getting the error as Invalid operation for device '0' also  tried out from vCenter server  as well but no luck on both online/offline.

 

There is no snapshots running on this VM.

 

VPXA logs:-

 

020-04-27T03:59:46.638Z info vpxa[8891692] [Originator@6876 sub=Default opID=vcd-752e124f-af8e-4bf7-9202-9260df3e59b0;activity=urn:uuid:06c92315-73e5-4295-8b75-bc7eed8a7063-29-01-37] [VpxLRO] -- ERROR task-17930 -- vm-233 -- vim.VirtualMachine.reconfigure: vim.fault.InvalidDeviceOperation:

--> Result:

--> (vim.fault.InvalidDeviceOperation) {

-->    faultCause = (vmodl.MethodFault) null,

-->    faultMessage = <unset>,

-->    property = "virtualDeviceSpec.device",

-->    deviceIndex = 0,

-->    badOp = "edit",

-->    badFileOp = <unset>

-->    msg = "Invalid operation for device '0'."

 

hostd logs

 

2020-04-27T03:59:46.484Z error hostd[2101441] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/vsan:523a90f10336da7b-df2f275d8f869fd4/e194735e-42a7-9f7d-d89c-d4ae52981f05/rfs-e-drive.vmx opID=vcd-752e124f-af8e-4bf7-9202-9260df3e59b0;activity=urn:uuid:06c92315-73e5-4295-8b75-bc7eed8a7063-29-01-37-8018 user=vpxuser:VSPHERE.LOCAL\Administrator] New disk capacity change request is ambiguous: (vim.vm.device.VirtualDisk) {

-->    key = 2001,

-->    deviceInfo = (vim.Description) {

-->       label = "Hard disk 2",

-->       summary = "827,983,920 KB"

-->    },

-->    backing = (vim.vm.device.VirtualDisk.FlatVer2BackingInfo) {

-->       fileName = "[]/vmfs/volumes/vsan:523a90f10336da7b-df2f275d8f869fd4/e194735e-42a7-9f7d-d89c-d4ae52981f05/rfs-d-drive.vmdk",

-->       datastore = 'vim.Datastore:datastore-15',

-->       backingObjectId = "ee94735e-a092-3899-4236-d4ae52981f05",

-->       diskMode = "persistent",

-->       split = false,

--> writeThrough = false,

--> thinProvisioned = true,

--> eagerlyScrub = <unset>,

-->       uuid = "6000C292-574e-9ef0-ca27-922b2185a051",

-->       contentId = "109a9a3551fe0a5ad2f14dae1068240a",

-->       changeId = <unset>,

-->       parent = (vim.vm.device.VirtualDisk.FlatVer2BackingInfo) null,

--> deltaDiskFormat = <unset>,

--> digestEnabled = false,

--> deltaGrainSize = <unset>,

--> deltaDiskFormatVariant = <unset>,

-->       sharing = <unset>,

-->       keyId = (vim.encryption.CryptoKeyId) null

-->    },

-->    connectable = (vim.vm.device.VirtualDevice.ConnectInfo) null,

-->    slotInfo = (vim.vm.device.VirtualDevice.BusSlotInfo) null,

--> controllerKey = 1000,

-->    unitNumber = 1,

-->    capacityInKB = 827988992,

--> capacityInBytes = 847860727808,

-->    shares = (vim.SharesInfo) {

-->       shares = 1000,

-->       level = "normal"

-->    },

--> storageIOAllocation = (vim.StorageResourceManager.IOAllocationInfo) {

-->       limit = -1,

-->       shares = (vim.SharesInfo) {

-->          shares = 0,

-->          level = "normal"

-->       },

-->       reservation = 0

-->    },

-->    diskObjectId = "242-2001",

--> vFlashCacheConfigInfo = (vim.vm.device.VirtualDisk.VFlashCacheConfigInfo) null,

-->    iofilter = <unset>,

-->    vDiskId = (vim.vslm.ID) null,

--> virtualDiskFormat = <unset>,

-->    nativeUnmanagedLinkedClone = <unset>

2020-04-27T03:59:46.485Z info hostd[2101441] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/vsan:523a90f10336da7b-df2f275d8f869fd4/e194735e-42a7-9f7d-d89c-d4ae52981f05/rfs-d-drive.vmx opID=vcd-752e124f-af8e-4bf7-9202-9260df3e59b0;activity=urn:uuid:06c92315-73e5-4295-8b75-bc7eed8a7063-29-01-37-8018 user=vpxuser:VSPHERE.LOCAL\Administrator] Reconfigure failed: N3Vim5Fault22InvalidDeviceOperation9ExceptionE(Fault cause: vim.fault.InvalidDeviceOperation

--> )

--> [context]zKq7AVICAgAAAJA0nQAYaG9zdGQAAAy3NWxpYnZtYWNvcmUuc28AAJDIGwDwuBcBg/ViaG9zdGQAAUQhagFcp7EBfKexAYK4sQG8VbABh/6wAZUlsAFhoLEBN6quAdIjrwHNLq8BjTGvgiIkAgFsaWJ2aW0tdHlwZXMuc28AATULwgEtFMIAtU0oAJNRKADLLDYDO30AbGlicHRocmVhZC5zby4wAAQdmw5saWJjLnNvLjYA[/context]

2020-04-27T03:59:46.492Z warning hostd[2101441] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/vsan:523a90f10336da7b-df2f275d8f869fd4/e194735e-42a7-9f7d-d89c-d4ae52981f05/rfs-d-drive.vmx opID=vcd-752e124f-af8e-4bf7-9202-9260df3e59b0;activity=urn:uuid:06c92315-73e5-4295-8b75-bc7eed8a7063-29-01-37-8018 user=vpxuser:VSPHERE.LOCAL\Administrator] Exception thrown during reconfigure: (vim.vm.ConfigSpec) {

 

2020-04-27T03:59:46.604Z warning hostd[2101441] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/vsan:523a90f10336da7b-df2f275d8f869fd4/e194735e-42a7-9f7d-d89c-d4ae52981f05/rfs-d-drive.vmx opID=vcd-752e124f-af8e-4bf7-9202-9260df3e59b0;activity=urn:uuid:06c92315-73e5-4295-8b75-bc7eed8a7063-29-01-37-8018 user=vpxuser:VSPHERE.LOCAL\Administrator] Reconfigure failed,

 

I dont know why D drive extension only creating this issue ?

 

Note:-  For testing purpose,we did restoring the VM from Veeam recent backup. After VM restore to vCenter,we tried to extend the D drive with another 100 GB it got successful.

 

But the main VM is still having the same issue.

 

Any ideas ?

 

Thanks,

Manivel R

Re: Teams backgrounds with View and PCoIP Zero Client

Tags / vAPI - what brings the future.. Powershell?

$
0
0

Good morning,

 

I have used vRO 7.6 and vAPI 7.5 on DEV/TEST vCenter 6.7.0 for a good while now. But I simply cant get it to work on my other vCenter.

I believe I have tried what I can to get it working - obliviously not enough..

 

It thows this error:

 

[2020-04-24 10:12:58.882] [E] com.vmware.vapi.std.errors.unauthorized => {data=<unset>, messages=[com.vmware.vapi.std.localizable_message => {args=[DOMAIN\vROUser, read, DynamicID (com.vmware.vapi.std.dynamic_ID) => {

    type = VirtualMachine,

    id = vm-972716:1b11fb66-0496-4db5-a40a-942644acb921

}], default_message=DOMAIN\vROUser does not have read privilege on DynamicID (com.vmware.vapi.std.dynamic_ID) => {

    type = VirtualMachine,

    id = vm-972716:1b11fb66-0496-4db5-a40a-942644acb921

}, id=cis.tagging.unauthorized.error}]} (Workflow:SetTag3 / Scriptable task (item1)#47)

 

The DOMAIN\vROUser is full admin on the vcenter, and the DEV API seems running with out issues..)

I have given up on the error, and consider new ways to do it..

 

I can read it is possible to do similar with a REST call to the API. As well can I do it why Powershell/PowerCLI via the PS Host..

 

My question is then (preferable how to fix above ) is, what do you expect the future for vRO to bring. Will it at some point be native vRO, is expected to move more in to PowerCLI etc.

What is your expierence and where to you see it more - and maybe also in general - more native, more powershell, or other?

 

Regards, K


Re: Error starting vm error: Failed - Unable to access file [datastore2_vms] srv_cv2 / srv_CV_0-000001.vmdk. Help please

$
0
0

Please check if and how much data you have loosed.

 

Normaly....

- The size of the -delta file indicated how much changed/new data was created in the given period

- The timestamp of the orginal -flat file show how old the snapshot was

 

In your case the -delta is missing and the -flat together with ALL other files have the same and a very recent timestamp. Also there is only a single vmware.log file which is not common for VMs which exists for longer time.

 

So if you have luck than there was a snapshot commit at 04:00 which was merge all -delta back into the -flat and than the error occur and failed to rename the files.

 

Regards,
Joerg

VPXD service gets stopped automatically. Could not connect to one or more vCenter Server systems: https://fqdn:443/sdk

$
0
0

I am running on VCSA 6.5 and facing a weird problem from yesterday. VPXD service goes down in few seconds again and again. Once restarted I get error Could not connect to one or more vCenter Server systems: https://fqdn:443/sdk.

 

There is no crash entry in postgresql. All tables are clean. Please help

 

Regards

Amit

The ESXi host has set configuration maximums that are either hard or soft limited

$
0
0

So we got a message from skyline about 4 critical errors. 3 of which were from

one host that has 2 tiny vms on it and using very little CPU ... actually close to 0

and only 18GB out of 500GB memory

  • Finding ID
    vSphere-EsxConfigLimits-KB#1003497
  • Severity
    CRITICAL
  • Category
    Compute
  • Finding First Observed
    04/23/2020

EXPORT

Description

The ESXi host has set configuration maximums that are either hard or soft limited. It is important to ensure that a host does not exceed these maximums as the server will fall outside of a supported configuration.

Risk if no action taken

Environmental Stability

Recommendations

• 5.5 - https://www.vmware.com/pdf/vsphere5/r55/vsphere-55-configuration-maximums.pdf

• 6.0 - https://www.vmware.com/pdf/vsphere6/r60/vsphere-60-configuration-maximums.pdf

• 6.5 - https://www.vmware.com/pdf/vsphere6/r65/vsphere-65-configuration-maximums.pdf

Helpful Links

https://www.vmware.com/pdf/vsphere6/r65/vsphere-65-configuration-maximums.pdf

Affected Objects (4)

Is this bogus or what ?

Re: OVA vCenter7 deployment problem: vami-lighttp

$
0
0

VMware vCenter Server Appliance

2020-04-02 | 7.0.0 | 6.42 GB | iso

ISO mounted on my Server; OS: Server 2016. In Workstation - > File - > Open - > from directory i took  vcsa.ova;  Basic Configuration Steps: IP Config; SSO; Passwords;last change at the end - switching from Bridged connection to NAT; already on start pop up this Error; when deployment finished i see: https://localhost:5480/......  and IP: https://10.10.67.15:443....which are not recognized and not responding.

 

 

Re: Adding Vcenter to skyline getting error

$
0
0

Hello Robymann,

 

Thank you for your time in the remote session.

 

We were able to add the vCenter using the IP address instead of FQDN and adding Custom SSO configuration details

Viewing all 229419 articles
Browse latest View live