Re: [Xen-devel] FAILED/MISSING cstate/cpufreq/cpupower support with Xen 4.13 + kernel 5.4.14; withOUT xen/hypervisor, WORKS. bug or config?

2020-01-29 Thread PGNet Dev
with xen cmd line opts reduced to options=dom0_max_vcpus=4 dom0_mem=4016M,max:4096M loglvl=all guest_loglvl=all noreboot=false sync_console=true sched_debug iommu=verbose apic_verbosity=verbose still no freq data/control and, xl dmesg (XEN) 92118000 -

[Xen-devel] FAILED/MISSING cstate/cpufreq/cpupower support with Xen 4.13 + kernel 5.4.14; withOUT xen/hypervisor, WORKS. bug or config?

2020-01-28 Thread PGNet Dev
( posted this already to xen-users, and @ distro list; advised to bring it here ) I'm running linux kernel lsb_release -rd Description:openSUSE Leap 15.1 Release:15.1 uname -rm 5.4.14-25.g170524c-default x86_64

Re: [Xen-devel] xen 4.13 + kernel 5.4.11 'APIC Error ... FATAL PAGE FAULT' on reboot? non-Xen reboot's ok.

2020-01-15 Thread PGNet Dev
On 1/15/20 9:21 AM, Andrew Cooper wrote: > That is the command line for dom0 which is a VM.  You need the Xen > hypervisor command line. thx. done. > You'll need to edit xen-4.13.0_04-lp151.688.cfg which will be somewhere > on the ESP (wherever that is mounted in an openSUSE system).

Re: [Xen-devel] xen 4.13 + kernel 5.4.11 'APIC Error ... FATAL PAGE FAULT' on reboot? non-Xen reboot's ok.

2020-01-15 Thread PGNet Dev
hi On 1/15/20 9:10 AM, Andrew Cooper wrote: >> Is this a known/fixable issue? > > The APIC errors aren't fatal. They need looking into and addressing in > due course. > > The real crash is EFI firmware falling over a NULL pointer which is > wildly known issue. Fixing it requires following the

[Xen-devel] xen 4.13 + kernel 5.4.11 'APIC Error ... FATAL PAGE FAULT' on reboot? non-Xen reboot's ok.

2020-01-15 Thread PGNet Dev
dev @distro suggested I post this here ... I've a recently upgraded Xen & Kernel on lsb_release -rd Description:openSUSE Leap 15.1 Release:15.1 Atm, I'm running Xen 4.13.0_04 server, on EFI hardware + Intel Xeon E3 CPU, with kernel

Re: [Xen-devel] Xen 4.12.0 Dom0=pvh mode EFI variables 'not supported' after boot

2019-05-27 Thread PGNet Dev
Let's clarify this a bit: a very useful & clear reply -- if that's all in the docs/wiki already, I managed to miss it! thx! ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel

Re: [Xen-devel] Xen 4.12.0 Dom0=pvh mode EFI variables 'not supported' after boot

2019-05-24 Thread PGNet Dev
After upgrading Kernel to 5.1.4/release on an x86_64 server, Xen 4.12.0 Dom0 successfully boots in PVH mode (dom0=pvh ...), with efi vars available so that efibootmgr functions, xl list NameID Mem VCPUs State Time(s)

Re: [Xen-devel] Xen 4.12.0 Dom0=pvh mode EFI variables 'not supported' after boot

2019-04-20 Thread PGNet Dev
On 4/18/19 5:52 AM, Roger Pau Monné wrote: >> Given some of the build 'fun' I've been having today, I'll take a closer >> look at the patched kernel build in the morning -- to make doubly sure I >> actually built correctly. finally! got that cleaned up. > OK, that patch seemed to fix the issue

Re: [Xen-devel] Xen 4.12.0 Dom0=pvh mode EFI variables 'not supported' after boot

2019-04-17 Thread PGNet Dev
On 4/17/19 8:30 PM, PGNet Dev wrote: > Thx. > > not ignoring you -- opensuse kernel build system is having a hissy-fit > atm; builds are failing. :-/ > > if I can't get it to behave a build a nice pkg for me, I'll work on a > manual spin. With a pkg instance of your

Re: [Xen-devel] Xen 4.12.0 Dom0=pvh mode EFI variables 'not supported' after boot

2019-04-17 Thread PGNet Dev
Monné wrote: Adding the Linux Xen maintainers, in case they can provide some insight. On Mon, Apr 15, 2019 at 03:27:43PM -0700, PGNet Dev wrote: ref: from chat in #xen [08:53] pgnd: would be good to send an email so we can keep track of this in a more formal way. I've got Xen PV Dom0

[Xen-devel] Xen 4.12.0 Dom0=pvh mode EFI variables 'not supported' after boot

2019-04-15 Thread PGNet Dev
ref: from chat in #xen [08:53] pgnd: would be good to send an email so we can keep track of this in a more formal way. I've got Xen PV Dom0 booted on a Linux UEFI box dmesg | grep -i "xen version" [1.185996] Xen version: 4.12.0_09-lp150.640 (preserve-AD)