Revision history [back]

click to hide/show revision 1
initial version

Hello,

Thank you for your answers, in fact I already tried with an image from cloud.centos.org and had the same problem.

After getting access to the console, i found a kernel panic message: "kernel panic not syncing io apic + timer doesn't work" so I rebuilt a new image with noapic in the grub configuration. After this step, the instance was booting correctly however I had issues with the network configuration.

The default network interface name in Centos 7 is enp0s3, however when I logged in to the console, it seems that the network service is trying to bring eth0 up. So I changed enp0s3 to eth0 in /etc/sysconfig/network-scripts/ifcfg-enp0s3 and renamed it to ifcfg-eth0.

Following these two steps (noapic in the grub configuration and changing the network interface name) the instance is booting correctly and accessible.

Thank you

Hello,

Thank you for your answers, in fact I already tried with an image from cloud.centos.org and had the same problem.

After getting access to the console, i found a kernel panic message: "kernel panic not syncing io apic + timer doesn't work" so I rebuilt a new image with noapic in the grub configuration. After this step, the instance was booting correctly however I had issues with the network configuration.

The default network interface name in Centos 7 is enp0s3, however when I logged in to the console, it seems that the network service is trying to bring eth0 up. So I changed enp0s3 to eth0 in /etc/sysconfig/network-scripts/ifcfg-enp0s3 and renamed it to ifcfg-eth0.(/sbin/ip link set enp0s3 down && /sbin/ip link set enp0s3 name eth0)

Following these two steps (noapic in the grub configuration and changing the network interface name) the instance is booting correctly and accessible.

Thank you