So you injected the drivers for this DELL Server into the image and that then worked in the VM?
↧
Re: USB3.0 no assignable to Windows 2008R2 machine
↧
Re: USB3.0 no assignable to Windows 2008R2 machine
Yes, the only problem is that you have to find the exact driver, assuming that it was released by the manufacturer for your server model.
I did it after 2 failed attempts.
If I think about the time taken to find the correct driver, the correct procedure, it would take me less time to upgrade from 2008r2 to 2012r2.
ARomeo
↧
↧
Re: vra 8.0.1 install error
↧
VMware Horizon 7 仮想デスクトップ展開時のエラーについて
お世話になっております。
■質問事項
Horizon Administrator管理ツールから仮想デスクトップ展開した際、Horizon Administrator管理画面のマシン項目に
展開後のマシン名が表示されるのですが、ステータスが「エラー」となり、以下のメッセージが表示されます。
※Horizon Administrator管理ツール→リソース→マシンの項目のステータス表示
No network communication between the View Agent and Connection Server.
Please verify that the vitual desktop can ping the Connection Server via the FQDN
※Horizon Administrator管理ツール→カタログ→デスクトッププールのステータス表示
マシンxxのプロビジョニングエラーが発生しました。ViewAgentとConnectionServerとのネットワーク通信がないことによる
カスタマイズエラー
デスクトッププールのイベントを見ると、メッセージが「プールxxの仮想マシンxxにビデオ設定が正常に構成されました」まで進んでます。
過去、同様の事象で解決された方とかいらっしゃいましたら、ご意見頂けますでしょうか。
■補足
・おおもとのESXiのポートグループを無差別モードに変更
・NestedESXiのネットワークアダプタをVMXNET3に変更
・AD/DNS/DHCPのドメインに関連サーバがドメイン参加されていることを確認(正引き、逆引きで名前解決されていることを確認済み)
・疎通確認済み
・仮想デスクトップ(Win10)のネットワーク設定のIP、DNSは自動取得に設定、ドメイン参加した状態でパワーオフ、スナップショット取得
・仮想デスクトップ展開後のWin10は該当のDHCPからIPアドレスがはらいだされている。ドメインは付与されている
■構成
以上、宜しくお願いします。
↧
Re: VMware Horizon Client Install Error on Windows 10 x64
For me, it still does not install and rolls back when I just try to run the x64 version of Horizon Client 5.3.0. I have not had this problem with previous versions, only with this one.
↧
↧
Re: VMware Horizon Client Install Error on Windows 10 x64
I used Verbose logging for the MSI install and at the very end of the log file is this:
=== Logging stopped: 1/25/2020 17:48:06 ===
MSI (c) (D8:20) [17:48:06:494]: Note: 1: 1708
MSI (c) (D8:20) [17:48:06:494]: Note: 1: 2205 2: 3: Error
MSI (c) (D8:20) [17:48:06:494]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1708
MSI (c) (D8:20) [17:48:06:494]: Note: 1: 2205 2: 3: Error
MSI (c) (D8:20) [17:48:06:494]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709
MSI (c) (D8:20) [17:48:06:494]: Product: VMware Horizon Client -- Installation failed.
MSI (c) (D8:20) [17:48:06:495]: Windows Installer installed the product. Product Name: VMware Horizon Client. Product Version: 5.3.0.8987. Product Language: 1033. Manufacturer: VMware, Inc.. Installation success or error status: 1603.
MSI (c) (D8:20) [17:48:06:496]: Grabbed execution mutex.
MSI (c) (D8:20) [17:48:06:496]: Cleaning up uninstalled install packages, if any exist
MSI (c) (D8:20) [17:48:06:497]: MainEngineThread is returning 1603
=== Verbose logging stopped: 1/25/2020 17:48:06 ===
I noticed these same error messages in previous VMWare install logs, but they mean nothing to me. Probably only VMWare can decode them.
↧
Re: How to keep VM DRS Disabled after vMotion to a different cluster?
Hi,
On the virtual machine we want to migrate, the DRS ((Distributed Resource Scheduler) must be correctly disabled.
This is because the cluster no longer has to count it for the redistribution of the resources of the hosts that are part of the cluster of that virtual machine.
To be migrated, the vm must be excluded from the DRS cluster.
ARomeo
↧
Bug report ESXI 6.7 build 15160138 - missing ISO file crashes any VM export command
Hey guys,
I just spent 4 hours trying to solve this problem and turns out it's a bug so I thought i'd share it here
Steps to reproduce:
1 - create a VM and setup its dvd player to use an ISO file in a datastore as boot device for installing
2 - after install is done the dvd player is automatically disconnected from the connected devices to avoid booting on it again.
3 - delete the ISO file in the datastore or through SSH.
4 - try to export the VM through any mean: web client, ovftools, anything... All fails, especially the web client which just shows a progress bar with no errors.
When you check the logs, you find this in hostd.log:
2020-01-25T22:46:28.314Z info hostd[2098582] [Originator@6876 sub=Solo.Vmomi opID=esxui-2b6c-039b user=root] Activation [N5Vmomi10ActivationE:0x00000063e4b18730] : Invoke done [exportVm] on [vim.VirtualMachine:6]
2020-01-25T22:46:28.314Z info hostd[2098582] [Originator@6876 sub=Solo.Vmomi opID=esxui-2b6c-039b user=root] Throw vim.fault.FileNotFound
2020-01-25T22:46:28.314Z info hostd[2098582] [Originator@6876 sub=Solo.Vmomi opID=esxui-2b6c-039b user=root] Result:
--> (vim.fault.FileNotFound) {
--> faultCause = (vmodl.MethodFault) null,
--> faultMessage = <unset>,
--> file = "/vmfs/volumes/5e2335a6-78aef506-d442-28f10e01eeaf/ISO/debian-10.2.0-amd64-DVD-1.iso"
So even when the dvd player of a VM is disconnected if it was previously set to an ISO file which has been later removed from a datastore it prevents any regular VM export command through any mean and without clear error message.
This shouldn't provoke a blocking to export a VM, and if it does the corresponding action should display "failed because of missing ISO file..." and not just show an infinite progress bar with no errors.
Thanks for your time
↧
conversion process denied
After installing this software, I am getting the following error when starting to convert my local machine: "permission to perform this function is denied", this occurs at the selection of the source machine. Any reason why?
↧
↧
Hyper-V není v mém systému nainstalovaný, ale stále jej VMware detekuje
Nutno podotknout, že používám Windows 10 Insider Preview, takže některé funkce systému mohou fungovat jinak nebo mohou být jinak pojmenované.
Ale: Po delší době jsem si chtěl zapnout svůj virtuální počítač s Windows 98 ve VMware Worstation 15 Player. Nejdříve to po mě chtělo vypnout Defender Guard Credential. Sice jsem jej už vypínal po instalaci VMware, ale ok, zřejmě se to po poslední aktualizaci opět zaplo nebo to doteď fungovalo bez tohoto opatření.
Ale může mi někdo vysvětlit, jak to, že VMware mi teď hlásí další chybu, a sice, že není kompatibilní s Hyper-V a nemůže tedy spustit virtuální počítač? Zaprvé - co to vůbec je za funkci? Zadruhé - jakto, že mi to hází detekci Hyper-V, když tu funkci ani nemám nainstalovanou a logicky tím pádem ani zapnutou?
Může to dělat WSL? To ale není Hyper-V, pokud se nepletu. WSL jsem si instaloval a updatoval na verzi 2 kvůli IDE Visual Studio, abych mohl využívat Cross-platform podporu.
Co můžu udělat pro to, abych mohl opět zase používat VMware? Jediné co chci je, aby mi fungovaly virtuální počítače (Windows 98, Windows 2000, MS-DOS, Linuxové systémy). S čím vším je vůbec VMware nekompatibilní, abych to prostě a jednoduše pozakázal, odinstaloval, případně se smířil s tím, že mi nějaké funkce na Windows a VS budou prostě chybět? Už mě to začíná docela štvát. Pořád něco nefunguje, pořád řeším nějaký problém. Možná jsem udělal chybu, že jsem si stáhl a začal používat VMware a měl jsem zůstat u VirtualBoxu. Chybějící zvuk PC speakeru u MS-DOS není až tak závažný nedostatek, abych si vychutnal staré hry, které buď ten zvuk nutně nepotřebují, nebo podporují zvukovou kartu Soundblaster a kompatibilní (DOOM, Quake).
↧
Re: Bug report ESXI 6.7 build 15160138 - missing ISO file crashes any VM export command
Hi,
well!, thanks for the info I'll try Monday.
ARomeo
↧
Re: Hyper-V není v mém systému nainstalovaný, ale stále jej VMware detekuje
ahoj,
Stejná chyba plus typy rozlišení. Podívejte se na tyto odkazy:
https://superuser.com/questions/1286791/vmware-workstation-and-hyper-v-are-not-compatible
Build 14295: VMware Workstation Pro 12 thinks Hyper-V is installed
ARomeo
↧
Want to set up multiple VLANS between Switch and ESXi 6.7U3
Struggling to get VLANs to work.
I have a couple of different LAB environments I want to set up on a singlw ESXi server.
I have set up the following:
Assigned uplinks 1,2,3 for use for LABS
Here are the physical NICs:
I then setup a Port Group as follows:
On the Ubiquiti Controller I have set the following Network up for VLAN 4:
When I assign port group LAB - ALPINE to the VM there is no network connection at all and no suggestion VLAN ID is being used. I can set a static IP of 10.0.0.1/24 but the VM is not physically bound to this network.
vmnic1, vmnic2, vmnic3 are plugged in to a 24 Port switch with the 3 ports aggregated but not assigned to any particular network.
Any help on what to do here. I've used pfsense in the past to achieve something similar however would rather not use pfsense this time unless I need to.
↧
↧
Re: Hyper-V není v mém systému nainstalovaný, ale stále jej VMware detekuje
I thought that I'd receive response of Czech members rather than automatically translated answer when I wrote in Czech. No Czechs are in tech support team?
Anyway, didn't even know that core security integrity is using Hyper-V engine. Unfortunately, I'm not quite sure if I can even turn it off, because my school's network quite requires me to have this feature enabled (kind of actually demanded, otherwise I couldn't use my computer in the network). It's sad that it doesn't work with such features of Windows. I'm gonna mark it as a correct answer, but I don't think that I'm going to follow it and rather return back to VirtualBox. I already converted all the virtual machines to OVF format to be used with VirtualBox, so I can return back.
Thanks anyway
P.S. - How did I know you run it through Google Translate? It's quite obvious if there are grammar mistakes and your profile links to Italian websites. No offense, but I think that you should just have responded in English. It's quite difficult for me to read through automatic translation and figure out what was meant by that. I understand English quite well, I just expected to receive help from Czech members, especially when the sites support Czech language as well.
↧
Re: Want to set up multiple VLANS between Switch and ESXi 6.7U3
If this is a lab, simplify it, using one port on the switch. You mention aggregating a bunch of them, just try one check network connectivity and move on to more complicated setups.
↧
Re: Hyper-V není v mém systému nainstalovaný, ale stále jej VMware detekuje
Hi,
I thought that I'd receive response of Czech members rather than automatically translated answer when I wrote in Czech. No Czechs are in tech support team?
Actually the majority of answers provided at this forum are from other users.
It is a peer to peer support forum. There's some Czech users that I know, but they are not very frequent visitors here.
The forum is in English, we have some forums that are in the local language of the user, but not in your (or even my) mother tongue.
(picture from: VMTN )
With the new beta of Workstation that was released earlier this week, it is actually possible to run it with Hyper-V, but... (there's always a catch isn't it?) you need to run a Windows insider preview version.
More details about that are here: VMware Workstation Tech Preview 20H1 - Hyper-V/Host VBS Support - VMware Workstation Zealot - VMware Blogs
--
Wil
↧
Cannot run linux(centos7) guest with resolution 1920*1080 under runlevel 3 console mode in host win10.
Hi,
I am running linux(centos7) guest with runlevel 3 console mode ( multi-user mode, which should be without X-server) under host win10, with Workstation 15 player.
I am not how to set it to run with resolution 1920x1080 mode, although it runs normally for runlevel 5, with X-server and Gnome.
When it boots up, it runs with default 800x600, then it seems not be able to change this resolution with full screen mode, unlike the runlevel 5, with X-server and Gnome, which will maximize the linux window with 1920x1080 under full screen mode.
My hardware is Dell notepad Latitude 5480 with Intel core i5.
For the vm hardware display setting, I tried options with/without 3D acceleration, using host setting for monitors, and specific monitor setting(1920x1080)/
From the grub2 boot and run 'vbeinfo' from grub2, it seems there is no 1920x1080 mode supported by bios. It shows max mode is 1152x864.
Attempted to set the below in grub2, but it failed.
GRUB_GFXMODE=1920x1080
GRUB_GFXPAYLOAD_LINUX=keep
I also attempted to change the default resolution to 1920x1080 from the driver vmwgfx, but failed.
- vmwgfx_drv.c
From the below dmesg after with vga mode (1152x864), it seems that drm vmwgfx driver initialized from this grub set resolution.
If BIOS cannot support 1920x1080, then can we change the resolution during vmwgfx initialized?
[ 20.648379] [drm] DMA map mode: Using physical TTM page addresses.
[ 20.649877] [drm] Capabilities:
[ 20.652662] [drm] Rect copy.
[ 20.653815] [drm] Cursor.
[ 20.654718] [drm] Cursor bypass.
[ 20.655635] [drm] Cursor bypass 2.
[ 20.656538] [drm] 8bit emulation.
[ 20.657746] [drm] Alpha cursor.
[ 20.659128] [drm] 3D.
[ 20.660012] [drm] Extended Fifo.
[ 20.661534] [drm] Multimon.
[ 20.663520] [drm] Pitchlock.
[ 20.664353] [drm] Irq mask.
[ 20.665139] [drm] Display Topology.
[ 20.666009] [drm] GMR.
[ 20.667656] [drm] Traces.
[ 20.668921] [drm] GMR2.
[ 20.669932] [drm] Screen Object 2.
[ 20.670871] [drm] Command Buffers.
[ 20.672784] [drm] Command Buffers 2.
[ 20.674149] [drm] Guest Backed Resources.
[ 20.674773] [drm] DX Features.
[ 20.675398] [drm] Max GMR ids is 64
[ 20.676017] [drm] Max number of GMR pages is 65536
[ 20.676642] [drm] Max dedicated hypervisor surface memory is 0 kiB
[ 20.677250] [drm] Maximum display memory size is 131072 kiB
[ 20.677871] [drm] VRAM at 0xe8000000 size is 4096 kiB
[ 20.678491] [drm] MMIO at 0xfe000000 size is 256 kiB
[ 20.679517] [drm] global init.
[ 20.684090] [TTM] Zone kernel: Available graphics memory: 2995720 kiB
[ 20.686497] [TTM] Zone dma32: Available graphics memory: 2097152 kiB
[ 20.687137] [TTM] Initializing pool allocator
[ 20.687754] [TTM] Initializing DMA pool allocator
[ 20.688435] vmwgfx 0000:00:0f.0: BAR 1: can't reserve [mem 0xe8000000-0xefffffff pref]
[ 20.689040] [drm] It appears like vesafb is loaded. Ignore above error if any.
[ 20.690205] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 20.690798] [drm] No driver support for vblank timestamp query.
[ 20.695720] [drm] Screen Target Display device initialized
[ 20.698090] [drm] width 1152
[ 20.698992] [drm] height 864
[ 20.700310] [drm] bpp 32
[ 20.706967] [drm] Fifo max 0x00040000 min 0x00001000 cap 0x0000077f
[ 20.710895] [drm] Using command buffers with DMA pool.
[ 20.711721] [drm] DX: yes.
[ 20.712435] [drm] Atomic: yes
[ 20.727048] checking generic (e8000000 400000) vs hw (e8000000 400000)
[ 20.727062] fb: conflicting fb hw usage svgadrmfb vs VESA VGA - removing generic driver
[ 20.727831] Console: switching to colour dummy device 80x25
[ 20.729772] fbcon: svgadrmfb (fb0) is primary device
[ 20.735793] Console: switching to colour frame buffer device 144x54
[ 20.741865] [drm] Initialized vmwgfx 2.14.0 20170612 for 0000:00:0f.0 on minor 0
Any suggestions were appreciated.
↧
↧
Re: Hyper-V není v mém systému nainstalovaný, ale stále jej VMware detekuje
With the new beta of Workstation that was released earlier this week, it is actually possible to run it with Hyper-V, but... (there's always a catch isn't it?) you need to run a Windows insider preview version.
As it happens (and you may even recall to original question), I do actually run Windows 10 Insider Preview. I have Windows 10 build 19546.1000, perfectly eligible to run beta version of VMware Workstation Player. However I must ask: Does free version of VMware Player have support for Hyper-V in beta version? As it turns out, neighter VirtualBox supports Hyper-V in stable releases.
↧
Re: Shrinking APFS?
Can you explain in more detail how you used CCC to shrink the disk?
↧
Re: Hyper-V není v mém systému nainstalovaný, ale stále jej VMware detekuje
Oh, I have found very interesting page: https://www.tenforums.com/tutorials/139405-run-hyper-v-virtualbox-vmware-same-computer.html
Basically it tells me that Hyper-V is Type1 hypervisor, whereas both VMware and VirtualBox are Type2, therefore they cannot run both at the same time. But there is a small problem:
Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \WINDOWS\system32\winload.efi
description Windows 10
locale cs-CZ
inherit {bootloadersettings}
recoverysequence {1aad407e-3437-11ea-8bb8-b2dedd1adf79}
displaymessageoverride Recovery
recoveryenabled Yes
isolatedcontext Yes
flightsigning Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {1aad407b-3437-11ea-8bb8-b2dedd1adf79}
nx OptIn
bootmenupolicy Standard
hypervisorlaunchtype Off
As you can see, Hyper-V is already disabled. Yet it still doesn't work. Neigther VMware nor VirtualBox will run their virtual machines. I guess it's a bug and they still think I'm running on Hyper-V engine even though I'm not. Well, that's it.
↧