Lee W. wrote: > So, following the quickstart guide religiously, I get my > golden-client (Dell Poweredge 2950, CentOS5-x86-64, kernel > 2.6.18-53.1.14.el5 all the latest packages, etc) image pushed back to > my image server (Dell 1950, Debian Etch 4.0, i686, kernel 2.6.24.2) no > problem. I boot my target node, it gets the IP from DHCP and the > pxelinux stuff from tftp no problem, and begins the imaging process. > After parted does its thing and gets the drives partitioned and > formatted, it sucks down the image to /a/ and tries to run > systemconfigurator, at which point I get this: > > <snip> > Override directory vps015 doesn't seem to exist, but that may be OK. > mount /dev /a/dev -o bind || shellout > Detecting systemconfigurator: > --- > chroot: cannot execute systemconfigurator: Exec format error > WARNING: systemconfigurator was not found in the image centos5-novz > --- > chroot: cannot execute systemconfigurator: Exec format error > Killing off running processes. > > write_variables > <snip generic SI "IT FAILED!" text> > > My full install log can be found here: http://pastebin.com/f178a7a2
Look at the kernel command line: Kernel command line: initrd=/i386/standard/initrd.img ... It seems you're using the i386 kernel to image a x86_64 image. You need to install the amd64 boot package, and select the correct kernel by si_mkclientnetboot --arch x86_64 ... Ok, there's not the 4.0.2 amd64 deb package, but you can use the 4.1.6, it can be considered stable enough for production. Otherwise you can try to build deb package from source if you've a x86_64 build server (just download the tar.bz2 from SF.net and run a "make deb"). > I'm using systemimager 4.0.2 and systemconfigurator 2.2.11 on both > the server and the golden client. To get it to install on the Centos > golden client, I also had to install perl-AppConfig-1.52.4. All the > packages I got were from the Sourceforge download page, and they all > installed without complaint. This is also a fresh install of > everything (from the SI server to the golden client) from the OS up > (this is our third SI server so far, and it deals with an environment > that is 100% isolated from the others) Any ideas? > Very good report! all versions, distribution, full output of installation and a focus on the specific problem with a clear description. Maybe we should use this mail as a template and write a page on wiki about "best practices for bug reporting". :) -Andrea ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users