user9922's Posts

But is it a good idea to attach a disk directly to you ESX in the first place? In my experience if a direct connected disk dies, the whole ESX box freezes incl. all VMs!!! Not only those which ... See more...
But is it a good idea to attach a disk directly to you ESX in the first place? In my experience if a direct connected disk dies, the whole ESX box freezes incl. all VMs!!! Not only those which are located on the disk, but all and everything. Or have I just been unlucky when that happened to me? It seem the only proper way to attach storage to ESX is by a RAID controller or SAN/NAS, it is simply not optimized or prepared for it.
Thank for you feedback and direct  honesty, I guess you really don't like ESX But I agree with you on many of the issues you point out. Quality of the software, the website, their product nam... See more...
Thank for you feedback and direct  honesty, I guess you really don't like ESX But I agree with you on many of the issues you point out. Quality of the software, the website, their product naming/branding. Management tool....I don't agree so much.Try to connect Hyper-V manager to a HyperV server (non-desktop version of course) not joined to the domain....that's take a lot of work! I think the ESXi did a pretty good job with the Web client, and I like you can SSH to your ESX  server....you can't do that to you Hyper-V. You can use PowerShell, but I still prefer my putty and WinSCP Unfortunately I need USB passthrough, that's why I consider ESXi.
me too...how can we do this in the console?
This solution is for ESX 6.5 web-client. I was not able to select another port-group in the VM either if I created the switch and port-group in the web-client. I had to create the switch and por... See more...
This solution is for ESX 6.5 web-client. I was not able to select another port-group in the VM either if I created the switch and port-group in the web-client. I had to create the switch and port-groupe using the CLI esxcli network vswitch commands (doc1, doc2) : Syntax: esxcli network vswitch standard add -v=vSwitchName esxcli network vswitch standard portgroup add -p=portgroup-name -v=SwitchName Example: esxcli network vswitch standard add -v=SW_iSCSI esxcli network vswitch standard portgroup add -p=PG_iSCSI -v=SW_iSCSI To change MTU on swith and port-groupt: esxcli network vswitch standard set -m=5000 -v=SW_iSCSI
While I would love to love ESX.....there is one thing that talk against it: Running local storage. VMware earn their money on their Enterprise customers which use SAN, e.g. i SCSI,  and expensiv... See more...
While I would love to love ESX.....there is one thing that talk against it: Running local storage. VMware earn their money on their Enterprise customers which use SAN, e.g. i SCSI,  and expensive enterprise hardware hence this is where focus is....and it shows! It means ESX have a limited hardware support and often terrible performance on local-storage-setup. One exception is USB pass-through though, which Hyper-V doesn't have. You can get good storage performance with SSD or/and have a lot of hardware storage cache to compensate for the terrible ESX-local-storage handling. To get a decent performance on ESX with local storage you have to virtualize something like FreeNAS to deliver iSCSI and  pass-through your local storage adapter(s) to FreeNAS so ESX doesn't touch it directly. Then have ESX use the iSCSI that FreeNAS deliver, which is virtualize by ESX itself, a long way to just get decent local storage! You can also pass-through a whole disk to a VM (using a RDM-file on ESX), but then VMs can share storage and not have a VM in one file, which it many cases is on of the biggest reasons to virtualize in the first place. Another thing to prove my point ESX doesn't support disk with 4K sectors which has been around for a long time and is the future. Hyper-V (and for that matter FreeNAS) does of course. But again ESX didn't want to use "5 minutes" to implement it in ESX....I believe the job is already done in the linux kernel, they can just grape it, they don't have to build from ground up. Compared with Hyper-V where local storage works like it should out of the box with good performance....even support Intel RSTe raid. ESX is Linux and have a small footprint.....Hyper-V is Windows and we all know what that means, although it's a Core version. The small-business market is HUGE and can be a good business....but VMware still have to wake-up and smell the coffee. VMware should put a price tag on ESXi at $125 instead of give it away free and sell 100.000 licenses...that should cover the "5 minutes" it take to implement descent local storage handling. On top of that VMware would get even more fans which would choose ESX over Hyper-V when they one day move to enterprise-class.
...but is the 960 Pro reliable in ESX 6.5 In this thread a user gets his datastore corrupted when using 960 Provirten.net... http://www.virten.net/2017/03/vmware-homeserver-esxi-on-7th-gen-inte... See more...
...but is the 960 Pro reliable in ESX 6.5 In this thread a user gets his datastore corrupted when using 960 Provirten.net... http://www.virten.net/2017/03/vmware-homeserver-esxi-on-7th-gen-intel-nuc-kaby-lake/ ?
I have the same problem...seem to only have USB 2.0. Intel C236 chipset. Device ID: Class 0c03: 8086:a12f
I have en LSI RAID controller. (9341-4i) There exist two different drivers the the device-id of this controller: -lsi-mr3 -scsi-megaraid-sas ESX default load the "lsi-mr3" driver. How do I... See more...
I have en LSI RAID controller. (9341-4i) There exist two different drivers the the device-id of this controller: -lsi-mr3 -scsi-megaraid-sas ESX default load the "lsi-mr3" driver. How do I force ESX to use the "scsi-megaraid-sas" driver instead using console? I guess I can uninstall the "lsi-mr3" driver package and hopefully the "scsi-megaraid-sas" will be used after reboot, but I would like to be able to change driver without uninstalling.
Still a problem in version 1.10.1
...using harddisk locally  attached to host, and with transfers above 80MBs. I've tried using an LSI RAID controller 9341i (SAS 3008 chipset), and using newest driver and firmware. Tried all co... See more...
...using harddisk locally  attached to host, and with transfers above 80MBs. I've tried using an LSI RAID controller 9341i (SAS 3008 chipset), and using newest driver and firmware. Tried all combination of RAID, non-RAID and setting the VM controller to use VMware paravirtual ....same result. By the way I got the exact same behaviour using the onboard SATA controller. When more than 2-3GB are copied in the guest (Windows) the harddisk latency goes crazy and transfers drops to anything between 0 to 30MBs. It seems like some kind of buffer is filled up. If I pause the copying a few second and resume, speed is regained for a while and then drops again. To recreate this problem the transfer has to be no less than about 80MBs otherwise this "buffer",  or whatever it is,  will not be filled up quickly enough. This RAID controller doesn't have have any cache memory, but ESX should still not behave like this? And I'm using SATA disks....it that why? (they have 64MB cache and should be filled up long before reaching 3GB copying). When using the RAID controller as pass-through I don't get this problem. But then I cannot have my Windows system in an VMDK file, right?. And I assume I can only use the controller for one VM, right? Using ESX 6 update 2. Chipset: Intel C232 and C236 (tried both)
My controller will not work if I set the controller ROM to use legacy mode (where you see e.g. Ctrl+R in the BIOS boot process). I have to set the controller's ROM to use UEFI mode......configur... See more...
My controller will not work if I set the controller ROM to use legacy mode (where you see e.g. Ctrl+R in the BIOS boot process). I have to set the controller's ROM to use UEFI mode......configuration of this is done inside the motherboards "normal" UEFI BIOS. And the controller config will now be accessible inside the motherboard bios.
If you enable Traffic shaping on the default switch the whole host server dies and your only option seem to be "Reset System Configuration" :smileycry: Why? There seem to be another bug in... See more...
If you enable Traffic shaping on the default switch the whole host server dies and your only option seem to be "Reset System Configuration" :smileycry: Why? There seem to be another bug in the storage system when using Intel SATA (chipset Intel C232) on the host system. E.g. if you start to copy data within the guest system, in this case Server 2016, the throughput drops dramastic after copying about 1.5-2.0 GB.  If I then pause the copy and resume after some seconds the throughput regain its speed for another 1.5-20GB. It seems like some kind of buffer is filled up. My idea was to limit the network bandwidth to e.g. 75MB/s and see if the buffer could keep up with these speed.....just as a work arround. I made another thread about it.
It would be nice to be able to specify a DNS hostname of the ESXi host in the VMware Host Client: It can be done directly on the host-console:
VMware Host Client version: 1.10.0 If a harddisk is physical removed but still add in the VM the Host Client will crash when you try to remove the harddisk by select "Edit" in the VM. Thi... See more...
VMware Host Client version: 1.10.0 If a harddisk is physical removed but still add in the VM the Host Client will crash when you try to remove the harddisk by select "Edit" in the VM. This disk doesn't exist anymore When you try to edit the VM to remove the harddisk you get this By the way when you login again, the welcome nag-screen reappear even though you disabled it....seems the host is reset in some way....I guess that's another bug
I don't know what "latest webclient" means. But have you tried this one? Ver. 1.9.1 (16/9-2016): https://labs.vmware.com/flings/esxi-embedded-host-client Direct URL: https://download3.vmware... See more...
I don't know what "latest webclient" means. But have you tried this one? Ver. 1.9.1 (16/9-2016): https://labs.vmware.com/flings/esxi-embedded-host-client Direct URL: https://download3.vmware.com/software/vmw-tools/esxui/esxui-signed-4393350.vib‌
If you, in datastore-browser, move a VM (e.g. the folder the VM is located) to another location, e.g. another datastore on the same host, the harddisk is no longer thin provisioned. I also tri... See more...
If you, in datastore-browser, move a VM (e.g. the folder the VM is located) to another location, e.g. another datastore on the same host, the harddisk is no longer thin provisioned. I also tried to use the OVF Tool with this command: ovftool -ds=DS2 vi://root:password@host1/VM1_DS1 vi://root:password@host1 The new harddisk it not thin provisioned afterwards I believe if I first export the VM to an OVF and then import it, the thin provisioning is preserved....but that is double work Any way to do this in one transfer? host-client version: 1.9.1 OVF Tool version: 4.1.0
Oh yea....I found it Yes, you can download the vmdk file perfectly.....and 50% faster than using OVF Export in the host-client or using the OVF Tool.
...I assume we're talking about the vSphere Client, right? But you can't access the VM files directly in then vSphere Client....I haven't found it? You can export to OVF,  but that's a differen... See more...
...I assume we're talking about the vSphere Client, right? But you can't access the VM files directly in then vSphere Client....I haven't found it? You can export to OVF,  but that's a different thing.
When I try to download a .vmdk file from a datastore, only 1KB is downloaded and the web-client crashes after 5-10 seconds. I have no problems downloading any of the other file types. I a... See more...
When I try to download a .vmdk file from a datastore, only 1KB is downloaded and the web-client crashes after 5-10 seconds. I have no problems downloading any of the other file types. I also tried to just copy the vmdk file to another folder on the datastore and it copied the whole file in 0,01sec....that doesn't seem right! I wonder if the file is empty? If you copy the whole folder is seems everything is being copied correctly, although it's NOT possible to cancel the copying
I tried with the newest version 1.9.1......and it didn't have this bug (at least not with only one disc). Haven't tried 1.9.1 with two disks.....yet.