Смоленск 1.6 Автозапуск vmware-tools
У меня что-то похожее было при запуске совсем другого сервиса (да и в совсем другом дистрибутиве, но это не имеет значения здесь) . предполагаю: запуск каких-то из сервисов *.wants, см. в /etc/systemd/system, требует старта вашего сервиса раньше, чем уже запущены требуемые ему сервисы . или что-то в этом роде.
Это вопросы конфигурирования systemd.
Куда можно копать?
Читать детальное описание systemd здесь: systemd для администраторов :
oko
New member
to Fafhard
Логи! /var/log/syslog и /var/log/messages — очистить (так проще всего), ребутнуть машину, читать, искать упоминание сервиса vmware-tools и, если результат неясен, выкладывать на форум.
И да, конфиг сервиса тоже было бы неплохо приложить.
Кстати, зачем вам VMWare tools в Astra Linux SE по умолчанию? В боевой эксплуатации иметь гипервизор под ESXi и гостевую ОС под Astra — то еще извращение.
Fafhard
New member
Логи! /var/log/syslog и /var/log/messages — очистить (так проще всего), ребутнуть машину, читать, искать упоминание сервиса vmware-tools и, если результат неясен, выкладывать на форум.
dministrator@astra-test:~$ sudo cat /var/log/syslog | grep vmw Aug 30 12:45:54 astra-test kernel: [ 0.000000] vmware: TSC freq read from hypervisor : 2933.437 MHz Aug 30 12:45:54 astra-test kernel: [ 0.000000] vmware: Host bus clock speed read from hypervisor : 66000000 Hz Aug 30 12:45:54 astra-test kernel: [ 0.000000] vmware: using sched offset of 6289807282329108 ns Aug 30 12:45:54 astra-test kernel: [ 5.301697] vmw_vmci 0000:00:07.7: Found VMCI PCI device at 0x11080, irq 16 Aug 30 12:45:54 astra-test kernel: [ 5.301779] vmw_vmci 0000:00:07.7: Using capabilities 0xc Aug 30 12:45:54 astra-test kernel: [ 5.625182] [drm] Initialized vmwgfx 2.14.0 20170612 for 0000:00:0f.0 on minor 0 administrator@astra-test:~$ sudo cat /var/log/messages | grep vmw Aug 30 12:45:54 astra-test kernel: [ 0.000000] vmware: TSC freq read from hypervisor : 2933.437 MHz Aug 30 12:45:54 astra-test kernel: [ 0.000000] vmware: Host bus clock speed read from hypervisor : 66000000 Hz Aug 30 12:45:54 astra-test kernel: [ 0.000000] vmware: using sched offset of 6289807282329108 ns Aug 30 12:45:54 astra-test kernel: [ 5.301697] vmw_vmci 0000:00:07.7: Found VMCI PCI device at 0x11080, irq 16 Aug 30 12:45:54 astra-test kernel: [ 5.301779] vmw_vmci 0000:00:07.7: Using capabilities 0xc Aug 30 12:45:54 astra-test kernel: [ 5.625182] [drm] Initialized vmwgfx 2.14.0 20170612 for 0000:00:0f.0 on minor 0Сервис при этом так и не запущен. Я так понимаю проблема где-то в systemd, за ссылку спасибо.
Когда я добавляю сервис в автозапуск, то у меня создается Unit-файл в /etc/systemd/system, например:
administrator@astra-test:~$ sudo systemctl enable ssh Synchronizing state of ssh.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install enable ssh Created symlink /etc/systemd/system/sshd.service → /lib/systemd/system/ssh.service.Когда же я пытаюсь добавить vmware-tools, то systemd-sysv-install запускается, но, видимо, ничего не делает:
administrator@astra-test:~$ sudo systemctl enable vmware-tools vmware-tools.service is not a native service, redirecting to systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install enable vmware-toolsadministrator@astra-test:~$ systemctl list-unit-files | grep ssh.service ssh.service enabled administrator@astra-test:~$ systemctl list-unit-files | grep vmware-tools.service vmware-tools.service generatedadministrator@astra-test:~$ systemctl is-enabled vmware-tools vmware-tools.service is not a native service, redirecting to systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install is-enabled vmware-tools enabled administrator@astra-test:~$ systemctl is-enabled sshd enabledКстати, зачем вам VMWare tools в Astra Linux SE по умолчанию? В боевой эксплуатации иметь гипервизор под ESXi и гостевую ОС под Astra — то еще извращение.
Это пока просто для тестирования. У нас в организации виртуализация только на ESXi и другие варианты не предвидятся.
VMware tools not running after Linux kernel upgrade
In this article, we will discuss solutions when VMware tools are not running after the Linux kernel upgrade.
Cause :
After kernel upgrade in the Guest VM Linux machine, you may see VMware tools are not running. This is because there are VMware tools modules that runs using kernel library files. After a kernel upgrade, they point to different library files than the one currently used by the kernel and hence failed to start.
Solution :
The issue can be resolved by reconfiguring VMware tools after the kernel upgrade. This process is on the fly and does not require downtime.
Login to Guest Linux operating system using root account and run reconfiguration script /usr/bin/vmware-config-tools.pl
You will be asked a few choices to make. If you know about those modules you choose your answers according to your requirement and just hit enter to accept defaults. See below sample output –
root@kerneltalks # /usr/bin/vmware-config-tools.pl Initializing. Making sure services for VMware Tools are stopped. Found a compatible pre-built module for vmci. Installing it. Found a compatible pre-built module for vsock. Installing it. The module vmxnet3 has already been installed on this system by another installer or package and will not be modified by this installer. The module pvscsi has already been installed on this system by another installer or package and will not be modified by this installer. The module vmmemctl has already been installed on this system by another installer or package and will not be modified by this installer. The VMware Host-Guest Filesystem allows for shared folders between the host OS and the guest OS in a Fusion or Workstation virtual environment. Do you wish to enable this feature? [no] Found a compatible pre-built module for vmxnet. Installing it. The vmblock enables dragging or copying files between host and guest in a Fusion or Workstation virtual environment. Do you wish to enable this feature? [no] VMware automatic kernel modules enables automatic building and installation of VMware kernel modules at boot that are not already present. This feature can be enabled/disabled by re-running vmware-config-tools.pl. Would you like to enable VMware automatic kernel modules? [no] Do you want to enable Guest Authentication (vgauth)? Enabling vgauth is needed if you want to enable Common Agent (caf). [yes] Do you want to enable Common Agent (caf)? [yes] No X install found. Creating a new initrd boot image for the kernel. NOTE: both /etc/vmware-tools/GuestProxyData/server/key.pem and /etc/vmware-tools/GuestProxyData/server/cert.pem already exist. They are not generated again. To regenerate them by force, use the "vmware-guestproxycerttool -g -f" command. vmware-tools start/running The configuration of VMware Tools 10.0.6 build-3560309 for Linux for this running kernel completed successfully. You must restart your X session before any mouse or graphics changes take effect. You can now run VMware Tools by invoking "/usr/bin/vmware-toolbox-cmd" from the command line. To enable advanced X features (e.g., guest resolution fit, drag and drop, and file and text copy/paste), you will need to do one (or more) of the following: 1. Manually start /usr/bin/vmware-user 2. Log out and log back into your desktop session; and, 3. Restart your X session. Enjoy, --the VMware team
If you are ok to accept the default and want the script to run non-interactive, run it with -d default switch.
root@kerneltalks # /usr/bin/vmware-config-tools.pl -d default
Once, the script finishes execution you can see in VMware console that it shows VMware tools are running on guest VM!
Vmware tools not starting linux
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- VMware Technology Network
- :
- Cloud & SDDC
- :
- ESXi
- :
- ESXi Discussions
- :
- VMWare Tools not starting in Ubuntu guest
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Sambo
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have an Ubuntu guest which I have just migrated to ESXi 5.1 from VMWare Server 2.0. I upgraded vmware tools on the guest which appeared to run fine without any errors, however, while the vSphere Client shows VMWare Tools as running and up to date, I can’t get vmware-user running after logging into the guest. When I try to run it from the command prompt I get the error:
vmware-user: could not open /proc/fs/vmblock/dev
the /proc/fs/vmblock folder does not exist on the system.
Any suggestions on how to fix this would be welcome!
ramkrishna1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Welcome to the communites.
Could you please update patch first through below command .
Sambo
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for your advice. I tried running the command, but I get the error:
«No module named cElementTree»
After some Googling I tried to install python-elementtree, however I apparently already have the latest version installed.
Any ideas? I apologise in advance for my lack of *nix experience. However, I am an IT professional so don’t feel you have to hand hold me too much
uggla
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I’m running Ubuntu server 12.04 64bit and have the same problem.
Sambo
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This issue is still unresolved and after quite a bit of Internet research it seems that there are quite a few people with this issue. I can’t believe that more people aren’t on here complaining about it!?
I did however, manage to find a workaround which was mentioned in a couple of places on the net; once you’ve started Ubuntu, log off and on again, then VMWare Tools starts automatically.
I also found this which shows some merit, however there is already a vmware-user.desktop file in the specified location; it is a shortcut to a file elsewhere.
I tried adding another file with the specified contents but it didn’t help unfortunately (in fact it broke the log out/in workaround!). Maybe someone with a little more *nix experience might have a bit more luck with this?
Edit: Hmm. after re-running ‘sudo vmware-config-tools.pl’ and answering ‘yes’ to the ‘Would you like to enable VMware automatic kernel modules?’ option, installing some Ubuntu updates, adding the above ‘fix’, rebooting and then removing it again, my VM now starts VMWare tools automatically on boot!? I’ve re-created this on another, identical VM, but I’m still unsure which actions re-produce the fix.
My suspicion is that it’s the vmware-config-tools.pl (possibly with the ‘enable VMware automatic kernel modules’ option enabled) that did it. I’m pretty sure that the updates were run during the reboot after I made the config change, so it’s hard to confirm whether this made any difference. However, during the re-creation on my 2nd VM, the updates by themselves made no difference; so either it’s a combination of both or the updates aren’t involved.
If anyone can confirm this I would be greatful!