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

Fusion 11 - Virtual machine library window cropped when VM is running

$
0
0

Hello VMware,

 

I like to keep the virtual machine library window small because I see no point in having it fill the screen.  When a virtual machine is running, the IP address and MAC address appear in the VM info, and causes the storage bar to be cropped from the view.  In order to see the complete bar and to access the refresh button at the end of the bar, I have to stretch the window all the way across the screen.  In some cases such as when using multiple network interfaces and running Fusion on a laptop screen, stretching the window across the entire width of the screen is still not enough to see the entire storage bar and the refresh button!

 

Please fix the virtual machine library window as follows:

1. The storage bar should be displayed on a separate line from the CPU, memory and networking info.

2. The storage bar should dynamically resize to fit the width of the virtual machine library window.

3. Instead of cropping the contents, the library window should have scroll bars so users can scroll to see everything without having to stretch the window all the way across the screen.

 

Pic1.jpg


failed VMware Tools install on OSX and Windows 7

$
0
0

Realy boring no copy and paste working on Fusion 11.5 on virtual Win 7 x64 nor OSX Mavericks.

 

During VMware Tools installation (Fusion 11.5) I get on both systems Win 7 and OSX a error during instalation.

On Win 7 I run setup64 with administration rights but there is always a VGauthService failed.

On OSX it says installation failed.

 

What can I do?

Re: role nd permission: only shutdown restart power on power off on both VM and ESXi host

$
0
0

Hi there,

 

sorry I do know this is quite an old topic, but I do have the same issue with ESXI 6.7.

 

I just want the user to be able to start / reboot / shutdown specific VMs without even seeing other VMs.

 

I've set the permissions like this for a group "just reboot"

 

 

Bildschirmfoto 2019-10-06 um 05.39.24.png

 

If I login with the created user I do only see the VMs the user is supposed to see. So far so good. But if I klick on one of the VMs or try to mark a VM this happens:

 

Bildschirmfoto 2019-10-07 um 00.08.50.png

 

Bildschirmfoto 2019-10-07 um 00.08.45.png

 

Any ideas?

Costum reports in vRops 6.2

$
0
0
Change the Cover Page of the generated reports, upload an image up to 5 MB.

Re:Costum reports in vRops 6.2

$
0
0
I also donnot know this question.

Is it possible to add Horizon to vIDM when using non-standard ports?

$
0
0

I have horizon redirected to port 444 on SSL in an environment, and I'm unable to add it to Workspace One Access. I would think this would be permitted, but apparently not? If you remove the port it is able to be added, but I need the port to be specified or it throws the error that it can't reach the service. Soooo

 

 

When i remove the port and connect directly to the connection server...as is expected it fails and can't connect to the URL.

 

Re: Windows 10 pop-up message: "VMWare Workstation Pro can't run on Windows" (Solved )

$
0
0

Thanks!...I will make a backup copy of C:\Windows\apppatch\sysmain.sdb

Lost datastore after converting RAID 1 array to RAID 5 on Dell PE...

$
0
0

I have a Dell PE R415 that I have upgraded to ESXi v6.0 allong with adding a third drive to an array, converting from a RAID 1 to RAID 5 to increase storage from 4TB to 8TB.  Upon reboot, I discovered my datastore was no longer mounted.  I have dug around and the other posts I have found don't match my situation.  When I list the contents of /dev/disks I see this:

 

[root@localhost:/dev/disks] ls -al

total 15628855120

drwxr-xr-x    2 root     root           512 Oct  6 23:19 .

drwxr-xr-x   15 root     root           512 Oct  6 23:19 ..

-rw-------    1 root     root     2104425984 Oct  6 23:19 mpx.vmhba33:C0:T0:L0

-rw-------    1 root     root       4161536 Oct  6 23:19 mpx.vmhba33:C0:T0:L0:1

-rw-------    1 root     root     262127616 Oct  6 23:19 mpx.vmhba33:C0:T0:L0:5

-rw-------    1 root     root     262127616 Oct  6 23:19 mpx.vmhba33:C0:T0:L0:6

-rw-------    1 root     root     115326976 Oct  6 23:19 mpx.vmhba33:C0:T0:L0:7

-rw-------    1 root     root     299876352 Oct  6 23:19 mpx.vmhba33:C0:T0:L0:8

-rw-------    1 root     root     8000450330624 Oct  6 23:19 naa.6848f690e0274300251d715007dfd58e

-rw-------    1 root     root     8000449265152 Oct  6 23:19 naa.6848f690e0274300251d715007dfd58e:1

lrwxrwxrwx    1 root     root            20 Oct  6 23:19 vml.0000000000766d68626133333a303a30 -> mpx.vmhba33:C0:T0:L0

lrwxrwxrwx    1 root     root            22 Oct  6 23:19 vml.0000000000766d68626133333a303a30:1 -> mpx.vmhba33:C0:T0:L0:1

lrwxrwxrwx    1 root     root            22 Oct  6 23:19 vml.0000000000766d68626133333a303a30:5 -> mpx.vmhba33:C0:T0:L0:5

lrwxrwxrwx    1 root     root            22 Oct  6 23:19 vml.0000000000766d68626133333a303a30:6 -> mpx.vmhba33:C0:T0:L0:6

lrwxrwxrwx    1 root     root            22 Oct  6 23:19 vml.0000000000766d68626133333a303a30:7 -> mpx.vmhba33:C0:T0:L0:7

lrwxrwxrwx    1 root     root            22 Oct  6 23:19 vml.0000000000766d68626133333a303a30:8 -> mpx.vmhba33:C0:T0:L0:8

lrwxrwxrwx    1 root     root            36 Oct  6 23:19 vml.02000000006848f690e0274300251d715007dfd58e504552432048 -> naa.6848f690e0274300251d715007dfd58e

lrwxrwxrwx    1 root     root            38 Oct  6 23:19 vml.02000000006848f690e0274300251d715007dfd58e504552432048:1 -> naa.6848f690e0274300251d715007dfd58e:1

[root@localhost:/dev/disks]

 

And in /vmfs/volumes:

 

[root@localhost:/vmfs/volumes] ls -al

total 772

drwxr-xr-x    1 root     root           512 Oct  6 23:18 .

drwxr-xr-x    1 root     root           512 Oct  2 00:53 ..

drwxr-xr-x    1 root     root             8 Jan  1  1970 2c5318ec-8a80a8fc-523c-16e28ab50e2a

drwxr-xr-x    1 root     root             8 Jan  1  1970 42508ee6-6a0fb0cc-ba22-9e19120afc17

drwxr-xr-x    1 root     root             8 Jan  1  1970 5d93e381-6cf0b5f0-f37a-e89a8fd28de6

[root@localhost:/vmfs/volumes]

 

Running esxcli storage core path list shows:

 

unknown.vmhba2-unknown.2:1-naa.6848f690e0274300251d715007dfd58e

   UID: unknown.vmhba2-unknown.2:1-naa.6848f690e0274300251d715007dfd58e

   Runtime Name: vmhba2:C2:T1:L0

   Device: naa.6848f690e0274300251d715007dfd58e

   Device Display Name: Local DELL Disk (naa.6848f690e0274300251d715007dfd58e)

   Adapter: vmhba2

   Channel: 2

   Target: 1

   LUN: 0

   Plugin: NMP

   State: active

   Transport: parallel

   Adapter Identifier: unknown.vmhba2

   Target Identifier: unknown.2:1

   Adapter Transport Details: Unavailable or path is unclaimed

   Target Transport Details: Unavailable or path is unclaimed

   Maximum IO Size: 131072

 

Running esxcli storage vmfs extent list yields a blank display.

 

Running esxcli storage filesystem list shows:

 

[root@localhost:/dev/disks] esxcli storage filesystem list

Mount Point                                        Volume Name  UUID                                 Mounted  Type       Size       Free

-------------------------------------------------  -----------  -----------------------------------  -------  ----  ---------  ---------

/vmfs/volumes/5d93e381-6cf0b5f0-f37a-e89a8fd28de6               5d93e381-6cf0b5f0-f37a-e89a8fd28de6     true  vfat  299712512   84189184

/vmfs/volumes/42508ee6-6a0fb0cc-ba22-9e19120afc17               42508ee6-6a0fb0cc-ba22-9e19120afc17     true  vfat  261853184  261849088

/vmfs/volumes/2c5318ec-8a80a8fc-523c-16e28ab50e2a               2c5318ec-8a80a8fc-523c-16e28ab50e2a     true  vfat  261853184   73515008

[root@localhost:/dev/disks]

 

Running esxcfg-mpath -b shows:

 

[root@localhost:/dev/disks] esxcfg-mpath -b

naa.6848f690e0274300251d715007dfd58e : Local DELL Disk (naa.6848f690e0274300251d715007dfd58e)

   vmhba2:C2:T1:L0 LUN:0 state:active Local HBA vmhba2 channel 2 target 1

 

 

mpx.vmhba33:C0:T0:L0 : Local USB Direct-Access (mpx.vmhba33:C0:T0:L0)

   vmhba33:C0:T0:L0 LUN:0 state:active Local HBA vmhba33 channel 0 target 0

 

 

mpx.vmhba1:C0:T0:L0 : Local TEAC CD-ROM (mpx.vmhba1:C0:T0:L0)

   vmhba1:C0:T0:L0 LUN:0 state:active Local HBA vmhba1 channel 0 target 0

 

 

t10.DP______BACKPLANE000000 : Local DP Enclosure Svc Dev (t10.DP______BACKPLANE000000)

   vmhba2:C0:T32:L0 LUN:0 state:active Local HBA vmhba2 channel 0 target 32

 

 

[root@localhost:/dev/disks]

 

esxcfg-scsidevs -l shows:

 

naa.6848f690e0274300251d715007dfd58e

   Device Type: Direct-Access

   Size: 7629824 MB

   Display Name: Local DELL Disk (naa.6848f690e0274300251d715007dfd58e)

   Multipath Plugin: NMP

   Console Device: /vmfs/devices/disks/naa.6848f690e0274300251d715007dfd58e

   Devfs Path: /vmfs/devices/disks/naa.6848f690e0274300251d715007dfd58e

   Vendor: DELL      Model: PERC H700         Revis: 2.10

   SCSI Level: 5  Is Pseudo: false Status: on

   Is RDM Capable: false Is Removable: false

   Is Local: true  Is SSD: false

   Other Names:

      vml.02000000006848f690e0274300251d715007dfd58e504552432048

   VAAI Status: unsupported

 

The output of esxcfg-scsidevs -m is blank.

 

Not so long ago, I watched a vmware support tech fix this very problem on a paid deploy, but it went too fast for me to follow, but basically she recreated the link between the vmfs on the local Dell disk and a datastore. 

 

Can someone point me in the correct direction?

 

Any assistance much appreciated!

 

Clay


Re: VMware Workstation and Hyper-V are not compatible. Remove the Hyper-V role from the system before running VMware Workstation.

$
0
0

I have made sure that Hyper-v is not installed, I have run the launch off command and rebooted, I have verified the Core Isolation memory integrity is off,

I STILL GET THIS ERROR - it is frankly driving me nuts

Same here. I don't have Hyper-V installed, yet I still get this error:

 

Hyper-Voff.png

 

Hyper-VerrorMessage.png

 

Any help solving this problem would be GREATLY appreciated!!!!

Re: How is this possible? I can't get... or even buy 32 bit vddk!!!

$
0
0

I already stated, I own many 64 bit Windoze on modern hardware (machines).

 

I also said, I prefer to work in Windows XP. Yes, I know, other companies besides Microsoft

are helping kill Windows XP.. Intel, has purged the driver support for the hardware I have of theirs.

So, I have to drag out my box of hard disks, old IDE/PATA disks that have the drivers on them.

 

Thank You...asajm, for ignoring the spirit of my request for help! I have machines you say are safe,

I just hate to use them!!!

 

My Windows XP machines are behind a hardware firewall... Live in their own little world.

I could care less about Microsoft supportingmy use of Windows XP!!! Wish they had not made

such a bad decision, and Bill Gates, the man who could not see the internet coming, but who's job it

was to know that it was in fact coming, knows that killing Windows XP is a bad decision. He left Microsoft

the same week that they would not make any new keys to activate XP. Yeah, he had his hay day.

And so did I... for me in my life, that occurred when windows XP was released to the masses.

I learned it, and know it like the back of my own hand.

 

I didn't join up on the community to be lectured about upgrading...Those of you that have, great for you,

but I am not going there with you! My heart is in 32 bit land. When I was a younger man, that was what I

became well versed in. Now that I am 62 years young, and have forgotten more than I know, I just want

to play with the computers I know best.

 

I am hoping someone here can help me get a copy of their previously downloaded 32 bit vddk.

I have backups going all the way back to 2000... I am sure other people here do too.

Re: Windows 10 pop-up message: "VMWare Workstation Pro can't run on Windows" (Solved )

$
0
0

Hello --- It seems that MS patch KB4524147 had made older version of vmware player invalid  --- I tried to install the latest version, but my hardware is old and

the new version will not run 

 

Is there any chance that vmware will fix the older version to they will now run in  w10/1903?

NSX-V migration options for agentless antivirus.

VMware Workstation throws Hyper-V Error Message even though Hyper-V is NOT Installed

$
0
0

Like the title says, whenever I try to boot up a virtual machine, I get an error message about VMware not being compatible with Hyper-V even though Hyper-V is not installed. Here are some screenshots:

 

Hyper-Voff.png

 

Hyper-VerrorMessage.png

 

So far, I cannot find a workaround. Any help would be appreciated. Thanks!

Re: How is this possible? I can't get... or even buy 32 bit vddk!!!

$
0
0

VMware-mount 5.5 from 2006 may be close - see attachment

Re: VCSA6.7におけるファイルバックアップにおけるプロトコル

$
0
0

nkaneda様

 

やはり、FTPサーバのactive、passive設定を変更しても(結局③のFTPサーバのactive、passiveはどちらでも良かった模様)

通信におけるファイアウォールを完全に無効にしても、データを転送することができませんでした。

事象として

・VCSAのバックアップを実行後、FTPサーバとの通信はとれて、vCenter/sn_<VCSAのホスト名>/のディレクトリは作成されている。

しかし、バックアップデータが保存されない。

ディレクトリが作成できていることから、通信要件と使用FTPユーザの権限に問題がない認識。

・通信時のログより、バックアップデータを約63KBまで送信したところでvCenter側から削除処理が走っており、タスクがエラーで停止。

・一時的に同クローズ環境内にWIN10にてFTPサーバを作成し、VCSAのバックアップ先に指定し実行したところ、正常に作成することができ、リストアできる。

 

対応

・バックアップログを取得し、VMwareにSRを上げて対応しております。


Re: Kernel Panic - Not Syncing - Failed Exception in Interrupt | Kali on ESXi

$
0
0

Thanks for the revert Tayfun, I will definitely try this and update.

 

In the meantime, I have a question. Since the VM was already working on 5.5, and does not on 6, and your suggestion is to update to 6.5 as the Debian 10 is supported in that version.

How is it that the same VM is supported on an older 5.5 version but not the newer 6.0 version and is now supported in 6.5 version? How is it that something that was already supported on an older version is not supported/working on a newer version?

 

Thanks & regards

Re: Defect report: cloning ready-for-easy-install machines

$
0
0

I have the same issue.

I need to start a lot of VM installations simultaneously with unique identifiers and custom hardware parameters.

As it requires a lot of manipulation via 'New Virtual Machine' wizard, I thought why not to create one, and before powering on - quickly create the clones?

Mac, bios id and hdd serial gets new identifiers.

However, in that scenario the autoinstall image left missing.

I would copy-paste it manually, but I suppose it carries some unique generated identifiers?

Re: VMWare 12 not working on Windows 10 1903

MKS作用

Windows 10 VM can not diag PPTP within NSX-T 2.41 Segment

$
0
0

If I put the Windows 10 VM within NSX-T 2.41 Segment, the PPTP can't diag on remote PPTP server. If I put the same Windows 10 VM outside NSX-T, then PPTP can diag PPTP server. Is there anyone encountered th problem?

 

The attached files are the packet capture files from ESXi.

Viewing all 231052 articles
Browse latest View live


Latest Images

<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>