Hej, > Am 28.07.2022 um 21:29 schrieb cirr%sdf.org@localhost: > > Hello, I'm attempting to get Xen running on an HP DL360p gen 8 and am > using configurations based on several successful supermicro instances. > > * NetBSD-9.2 > * xentools-4.11 > * xenkernel-4.15 (tried xenkernel-4.11 and xenkernel-4.13 as well) On my DL380p gen8 i am using xenkernel 4.15.3 and xentools 4.15.3 under the assumption that things should be all from the same release. That works fine and boots with the following boot.cfg line: menu=Boot Xen com:load /netbsd-XEN3_DOM0 root=dk8 console=com1,115200;multiboot /xen.gz dom0_mem=32768M dom0_max_vcpus=6 console=com2 com2=115200,8n1,0x2f8 that currently boots uncompressed XEN3_DOM0 from current as of June 26th (9.99.98) > > Processor Options are: > > * No-Execute Memory Protection - disabled I have this set to enabled. > * Intel(R) Virtualization Technology - enabled > * Intel(R) Hyperthreading Options - (tried both enabled and disabled) I have this enabled, but disabled did work also. > > First issue was "Heap Full" which was improved by uncompressing > netbsd-XEN3_DOM0.gz and updating /boot.cfg based on a previous post to the > list. > > That resulted in the system booting, but then almost immediately rebooting. > > Second issue was warnings about L1TF-vulnerable hardware with > SMT/Hyperthreading enabled. Added 'smt=1' to /boot.cfg in the multiboot > section for the 'xen.gz' kernel. I just ignored that. I don’t know if that makes a difference > The system boots up to no errors, with the last portion being in regard to > VIRTUAL MEMORY ARRANGEMENT and finally '(XEN) Dom0 has maximum 1VCPU(s)' > which is what is set in boot.cfg. However, it then immediately reboots > after: > > (XEN) Initial low memory virq threshold set at 0x4000 pages. > (XEN) Scrubbing Free RAM on 1 nodes using 6 CPUs > (XEN) ..... last lines are: (XEN) Initial low memory virq threshold set at 0x4000 pages. (XEN) Scrubbing Free RAM in background (XEN) Std. Loglevel: Errors and warnings (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) (XEN) *************************************************** (XEN) Booted on L1TF-vulnerable hardware with SMT/Hyperthreading (XEN) enabled. Please assess your configuration and choose an (XEN) explicit 'smt=<bool>' setting. See XSA-273. (XEN) *************************************************** (XEN) Booted on MLPDS/MFBDS-vulnerable hardware with SMT/Hyperthreading (XEN) enabled. Mitigations will not be fully effective. Please (XEN) choose an explicit smt=<bool> setting. See XSA-297. (XEN) *************************************************** (XEN) 3... 2... 1... (XEN) *** Serial input to DOM0 (type 'CTRL-a' three times to switch input) (XEN) Freed 604kB init memory [ 1.0000000] Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, [ 1.0000000] 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, > > boot.cfg looks like this: > > menu=Xen:load /netbsd-XEN3_DOM0;multiboot /xen.gz allow_unsafe=true > dom0_mem=1024M dom0_max_vcpus=1 dom0_vcpus_pin smt=1 > menu=Boot normally:rndseed /var/db/entropy-file;boot netbsd > menu=Boot single user:rndseed /var/db/entropy-file;boot netbsd -s > menu=Disable ACPI:rndseed /var/db/entropy-file;boot netbsd -2 > menu=Disable ACPI and SMP:rndseed /var/db/entropy-file;boot netbsd -12 > menu=Drop to boot prompt:prompt I really don’t know, but the cpu_pinning, only one gig mem and the explicit smt are the only differences i can think of as relevant. Godd luck experimentig ;-) Cheers Oskar
Attachment:
smime.p7s
Description: S/MIME cryptographic signature