Linode Forum
Linode Community Forums
 FAQFAQ    SearchSearch    MembersMembers      Register Register 
 LoginLogin [ Anonymous ] 
Post new topic  Reply to topic
Author Message
PostPosted: Wed Jun 17, 2015 7:44 am 
Offline
Newbie

Joined: Wed Jun 17, 2015 7:38 am
Posts: 2
Hello all,

Sorry if this is a very noobish or basic question, but we used to use the 'PV-Grub' method of running a custom Kernel under Xen (https://www.linode.com/docs/tools-refer ... ith-pvgrub). Now everything is moving to KVM, how do we ensure this carries across our Linodes?

We attempted to upgrade one to KVM without changing any settings (on hindsight probably a stupid idea) and it defaulted to booting straight to grub and not doing much else. We had to fix this by editing the configuration and selecting a 'latest x64' Kernel instead so the machine would boot. Of course, this means we are no longer using the custom installed kernel...

We tried 'Direct Disk' as an option but the console complained about a missing MBR. As the name suggests, I'm learning here so this is a little new to me. Sorry if this is a silly and obvious question. Any new pointers on how to do this on the new KVM platform? Thanks in advance.


Top
   
PostPosted: Wed Jun 17, 2015 12:08 pm 
Offline
Senior Member

Joined: Fri Feb 13, 2015 8:12 pm
Posts: 101
Direct-to-disk will only work after "grub-install /dev/sda" (so to speak), but for a custom kernel, you don't need that.

What you need is

1) a kernel which may be run under KVM (make sure you didn't customize so much that it only supports Xen)

2) Either:

* A well written /boot/grub/grub.cfg if you select "GRUB2" as the "kernel".
* A well written /boot/grub/menu.lst if you select "GRUB (Legacy)" as the "kernel".

and

3) A well written /etc/fstab.

The so called "distro-helper" modifies /etc/fstab for you, but I'm not sure it's smart enough to modify menu.lst or grub.cfg as well.

So, my recommendation would be to use UUID wherever possible. Then you can stop worrying about disk name changes.


Top
   
PostPosted: Wed Jun 17, 2015 1:17 pm 
Offline
Newbie

Joined: Wed Jun 17, 2015 7:38 am
Posts: 2
Thanks for your response.

It looks like our problems were caused by an issue Linode side. An operator on IRC has confirmed legacy grub was misconfigured and this problem has now been resolved. I can confirm things are now working correctly after a few changes to grub's menu.lst file. For those who are interested, we needed to do the following to get our CentOS 6.5 boxes to work correctly after conversion to KVM:

1. Replace '/dev/xvda' with '/dev/sda' in /boot/grub/menu.lst
2. Add "console=ttyS0" to the end of the kernel line(s).

If we've missed any steps or it may be advisable to perform some additional steps, please let us know.


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic


Who is online

Users browsing this forum: No registered users and 5 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
Jump to:  
RSS

Powered by phpBB® Forum Software © phpBB Group