Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 233782 - app-emulation/vmware-player 2.0.4.93057 failing to bring up interface
Summary: app-emulation/vmware-player 2.0.4.93057 failing to bring up interface
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo VMWare Bug Squashers [disabled]
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-03 10:32 UTC by Daniele C.
Modified: 2008-08-03 14:04 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniele C. 2008-08-03 10:32:08 UTC
1) I start vmware through '/etc/init.d/vmware start' and I get the following on screen
--------
 * Loading vmblock for drag and drop support ...                                                                       [ ok ]
 * Starting VMware services:                                                                                           [ ok ]
 *   Virtual machine monitor                                                                                           [ ok ]
 *   Virtual ethernet                                                                                                  [ ok ]
 *   Bridged networking on /dev/vmnet0                                                                                 [ ok ]
 *   Host-only networking on /dev/vmnet8                                                                               [ !! ]
 *   NAT service on /dev/vmnet8                                                                                        [ ok ]
--------

Although the [ !! ], I can see the vmnet8 device running 'ifconfig'.

I find these in dmesg:
----------
vmblock: module license 'unspecified' taints kernel.
vmmon: no version magic, tainting kernel.
/dev/vmmon[6614]: VMCI: Driver initialized.
/dev/vmmon[6614]: Module vmmon: registered with major=10 minor=165
/dev/vmmon[6614]: Initial HV check: anyNotCapable=1 anyUnlocked=0 anyEnabled=0 anyDisabled=0
/dev/vmmon[6614]: Module vmmon: initialized
parport_pc 00:08: reported by Plug and Play ACPI
parport0: PC-style at 0x378, irq 7 [PCSPP(,...)]
vmnet: no version magic, tainting kernel.
/dev/vmnet: open called by PID 6655 (vmnet-bridge)
/dev/vmnet: hub 0 does not exist, allocating memory.
/dev/vmnet: port on hub 0 successfully opened
bridge-eth1: enabling the bridge
bridge-eth1: up
bridge-eth1: already up
bridge-eth1: attached
/dev/vmnet: open called by PID 6694 (vmnet-netifup)
/dev/vmnet: hub 8 does not exist, allocating memory.
/dev/vmnet: port on hub 8 successfully opened
/dev/vmnet: open called by PID 6711 (vmnet-natd)
/dev/vmnet: port on hub 8 successfully opened
vmnet8: no IPv6 routers present
----------

After running /opt/vmware/player/bin/vmware-config.pl I get in dmesg these:

----------
/dev/vmmon[6847]: Module vmmon: unloaded
parport_pc 00:08: disabled
bridge-eth1: down
bridge-eth1: detached
vmmon: no version magic, tainting kernel.
/dev/vmmon[7033]: VMCI: Driver initialized.
/dev/vmmon[7033]: Module vmmon: registered with major=10 minor=165
/dev/vmmon[7033]: Initial HV check: anyNotCapable=1 anyUnlocked=0 anyEnabled=0 anyDisabled=0
/dev/vmmon[7033]: Module vmmon: initialized
parport_pc 00:08: activated
parport_pc 00:08: reported by Plug and Play ACPI
parport0: PC-style at 0x378, irq 7 [PCSPP(,...)]
vmnet: no version magic, tainting kernel.
/dev/vmnet: open called by PID 7066 (vmnet-bridge)
/dev/vmnet: hub 0 does not exist, allocating memory.
/dev/vmnet: port on hub 0 successfully opened
bridge-eth1: enabling the bridge
bridge-eth1: up
bridge-eth1: already up
bridge-eth1: attached
/dev/vmnet: open called by PID 7087 (vmnet-netifup)
/dev/vmnet: hub 8 does not exist, allocating memory.
/dev/vmnet: port on hub 8 successfully opened
/dev/vmnet: open called by PID 7104 (vmnet-natd)
/dev/vmnet: port on hub 8 successfully opened
vmnet8: no IPv6 routers present
----------

I delete /etc/vmware/not_configured and then I can successfully use the VMWare player (with network functionality). Problem is that I always see those [ !! ] for the network device vmnet? and that sometimes the vmnet interface does not come up.

It is not working as expected.
Comment 1 Mike Auty (RETIRED) gentoo-dev 2008-08-03 12:11:16 UTC
The host-only networking by default is on /dev/vmnet1 whilst NAT is on /dev/vmnet8, and the conflict between the NAT service and the host-only serivce is *probably* what's causing the problem.

Please move the /etc/vmware/ directory away (back it up somewhere) and try reconfiguring vmware player.  Please accept all the default options when choosing a network, and report back here whether that solves the problem.
Comment 2 Daniele C. 2008-08-03 12:31:35 UTC
It happens also without using NAT. The host-only interface is the one always failing (apparently, since the interface is actually put up most times).

I have backed up and removed /etc/vmware and run 'emerge --oneshot vmware-player'.

Then I ran '/opt/vmware/player/bin/vmware-config.pl', choose to active only the bridged network to eth1 (my LAN) and got:

------------------------
Making sure services for VMware Player are stopped.

 * Caching service dependencies ...                                       [ ok ]
 * Stopping VMware services:                                              [ ok ]
 *   Virtual machine monitor                                              [ ok ]

Configuring fallback GTK+ 2.4 libraries.

Do you want networking for your virtual machines? (yes/no/help) [yes] 

Configuring a bridged network for vmnet0.

Your computer has multiple ethernet network interfaces available: eth1, vmnet8.
Which one do you want to bridge to vmnet0? [eth0] eth1

The following bridged networks have been defined:

Do you wish to configure another bridged network? (yes/no) [no] no

Do you want to be able to use NAT networking in your virtual machines? (yes/no)
[yes] no

Do you want to be able to use host-only networking in your virtual machines? 
[no] no

 * Loading vmblock for drag and drop support ...                          [ ok ]
 * Starting VMware services:                                              [ ok ]
 *   Virtual machine monitor                                              [ ok ]
 *   Virtual ethernet                                                     [ ok ]
 *   Bridged networking on /dev/vmnet0                                    [ !! ]
 *   Host network detection                                               [ ok ]

The configuration of VMware Player 2.0.4 build-93057 for Linux for this running
kernel completed successfully.

You can now run VMware Player by invoking the following command: 
"/opt/vmware/player/bin/vmplayer".

Enjoy,

--the VMware team
------------------------

As you can see the problem is still there. Since I forgot to stop vmware before doing this operation, I will now do it again after having rebooted.

In messages we have:

------------------------
Aug  3 14:23:54 machina /dev/vmmon[13330]: Module vmmon: unloaded
Aug  3 14:23:54 machina vmware-stop: Virtual machine monitor done
Aug  3 14:23:54 machina parport_pc 00:08: disabled
Aug  3 14:24:24 machina vmmon: no version magic, tainting kernel.
Aug  3 14:24:24 machina /dev/vmmon[13411]: VMCI: Driver initialized.
Aug  3 14:24:24 machina /dev/vmmon[13411]: Module vmmon: registered with major=10 minor=165
Aug  3 14:24:24 machina /dev/vmmon[13411]: Initial HV check: anyNotCapable=1 anyUnlocked=0 anyEnabled=0 anyDisabled=0
Aug  3 14:24:24 machina /dev/vmmon[13411]: Module vmmon: initialized
Aug  3 14:24:24 machina vmware-start: Virtual machine monitor done
Aug  3 14:24:24 machina parport_pc 00:08: activated
Aug  3 14:24:24 machina parport_pc 00:08: reported by Plug and Play ACPI
Aug  3 14:24:24 machina parport0: PC-style at 0x378, irq 7 [PCSPP(,...)]
Aug  3 14:24:24 machina vmware-start: Virtual ethernet done
Aug  3 14:24:24 machina /dev/vmnet: open called by PID 13462 (vmnet-bridge)
Aug  3 14:24:24 machina device eth1 entered promiscuous mode
Aug  3 14:24:24 machina bridge-eth1: enabled promiscuous mode
Aug  3 14:24:24 machina /dev/vmnet: port on hub 0 successfully opened
Aug  3 14:24:24 machina bridge-eth1: enabling the bridge
Aug  3 14:24:24 machina bridge-eth1: up
Aug  3 14:24:24 machina bridge-eth1: already up
Aug  3 14:24:24 machina bridge-eth1: attached
Aug  3 14:24:24 machina device eth1 left promiscuous mode
Aug  3 14:24:24 machina bridge-eth1: disabled promiscuous mode
Aug  3 14:24:24 machina device eth1 entered promiscuous mode
Aug  3 14:24:24 machina bridge-eth1: enabled promiscuous mode
Aug  3 14:24:24 machina bridge-eth1: down
Aug  3 14:24:24 machina bridge-eth1: detached
Aug  3 14:24:24 machina device eth1 left promiscuous mode
Aug  3 14:24:24 machina bridge-eth1: disabled promiscuous mode
Aug  3 14:24:24 machina vmnet-detect[13470]: NetDetectDaemonInit: No host policy file found. Not initializing filter.
Aug  3 14:24:24 machina vmnet-detect[13470]: Unable to initialize the daemon
Aug  3 14:24:24 machina vmware-start: Host network detection done
------------------------

Thank you
Comment 3 Daniele C. 2008-08-03 14:04:55 UTC
I am now using the bridged network mode and everything works correctly.

Thanks