Hi, 

the IP 192.168.0.79 of a vmware machine started with ResourceManager 
is able to be ping'ed but not reached with ssh from the host (lenny).
The ResourceManager of heartbeat seems to start vmplayer in a encapsulated
 environment. How can reach the vmplayer with ssh? BTW: the vmware machine 
is reachable with ssh, http, ... from *any* machine in my LAN except from
the host lenny! 


Thats what I've done: 
=====================
I've installed a vmplayer machine (Suse 9.2) in a drbd device. 
And it works starting at command line:
   # vmrun -T player start /data/suse92_mysql/suse92/Suse9.2.vmx nogui
I can ssh to 192.168.0.79. All right. 

But starting vmplayer by heartbeat ResourceManager configured in haresources,
I can ping to 192.168.0.79 as soon as the ResourceManager starts 
Suse9.2 - although the machine is not booted completely yet.
The 192.168.0.79 seems to be simulated somehow by ResourceManager.
  drbddisk::suse92_mysql Filesystem::/dev/drbd6::/data/suse92_mysql::ext3 
192.168.0.79 vmplay
And after the Suse9.2 vmplayer is started completely the ports of Suse 9.2 are 
not reachable from the host (lenny). 

tia
Ekkard 


_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to