AveryFreeman's Posts

Sorry to bump necrothread, but was a top google hit so I thought I'd weigh in Is there some way you can just reference the VMDK from the USB drive instead of the drive itself? Also, under Workstation preferences, you can set a USB drive to automatically connect to the VM instead of the host when it's plugged in, maybe that would help. Good luck!

I started the task in vCenter, so I actually powered off the vCenter VM and rebooted the host (it's a new one I'm working on setting up still). Lucky for me, the VM was in tact, it just had compute and storage resources on two separate drives.  I migrated the storage back to its original location, tested it and it was fine. I don't recommend this as a solution, it's likely nobody else will be as lucky as I was.

Did you ever resolve this issue? I cancelled a simple migration from one datastore to another and it hung, leaving the source datastore in limbo.  Now I get the same error message both in vCenter and through powercli: "The operation is not allowed in the current state." which is rather cryptic, and I don't seem to be able to get any more information than that. I tried to list the source datastore in SSH or through the web UI and both are inaccessible.  I'm afraid I just destroyed an entire VM by simply hitting the cancel button.

I had a very similar set of symptoms with an Adaptec SmartHBA 2100.  It was advertised as being compatible with native 7.0 drivers, but I couldn't get ESXi to recognize it as an HBA.  It would show up in lspci, but that's it. I upgraded the firmware for the HBA and it started working fine after that. Have you tried updating the firmware yet?

I had this same issue in an AD environment I had to: Shut down VCSA Unsign the dnssec zone delete any references to VCSA in Windows dns server  Restart the domain controllers Create a single A reference to the static IP of VCSA (not sure if this necessary if VCSA is dhcp - probably not)  Start VCSA again Then, and only then, would the hostname resolve and the SSO token be accurate

Just wanted to confirm this worked for me with a Dell H092P 4-port nic on a whitebox AsRock J3455B-ITX I'm putting together for a needy cyber security student (installing OPNSense and wanted an isolated NIC for WAN).  Thanks!

Hello, and thanks for your reply I am seeing vSphere report the MHz in the Hosts and VMs section under the VM--> Configure page - you know, where it has the 'play' button and the link to open Workstation to view the console. I am actually working on using this as a desktop with GPU passthrough.  I had a Nvidia 740 GT working with passthrough for a while but it appears to have stopped working, but that's for another thread. Yes, vmware tools is installed because I am using paravirtualized drivers for SCSI and NIC.  I load the drivers for pvscsi during installation and then install vmware tools 64-bit immediately on first boot for vmxnet3. Just noticed when I was making the VM that it is ungodly slow.  Had never noticed a MHz report in vSphere before, but there it was.  I know resource utilization is extremely low as per esxtop and meters in vSphere - but a 4-core VM should be able to operate Windows in a plenty snappy way. So far now I've tried turning off P and C states in the BIOS and it appears to subjectively made things a little faster.  The processor has a base freq of 2.0GHz but it's 2.7GHz  turbo so I'd think it'd be capable of being at least mildly peppy. I am going to see if I can find a reference for common BIOS settings to enable for ESXi hosts.  It's my first E5 motherboard, there's a lot of additional settings I don't recognize having only worked with E3s. Another thread I was reading was talking about virtual machine monitor mode, which turned up this KB article:  VMware Knowledge Base However, I don't see that setting in my version of vSphere.  I tried setting monitor.virtual_exec = hardware monitor.virtual_mmu = hardware manually in the VMX file (through edit -> vm options -> advanced settings).  But I do not see any difference from that. Any thoughts? Thanks

I haven't tried passing through a USB controller, only my LSI 2008 controller for my FreeBSD VM. I may try it just to see if it works. It's interesting, on the computer I was having issues with passthrough on, I removed 6.7 (which was an install from ISO to USB drive) and replaced it with a new copy of 6.5U1 (installed on same USB drive). I then updated it to 6.7 using the following method and I no longer experience passthrough issues (although I do still see an error message while starting up the server, but it doesn't appear to affect functionality).  I do not currently have vmkernel.boot.disableACScheck = true and it appears to be working fine. Essentially involved using a datastore as swap by going to manage-->system-->swap-->edit (or new) The update pretty much just involves allowing https access through the firewall and using this esxcli command: esxcli software profile update -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml -p ESXi-6.7.0-8169922-standard The update is detailed here: https://tinkertry.com/easy-update-to-esxi-67http:// I do not see the error when # grep -i pass /var/log/vmkernel.log -- [code] 2018-05-09T21:42:30.877Z cpu3:2097597)vmk_MemPoolCreate passed for 64 pages 2018-05-09T21:42:31.315Z cpu0:2097642)vmk_MemPoolCreate passed for 4 pages 2018-05-09T21:42:33.428Z cpu2:2097712)vmk_MemPoolCreate passed for 256 pages 2018-05-09T21:43:09.539Z cpu0:2097526)Activating Jumpstart plugin pciPassthru. 2018-05-09T21:43:09.543Z cpu3:2098058)Loading module pciPassthru ... 2018-05-09T21:43:09.546Z cpu3:2098058)Elf: 2101: module pciPassthru has license VMware 2018-05-09T21:43:09.548Z cpu3:2098058)Device: 192: Registered driver 'PCIPassthru' from 78 2018-05-09T21:43:09.548Z cpu3:2098058)Mod: 4962: Initialization of pciPassthru succeeded with module ID 78. 2018-05-09T21:43:09.548Z cpu3:2098058)pciPassthru loaded successfully. 2018-05-09T21:43:09.553Z cpu0:2097526)Jumpstart plugin pciPassthru activated. 2018-05-09T21:43:10.472Z cpu1:2097526)Activating Jumpstart plugin autodeploy-setpassword. 2018-05-09T21:43:10.499Z cpu1:2097526)Jumpstart plugin autodeploy-setpassword activated. 2018-05-09T21:43:12.116Z cpu7:2097526)Activating Jumpstart plugin pcipassthrupool. 2018-05-09T21:43:12.140Z cpu7:2097526)Jumpstart plugin pcipassthrupool activated. 2018-05-09T21:43:23.041Z cpu5:2098605)WARNING: PCI: 178: 0000:01:00.0: Bypassing non-ACS capable device in hierarchy 2018-05-09T21:47:38.028Z cpu2:2099906)PCIPassthru: 5608: No such device: 0000:02:00.0 2018-05-09T21:48:09.951Z cpu5:2100057)PCIPassthru: 5608: No such device: 0000:02:00.0 2018-05-09T21:49:13.802Z cpu5:2098647 opID=9eb6c991)WARNING: PCI: 178: 0000:01:00.0: Bypassing non-ACS capable device in hierarchy TSC: 898440 cpu0:1)BootConfig: 908: disablePciPassthrough = FALSE 0:00:00:04.802 cpu0:2097152)PCI: 216: enablePCIErrors: 0, enableValidPCIDevices: 1, pciSetBusMaster: 1, disableACSCheck: 0, disableACSCheckForRP: 1, enablePCIEHotplug: 1, pciBarAllocPolicy: 1, disablePciPassthrough: 0 0:00:00:04.856 cpu0:2097152)Initializing PCI passthru ... 2018-05-09T21:50:49.315Z cpu4:2097549)WARNING: PCI: 178: 0000:01:00.0: Bypassing non-ACS capable device in hierarchy 2018-05-09T21:50:50.889Z cpu7:2097597)Loading module pciPassthru ... 2018-05-09T21:50:50.893Z cpu7:2097597)Elf: 2101: module pciPassthru has license VMware 2018-05-09T21:50:50.894Z cpu7:2097597)Device: 192: Registered driver 'PCIPassthru' from 20 2018-05-09T21:50:50.894Z cpu7:2097597)Mod: 4962: Initialization of pciPassthru succeeded with module ID 20. 2018-05-09T21:50:50.894Z cpu7:2097597)pciPassthru loaded successfully. 2018-05-09T21:50:50.899Z cpu6:2097561)WARNING: PCI: 178: 0000:01:00.0: Bypassing non-ACS capable device in hierarchy 2018-05-09T21:50:50.899Z cpu6:2097561)PCIPassthru: PCIPassthruAttachDev:221: Attached to PCI device at 0000:01:00.0 2018-05-09T21:50:50.899Z cpu6:2097561)Device: 327: Found driver PCIPassthru for device 0x25894304be777d1e 2018-05-09T21:50:50.899Z cpu6:2097561)PCIPassthru: PCIPassthruStartDev:362: Received start request for PCI device at 0000:01:00.0 2018-05-09T21:50:50.899Z cpu6:2097561)PCIPassthru: PCIPassthruScanDev:264: Received scan request for PCI device at 0000:01:00.0 2018-05-09T21:51:02.675Z cpu0:2097526)Activating Jumpstart plugin pciPassthru. 2018-05-09T21:51:02.677Z cpu0:2097526)Jumpstart plugin pciPassthru activation failed: pciPassthru->start() failed: error while executing the cli 2018-05-09T21:51:03.563Z cpu4:2097526)Activating Jumpstart plugin autodeploy-setpassword. 2018-05-09T21:51:03.588Z cpu0:2097526)Jumpstart plugin autodeploy-setpassword activated. 2018-05-09T21:51:05.205Z cpu3:2097526)Activating Jumpstart plugin pcipassthrupool. 2018-05-09T21:51:05.233Z cpu3:2097526)Jumpstart plugin pcipassthrupool activated. [/code]

I am having issues with passthrough in 6.7 after using passthrough since 5.5 just fine I think it may have to do with vmkernel.boot.disableACScheck flag - want to set to = true, but all settings reset to default after rebooting the hypervisor now that I upgraded to 6.7 Seems like a weird issue, must be something I have to change to be able to save settings.

Samba can run on FreeBSD, Linux, Solarish, etc. and has AD domain controller functionality.  It actually works really well and is fairly easy to set up. I've managed to get it working fairly well under FreeBSD 11.1 and a few Linux flavors (Arch, Ubuntu, Debian, CentOS, Fedora, OpenSUSE).  It's super, super easy with OpenSUSE since they have  YAST graphical configuration tools (but can't control with RSAT afaik).  Feature-wise, FreeBSD is the easiest to build with MIT Kerberos (as of v4.7) because of the ports tree.  Otherwise, you can either use the included Heimdal kerberos or build it yourself (have successfully compiled with MIT krb5 under Ubuntu and Debian).  Has great features - new versions still include rfc2307 "Unix Attributes" feature which have been depreciated in Server 2016, which is wonderful if you're on Unix machines.  Can even control with RSAT, if that's your thing, if you configure your DC using samba-tool, but Unix Attributes tab is gone from Windows 10 RSAT (limited to Windows 8.1 or 7 if you want the Unix Attributes tab in RSAT).  DNS control with RSAT works out of the box, even with built-in DNS, although it's a little flakey.  DHCP w/DDNS and DNS can also be controlled with RSAT if you install Bind9 and isc-dhcpd as your backend (so I hear, but I haven't tried it yet).  Anyone can have an ADDC now!  http://wiki.samba.org

OK, so the PTR record for ESXi wasn't being created automatically by my MS DNS server VM for some reason - worked fine for everything else AFAIK.   I tried to create it manually but it said it already existed, so I just deleted the A-name and re-created it immediately afterwards.  Had to "refresh" in MS DNS for the PTR to show up in the list but it is there now That didn't start the Debian VM's screen after I re-loaded the web client, so I shut it down using SSH and adjusted the VM's video ram from 4MB to 16MB. That did it!  I will have to remember that from now on in case it happens again.  Thank you very much, I really appreciate it!