From: "John L. Poole" <jlpoole56@gmail.com>
To: xen-devel@lists.xen.org
Subject: Intel Atom CPU model (C2750) Woes & Debian
Date: Wed, 29 May 2019 14:36:24 -0700 [thread overview]
Message-ID: <15101486-c6a3-536d-eddb-52a9cc3731b8@gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1636 bytes --]
Referencing the expanding the thread I started several months ago entitled
"Xen 4.12.0-rc Hangs Around masked ExtINT on CPU#", I installed a fresh hard
drive on my Supermicro Atom server class unit and did the following:
per:
https://wiki.xen.org/wiki/Xen_Project_Beginners_Guide#Download_and_Burn_the_Debian_Installer_CD
downloaded:
http://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-9.9.0-amd64-netinst.iso
burned CD
on boot had to select UEFI ASUS install, the regular ASUS did not work.
console was blank,
screen attached has graphical image light blue, selected graphical install
proceeded with install.
Reboot.
did NOT perform the suggested: apt-get install firmware-linux-nonfree
performed:
apt-get install xen-system-amd64
restart.
startup hangs.
So, I had in November of 2016 installed Debian on this then-new server
using:
debian-8.6.0-amd64-netinst.iso
and then installed Xen using the above instructions.
What I propose to do now is duplicate my steps of November 2016.
If I succeed in launching DOM0 as I did in November/December 2016,
then we'll know this is a software issue. If I fail, then I'd conclude
there is a hardware problem. Recall, though I can install a standard
build of Debian 9.9 and Gentoo and the kernels load, it's only when
I have a Xen modified kernel that the boot-up hangs.
I'm not familiar with Debian other than I have easily installed it
before. What would help me are some pointers to make sure
the Debian 8.6.0 does not go into auto-update mode and to identify and
select
the Xen packages which were the high watermark in November 2016.
John
[-- Attachment #1.2: Type: text/html, Size: 2657 bytes --]
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
reply other threads:[~2019-05-29 21:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=15101486-c6a3-536d-eddb-52a9cc3731b8@gmail.com \
--to=jlpoole56@gmail.com \
--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).