So no suggestions on how to resolve this?
On Tue, Mar 13, 2012 at 3:22 PM, Lonni J Friedman
On Tue, Feb 28, 2012 at 2:14 AM, Uwe Gansert
wrote: Moin,
JFYI - SLES11 SP2 is ready for download http://www.suse.com/de-de/products/server/eval.html
The AutoYaST changes to SP1 can be found here: http://www.suse.de/~ug/autoyast_changes_SLES11SP2.html
I'm seeing a strange problem when installing SLES11-SP2 inside of a kvm (virtualized) environment using autoyast. The OS installs fine, but when it reboots afterwards, kvm can't find an active partition to boot from. Sure enough when I run fdisk on the OS image file, none of the partitions have the 'boot' flag set:
######### Disk cuda-linux64-build17.img: 116.0 GB, 115964116992 bytes 255 heads, 63 sectors/track, 14098 cylinders, total 226492416 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000f3e90
Device Boot Start End Blocks Id System cuda-linux64-build17.img1 2048 226492415 113245184 f W95 Ext'd (LBA) cuda-linux64-build17.img5 4096 159743 77824 83 Linux cuda-linux64-build17.img6 161792 2248703 1043456 82 Linux swap / Solaris cuda-linux64-build17.img7 2250752 226467839 112108544 83 Linux ########
I tried to manually set the boot flag to the very first partition (which is what gets set for a non-virtualized installation), but all that seemed to do was change the "no active partition" error to a "no bootable OS" error.
Here's what the partitioning and bootloader sections of my autoyast.xml file look like:
<partitioning config:type="list"> <drive> <use>all</use> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <mount>/boot</mount> <size>75mb</size> <filesystem config:type="symbol">ext2</filesystem> </partition> <partition> <mount>swap</mount> <size>1012mb</size> <filesystem config:type="symbol">swap</filesystem> </partition> <partition> <mount>/</mount> <size>max</size> <filesystem config:type="symbol">ext3</filesystem> </partition> </partitions> </drive> </partitioning> <bootloader> <global config:type="list">
<key>prompt</key> <value config:type="boolean">false</value> <key>default</key><value>0</value> <key>timeout</key><value>3</value> </global>console=ttyS0,115200 console=tty0 grub <location>mbr</location> <sections config:type="list"/> </bootloader>While I'd love to chalk this up to some weird kvm bug, the only Linux distro exhibiting this problem is SLES11-SP2. It works fine with the latest releases from RHEL, Fedora, Ubuntu, and even OpenSUSE(-12.1).
help?
thanks -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner@opensuse.org