Can not reboot after installation

[butjar]

Hi,

I tried installing xen-blanket on the AMI you proposed in your first version (AMI ID: ami-7ea24a17, Name: EC2 CentOS 5.4 HVM AMI).

I think I made some mistakes in my grub.conf.

This is what my grub.conf looks like:

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /boot/, eg.
#          root (hd0,0)
#          kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
#          initrd /initrd-version.img
#boot=/dev/hda
default=0
timeout=5
serial --unit=0 --speed=115200 --word=8 --parity=no --stop=1
terminal --timeout=10 serial console
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title XENBLANKET
    root (hd0,0)
    kernel /xen.gz sched=credit tdt=0
    module /vmlinuz-3.1.2 ro root=/dev/VolGroup00/LogVol00 rootfstype=ext3 highres=off acpi=off quiet
    module /initramfs-3.1.2.img
title XENBLANKET-DEBUG
        root (hd0,0)
        kernel /xen.gz apic_verbosity=verbose sched=credit tdt=0 com1=115200,8n1 console=com1 dom0_vcpus=2
        module /vmlinuz-3.1.2 ro root=/dev/VolGroup00/LogVol00 rootfstype=ext3 highres=off acpi=off earlyprintk=xen console=hvc0 console=ttyS0,115200n8
        module /initramfs-3.1.2.img
title CentOS (2.6.18-164.15.1.el5)
    root (hd0,0)
    kernel /vmlinuz-2.6.18-164.15.1.el5 ro root=/dev/VolGroup00/LogVol00 rhgb quiet console=tty0 console=ttyS0,115200n8
    initrd /initrd-2.6.18-164.15.1.el5.img
title CentOS (2.6.18-164.el5)
    root (hd0,0)
    kernel /vmlinuz-2.6.18-164.el5 ro root=/dev/VolGroup00/LogVol00 rhgb quiet console=tty0 console=ttyS0,115200n8
    initrd /initrd-2.6.18-164.el5.img

Here is a section from the log:

ip-10-149-24-37 login: 
INIT: version 2.86 reloading

INIT: Switching to runlevel: 6

INIT: Sending processes the TERM signal

Shutting down smartd: [  OK  ]

Stopping yum-updatesd: [  OK  ]

Stopping atd: [  OK  ]

Stopping cups: [  OK  ]

Stopping hpiod: [  OK  ]

Stopping hpssd: [  OK  ]

Shutting down xfs: [  OK  ]

Shutting down console mouse services: [  OK  ]

Stopping sshd: [  OK  ]

Shutting down sm-client: [FAILED]

Shutting down sendmail: [  OK  ]

Stopping xinetd: [  OK  ]

Stopping crond: [  OK  ]

Stopping autofs:  Stopping automount: [  OK  ]

[  OK  ]

Stopping acpi daemon: [  OK  ]

Stopping HAL daemon: [  OK  ]

Stopping system message bus: [  OK  ]

Stopping RPC idmapd: [  OK  ]

Stopping NFS statd: [  OK  ]

Stopping portmap: [  OK  ]

Stopping auditd: audit(1378732607.192:83): audit_pid=0 old=2064 by auid=4294967295
[  OK  ]

Stopping PC/SC smart card daemon (pcscd): [  OK  ]

Shutting down kernel logger: [  OK  ]

Shutting down system logger: [  OK  ]

Shutting down hidd: [  OK  ]

[  OK  ]
[  OK  ]
Shutting down interface eth0:  [  OK  ]

Shutting down loopback interface:  [  OK  ]

Starting killall:  [  OK  ]

Sending all processes the TERM signal... 
Sending all processes the KILL signal... 
Saving random seed:  
Syncing hardware clock to system time type=1111 audit(1378732615.998:84): user pid=10612 uid=0 auid=4294967295 msg='changing system time: exe="/sbin/hwclock" (hostname=?, addr=?, terminal=console res=success)'

Turning off swap:  
Turning off quotas:  
Unmounting pipe file systems:  
Unmounting file systems:  
Please stand by while rebooting the system...
md: stopping all md devices.
Restarting system.
.
machine restart

Press any key to continue.

Press any key to continue.

Press any key to continue.

Press any key to continue.

Press any key to continue.

Press any key to continue.

Press any key to continue.

Press any key to continue.

Hope you can help me. Are you using a public AMI where it just works out of the box ?

Regards

[danlythemanly]

Does it work when you follow the steps from the first version (xen.blanket.1.0.1)?

[butjar]

I'll try that now, but the setup will take more time. So you think it could be an issue with the AMI ?

[danlythemanly]

I'm not sure what AMI the newer version of the Xen-Blanket runs out of the box on, but it's likely that it wasn't tested rigorously on the AMI specified for the older version. The older Xen-Blanket should work, though.

[butjar]

What do you mean by saying "Be Patient" in your documentation. How long could the reboot take by your experience ? Looks like I'm having the same issue with the old installation guide.

[butjar]

I got Xen-Blanket 1.0 working now, I think I had some issues in the grub config, so i'll close this issue. If I'm able to install the new setup on any AMI I will let you know and give you the required installation steps.

[butjar]

I think I found the problem with the new version. After I fixed the grub.conf (should be working now) I got this error from the logs:

...
Restarting system.
.
machine restart
Press any key to continue.
Press any key to continue.
Press any key to continue.
Press any key to continue.
Press any key to continue.
[    0.001830] BUG: scheduling while atomic: swapper/0/0x10000002
�Red Hat nash version 5.1.19.6 starting
  Reading all physical volumes.  This may take a while...
  No volume groups found
  Volume group "VolGroup00" not found
Unable to access resume device (/dev/VolGroup00/LogVol01)
mount: could not find filesystem '/dev/root'
setuproot: moving /dev failed: No such file or directory
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
switchroot: mount failed: No such file or directory
[    0.850040] Kernel panic - not syncing: Attempted to kill init!
[    0.850380] Pid: 1, comm: init Not tainted 3.1.2 #1
[    0.850380] Call Trace:
[    0.850380]  [] panic+0xcb/0x1df
[    0.850380]  [] ? task_rq_unlock+0x27/0x2c
[    0.850380]  [] ? sched_move_task+0xb8/0xc3
[    0.850380]  [] do_exit+0x9d/0x704
[    0.850380]  [] do_group_exit+0x99/0x99
[    0.850380]  [] sys_exit_group+0x17/0x1b
[    0.850380]  [] system_call_fastpath+0x16/0x1b
...

searching for similar problem I found: http://comments.gmane.org/gmane.comp.emulators.xen.user/41026 and http://wiki.xen.org/wiki/Migrate_from_Linux_2.6.18_to_2.6.31_and_higher

So I suppose an issue with /etc/modprobe.conf In your old README you also described how to modify modprob.conf, did you also change in your new installation ?

[danlythemanly]

I implemented the older version and a different student ported it to the newer Xen. I'm afraid I haven't had the time to really test that setup.