FS#28062 - [open-vmware-tools] won't start since module upgrade
Attached to Project:
Community Packages
Opened by Frank Ickstadt (frigg) - Monday, 23 January 2012, 08:30 GMT
Last edited by Sergej Pupykin (sergej) - Tuesday, 13 March 2012, 16:30 GMT
Opened by Frank Ickstadt (frigg) - Monday, 23 January 2012, 08:30 GMT
Last edited by Sergej Pupykin (sergej) - Tuesday, 13 March 2012, 16:30 GMT
|
Details
Description:
After upgrading from open-vm-tools-modules 2011.12.20-2 to open-vm-tools-modules 2011.12.20-3 open-vmware-tools won't start Additional info: 1) /var/log/kernel.log: vmblock: no symbol version for module_layout 2) a)rc.d start open-vm-tools --> [FAIL] b)/var/log/boot: Starting Open Virtual Machine Tools [BUSY] [FAIL] 3)uname -r 3.2.1-1-ARCH regards, Frank Steps to reproduce: |
This task depends upon
modprobe -f vmblock
but can be loaded with:
modprobe vmblock
Do you use kmod or module-init-tools?
As far as I'm concerned, I think that the problem only occurred after the removal of module-init-tools during my last pacman -Suy today (2012-01-24)...
Everything is working as expected on another (virtual) machine which was updated on 2012-01-20, just prior to the removal of module-init-tools:
upgraded open-vm-tools-modules (2011.12.20-1 -> 2011.12.20-3)
And of course, I have moved /etc/modprobe.d/modprobe.conf.pacsave back to /etc/modprobe.d/modprobe.conf as advised here:
http://www.archlinux.org/news/kmod-replaces-module-init-tools/
Hope this helps.
as I've performed a pacman -Syu kmod has replaced module-init-tools and there is no /etc/modprobe.d/modprobe.* file just a alsa.conf file ?!
[root@archie ~]# modprobe vmblock
ERROR: could not insert 'vmblock': Exec format error
[root@archie ~]# /etc/rc.d/open-vm-tools restart
:: Stopping Open Virtual Machine Tools [FAIL]
:: Starting Open Virtual Machine Tools [BUSY] ERROR: could not insert 'vmblock': Exec format error
https://bugs.archlinux.org/task/28222
https://bugs.archlinux.org/task/28062
https://bugs.archlinux.org/task/28109