public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <mtosatti@redhat.com>
To: Morgan Cox <morgancoxuk@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: Latest Centos6.3 kernel, rebooting from inside centos6.3 VM - gets stuck on seabios/grub loop - previous kernels fine
Date: Wed, 18 Jul 2012 18:06:49 -0300	[thread overview]
Message-ID: <20120718210649.GC18886@amt.cnet> (raw)
In-Reply-To: <CAGfHYASw4twOo_=disLZ2r2=8NzubM7Dgtib16LOniUZGKrx0g@mail.gmail.com>

On Wed, Jul 11, 2012 at 10:54:34PM +0100, Morgan Cox wrote:
> Hi
> 
> I have an Ubuntu 12.04 KVM server
> 
> In Centos6 VM's - when I install the latest kernel for centos 6.3 -
> 2.6.32-279.1.1.el6 - if you reboot from inside a Centos6 vm it gets
> stuck in a loop between seabios/grub.
> 
> If i use virsh/virt-manager to reboot its fine, only from inside a
> centos6 vm (with latest centos kernel) does this occur - I am 100% its
> connected with the latest kernel (or at least the 6.3 updates).
> 
> As a test I installed centos 6.2 - this was 100% fine *until* I did a
> yum update then I got the same issue.
> 
> If I use the older kernel with all the rest of the Centos 6.3 updates
> the issue does not occur either (so it 'must'? be related to the
> kernel update)
> 
> How can this be fixed ?

Morgan,

What is the last working kernel RPM version?

Can you disable kvmclock? (by appending "no-kvmclock" to the end of the
"kernel" line of 2.6.32-279.1.1.el6 entry in /boot/grub/menu.lst).


  reply	other threads:[~2012-07-18 21:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-11 21:54 Latest Centos6.3 kernel, rebooting from inside centos6.3 VM - gets stuck on seabios/grub loop - previous kernels fine Morgan Cox
2012-07-18 21:06 ` Marcelo Tosatti [this message]
2012-07-19 11:27   ` Morgan Cox
2012-07-20  1:09     ` Marcelo Tosatti

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120718210649.GC18886@amt.cnet \
    --to=mtosatti@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=morgancoxuk@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox