From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Derek Piper <dcpiper@indiana.edu>
Cc: xen-devel@lists.xen.org
Subject: Re: Crashing with Xen (Debian Wheezy) 4.1 (deb) and 4.4 (source)
Date: Tue, 03 Dec 2013 12:12:42 -0500 [thread overview]
Message-ID: <529E110A.4020404@oracle.com> (raw)
In-Reply-To: <201312031155.12693.dcpiper@indiana.edu>
On 12/03/2013 11:55 AM, Derek Piper wrote:
> What version of kernel is recommended? I went for the latest in the 3.2
> line (3.2.52 at the time) since I didn't want to worry about other system
> dependencies messing anything up. I could probably go to the 3.4 line if
> that's a good thing?
I was thinking of something like 3.12 (from kernel.org). Unless you have
some out-of-tree drivers I don't see how you can mess up your system.
But if you can't, then adding those two parameters to your existing boot
would still be useful. And output of 'xl dmesg' is also good to have.
-boris
>
> I will certainly try the debug line and report back after it dies again.
>
>
> On Tuesday, December 03, 2013 11:36:17 AM Boris Ostrovsky wrote:
>> On 12/03/2013 09:50 AM, Derek Piper wrote:
>>> Hi,
>>>
>>> I have a system (AMD FX 8320 w/8GB RAM) that I am trying to get working
>>>
>>> with Xen. The system is installed with Debian Wheezy (7.2). I have used
>>> the pre-built xen packages and followed the instructions in the Debian
>>> Xen wiki:
>>>
>>> https://wiki.debian.org/Xen
>>>
>>> I get a crash (relevant kernel panic attached) very soon after boot on
>>>
>>> the Debian Xen 4.1 version using the stock kernel (3.2.0-4-amd64).
>>>
>>> I decided to remove the xen debian packages, make my own kernel (3.2.52)
>>>
>>> with the Xen virtualization enabled and try that one. Normally the
>>> machine runs fine with it (i.e. as a regular machine). I compiled the
>>> Xen 4.4 from source and it compiled and installed without problems. When
>>> enabling the Xen kernel (via the same method as Debian - I kept the grub
>>> script
>>> /etc/grub.d/08_linux_xen ) I can boot Xen 4.4.
>>>
>>> I get a crash AGAIN (and unfortunately I can find no log of it, but the
>>>
>>> oops on the screen talked about kernel paging request again).
>>>
>>> Any hints on what I should look at? This is just without any VMs
>>>
>>> configured at all, just trying to get a stable Dom0 so I can even
>>> consider using Xen.
>> Have you tried running with a newer kernel?
>>
>> There is a fair number of errors prior to the crash and it may also help
>> booting more verbosely (e.g. add 'debug loglevel=8' to your vmlinuz boot
>> like) to better understand where they are coming from.
>>
>> -boris
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xen.org
>> http://lists.xen.org/xen-devel
prev parent reply other threads:[~2013-12-03 17:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 14:50 Crashing with Xen (Debian Wheezy) 4.1 (deb) and 4.4 (source) Derek Piper
2013-12-03 16:36 ` Boris Ostrovsky
2013-12-03 16:55 ` Derek Piper
2013-12-03 17:12 ` Boris Ostrovsky [this message]
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=529E110A.4020404@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=dcpiper@indiana.edu \
--cc=xen-devel@lists.xen.org \
/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;
as well as URLs for NNTP newsgroup(s).