Open Stack

Hi Bob,

I'm sorry I just found that compiled a patched Kernel (used for install a
software). It might be some problem with the patches. I will let you know
if there is problem install a clean kernel.

Thanks,
Qin


On Fri, Sep 27, 2013 at 4:02 PM, Bob Ball <bob.ball at citrix.com> wrote:

>  Hi,
>
>  That sounds like something that would be best answered by either the
> xen-devel list or the xs-devel list.  Can I suggest that you ask the
> question there?
>
>  It might be worth just confirming that the behaviour is the same when
> you perform those steps outside OpenStack - i.e. just using XenCenter to
> set up a Fedora VM and then upgrading the kernel.
>
>  Thanks,
>
>  Bob
>
>  ------------------------------
> *From:* Qin Jia [jiaqin1017 at gmail.com]
> *Sent:* 27 September 2013 20:18
> *To:* Bob Ball
> *Cc:* openstack at lists.openstack.org
> *Subject:* Re: [Openstack] Loading Kernel Module during reboot
>
>   Hi Bob,
>
>  Thank you for your reply. I used a single-part image to start a instance
> of Fedora 14. Inside the instance, I complied the Linux 3.1.2 kernel and
> updated the grub. However, the boot process will stuck when choosing the
> newly built kernel in grub. For Xencenter, I saw the error message shown on
> the screen is (It go through very quickly, I catched this by snapshoots.)
>
>  BUG: scheduling while atomic: swapper/0/0x10000002
> BUG: scheduling while atomic: kworker/0:0/0x10000002
> Error: Driver 'xen-platform-pci' is already registered. aborting...
>
>  And after this, the screen stuck like the attached picture.
>
>  Do you have any ideas about why this happens?
>
>  Thanks,
> Qin
>
>  [image: Inline image 2]
>
>
> On Mon, Sep 23, 2013 at 6:24 AM, Bob Ball <bob.ball at citrix.com> wrote:
>
>>  It depends what type of image you are booting.****
>>
>> ** **
>>
>> If you are using a 3-part image, where the kernel and the initrd were
>> originally outside of the root disk, then I’ve never tested how to make the
>> necessary changes so the next boot pulls the kernel/initrd out from the
>> image.****
>>
>> ** **
>>
>> If the original image was a single-part and the kernel/initrd were
>> extracted automatically at boot time then yes, simply updating grub.conf to
>> reference the new kernel+initrd should be sufficient.****
>>
>> ** **
>>
>> Bob****
>>
>> ** **
>>
>> *From:* Qin Jia [mailto:jiaqin1017 at gmail.com]
>> *Sent:* 23 September 2013 05:57
>>
>> *To:* openstack at lists.openstack.org
>> *Subject:* [Openstack] Loading Kernel Module during reboot****
>>
>>  ** **
>>
>> Hello,****
>>
>> ** **
>>
>> I have openstack run on top of Xenserver. I have created images (initrd
>> and kernel images)  inside the /boot directory of the instance. I was
>> wondering if it is possible to load the image during rebooting of the
>> instance by changing the grub.conf? ****
>>
>> ** **
>>
>> Thanks,****
>>
>> Qin****
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20130927/ea975c72/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: snapshot.jpg
Type: image/jpeg
Size: 142201 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20130927/ea975c72/attachment.jpg>