SUSE Linux Enterprise Server for SAP Applications 12 SP1
SUSE | v20170121Linux/Unix, Other 12 SP1 - 64-bit Amazon Machine Image (AMI)
External reviews
External reviews are not included in the AWS star rating for the product.
Same issues as others. Kernel panic after first reboot. Can't connect
[ 1.685530] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 1.688829] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 3.12.57-60.35-default #1
[ 1.688829] Hardware name: Xen HVM domU, BIOS 4.2.amazon 05/12/2016
[ 1.688829] 0000000000000000 ffffffff815202d0 ffffffff817df358 ffff881e0c291e20
[ 1.688829] ffffffff8151b251 ffff881e00000010 ffff881e0c291e30 ffff881e0c291dd0
[ 1.688829] ffff881e0c291e20 ffff881e0c291e38 0000000000000012 0000000000000001
[ 1.688829] Call Trace:
[ 1.688829] [
[ 1.688829] [
[ 1.688829] [
[ 1.688829] [
[ 1.688829] [
[ 1.688829] [
[ 1.688829] [
[ 1.688829] [
[ 1.688829] [
[ 1.688829] [
- Leave a Comment |
- Mark review as helpful
Not usable currently
Same problem as the other reviewers: Disfunctinal after first reboot. HANA Express install itself was fine, until I shudown the instance and rebooted. Tried several new installations, all the same result. Viewing EC2 console system log shows that it panics because of missing/corrupt root device. Hope they wil fix it....
Kernel panic after first reboot
Same issue as first reviewer. First boot worked fine, could do work as required. When rebooting the instance, the instance was never reachable anymore. The system log in the EC2 Management Console shows a Kernel Panic.
Unable to connect to instance after reboot
Our experince is not at all Good....After simply launching the instance ,we logged on to server .And checked basic stuff . Found the OS fine for SAP.But And rebooting the server we are unable to loggon. AWS support saying that issue with this AMI....