On 2/2/2024 11:25 AM, David Woodhouse wrote:
> On Thu, 2024-02-01 at 18:39 +0000, John L. Poole wrote:
>> While the Xen Project "make" works, the Gentoo emerge
>> of app-emulation/xen-tools does not unless the three lines are
>> removed to simulate prior 4.17.3 an
On Thursday, February 1st, 2024 at 9:18 AM, David Woodhouse
wrote:
> (Thanks Andy for the explicit cc)
>
> On Thu, 2024-02-01 at 00:05 +0000, John L. Poole wrote:
>
> > cause Gentoo's build to error out. See line 24790:
> >
> > 5 | #error In Xen native file
Greetings,
Gentoo Linux maintains two packages for Xen:
1) app-emulation/xen-tools ("xen-tools")
2) app-emulation/xen ("xen")
xen-tools is a prerequisite to xen. So a failure
to install xen-tools will preclude any attempt to install xen.
I acknowledge that building xen-tools before
Greetings,
I try to run Xen on low energy platforms. I've previously been here
about an Intal Atom which died
just after the 3 year warranty expired. So I'm trying AMD's laptop
Ryzen. I think I've been using Xen
for 8 years.
I have Debian (Linux snuc 4.19.0-13-amd64 #1 SMP Debian
On 5/28/2019 8:02 AM, John L. Poole wrote:
On 5/28/2019 12:41 AM, Roger Pau Monné wrote:
On Mon, May 27, 2019 at 03:35:21PM -0700, John L. Poole wrote:
On 5/27/2019 9:18 AM, Roger Pau Monné wrote:
On Mon, Apr 29, 2019 at 05:27:34PM +0200, Roger Pau Monné wrote:
IMO it would be better
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:
On 5/28/2019 12:41 AM, Roger Pau Monné wrote:
On Mon, May 27, 2019 at 03:35:21PM -0700, John L. Poole wrote:
On 5/27/2019 9:18 AM, Roger Pau Monné wrote:
On Mon, Apr 29, 2019 at 05:27:34PM +0200, Roger Pau Monné wrote:
IMO it would be better if you can build directly from the upstream git
On 5/28/2019 12:41 AM, Roger Pau Monné wrote:
On Mon, May 27, 2019 at 03:35:21PM -0700, John L. Poole wrote:
On 5/27/2019 9:18 AM, Roger Pau Monné wrote:
On Mon, Apr 29, 2019 at 05:27:34PM +0200, Roger Pau Monné wrote:
IMO it would be better if you can build directly from the upstream git
On 5/27/2019 9:18 AM, Roger Pau Monné wrote:
On Mon, Apr 29, 2019 at 05:27:34PM +0200, Roger Pau Monné wrote:
IMO it would be better if you can build directly from the upstream git
repository [0], that way you could use git-bisect(1) in order to figure
out which commit broke your system. For
On 4/29/2019 5:02 AM, Roger Pau Monné wrote:
On Tue, Apr 16, 2019 at 09:23:11AM -0700, John L. Poole wrote:
On 3/27/2019 7:21 AM, Jan Beulich wrote:
On 27.03.19 at 14:25, wrote:
On 3/27/2019 1:14 AM, Jan Beulich wrote:
On 26.03.19 at 18:21, wrote:
zeta /usr/local/src/xen # cat xen
On 3/27/2019 7:21 AM, Jan Beulich wrote:
On 27.03.19 at 14:25, wrote:
On 3/27/2019 1:14 AM, Jan Beulich wrote:
On 26.03.19 at 18:21, wrote:
zeta /usr/local/src/xen # cat xen/.config |grep CONFIG_HVM
# CONFIG_HVM is not set
zeta /usr/local/src/xen #
# tried 2 boot attempts
log at:
On 3/27/2019 1:14 AM, Jan Beulich wrote:
On 26.03.19 at 18:21, wrote:
zeta /usr/local/src/xen # cat xen/.config |grep CONFIG_HVM
# CONFIG_HVM is not set
zeta /usr/local/src/xen #
# tried 2 boot attempts
log at: https://pastebin.com/nL4BWJ6Y
Hang points at lines:
Thanks for trying anyway;
On 3/26/2019 1:04 AM, Jan Beulich wrote:
On 25.03.19 at 18:00, wrote:
I removed the "maxcpus=1" and attempted seven (7) boots.
There were minor variations, they do not seem to get
past the first additional processor. Below is a summary.
And with "maxcpus=1" in place, is it as stable hanging
On 3/25/2019 8:53 AM, Jan Beulich wrote:
On 22.03.19 at 10:53, wrote:
2) Xen Source - here is the log of an attempt adding "cpuinfor maxcpus=1"
as an option in myman_xen.cfg:
https://pastebin.com/ifHZqCuX (6months)
Well, the "maxcpus=1" doesn't really hide the issue (anymore) because
we now
On 3/23/2019 11:50 PM, Roger Pau Monné wrote:
On Fri, Mar 22, 2019 at 05:46:26PM -0700, John L. Poole wrote:
On 3/22/2019 7:40 AM, Andrew Cooper wrote:
On 22/03/2019 09:53, John L. Poole wrote:
3)Xen Source - here is the log of an attempt adding
"cpuinfor maxcpus=1 watchdog"
as
On 3/22/2019 7:40 AM, Andrew Cooper wrote:
On 22/03/2019 09:53, John L. Poole wrote:
3)Xen Source - here is the log of an attempt adding
"cpuinfor maxcpus=1 watchdog"
as an option in myman_xen.cfg:
https://pastebin.com/b682FWmC (6 months)
The last 12 lines:
(XEN) [2019-03-22 09:37:4
On 3/22/2019 12:59 AM, Roger Pau Monné wrote:
On Thu, Mar 21, 2019 at 10:06:38AM -0700, John L. Poole wrote:
Boot Hangs at: HVM: HAP page sizes: 4kB, 2MB or Adding cpu [INSERT 1-7] to
runqueue 0
Log (preserved for 6 months at https://pastebin.com/BDPP7Pzk)
fs0:\efi\gentoo> man_xen.ef
Boot Hangs at: HVM: HAP page sizes: 4kB, 2MB or Adding cpu [INSERT 1-7]
to runqueue 0
Log (preserved for 6 months at https://pastebin.com/BDPP7Pzk)
fs0:\efi\gentoo> man_xen.efiip startup.nsh, any other key to continue.
Xen 4.12.0-rc (c/s Mon Feb 25 13:06:22 2019 + git:f393b82fe5-dirty)
On 3/15/2019 2:30 PM, Andrew Cooper wrote:
On 15/03/2019 20:49, Andrew Cooper wrote:
On 15/03/2019 18:35, John L. Poole wrote:
I have a Supermicro Intel Atom based server with UEFI. I purchased the
server in November 2016 intending to run Xen server. I was able
to overcome some problem
On 3/15/2019 1:49 PM, Andrew Cooper wrote:
On 15/03/2019 18:35, John L. Poole wrote:
I have a Supermicro Intel Atom based server with UEFI. I purchased the
server in November 2016 intending to run Xen server. I was able
to overcome some problem in 2016 with help from the Xen Project and
I
I have a Supermicro Intel Atom based server with UEFI. I purchased the
server in November 2016 intending to run Xen server. I was able
to overcome some problem in 2016 with help from the Xen Project and
I was able to load a xen kernel built in Gentoo for Gentoo VMs manually
using the EFI
21 matches
Mail list logo
