Hi,
I need to use PVGRUB on my new CentOS 7.

Don't ask me why, I need it.
On CentOS 6.5 I can do that selecting pvgrub in the boot option of my linode manager.

this command:
mkdir /boot/grub/
ln -s /boot/grub/grub.conf /boot/grub/menu.lst
ln -s /boot/grub/grub.conf /etc/grub.conf
yum -y install kernel-xen

than fill in the grub.conf.


How can I do now?
Is there someone who can help booting in pvgrub my centos 7?

very disappointed from linode.
there is no way to use pvgrub on CentOS 7 since they don't support GRUB2.

I've not used CentOS 7 but in other distros you can install either grub or grub2. Have you checked the package repos for the old grub?

_________________
Paid support
How to ask for help
1. Give details of your problem
2. Post any errors
3. Post relevant logs.
4. Don't hide details i.e. your domain, it just makes things harder
5. Be polite or you'll be eaten by a grue

Yes, no grub1.
RHEL/CentOS 7 does not support Grub anymore.

Great! Here's a link that will help you get started with your move to DigitalOcean. Be sure to become familiar with their community forum as well.

If there's anything the Linode Community can do to make your departure quicker, please let us know.

_________________

/* TODO: need to add signature to posts */

I solved using pvgrub on linode centos 7.

linode team is always incredible...

Note: You do not need the grub or grub2 package installed at all for pv-grub. You nee a kernel and a /boot/grub/menu.lst file.

- Les

I've noticed it
thanks

Now if he'd only change from CentOS to OpenSUSE, he'd stop being a major pain on the CentOS forum.

_________________
Either provide enough details for people to help, or sit back and listen to the crickets chirp.
Security thru obscurity is a myth - and really really annoying.

So what is the bottom line here? I have my COS7 system booting up then dying as follows:

[ OK ] Listening on udev Kernel Socket.
[ OK ] Listening on udev Control Socket.
[ OK ] Reached target Sockets.
Starting Create list of required static device nodes...rrent kernel...
Starting Apply Kernel Variables...
[ OK ] Reached target Swap.
[ OK ] Reached target Local File Systems.
[8519539.500429] systemd-journald[137]: Vacuuming done, freed 0 bytes
[ OK ] Started Apply Kernel Variables.
[ OK ] Started Create list of required static device nodes ...current kernel.
[ OK ] Started Setup Virtual Console.
Starting Create static device nodes in /dev...
[ OK ] Started Create static device nodes in /dev.
Starting udev Kernel Device Manager...
[8519539.522124] systemd-udevd[155]: starting version 208
[ OK ] Started udev Kernel Device Manager.
Starting udev Coldplug all Devices...
Mounting Configuration File System...
[ OK ] Mounted Configuration File System.
[ OK ] Started udev Coldplug all Devices.
Starting dracut initqueue hook...
[ OK ] Reached target System Initialization.
Starting Show Plymouth Boot Screen...
[ OK ] Started Show Plymouth Boot Screen.
[ OK ] Reached target Paths.
[ OK ] Reached target Basic System.
dracut-initqueue[174]: Warning: Could not boot.
[ OK ] Started Show Plymouth Boot Screen.
[ OK ] Reached target Paths.
[ OK ] Reached target Basic System.
dracut-initqueue[174]: Warning: Could not boot.
dracut-initqueue[174]: Warning: /dev/xvda does not exist
Starting Dracut Emergency Shell...
Warning: /dev/xvda does not exist

Generating "/run/initramfs/rdsosreport.txt"


Entering emergency mode. Exit the shell to continue.
Type "journalctl" to view system logs.
You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot
after mounting them and attach it to a bug report.


dracut:/#


Anyone have an answer as to what I might have missed?

Thanks,
Mike

You almost never want an initrd/initramfs; I'd suggest investigating why dracut is involved.

- Les

Solved by booting with linode kernel and re-installing distro kernel (probably due to the re-build of initrd).