New answers tagged

0

I opened this post in the RedHat discussion and a support member suggested me this other post. I tried the different solutions shown and adding the kernel option vmwgfx.enable_fbdev=0 in the grub configuration file worked. Thanks everyone.


1

If your VLAN and routing settings are correct, that shouldn't be a problem. We use pfSense as DHCP/ gateway for all our physical and VM servers (the pfSens is a VM).


2

This is probably due to OS support or a resource issue. EL7 was not intended for use with vSphere 4. The VMware support matrix reinforces this. I see you're using open-vm-tools, but it looks like you may have a deeper issue. See: https://access.redhat.com/solutions/21849 and: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=...


0

PowerCLI is nothing less than a powershell console that is started with a ps1 script which initializes the Powershell VMWare Commandlets. So i would say you could do anything with this powerCLI that you can do with the powerShell. You could even add lines into the loaded ps1 file - which on my Server is located at %ProgramFiles(x86)\VMware\Infrastructure\...


1

In a nutshell: Try disabling VMware's svgadrmfb framebuffer driver. I had the same change in resolution and discovered that the framebuffer became enabled after an update on one of my virtual machines. Now for the long answer... I came across your question in search of an answer to the same exact issue, although in my case the display resolution had ...


4

The following best practice prevents this problem from occurring: Always unmark devices for passthrough before removing them from the server. The following workaround describes how to force the change from passthrough mode to non-passthrough mode: Edit the /etc/vmware/esx.conf file by changing the owner of the PCI device from passthru to vmkernel. The ...


2

Using the Vsphere Client select your host, then the Configuration tab, select Advanced Settings in the Hardware section, then Configure Passthrough and de-select the PCI device you're concerned about and reboot the host.


0

I think the following recommendation is probably what's tripping it but we've never followed this recommendation and never had any serious issues. We do however use write protective hardware, battery backed raid controllers and such, "To ensure durability of Active Directory writes, do not deploy a virtual domain controller’s database files (the Active ...


0

You can use vim-cmd: Here is an example (shutdown only one VM: SRV1): [root@ESX1:~] vim-cmd vmsvc/getallvms Vmid Name File Guest OS Version 1 SRV2 [NAS] SRV2/SRV2.vmx winLonghornGuest vmx-08 2 SRV1 [SAN] SRV1/SRV1.vmx winLonghornGuest vmx-08 [root@ESX1:~] vim-cmd vmsvc/power.shutdown 2 You can also ...


0

I can't speak on the PowerCLI side, but there are other options to automate the deployment/management of multiple VMs. Two great tools are Chef and Puppet. Makes live easy by specifying the template of the server you want, with some basic parameters then it takes care of the rest. Even makes updating and tracking software on the servers easy as well.


2

Pity you're not on v6, it has this thing called Instant Clone that would speed up this kind of deployment. Anyway have you thought about just using a DHCP/dynamic-DNS solution for this kind of thing, you can pipe through a unique MAC to each VM which would then feed the DHCP to get hostname/IP/DNS details and then register with a dynamic DNS server once ...


0

After many tests it seems the motherboard or something else in the system is incompatible. The Gigabyte motherboard is incompatible. I also tried a second system I had around, BIOSTAR A770E3 AM3 this also seems to be incompatible. Tried these approaches: I tried the CD in other systems, was able to get to the ESXi install screen Tried several CDs and ...


1

You're doing right things. Just a few tips to consider before you start (if not too late). If you use incremental backup chains (not incremental-forever), then you should be able to free some space up by deleting previously used chain(s). In case of reverse incremental chain, it's even easier with deletion of the most outdated points. General recommendation, ...


2

See: http://www.yellow-bricks.com/2012/02/08/distributed-vswitches-and-vcenter-outage-whats-the-deal/ Network connectivity during a vCenter outage is preserved. The ability to modify the vDS settings is impaired, but the VMs will maintain connectivity.


0

The descriptor file defines how and where the data of the VMDK image is stored. The data is stored in extent data files. I think copy-datastoreitem only copies a file, that is in your case: You just copy / download the descriptor file which is pretty small. I didn't find a PowerCLI command to download a VMDK but maybe Export-VApp can help you. On reddit ...


0

Use PowerCLI to automate this process. This isn't a trivial project, but it is extremely flexible and can lay the foundation for future VM automation. The workflow would look something like this Deploy a template with the RHEL 7.2 mounted and Power on Wait for deploy to finish (this might need to be a powershell loop with a sleep() call and a test to ...


1

The VMware vSphere documentation (https://pubs.vmware.com/vsphere-60/index.jsp#com.vmware.vsphere.monitoring.doc/GUID-FB4C372B-49AC-4A0F-8573-D8E23241570A.html), about CPU charts said: Amount of CPU actively used by the host, resource pool, or virtual machine in the cluster. ■ Counter: usagemhz ■ Stats Type: Rate ■ Unit: MegaHertz (MHz) So,...


0

I find the solution : First when I modify theses parameters it was still laggy but after a reboot and wait a few minutes all back to normal. First I installed VMware tools for Debian using this command : sudo apt-get install open-vm-tools Then I added 4 Gb of RAM (from 1Gb), keep one processor, set the OS to be Other (64 bits) (from Other (32 bits))


1

Instead of tinkering with the config file you should use the vim-cmd command (and its namespace hostsvc/autostartmanager) to configure VM autostart. Run vim-cmd help hostsvc/autostartmanager to get help. A good overview with examples is here: http://msmhec.pl/vmw/Documents/VIM-CMD.pdf (mentions ESXi 4.1, but still applies to recent ESXi versions)


0

$oneMonthAgo = (Get-Date).AddDays(-30) Get-VM | Foreach-Object { Get-Snapshot -VM $_ | Foreach-Object { if($_.Created -lt $oneMonthAgo) { Remove-Snapshot $_ -Confirm:$false }}} I guess the above script will do and yes add it to task scheduler which will still ease of the work. Recommend to delete the snapshots that are 3 days old.


2

Hot swapping components is a hardware feature, and has nothing to do with the software installed on the hardware. If your machines allow for cpu and ram hotswap then you should be able to do just that. But that's not really a heard of option of course.


5

Think about the question here: Hyperconverged solutions are focused on combining virtualization compute and storage resources together. These are still built atop commodity servers (Supermicro, Dell, HP, etc.), so the reasonable expectation is that you can hot-swap disks, but you likely would not be able hot-swap RAM. The point of these solutions is ...


0

Assuming you have DNS set up correctly for ESXi, wget could be incorrectly preferring the IPv6 address for packages.ubuntu.com: $ host releases.ubuntu.com releases.ubuntu.com has address 91.189.92.151 releases.ubuntu.com has IPv6 address 2001:7b8:3:37::21:3 Try forcing IPv4 mode: wget -4 http://releases.ubuntu.com/16.04/ubuntu-16.04-server-amd64.iso ...


2

I am not sure why you have not tried using PowerCLI, that would be the easiest and fastest way to do that. You can change the network adapter from connected to disconnected, change the network label (vLAN), or remove it all together. From all the times I have used this I have not come across any adverse effects on the VM's.



Top 50 recent answers are included