On Tuesday 29 August 2006 09:40, Peter Ludikovsky wrote:
While the used linuxrc.config & info files should tell AutoYaST to use a static IP address (using VMwares emulated AMD PCnet32 card) it always tries to fetch information from a DHCP server, which is not present, or skips this step all together without BOOTP fallback. This is a major problem since the autoinstall directives should be fetched by HTTP.
are we talking about SLES10? I just tried it in vmware and for me it works fine with
hostip=1.2.3.4 netmask=255.255.0.0 insmod=pcnet32 autoyast=http://... install=cd
no DHCP request is sent then. You can try to add netsetup=-dhcp but I did not need it isoinfo tells me the application ID is SuSE-Linux-10.1-DVD-i386-10.1#0 When specifying these options on the isolinux command line they work fine for me too. But they are ignored as soon as they should be read from /info or /linuxrc.config which worked when I ran the last setup test 2 weeks ago. Since then the only changes made were at the
2006/8/29, Uwe Gansert <ug@suse.de>: post-install scripts.
As soon as the installation proceeds past this it stops short at partitioning. I already tried using fresh disks (remember, still in VMware) and disks that had all required partitions written but to no avail. Is this a general problem with VMware or did I find a glitch?
your partitioning is very complex. I suggest you to start with sda only and then add drive by drive, partition by partition until it fails. Tried that. Thing is, like the problem with configuring the IP, it worked before. For reference, the partition layout is as follows: Partition FS Mount Size sda1 ext2 /boot auto sda2 swap max / fixed sda5 reiserfs / fixed sda6 reiserfs /usr fixed sda7 reiserfs /var fixed sd{b,c,d,e,f}1 raid5 max sd{b,c,d,e,f}2 swap fixed
I would really like to be able to continue my test within VMware since I don't want to stress out the hardware now and have it break too soon.
vmware should work. Good to know.
Regards, Peter