Bug 5483

Summary: Installing VMware-tools not finnish when trying to create an image
Product: Mageia Reporter: Jan Pihlgren <jan>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED FIXED QA Contact:
Severity: minor    
Priority: Normal CC: marja11, tmb
Version: CauldronKeywords: NEEDINFO
Target Milestone: ---   
Hardware: i586   
OS: Linux   
Whiteboard:
Source RPM: VMwareTools-8.8.2-590212.tar.gz CVE:
Status comment:

Description Jan Pihlgren 2012-04-19 06:28:06 CEST
Description of problem:
VMware® Workstation
8.0.2 build-591240

Host OS version: 2.6.38.8-desktop-10.mga
Guest OS version: Mageia 2 Beta 3

The lates info writed in the konsol when installing vmware-tools-distrib:

Disabling timer-based audio scheduling in pulseaudio.



Detected X server version 1.11.4



Distribution provided drivers for Xorg X server are used.

Skipping X configuration because X drivers are not included.

Creating a new initrd boot image for the kernel.

The program will never finish. I have to interupt it with ctrl-C.



How reproducible:
Install VMware-tools at Mageia 2 Beta 3


Steps to Reproduce:
1. Install Mageia 2 Beta 3 in VMware Workstation 8.0.2
2. Copy VMwareTools-8.8.2-590212.tar.gz to directory /home/xx/download
3. Unpack the file with Ark
4. In a konsolwindow as root run  vmware-install.pl

Disclaimer:
I'm not sure if this is an error related to Mageia or VMware but the same procedure will work at Windows 7 an other OS.
Comment 1 Manuel Hiebel 2012-04-19 09:02:54 CEST
First, we don't support wmware, second I don't see where is the issue in fact, does wmware build the initrd from outside ? in that case does is support dracut ? (replacement mkintrd)
Manuel Hiebel 2012-04-19 09:03:22 CEST

Keywords: (none) => NEEDINFO

Comment 2 Jan Pihlgren 2012-04-19 09:52:00 CEST
I understand that you don't support vmware.
But isn't you responsible for the possibility to use such software?
Or do I have to report to VMware that Mageia does not accept VMware?

I don't know if vmware-tools support dracut.
For me it looks like that dracut isn't ready for use if other software not yet support it.

But as I say this is a minor problem.
Comment 3 Thomas Backlund 2012-04-20 11:10:30 CEST
(In reply to comment #2)
> I understand that you don't support vmware.
> But isn't you responsible for the possibility to use such software?

Nope.
We do try to help out with obvious problems, but we wont "bend over backwards" to get it to work...

We do promote open source after all...

> Or do I have to report to VMware that Mageia does not accept VMware?

It's not about accepting, 
But it's VMwares work to make sure their stuff works with
open source solutions, not the other way around...

> 
> I don't know if vmware-tools support dracut.
> For me it looks like that dracut isn't ready for use if other software not yet
> support it.

dracut is ready for use, and it replaces mkinitrd just fine. but we cant "wait forever" for companies to get their proprietary stuff to work with open source, as that would keep delaying progress 5-10-15 years or so (wich means stone age in IT industry...)

Now, if this is a dracut problem, it's not just Mageia that will have the problem as other distros have switched (or about to) to dracut too

> 
> But as I say this is a minor problem.

You need to figure out what makes it hang...
check the logs, run it under strace, check the documentation, ask upstream, ...

If it can be fixed without breaking other stuff, we will try to help out...

(and btw, we also still provide plain old mkinitrd for those that need it, but that is only when used with sysvinit-legacy. for systemd usage you need dracut)

CC: (none) => tmb

Comment 4 Jan Pihlgren 2012-04-20 13:07:48 CEST
OK.
I accept what you say.
I hope VMware will include dracut update in the future.
Good luke.
Regards
Comment 5 Marja Van Waes 2012-05-06 17:36:11 CEST
Thanks, Jan.

Closing as wontfix for now.

Feel free to reopen with additional information, because of what Thomas said in comment 3

> If it can be fixed without breaking other stuff, we will try to help out...

Status: NEW => RESOLVED
CC: (none) => marja11
Resolution: (none) => WONTFIX

Comment 6 Jan Pihlgren 2012-05-15 08:27:38 CEST
Problem solved
With VMware Workstation 8.0.3 the problem where solved.
Comment 7 Thomas Backlund 2012-05-15 12:22:32 CEST
Oh, Thats good to hear. Thanks for informing us.

Resolution: WONTFIX => FIXED