From: Walker, Bruce J <bruce.walker@hp...> - 2004-11-28 16:35:40
Don't have a Debian system handy (or a vmware one of any kind) but I
remember a similar problem someone else reporting. You need the NIC
driver Vmware is going to use to be in the modules.conf so it gets
loaded in the ramdisk. The
/etc/clustertab (and thus boottab in the ramdisk) need to have the MAC
address that vmware gave the machine.
So I guess, off the top of my head:
1. get debian up on vmware; must use a certain kind of networking (not
NAT; bridge?; redirect?)=20
2. determine MAC address and NIC module name
3. put NIC module in /etc/modules.conf so it will be loaded in ramdisk
4. run ssi_create, which should create /etc/clustertab and ramdisk
5. reboot into single node cluster;
6. add other nodes; not sure how you get their MAC addresses?
Hope this helps; sorry I don't have real specifics; we will get the
README.vmware written soon, I hope,
> -----Original Message-----
> From: ssic-linux-users-admin@...=20
> [mailto:ssic-linux-users-admin@...] On=20
> Behalf Of Stefan Fuhrmann
> Sent: Sunday, November 28, 2004 7:15 AM
> To: Aneesh Kumar; ssic-linux-users@...
> Subject: [SSI-users] Some problems after installing
> Hello @ all
> I tried to install openssi on deabin on a vmware GSX-Server 3.1.
> The installation goes fine.
> But I can't boot the new Kernel after mkinitrd > panic kernel.
> I tried it without mkinitrd than I got the msg could not find NIC.
> What have I done wrong??
> I boot the old kernel and here is no networking available.=20
> The interfaces is emty only lo is present, the module seems=20
> to be okay,=20
> I tried to edit the interfaces, but I don't get it run!! Only=20
> lo goes!!
> What is happened here??
> Please, help me to get it run!!
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from=20
> real users.
> Discover which products truly live up to the hype. Start reading now.=20
> Ssic-linux-users mailing list