Re: [CentOS] Cannot boot CentOS 7 VM after updating Host CentOS 7 Kernel

2016-10-30 Thread Steven Tardy
> On Oct 30, 2016, at 7:31 PM, Paul R. Ganci wrote: > > Now the question is how did this happen. I've seen something similar when installing a kernel if /etc/fstab didn't match df. Mkinitrd bombs out leaving the system unbootable. The rescue .iso/mkinitrd path you followed

Re: [CentOS] Cannot boot CentOS 7 VM after updating Host CentOS 7 Kernel

2016-10-30 Thread Paul R. Ganci
On 10/30/2016 03:05 PM, Eero Volotinen wrote: so, Just chroot to mountpoint: http://www.cyberciti.biz/faq/unix-linux-chroot-command-examples-usage-syntax/ chroot /mounted/path /bin/bash and then .. mkinitrd (see man page for documentation) Thank you for the hint. The way I fixed this

Re: [CentOS] Cannot boot CentOS 7 VM after updating Host CentOS 7 Kernel

2016-10-30 Thread Eero Volotinen
so, Just chroot to mountpoint: http://www.cyberciti.biz/faq/unix-linux-chroot-command-examples-usage-syntax/ chroot /mounted/path /bin/bash and then .. mkinitrd (see man page for documentation) 2016-10-30 22:57 GMT+02:00 Eero Volotinen : > A bit hard to say. Try

Re: [CentOS] Cannot boot CentOS 7 VM after updating Host CentOS 7 Kernel

2016-10-30 Thread Eero Volotinen
A bit hard to say. Try chrooting into environment and rebuilding initrd? -- Eero 2016-10-30 22:53 GMT+02:00 Paul R. Ganci : > On 10/30/2016 12:26 PM, Paul R. Ganci wrote: > >> I am thinking of putting the CentOS iso out and then booting the VM >> into it just to poke around

Re: [CentOS] Cannot boot CentOS 7 VM after updating Host CentOS 7 Kernel

2016-10-30 Thread Paul R. Ganci
On 10/30/2016 12:26 PM, Paul R. Ganci wrote: I am thinking of putting the CentOS iso out and then booting the VM into it just to poke around the file system. Otherwise my other option is to just clone a twin VM on another server and then just change the networking IPs/hostname. Anybody have

Re: [CentOS] Cannot boot CentOS 7 VM after updating Host CentOS 7 Kernel

2016-10-30 Thread Eero Volotinen
You could mount image ja rebuild initrd. Eero 2016-10-30 20:26 GMT+02:00 Paul R. Ganci : > On 10/30/2016 07:33 AM, FrancisM wrote: > >> Any error in your host logs? >> > Nothing obvious. I checked /var/log/messages, /var/log/libvirt/qemu, > /var/log/libvirt/lxc &

Re: [CentOS] Cannot boot CentOS 7 VM after updating Host CentOS 7 Kernel

2016-10-30 Thread Paul R. Ganci
On 10/30/2016 07:33 AM, FrancisM wrote: Any error in your host logs? Nothing obvious. I checked /var/log/messages, /var/log/libvirt/qemu, /var/log/libvirt/lxc & /var/log/qemu-ga. The /var/log/libvirt/lxc & /var/log/qemu-ga were empty. The /var/log/libvirt/qemu directory had a log file of

Re: [CentOS] Cannot boot CentOS 7 VM after updating Host CentOS 7 Kernel

2016-10-30 Thread Paul R. Ganci
On 10/30/2016 06:57 AM, Steven Tardy wrote: On Oct 30, 2016, at 3:27 AM, Paul R. Ganci wrote: grub> set root=(hd0,msdos2) grub> linux (hd0,1)/vmlinuz-3.10.0-327.36.2.el7.x86_64 root=(hd0,msdos2)/ grub> initrd initrd-plymouth.img grub> boot Try the initrd matching the kernel

Re: [CentOS] Cannot boot CentOS 7 VM after updating Host CentOS 7 Kernel

2016-10-30 Thread FrancisM
Any error in your host logs? On Sunday, 30 October 2016, Steven Tardy wrote: > > > On Oct 30, 2016, at 3:27 AM, Paul R. Ganci > wrote: > > > > grub> set root=(hd0,msdos2) > > grub> linux (hd0,1)/vmlinuz-3.10.0-327.36.2.el7.x86_64 >

Re: [CentOS] Cannot boot CentOS 7 VM after updating Host CentOS 7 Kernel

2016-10-30 Thread Steven Tardy
> On Oct 30, 2016, at 3:27 AM, Paul R. Ganci wrote: > > grub> set root=(hd0,msdos2) > grub> linux (hd0,1)/vmlinuz-3.10.0-327.36.2.el7.x86_64 root=(hd0,msdos2)/ > grub> initrd initrd-plymouth.img > grub> boot Try the initrd matching the kernel?

[CentOS] Cannot boot CentOS 7 VM after updating Host CentOS 7 Kernel

2016-10-30 Thread Paul R. Ganci
I have something very strange that occurred. After updating the kernel on my host CentOS 7 Dell 2950iii I have found that one of my CentOS 7 guest VMs will no longer boot... it just stops at the grub prompt (a second VM functions just fine). I have no idea why this problem occurred and have