I don't have any suggestions as to the cause of the problem, but a
backtrace would likely be helpful. Easiest way is probably to configure
kdump:
http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Deployment_Guide/ch-kdump.html

On Tue, Dec 27, 2011 at 2:12 PM, Vu Pham <v...@sivell.com> wrote:

> On 12/27/2011 12:52 PM, solarflow99 wrote:
>
>> bios settings?  processor type?  you're likely going from para to full
>> virtualization right?
>>
>
> This is a Dell server R710 with one Xeon E5620 processor. The
> virtualization is set to on in the BIOS. This is the first guest on this
> server and it is  a full virtualization system.
>
> Thanks,
> Vu
>
>
>
>
>
>
>>
>> On Tue, Dec 27, 2011 at 1:33 PM, Vu Pham<v...@sivell.com>  wrote:
>>
>>> I have had this Dell server running Xen for a couple of years and
>>> decided to
>>> move to KVM. After moving all the guests to another server, I reboot this
>>> server using the non-Xen kernel and install KVM.
>>>
>>> Duing the process of installing the first guest, the host server panics.
>>> This happens three times in the same manner: after selecting the
>>> installation media, which is a local ISO file of RHEL5.5, the gurst's
>>> RHEL
>>> boot screen starts and loads files. Then boom, the console shows the
>>> panic
>>> screen and the server hangs.
>>>
>>> The server is RHEL5.7 and already yum updated.
>>>
>>>
>>> Any advices is greatly appreciated.
>>>
>>> Thanks,
>>> Vu
>>>
>>> ______________________________**_________________
>>> rhelv5-list mailing list
>>> rhelv5-list@redhat.com
>>> https://www.redhat.com/**mailman/listinfo/rhelv5-list<https://www.redhat.com/mailman/listinfo/rhelv5-list>
>>>
>>
> ______________________________**_________________
> rhelv5-list mailing list
> rhelv5-list@redhat.com
> https://www.redhat.com/**mailman/listinfo/rhelv5-list<https://www.redhat.com/mailman/listinfo/rhelv5-list>
>
_______________________________________________
rhelv5-list mailing list
rhelv5-list@redhat.com
https://www.redhat.com/mailman/listinfo/rhelv5-list

Reply via email to