Mailinglist Archive: opensuse-autoinstall (36 mails)
| < Previous | Next > |
RE: [opensuse-autoinstall] AutoYaST auto-installation in aVMware guest machine
- From: "John Bown" <john.bown@xxxxxxxxxxx>
- Date: Mon, 22 Oct 2007 10:57:53 -0400
- Message-id: <3F2FB49ADAE57C409F1927B1C7389D6E03D12262@xxxxxxxxxxxxxxxxxxxx>
Hello again to both the list and Chris. Strangely, before I could even
try Chris' fix, any and all virtual installations of SLES10, both with
and without SP1, mysteriously power off during installation without
warning. A test installation of XP finished without issue. Has anyone
seen this sort of thing before? Many thanks.
-----Original Message-----
From: Chris Partridge [mailto:cpartridge@xxxxxxxxxx]
Sent: Thursday, October 11, 2007 11:56 AM
To: John Bown; opensuse-autoinstall@xxxxxxxxxxxx
Subject: Re: [opensuse-autoinstall] AutoYaST auto-installation in
aVMware guest machine
On the installed system, from the grub menu, you can look at the
contents of the /boot folder. This may have happened if you installed
updates during installation. When your autoyast file was created, it
would have configured bootloader with the current installed kernel. But
the installation media won't have that version. Check that the kernel
version in the bootloader section of your autoyast file is the same as
the version on your installation media. One way to get around this and
not worry about the kernel version is to change your autoyast file (for
future installs) and your /boot/grub/menu.lst (for the currently
installed system) to point to /boot/vmlinuz and /boot/initrd instead.
The installation automatically creates these symlink files that point to
the latest kernel installed. I did this during testing of SLES 10 SP1,
and it worked great.
>>> On Thu, Oct 11, 2007 at 7:46 AM, in message
<3F2FB49ADAE57C409F1927B1C7389D6E03BDF7BF@xxxxxxxxxxxxxxxxxxxx>, "John
Bown" <john.bown@xxxxxxxxxxx> wrote:
Hello everyone. My job requires that I frequently deploy fresh virtual
(VMware) installations of SLES 10, both with and without SP1, to our
developers. To that end, I recently setup a machine from which I'd like
to test automating the process using a DVD as the source of the
installation files, and a floppy disk as the location of the control
file. However, there seems to be a problem.
I boot the virtual machine to the DVD drive, the autoinst.xml file on
the floppy is then located, and off it goes. The installation completes
flawlessly; however, when the newly created virtual machine attempts to
boot for the first time, I get the following, GRUB related error:
>>>>>SNIP<<<<<
root (hd0,1)
Filesystem type is reiserfs, partition type 0x83
kernel /boot/vmlinuz-2.6.16.53-0.8-smp root=/dev/sda2 vga=0x31a
resume=/dev/sda1 splash=silent
Error 15: File not found
Press any key to continue...
>>>>>SNIP<<<<<
Has anyone else out there come across this? Are there any special steps
that need to be taken when performing an automated installation in a
virtual environment? Many thanks.
John Bown
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-autoinstall+help@xxxxxxxxxxxx
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-autoinstall+help@xxxxxxxxxxxx
try Chris' fix, any and all virtual installations of SLES10, both with
and without SP1, mysteriously power off during installation without
warning. A test installation of XP finished without issue. Has anyone
seen this sort of thing before? Many thanks.
-----Original Message-----
From: Chris Partridge [mailto:cpartridge@xxxxxxxxxx]
Sent: Thursday, October 11, 2007 11:56 AM
To: John Bown; opensuse-autoinstall@xxxxxxxxxxxx
Subject: Re: [opensuse-autoinstall] AutoYaST auto-installation in
aVMware guest machine
On the installed system, from the grub menu, you can look at the
contents of the /boot folder. This may have happened if you installed
updates during installation. When your autoyast file was created, it
would have configured bootloader with the current installed kernel. But
the installation media won't have that version. Check that the kernel
version in the bootloader section of your autoyast file is the same as
the version on your installation media. One way to get around this and
not worry about the kernel version is to change your autoyast file (for
future installs) and your /boot/grub/menu.lst (for the currently
installed system) to point to /boot/vmlinuz and /boot/initrd instead.
The installation automatically creates these symlink files that point to
the latest kernel installed. I did this during testing of SLES 10 SP1,
and it worked great.
>>> On Thu, Oct 11, 2007 at 7:46 AM, in message
<3F2FB49ADAE57C409F1927B1C7389D6E03BDF7BF@xxxxxxxxxxxxxxxxxxxx>, "John
Bown" <john.bown@xxxxxxxxxxx> wrote:
Hello everyone. My job requires that I frequently deploy fresh virtual
(VMware) installations of SLES 10, both with and without SP1, to our
developers. To that end, I recently setup a machine from which I'd like
to test automating the process using a DVD as the source of the
installation files, and a floppy disk as the location of the control
file. However, there seems to be a problem.
I boot the virtual machine to the DVD drive, the autoinst.xml file on
the floppy is then located, and off it goes. The installation completes
flawlessly; however, when the newly created virtual machine attempts to
boot for the first time, I get the following, GRUB related error:
>>>>>SNIP<<<<<
root (hd0,1)
Filesystem type is reiserfs, partition type 0x83
kernel /boot/vmlinuz-2.6.16.53-0.8-smp root=/dev/sda2 vga=0x31a
resume=/dev/sda1 splash=silent
Error 15: File not found
Press any key to continue...
>>>>>SNIP<<<<<
Has anyone else out there come across this? Are there any special steps
that need to be taken when performing an automated installation in a
virtual environment? Many thanks.
John Bown
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-autoinstall+help@xxxxxxxxxxxx
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-autoinstall+help@xxxxxxxxxxxx
| < Previous | Next > |