Set console window screen resolution a general system error occurred invalid fault

Содержание

Cannot Reboot VM from Vsphere
Popular Topics in VMware
4 Replies
Read these next.
poor wifi, school’s third floor
Need help crafting a job posting for an IT Pro
Snap! — AI Eye Contact, Mine Batteries, Headset-free Metaverse, D&D Betrayal
Spark! Pro series – 13th January 2023
General system error occurred invalid fault
General system error occurred invalid fault
General system error occurred invalid fault
Как решается ошибка a general system error occurred

Cannot Reboot VM from Vsphere

We have a DC, that’s not responding to our login, either from RDC or from the Console via vsphere. The VM is running Wi9n Server 2012 as DC

I cannot reboot the VM also, its giving the following error:

Cannot reboot the guest OS for XXXXDC1 on XXX.XXX.XXX.XXX in XXXXXXX. A general system error occurred: Invalid fault

Had googled it but no results, for my specific error.

Should I shut-down the VM or reset?

I dont have a image of this VM either.

local_offer Tagged Items
vmware

Read these next.

poor wifi, school’s third floor

I work as a help desk technician at a high school for a school district. Teachers/students on the building’s third floor have been reporting poor wifi, with their Chromebooks/laptops etc experiencing slow connectivity and random disconnections. We hav.

Need help crafting a job posting for an IT Pro

I’d really appreciate some thoughts and advice. I’m looking to hire an IT pro to be our resident go-to for all things IT (device support, SQL Server, network admin, etc) but who also is interested in learning — or even has some experience in — the.

Snap! — AI Eye Contact, Mine Batteries, Headset-free Metaverse, D&D Betrayal

Your daily dose of tech news, in brief. Welcome to the Snap! Flashback: January 13, 1874: Adding Machine Patented (Read more HERE.) Bonus Flashback: January 13, 1990: Astronauts awakened to the song Attack of the Killer Tomatoes (Read mor.

Spark! Pro series – 13th January 2023

Happy Friday the 13th! This day has a reputation for being unlucky, but I hope that you’ll be able to turn that around and have a great day full of good luck and good fortune. Whether you’re superstitious or not, .

Источник

General system error occurred invalid fault

Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Report Inappropriate Content

I suddenly seem to have issues with my DRS cluster. One of my host is in red state and gives me the following error:

Unable to apply drs settings on host: a general system error occured:invalid fault.

It seem to have started when I added some VMs to a resource pool. There are no limitations on RP and

the load on server appears to be low

Removing the VMs does not make a difference. Makes me think it might be unrelated. Any ideas?

Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Report Inappropriate Content

I think I found the problem. My first host is connected to two LUNs on my SAN.

The second one is only connected to one LUN and the VM files were sitting on a LUN that was not accessible by second host.

I must have forgot to move it in correct location. Doh

Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Report Inappropriate Content

I got the same error after upgrading my esx server 3.5U4, please use the command below to resolve the issue:

1. Disconnect your host from the cluster and create an SSH session to that host

2. use su — to become root

rpm -qa | egrep -i ‘(vpx|lgto|aam)’; ls /tmp/vmware-root

rpm -e `rpm -qa | egrep -i ‘(vpx|lgto|aam)’`; rm -rf /etc/vmware/hostd/pools.xml; rm -rf /etc/vmware/license.cfg; userdel vpxuser;service mgmt-vmware restart

tail -f /var/log/vmware/hostd.log | grep BEGIN

Wait for the BEGIN to show up on your console

Reconnect the host to the cluster.

Thanks — Please consider giving points, if you think this post was helpful.

Источник

General system error occurred invalid fault

I am attempting to migrate VMs from an older VMWare environment, using an ESXi 5.5 host (build 1331820), using the vcenter converter standalone utility (version 5.5.3), to a new ESXi 5.5 U2 (build 2068190). The new environment has a vCenter 5.5 server running on it, and the new ESXi 5.5U2 server has been registered with it.

The data store sizes are exactly the same on the old and new ESXi servers, just using separate SANs (the new environment is meant to be a 100% clean restart for this environment).

However, when I attempt to migrate a VM (version from the old environment to the new environment, and convert it to hardware version 10, I get an «Invalid fault» error from the standalone converter.

The only line I can find in the error log before the ‘invalid fault’ entry is:

2015-04-14T15:36:01.267-07:00 [08268 info ‘wizardController’] FillPage()

2015-04-14T15:36:11.637-07:00 [00400 error ‘wizardController’] Unable to submit job: vmodl.fault.SystemError

2015-04-14T15:36:11.637-07:00 [10620 error ‘ConversionState’] Submit job failed: A general system error occurred: Invalid fault

2015-04-14T15:36:11.637-07:00 [10620 error ‘ConverterWizardWindow’] Next/Finish failed: A general system error occurred: Invalid fault

2015-04-14T15:36:18.559-07:00 [09980 verbose ‘HttpConnectionPool-000008’] [RemoveConnection] Connection removed; cnx: , >)>; pooled: 0

I’m stumped as to what else I should be looking at, in regards to migrating and convering VMs from my old environment to the new environment.

Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Report Inappropriate Content

So the issue was with the vCenter server (the Linux appliance version, which is a little disconcerning) not being in a ‘ready state’ to allow for migrations.

I restarted the vCenter server and everything started working as expected, immediately.

Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Report Inappropriate Content

Your VM have any GPT disk ?

Anyway, if this VM are running from a SAN, why not just present the datastore storing this VM, remove the VM from the old host, register on the new host, and migrate the VM using Storage vMotion to the new datastore on the new SAN and then upgrade the VMware Tools and the Hardware Version.

Richardson Porto
Senior Infrastructure Specialist
LinkedIn: http://linkedin.com/in/richardsonporto

Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Report Inappropriate Content

I was hoping to have avoided going through all the trouble of setting up the old ESXi environment and doing vMotion, by using the stand alone converter. It’s only 8-10 VMs that I’m dealing with.

None of the VMs are GPT partitioned. They are all Windows 2008 R2 server and Windows 7 hosts. I’m suspect as to why this isn’t working, since I was able to do the ‘exact’ same type of migration at another location between an older ESXi server, and a new ESXi 5.5U2 server, without incident.

Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Report Inappropriate Content

Could you upload log bundle?

Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Report Inappropriate Content

Is there a way for me to PM to you, so that I don’t potentially expose any of our internal details?

Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Report Inappropriate Content

The target ESXi host is registered with a vCenter server (running as a virtual machine on the target host). Does the target ESXi host need to be disconnected from vCenter in order to use the standalone converter?

Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Report Inappropriate Content

Yes, send me the logs as PM.

Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Report Inappropriate Content

No, this is not needed, moreover after VC version 5.x (not sure exactly) if the ESX host is managed from the VC you can’t add a VM to the ESX directly but from the VC only.

Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Report Inappropriate Content

I installed the converter on a 100% clean Windows 8 workstation and attempted to run the migration and received the exact same ‘Invalid Fault error’. However, this time I noticed the following lines in the converter-worker log:

2015-04-17T11:55:08.779-07:00 [04088 info ‘Default’] TargetVmManagerImpl::CreateVM: Creating the target VM.

2015-04-17T11:55:08.779-07:00 [04088 info ‘Default’] Reusing existing VIM connection to vcenter1-sj1.quantumscape.com

2015-04-17T11:55:08.779-07:00 [04088 info ‘Default’] ComputeResource for vim.HostSystem:host-43 is vim.ComputeResource:domain-s41

2015-04-17T11:55:08.779-07:00 [04088 info ‘Default’] ResourcePool for vim.ComputeResource:domain-s41 is vim.ResourcePool:resgroup-42

2015-04-17T11:55:08.779-07:00 [04088 info ‘Default’] Creating VM OpsCenter-sj1 in folder vim.Folder:group-v22 on host vim.HostSystem:host-43 and resource pool vim.ResourcePool:resgroup-42 (isVirtualApp = false).

2015-04-17T11:55:11.248-07:00 [04088 error ‘Default’] CreateVm task failed: The operation is not allowed in the current state.

2015-04-17T11:55:11.248-07:00 [04088 error ‘Default’] TargetVmManagerImpl::CreateVM: Vm creation failed with fault vim.fault.InvalidState

2015-04-17T11:55:11.248-07:00 [04088 info ‘Default’] Scheduled timer canceled, StopKeepAlive succeeds

2015-04-17T11:55:11.263-07:00 [04088 info ‘vmomi.soapStub[14]’] Resetting stub adapter for server : Closed

2015-04-17T11:55:11.263-07:00 [04088 error ‘Ufa’] Method converter.worker.ConverterWorker.createVM threw undeclared fault of type vim.fault.InvalidState

2015-04-17T11:56:02.627-07:00 [05272 info ‘Default’] [Converter.Worker.DiagnosticManagerImpl] Generating LogBundle.

So it almost looks like the converter isn’t able to create the new VM on the target ESXi host, but I’m not sure why. This is a brand new target host with nothing running on it except a clean build of ESXi 5.5U2, and a single VM running the latest version of vCenter 5.5. I’ve created a new LUN from my storage and mounted it to the iSCSi storage adapter for the target VM that I want to migrate and everything there looks like it’s prepped.

Источник

General system error occurred invalid fault

Вот как выглядит ошибка A general system error occurred-Authorize Exception в VMware vCenter, небольшое окно с предупреждением и сделать ничего нельзя, кроме как нажать ок.

Немного погугли смысл сводился к тому что служба SSO не может подцепиться к LDAP. Если кто не помнит, то SSO (Single Sign-On) мы устанавливали вместе с VMware VirtualCenter Server, в двух словах это некая база единой аутентификации, которую можно использовать во многих сервисах. Так у меня домен Active Directory, то логично, что мне было удобно раздавать права на объекты VMware VirtualCenter Server, через AD учетки.

Посмотрев еще логи в Windows, обнаружилось вот такое сообщение, что не получается соединиться с контроллером домена, Event ID 1000.

A general system error occurred-Authorize Exception в VMware vCenter 5.1-02

Как решается ошибка a general system error occurred

Заходим на vSphere Web Client https://hostname:9443, вы его так же ставили при установке VMware VirtualCenter Server.

Пытаемся ввести наши данные доменные, и конечно же он нас посылает)))

A general system error occurred-Authorize Exception в VMware vCenter 5.1-03

Но при установке мы заводили пользователя admin@system-domain и его пароль, помогут для входа, еще в качестве логина может подойти administrator@ vsphere.local

Идем в Administration > Configuration > identity Sources. Выбираем активное подключение к домену.

A general system error occurred-Authorize Exception в VMware vCenter 5.1-04

Смотрим что есть, в моем случае один криворукий админ поигрался с контроллером, поэтому старый коннект я удалил и сделал так

A general system error occurred-Authorize Exception в VMware vCenter 5.1-05

Так же можно выбрать от имени кого проверять требуется в некоторых случаях, и есть возможность с сертификатом сделать. Как более простой вариант можно использовать Integrated Windows Authentication, она позволяет подключиться к AD от имени учетной записи компьютера (он должен быть членом домена)

После чего нажмите кнопку использовать по умолчанию данное подключение. Вот так вот просто решается ошибка а general system error occurred: Authorize Exception в VMware vCenter 5.X.

Источник

Solving the «A general system error occured:Invalid fault» error in vSphere 4

Below error was come out when you try to migrate VM to other host for some reason.

Below error was come out when you try to edit VM setting.

Below error was come out when you power on the VM.

How to solve those error?

Here is how I resolve the error!

Enter below command and press enter.
services.sh restart

Wait until all VMware Services are restarted.

After that try to Power On/Edit Settings or Migrate the errored VM and you will see all you can do without any error pop-up.

This kind of errors can occur if you shutdown/restart VM unproperly or shutdown/restart the Host unproperly that VM exist.

You can check log file deeply if you willing to know precisely on this.

May you all be happy.
(Be knowledgeable, pass it on then)

Comments

I am running Ubuntu 18.10 as a guest using VMWare 15 player on a Windows 10 host.

I go through the install process for Ubuntu, restart, and everything looks fine. I restart the VM again and the screen wont resize, it is stuck at its default. Resizing the VM window doesn’t have any affect.

running «ps aux | grep vmtoolsd» I get the following:

root        385  0.4  0.0 142756 10844 ?        Ssl  11:19   0:00 /usr/bin/vmtoolsd
corrin     1859  0.3  0.2 391940 36704 tty2     Sl+  11:19   0:00 /usr/bin/vmtoolsd -n vmusr --blockFd 3
corrin     2278  0.0  0.0  17480   956 pts/0    S+   11:20   0:00 grep --color=auto vmtoolsd

Copy and paste between host and guest works fine.

If I execute «systemctl restart open-vm-tools.service» automatic resizing to the VM window works again.

I’ve also the same problem.
I’ve updated system from 18.04 to 18.10 and got that problem, which resolved every boot by:

systemctl restart open-vm-tools.service

ps aux | grep vmtoolsd:

root        418  0.1  0.0  60612 10860 ?        Ss   17:32   0:00 /usr/bin/vmtoolsd
test       1709  0.3  0.3 382016 35976 ?        Sl   17:33   0:00 /usr/bin/vmtoolsd -n vmusr --blockFd 3
test       1999  0.0  0.0   8864   824 pts/0    S+   17:34   0:00 grep --color=auto vmtoolsd

lin2code, MohamedFaroukAbdelazeem, duecorda, jwhayman, dinbtechit, aparolin, Mincka, K-Cardoso, Rmanaf, skatsumata, and 14 more reacted with thumbs up emoji

I too have the same problem with Xubuntu 18.10, whether upgraded from 18.04 or clean installed. Restarting the open-vm-tools.service will get it working until rebooted.

Not sure if it matters but it is the same for both Wayland and Xorg for me. The issue is present right from the beginning with the login screen.

This might be a dup of issue #253. Can you please try adding this line in the Unit section of open-vm-tools?

After=graphical.target

That seems to fix it for me. Thank you.

Yes, that’s works! Thanks!

➜ ~ systemctl restart open-vm-tools.service
Failed to restart open-vm-tools.service: Unit open-vm-tools.service not found.

why

@king-gu
try to reinstall open-vm-tools

I am a beginner, can attach code

@king-gu
try to reinstall open-vm-tools

Thank you very much for the

sudo apt purge open-vm-tools
sudo apt update
sudo apt install open-vm-tools open-vm-tools-desktop

shaynethiessen, c5creative, angudu, RoiEXLab, navkore, JorgeLAB, inbareyal, borisdaeppen, stardev-123, hsugabrahmam, and 4 more reacted with thumbs up emoji

sudo apt purge open-vm-tools
sudo apt update
sudo apt install open-vm-tools open-vm-tools-desktop

错误：未找到目标：open-vm-tools-desktop

why

Most of the Linux distributions ship two open-vm-tools packages, «open-vm-tools» and «open-vm-tools-desktop». «open-vm-tools» is the core package without any dependencies on X libraries and «open-vm-tools-desktop» is an additional package with dependencies on «open-vm-tools» core package and X libraries.

If your VM is using a desktop environment, you need the open-vm-tools-desktop to enable resizing.

sudo apt purge open-vm-tools
sudo apt update
sudo apt install open-vm-tools open-vm-tools-desktop

错误：未找到目标：open-vm-tools-desktop

why

@king-gu because you didn’t install open-vm-tools, try only:

sudo apt install open-vm-tools open-vm-tools-desktop

marcocucinato, ktakkun, dinbtechit, darren-etheridge, jontybrook, asfarley, gshockxia, SvenAelterman, bufferbandit, lainisourgod, and 7 more reacted with thumbs up emoji
bufferbandit, robellegate, RoiEXLab, and crfrolik reacted with hooray emoji

Restarting the service and editing it haven’t resolved this issue for me.

ps aux | grep vmtoolsd:

shuri      1496  0.1  1.7 390808 35992 tty2     Sl+  11:13   0:02 /usr/bin/vmtoolsd -n vmusr --blockFd 3
root       4437  0.0  0.5  69264 11088 ?        Ss   11:22   0:01 /usr/bin/vmtoolsd
shuri      8601  0.0  0.0  17480   956 pts/0    S+   11:46   0:00 grep --color=auto vmtoolsd

This might be a dup of issue #253. Can you please try adding this line in the Unit section of open-vm-tools?

After=graphical.target

Here is how to fix it…

Edit:
/etc/systemd/system/multi-user.target.wants/open-vm-tools.service

Add the following to the end of the «Unit» section:

Requires=graphical.target
After=graphical.target

Reboot.

Thanks to Robert G @ askubuntu, and for your reference:
https://askubuntu.com/questions/1085621/vmware-workstation-ubuntu-18-10-full-screen-problem

Both don’t work here, so I’ll have to stick to restarting the service. Any other ideas?

I managed to work around the issue by installing only open-vm-tools-desktop. Most of the times it works, and when it doesn’t, I restart the service and it’s good to go. Worth mentioning that it happens only in Ubuntu but not on Kubuntu, at least so far in my testing.

Here is how to fix it…

Edit:
/etc/systemd/system/multi-user.target.wants/open-vm-tools.service

Add the following to the end of the «Unit» section:

Requires=graphical.target
After=graphical.target

Reboot.

Thanks to Robert G @ askubuntu, and for your reference:
https://askubuntu.com/questions/1085621/vmware-workstation-ubuntu-18-10-full-screen-problem

This worked for me.

I am running a 1440p monitor, so it makes sense that this is somehow related to HiDPI on the host machine. Surely something VMWare can fix.

Delaying the service open-vm-tools to start after the display manager and it seems to work.

~$ sudo vi /lib/systemd/system/open-vm-tools.service

Add under [Unit] the following line:

After=display-manager.service

Reference https://communities.vmware.com/thread/576221

Save the file and reboot. The screen should be able to fit as needed.

I have a similar problem with a Windows guest running inside an Ubuntu 18 host using VMWare 15

this worked for me also FYI

Backup the original file, of course
cp /etc/systemd/system/multi-user.target.wants/open-vm-tools.service /etc/systemd/system/multi-user.target.wants/open-vm-tools.service.ORIGINAL

Edit the config file below
vi /etc/systemd/system/multi-user.target.wants/open-vm-tools.service

Under the [Unit] section of the file, add in the following two lines:
Requires=graphical.target After=graphical.target

It should look similar to this once complete:

reload the systemctl daemon
systemctl daemon-reload

After reading https://communities.vmware.com/thread/576221 the solution indicated on post nr 5 had worked perfectly for me. I have added also the indicated Requires line like described above.

I have done a backup like 905jay indicated:
cp /etc/systemd/system/multi-user.target.wants/open-vm-tools.service /etc/systemd/system/multi-user.target.wants/open-vm-tools.service.ORIGINAL

I have edited the file:
sudo vim /etc/systemd/system/multi-user.target.wants/open-vm-tools.service

I have added under the [Unit] section this 2 lines:
Requires=graphical.target
After=display-manager.service

After that I have done
sudo systemctl daemon-reload

Everything is working now as expected.

This is no longer working with 18.04, 18.10 or 19.04. By added the lines to the config file you can stretch the screen a bit, but still too small when it maxes out. Restarting the daemon doesn’t change it

Not working on 18.04, with all edits suggested in this thread so far

Just to throw this out there —
Before the updates in late June or early July to 18.04, I never had to set a screen resolution in the host. From day one of install, through many months of use, I opened the host in VMRC and stretched the window to any size at all and it normally kept that size the next time I opened it. I frequently resized it depending on what I was doing on my computer screens.
After this happened I even looked at setting the screen resolution, but that doesn’t seem to be available either. I can’t set it to anything over 1176×885. I’ve tried adding modes with xrandr and that does nothing. I’ve set the Host settings to use Host Screen Settings or to 1 monitor and still nothing. Not sure if this is really a vmtools issue or an Ubuntu issue, but it’s screwed from then through 18.10 through 19.04.

I may do a fresh install of 19.04 just to see if anything changes.

UPDATE: Installed fresh 19.04 VM. Soon as I logged in I was able to resize normally and it shows the currently sized screen properly in the display resolution. open-vm-tools and open-vm-tools desktop were already installed by default, indicated properly on vcenter, and identical to versions on the original host that won’t resize past 1176×885. Only thing I had to do was blacklist the piix4-smbus module to eliminate the smbus error on boot. No idea what’s different between the 2 systems that it won’t allow resizing

One thing I forgot to check was my VM video settings were set incorrectly, and I had way too little VRAM allocated. Once I changed these settings, I was able to resize properly.

What are your display settings configured as in VMWare?

systemctl restart open-vm-tools.service

Yup. If using vmware-tools, do

systemctl restart vmware-tools.service

Yup. If using vmware-tools, do
systemctl restart vmware-tools.service

«Failed to restart vmware-tools.service: Unit vmware-tools.service not found.»

and on the VCenter logs I see «A general system error has occurred: Invalid Fault»

I’ve already tried uninstalling and reinstalling vmware-tools as well.

@unicav I can confirm same error as yours, on ESX VCenter…

I have uninstalled openvm tools, and installed VmWare ones, same thing…

And I am on 18.04.2

Got this issue when my kernel upgraded to 5.0.0. Rolling back to 4.19.0 fixed my problem.

How i fixed my issue:

Reinstall tools by @titan99855 guide in my VM.
Apply @ManuelBerrueta config fix.
Repair your VMware Workstation/Player (Programs -> VMware -> Change -> Setup Wizard -> Repair)
Create new Virtual Machine with the same system configuration
Do not create new disk, use existing disk from your broken VM.
Boot from new VM.

Full screen mode is working now. Even after reboot new VM.

So basically there’s no fixing an existing install at this point you just
have to create a new VM.
I knew the current packages work fine with a new install because I already
did a new install of 18.04 then upgraded it to 18.10 and then 19.04
On a fresh install of 19.04 you don’t even have to install vmtools it
installed automatically and works fine immediately.
I’m done fooling with the broken 18.04 system at this point. Kept it around
to test possible fixes for the community but I don’t think there’s a point
now.

…

On Fri, Sep 20, 2019 at 5:35 AM Андрей ***@***.***> wrote:
How i fixed my issue:

1. Reinstall tools by @titan99855 <https://github.com/titan99855>
guide in my VM.
2. Apply @ManuelBerrueta <https://github.com/ManuelBerrueta> config
fix.
3. Repair your VMware Workstation/Player (Programs -> VMware -> Change
-> Setup Wizard -> Repair)
4. Create new Virtual Machine with the same system configuration
5. Do not create new disk, use existing disk from your broken VM.
6. Boot from new VM.

Full screen mode is working now. Even after reboot new VM.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#303?email_source=notifications&email_token=AMVZ7QA2TVYV47H3VPFNDKTQKSRO7A5CNFSM4GARJZKKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7GJNOQ#issuecomment-533501626>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AMVZ7QDEXOAINMYTS74P2LTQKSRO7ANCNFSM4GARJZKA>
.

I just encountered the same issue, it went away by restarting the service one time manually and rebooting the VM.

Edit the systemd unit file directly will not survive an update of open-vm-tools package (if any). Instead, use the recommanded way provided by systemd to create an override configuration file.

The all-in-one solution, tested on a newly installed Lubuntu 18.04.

sudo apt install open-vm-tools open-vm-tools-desktop
sudo systemctl edit open-vm-tools.service  # will popup an editor window

Fill the following content into the editor window.

[Unit]
Requires=graphical.target
After=graphical.target

Reboot VM and everything works.

That’s works! Thanks!

sudo apt purge open-vm-tools
sudo apt update
sudo apt install open-vm-tools open-vm-tools-desktop

None of the above work with Ubuntu 20.

After a clean install on 18.10 this issue went away. I recently upgraded to 20.04 with no issues either

Now it works for me too! But only after I pasted the logging/debugging version of the config file https://kb.vmware.com/s/article/1007873 and rebooted. I immediately noticed the ballooning was active (host memory usage much lower). And everything else that I tried (video res changes, copy-pasta) works too but there are some weird errors logged:

[2020-06-16T22:37:43.996Z] [ message] [vix] ToolsDaemonTcloReceiveVixCommand: command 62, additionalError = 17

And everything else that I tried (video res changes, copy-pasta) works too but there are some weird errors logged:
[2020-06-16T22:37:43.996Z] [ message] [vix] ToolsDaemonTcloReceiveVixCommand: command 62, additionalError = 17

Don’t worry about that; its showing a successful operation where something (probably the WS UI) is just checking the state of Tools.

I was struggling with this on 18.04 and 20.04 running on ESXi. When I was reinstalling after messing with everything on this page, I selected to install third-party software during install and now it works perfectly right out the box. Hope this helps someone!

I encountered something similar with Ubuntu Desktop 20.04 and VMware vSphere 6.7. Just increasing the available video memory from 4MiB to 16MiB did the trick. It does not kick in immediately after boot. A cycle of enter-exit fullscreen is needed.

sudo apt install open-vm-tools open-vm-tools-desktop

this is fixed!!! thanks

Источник

Posted by Wrathyimp 2015-04-27T08:09:39Z

Hi,

We have a DC, that’s not responding to our login, either from RDC or from the Console via vsphere. The VM is running Wi9n Server 2012 as DC

I cannot reboot the VM also, its giving the following error:

Cannot reboot the guest OS for XXXXDC1 on XXX.XXX.XXX.XXX in XXXXXXX. A general system error occurred: Invalid fault

Had googled it but no results, for my specific error.

Should I shut-down the VM or reset?

I dont have a image of this VM either.

4 Replies

LWBM

This person is a verified professional.

Verify your account
to enable IT peers to see that you are a professional.

datil
Try a veeam back up — free edition (not tried on a running system, could be worth a shot)
BASH
```
shutdown.exe -r -t 5 -m //SERVER/ 
```
Install/update VMWare tools (may not work at all, sounds like things are hooked up)

Are you able to \c$ to it at all?

If you’re forced to, do a poweroff. Disk Check after.

Was this post helpful?
thumb_up
thumb_down
pure capsaicin

VMware Expert
- check
  361
  Best Answers
- thumb_up
  999
  Helpful Votes
reset or shutdown will both work, reset it like pressing the reset button on a physical machine and shutdown the same but with the power button held in the hard reboot.

Both should work

Was this post helpful?
thumb_up
thumb_down
open console to the VM -> Ctrl-T — this is the «reset button»

Was this post helpful?
thumb_up
thumb_down
Thanks for your comments, but had to shutdown the VM, and then start it again.

Was this post helpful?
thumb_up
thumb_down

Read these next…

Can’t communicate with scanner

Hardware

Hello everyone,I have a client that uses Kodak ScanMate i940 scanners at their desks. They recently got a new computer that we prepped and put on their domain. This new computer is recognizing the scanner but it is unusable with the error «can’t communica…
Different MAC address, same computer name — multiple DHCP leases

Windows

I’m noticing a lot more now that our Wifi DHCP scopes are filled by the same computer name, but with different mac addresses. I know there’s a feature in Windows 10 called Random hardware addresses, but that setting is off. Is there anything else that cou…
Snap! — No-Password Logins, Solar Powered Water Filter, Glitch in the Matrix?

Spiceworks Originals

Your daily dose of tech news, in brief.

Welcome to the Snap!

Flashback: February 9, 1996: Introduction of the Bandai Pippin (Read more HERE.)

Bonus Flashback: February 9, 1990: Galileo Probe does a Venus Flyby (Read more HERE.)

You nee…
Roku TV being used as Wallboard Issues

Hardware

Helping someone out at their shop. They have 4 large Roku screens and 2 laptops with dual HDMI ports for video. They are viewing static website business dashboards and PowerPoint. At first all 4 screens connected to wireless, worked for a while but with a…
Charging for SSO

Security

We have SSO set up with around 5 or 6 solution providers via our M365. Not one of them charges for this, they just sent us the documentation.I identified another online service in use by one of our departments which would benefit from using SSO for staff …