Continuing from discussion at https://groups.google.com/g/qubes-users/c/gsGnRuN1A7k
–
There’s a bunch of new commits for Xen on the master branch.
Specifically there’s an AMD Commit here, I tried exporting this commit however it didn’t apply to the specific branch Qubes 4.1 is using.
I’ll try manually apply this and see how it goes.
We’re actually missing quite a few commits for AMD’s passthru drivers
Last commit for 4.13.1 was in April 2020, master we’re talking August 15 2020 (Few weeks ago)
Does anyone know what the update cycle is like for Xen on Qubes? I’m guessing if I try rebase 4.13.1 to master it’ll break all of the other Qubes related patches.
In any case I’ll try manually splice in some of these commits, I can’t see anything that directly relates to gpu/black screen issues tho.
I managed to compile 4.14 from @marmarek’s Github
However it seems to not be possible to splice Xen from a R4.1 ISO, I think this is because the ISO is laid out differently now, it’s not possible to simply load the ISO onto a USB and edit files anymore.
Sorry about that. I’ve approved your posts now. I’ll look into this!
Edit: I’ve promoted you to basic user. It shouldn’t happen anymore
(the reason was discourse sometimes flags posts from new users with a few links in them, but this kind of disregards the fact that people may already be coming from another forum / mailing list.)
No worries deeplow, thanks
Some good news! I’ve managed to compile an ISO from @marmarek’s Github repo and it boots! 
Complete!
-> Building installer-qubes-os iso for fc32 (logfile: build-logs/installer-qubes-os-iso-fc32.log)...
--> Done:
The ISO can be found in iso/ subdirectory.
Thank you for building Qubes. Have a nice day!
Specifically with
BRANCH_vmm_xen = xen-4.14
BRANCH_linux_kernel = master
So 4.14 and master branch of the Kernel currently 5.8.1
I’m going to attempt to diff Xen 4.13.1 with 4.14 to see if I can cherrypick the fix into Xen 4.8 (Qubes 4.0.3)
[dylanger] dylanger https://forum.qubes-os.org/u/dylanger
August 27No worries deeplow, thanks
Some good news! I’ve managed to compile an ISO from @marmarek
https://forum.qubes-os.org/u/marmarek’s Github repo and it
boots!
No kidding? That’s awesome… good work!
Complete! → Building installer-qubes-os iso for fc32 (logfile:
build-logs/installer-qubes-os-iso-fc32.log)… → Done: The ISO can be
found in iso/ subdirectory. Thank you for building Qubes. Have a nice day! |Specifically with
BRANCH_vmm_xen = xen-4.14 BRANCH_linux_kernel = master |
So 4.14 and master branch of the Kernel currently 5.8.1
I’m going to attempt to diff Xen 4.13.1 with 4.14 to see if I can
cherrypick the fix into Xen 4.8 (Qubes 4.0.3)
If that doesn’t easily work for 4.0.3 / Xen 4.8, I would be willing to
try using Qubes 4.1 on my system.
The changes between 4.8.5 and 4.14 are, large.
I think we may be better off using Qubes 4.1, however I’m concerned around trust, I like the fact Qubes’s team signs ISOs.
During the make get-sources stage, I do believe every commit is signed and verified when checking out every repo.
In any case @marmarek has 4.14 in his testing repo, so expect 4.14 to land in OpenQA’s (https://openqa.qubes-os.org/assets/iso/Qubes-4.1-{DATE}-x86_64.iso) assets directory soon, at least I know I don’t need to return this X13.
If anyone is interested in compiling from Marek’s repo, here’s the builder.conf I used, note I removed all debian templates etc, I also haven’t attempted to actually install, I built this just to test it would boot.
My immediate question is, can the Qubes team start signing these releases? Or maybe another way to ask this is when will we see 4.1 RC?
My immediate question is, can the Qubes team start signing these releases? Or maybe another way to ask this is when will we see 4.1 RC?
I’ve had a similar problem with my laptop that required at least Xen
4.12. My solution was much the same as yours: build the ISO myself.
The problem with signing the OpenQA builds is not necessarily trusting
the infrastructure they are built on. There was a thread about getting
hashes/signatures on the mailing list a while back which makes me doubt
there will ever be signatures for them.
Given that you’ve provided your builder.conf, it shouldn’t be too hard
for others to follow your build and get a trusted ISO.
4.14 has been merged into the QubesOS Repo.
I had to accept a bunch of “Warning, don’t rely on this yet” confirmations.
Are we low-key past that or should I not use 4.1 as my daily yet?
4.14 has been merged into the QubesOS Repo.
I had to accept a bunch of “Warning, don’t rely on this yet” confirmations.
Are we low-key past that or should I not use 4.1 as my daily yet?
While there are plenty who do run R4.1 daily, be ready for things to
break as it is under heavy development.
As an example, that Xen 4.14 package broke HVMs (meaning sys-net and
sys-usb). It has since been pulled from the repos, but I got the update
a few minutes before that.
R4.1 works, but it should not be considered stable at this time.
Ah, I just installed and noticed sys-usb and sys-net are not coming up.
I’m eagerly awaiting the fix 
I was able to install and boot QubesOS 4.1 (Linux 5.4, Xen 4.14) on the AMD V1605B (Udoo Bolt Gear) flawlessly. But the ‘sys-net’ HVM was not brought up. PVH Domains worked perfectly fine.
I am guessing we could have the same issue here.
In my case, the creation of the sys-net-HVM fails here:
(XEN) MMIO emulation failed (1): d1v0 32bit @ 0008:fffeedfd ->
(XEN) d1v0 Triple fault - invoking HVM shutdown action 1
(XEN) parameter "no-real-mode" unknown!
(XEN) parameter "edd" unknown!
Xen 4.14.0
(XEN) Xen version 4.14.0 (user@[unknown]) (gcc (GCC) 10.2.1 20200723 (Red Hat 10.2.1-1)) debug=n Mon Aug 31 11:18:36 UTC 2020
(XEN) Latest ChangeSet:
(XEN) build-id: 38c97e5f5908dcc9d9416f530247bb81b2464d1d
(XEN) Bootloader: GRUB 2.04
(XEN) Command line: placeholder console=none dom0_mem=min:1024M dom0_mem=max:4096M ucode=scan smt=off gnttab_max_frames=2048 gnttab_max_maptrack_frames=4096 loglvl=all guest_loglvl=all no-real-mode edd=off
(XEN) Xen image load base address: 0xa5e00000
(XEN) Video information:
(XEN) VGA is graphics mode 1920x1080, 32 bpp
(XEN) Disc information:
(XEN) Found 0 MBR signatures
(XEN) Found 1 EDD information structures
(XEN) CPU Vendor: AMD, Family 23 (0x17), Model 17 (0x11), Stepping 0 (raw 00810f10)
(XEN) EFI RAM map:
(XEN) [0000000000000000, 000000000009ffff] (usable)
(XEN) [00000000000a0000, 00000000000fffff] (reserved)
(XEN) [0000000000100000, 0000000009601fff] (usable)
(XEN) [0000000009602000, 00000000097fffff] (reserved)
(XEN) [0000000009800000, 000000000a1fffff] (usable)
(XEN) [000000000a200000, 000000000a209fff] (ACPI NVS)
(XEN) [000000000a20a000, 00000000ad00afff] (usable)
(XEN) [00000000ad00b000, 00000000adaedfff] (reserved)
(XEN) [00000000adaee000, 00000000adb7efff] (usable)
(XEN) [00000000adb7f000, 00000000adcd4fff] (ACPI NVS)
(XEN) [00000000adcd5000, 00000000ae526fff] (reserved)
(XEN) [00000000ae527000, 00000000aeffffff] (usable)
(XEN) [00000000af000000, 00000000efffffff] (reserved)
(XEN) [00000000f8000000, 00000000fbffffff] (reserved)
(XEN) [00000000fd100000, 00000000fdffffff] (reserved)
(XEN) [00000000feb80000, 00000000fec01fff] (reserved)
(XEN) [00000000fec10000, 00000000fec10fff] (reserved)
(XEN) [00000000fed00000, 00000000fed00fff] (reserved)
(XEN) [00000000fed40000, 00000000fed44fff] (reserved)
(XEN) [00000000fed80000, 00000000fed8ffff] (reserved)
(XEN) [00000000fedc2000, 00000000fedcffff] (reserved)
(XEN) [00000000fedd4000, 00000000fedd5fff] (reserved)
(XEN) [00000000fee00000, 00000000feefffff] (reserved)
(XEN) [00000000ff000000, 00000000ffffffff] (reserved)
(XEN) [0000000100000000, 000000080f33ffff] (usable)
(XEN) [000000080f340000, 000000080fffffff] (reserved)
(XEN) ACPI: RSDP ADB7F000, 0024 (r2 ALASKA)
(XEN) ACPI: XSDT ADB7F098, 00AC (r1 ALASKA A M I 1072009 AMI 10013)
(XEN) ACPI: FACP ADB87910, 0114 (r6 ALASKA A M I 1072009 AMI 10013)
(XEN) ACPI: DSDT ADB7F1D8, 8738 (r2 ALASKA A M I 1072009 INTL 20120913)
(XEN) ACPI: FACS ADCBFF00, 0040
(XEN) ACPI: APIC ADB87A28, 00DE (r3 ALASKA A M I 1072009 AMI 10013)
(XEN) ACPI: FPDT ADB87B08, 0044 (r1 ALASKA A M I 1072009 AMI 10013)
(XEN) ACPI: FIDT ADB87B50, 009C (r1 ALASKA A M I 1072009 AMI 10013)
(XEN) ACPI: SSDT ADB87BF0, 5419 (r2 AMD AmdTable 2 MSFT 2000002)
(XEN) ACPI: CRAT ADB8D010, 0810 (r1 AMD AMD CRAT 1 AMD 1)
(XEN) ACPI: CDIT ADB8D820, 0029 (r1 AMD AMD CDIT 1 AMD 1)
(XEN) ACPI: MCFG ADB8D850, 003C (r1 ALASKA A M I 1072009 MSFT 10013)
(XEN) ACPI: HPET ADB8D890, 0038 (r1 ALASKA A M I 1072009 AMI 5)
(XEN) ACPI: UEFI ADB8D8C8, 0048 (r1 0 0)
(XEN) ACPI: VFCT ADB8D910, D484 (r1 ALASKA A M I 1 AMD 31504F47)
(XEN) ACPI: BGRT ADB9AD98, 0038 (r1 ALASKA A M I 1072009 AMI 10013)
(XEN) ACPI: IVRS ADB9ADD0, 00D0 (r2 AMD AMD IVRS 1 AMD 0)
(XEN) ACPI: SSDT ADB9AEA0, 0C33 (r1 AMD AmdTable 1 INTL 20120913)
(XEN) ACPI: SSDT ADB9BAD8, 1B4E (r1 AMD AmdTable 1 INTL 20120913)
(XEN) ACPI: SSDT ADB9D628, 119C (r1 AMD AMD CPU 1 AMD 1)
(XEN) ACPI: WSMT ADB9E7C8, 0028 (r1 ALASKA A M I 1072009 AMI 10013)
(XEN) System RAM: 31692MB (32452916kB)
(XEN) No NUMA configuration found
(XEN) Faking a node at 0000000000000000-000000080f340000
(XEN) Domain heap initialised
(XEN) SMBIOS 3.1 present.
(XEN) Using APIC driver default
(XEN) ACPI: PM-Timer IO Port: 0x808 (32 bits)
(XEN) ACPI: v5 SLEEP INFO: control[0:0], status[0:0]
(XEN) ACPI: SLEEP INFO: pm1x_cnt[1:804,1:0], pm1x_evt[1:800,1:0]
(XEN) ACPI: 32/64X FACS address mismatch in FADT - adcbff00/0000000000000000, using 32
(XEN) ACPI: wakeup_vec[adcbff0c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x04] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x05] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x06] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x07] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x09] lapic_id[0x00] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x00] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x00] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x00] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x00] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x00] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x00] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x10] lapic_id[0x00] disabled)
(XEN) ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
(XEN) ACPI: IOAPIC (id[0x09] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 9, version 33, address 0xfec00000, GSI 0-23
(XEN) ACPI: IOAPIC (id[0x0a] address[0xfec01000] gsi_base[24])
(XEN) IOAPIC[1]: apic_id 10, version 33, address 0xfec01000, GSI 24-55
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode: Flat. Using 2 I/O APICs
(XEN) ACPI: HPET id: 0x10228201 base: 0xfed00000
(XEN) PCI: MCFG configuration 0: base f8000000 segment 0000 buses 00 - 3f
(XEN) PCI: MCFG area at f8000000 reserved in E820
(XEN) PCI: Using MCFG for segment 0000 bus 00-3f
(XEN) ACPI: BGRT: invalidating v1 image at 0xaa599018
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) SMP: Allowing 16 CPUs (8 hotplug CPUs)
(XEN) IRQ limits: 56 GSI, 1608 MSI/MSI-X
(XEN) CPU0: 1600..2000 MHz
(XEN) xstate: size: 0x340 and states: 0x7
(XEN) CPU0: AMD Fam17h machine check reporting enabled
(XEN) Speculative mitigation facilities:
(XEN) Hardware features: IBPB
(XEN) Compiled-in support: INDIRECT_THUNK
(XEN) Xen settings: BTI-Thunk LFENCE, SPEC_CTRL: No, Other: IBPB BRANCH_HARDEN
(XEN) Support for HVM VMs: RSB
(XEN) Support for PV VMs: RSB
(XEN) XPTI (64-bit PV only): Dom0 disabled, DomU disabled (without PCID)
(XEN) PV L1TF shadowing: Dom0 disabled, DomU disabled
(XEN) Using scheduler: SMP Credit Scheduler rev2 (credit2)
(XEN) Initializing Credit2 scheduler
(XEN) load_precision_shift: 18
(XEN) load_window_shift: 30
(XEN) underload_balance_tolerance: 0
(XEN) overload_balance_tolerance: -3
(XEN) runqueues arrangement: socket
(XEN) cap enforcement granularity: 10ms
(XEN) load tracking window length 1073741824 ns
(XEN) Platform timer is 14.318MHz HPET
(XEN) Detected 1996.215 MHz processor.
(XEN) EFI memory map:
(XEN) 0000000000000-0000000003fff type=2 attr=000000000000000f
(XEN) 0000000004000-000000008ffff type=7 attr=000000000000000f
(XEN) 0000000090000-000000009ffff type=2 attr=000000000000000f
(XEN) 0000000100000-0000000822fff type=2 attr=000000000000000f
(XEN) 0000000823000-0000000ffffff type=7 attr=000000000000000f
(XEN) 0000001000000-000000101ffff type=4 attr=000000000000000f
(XEN) 0000001020000-000000360efff type=2 attr=000000000000000f
(XEN) 000000360f000-0000009601fff type=7 attr=000000000000000f
(XEN) 0000009602000-00000097fffff type=0 attr=000000000000000f
(XEN) 0000009800000-000000a1fffff type=7 attr=000000000000000f
(XEN) 000000a200000-000000a209fff type=10 attr=000000000000000f
(XEN) 000000a20a000-000007e5ecfff type=7 attr=000000000000000f
(XEN) 000007e5ed000-00000a8801fff type=1 attr=000000000000000f
(XEN) 00000a8802000-00000a8802fff type=2 attr=000000000000000f
(XEN) 00000a8803000-00000a8808fff type=7 attr=000000000000000f
(XEN) 00000a8809000-00000a89d0fff type=1 attr=000000000000000f
(XEN) 00000a89d1000-00000aca0afff type=4 attr=000000000000000f
(XEN) 00000aca0b000-00000accf5fff type=7 attr=000000000000000f
(XEN) 00000accf6000-00000ad00afff type=3 attr=000000000000000f
(XEN) 00000ad00b000-00000adaedfff type=0 attr=000000000000000f
(XEN) 00000adaee000-00000adb7efff type=7 attr=000000000000000f
(XEN) 00000adb7f000-00000adcd4fff type=10 attr=000000000000000f
(XEN) 00000adcd5000-00000ae488fff type=6 attr=800000000000000f
(XEN) 00000ae489000-00000ae526fff type=5 attr=800000000000000f
(XEN) 00000ae527000-00000ae6a9fff type=4 attr=000000000000000f
(XEN) 00000ae6aa000-00000ae6c7fff type=3 attr=000000000000000f
(XEN) 00000ae6c8000-00000ae6f6fff type=4 attr=000000000000000f
(XEN) 00000ae6f7000-00000ae70bfff type=3 attr=000000000000000f
(XEN) 00000ae70c000-00000aef89fff type=4 attr=000000000000000f
(XEN) 00000aef8a000-00000aef90fff type=3 attr=000000000000000f
(XEN) 00000aef91000-00000aefb5fff type=4 attr=000000000000000f
(XEN) 00000aefb6000-00000aefc5fff type=3 attr=000000000000000f
(XEN) 00000aefc6000-00000aefe6fff type=4 attr=000000000000000f
(XEN) 00000aefe7000-00000aeffffff type=3 attr=000000000000000f
(XEN) 0000100000000-000080f33ffff type=7 attr=000000000000000f
(XEN) 00000000a0000-00000000fffff type=0 attr=000000000000000f
(XEN) 00000af000000-00000efffffff type=0 attr=000000000000000f
(XEN) 00000f8000000-00000fbffffff type=11 attr=800000000000100d
(XEN) 00000fd100000-00000fdffffff type=11 attr=800000000000100d
(XEN) 00000feb80000-00000fec01fff type=11 attr=800000000000100d
(XEN) 00000fec10000-00000fec10fff type=11 attr=800000000000100d
(XEN) 00000fed00000-00000fed00fff type=11 attr=800000000000100d
(XEN) 00000fed40000-00000fed44fff type=11 attr=800000000000100d
(XEN) 00000fed80000-00000fed8ffff type=11 attr=800000000000100d
(XEN) 00000fedc2000-00000fedcffff type=11 attr=800000000000100d
(XEN) 00000fedd4000-00000fedd5fff type=11 attr=800000000000100d
(XEN) 00000fee00000-00000feefffff type=11 attr=800000000000100d
(XEN) 00000ff000000-00000ffffffff type=11 attr=800000000000100d
(XEN) 000080f340000-000080fffffff type=0 attr=000000000000000f
(XEN) alt table ffff82d0403ef0b0 -> ffff82d0403f8936
(XEN) AMD-Vi: IOMMU Extended Features:
(XEN) - Peripheral Page Service Request
(XEN) - NX bit
(XEN) - Invalidate All Command
(XEN) - Guest APIC
(XEN) - Performance Counters
(XEN) - Host Address Translation Size: 0x2
(XEN) - Guest Address Translation Size: 0
(XEN) - Guest CR3 Root Table Level: 0x1
(XEN) - Maximum PASID: 0xf
(XEN) - SMI Filter Register: 0x1
(XEN) - SMI Filter Register Count: 0x2
(XEN) - Guest Virtual APIC Modes: 0x1
(XEN) - Dual PPR Log: 0x2
(XEN) - Dual Event Log: 0x2
(XEN) - User / Supervisor Page Protection
(XEN) - Device Table Segmentation: 0x3
(XEN) - PPR Log Overflow Early Warning
(XEN) - PPR Automatic Response
(XEN) - Memory Access Routing and Control: 0x1
(XEN) - Block StopMark Message
(XEN) - Performance Optimization
(XEN) - MSI Capability MMIO Access
(XEN) - Guest I/O Protection
(XEN) - Host Access
(XEN) - Enhanced PPR Handling
(XEN) - Attribute Forward
(XEN) - Invalidate IOTLB Type
(XEN) - VM Table Size: 0
(XEN) AMD-Vi: Disabled HAP memory map sharing with IOMMU
(XEN) AMD-Vi: IOMMU 0 Enabled.
(XEN) I/O virtualisation enabled
(XEN) - Dom0 mode: Relaxed
(XEN) Interrupt remapping enabled
(XEN) nr_sockets: 2
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using new ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) Allocated console ring of 64 KiB.
(XEN) mwait-idle: does not run on family 23 model 17
(XEN) HVM: ASIDs enabled.
(XEN) SVM: Supported advanced features:
(XEN) - Nested Page Tables (NPT)
(XEN) - Last Branch Record (LBR) Virtualisation
(XEN) - Next-RIP Saved on #VMEXIT
(XEN) - VMCB Clean Bits
(XEN) - DecodeAssists
(XEN) - Virtual VMLOAD/VMSAVE
(XEN) - Virtual GIF
(XEN) - Pause-Intercept Filter
(XEN) - Pause-Intercept Filter Threshold
(XEN) - TSC Rate MSR
(XEN) HVM: SVM enabled
(XEN) HVM: Hardware Assisted Paging (HAP) detected
(XEN) HVM: HAP page sizes: 4kB, 2MB, 1GB
(XEN) alt table ffff82d0403ef0b0 -> ffff82d0403f8936
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) Brought up 4 CPUs
(XEN) Parked 4 CPUs
(XEN) Scheduling granularity: cpu, 1 CPU per sched-resource
(XEN) Adding cpu 0 to runqueue 0
(XEN) First cpu on runqueue, activating
(XEN) Adding cpu 2 to runqueue 0
(XEN) Adding cpu 4 to runqueue 1
(XEN) First cpu on runqueue, activating
(XEN) Adding cpu 6 to runqueue 1
(XEN) mcheck_poll: Machine check polling timer started.
(XEN) xenoprof: Initialization failed. AMD processor family 23 is not supported
(XEN) NX (Execute Disable) protection active
(XEN) Dom0 has maximum 888 PIRQs
(XEN) *** Building a PV Dom0 ***
(XEN) Xen kernel: 64-bit, lsb, compat32
(XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x3a00000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 00000007ec000000->00000007f0000000 (1022481 pages to be allocated)
(XEN) Init. ramdisk: 000000080cc11000->000000080f1ff2f9
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: ffffffff81000000->ffffffff83a00000
(XEN) Init. ramdisk: 0000000000000000->0000000000000000
(XEN) Phys-Mach map: 0000008000000000->0000008000800000
(XEN) Start info: ffffffff83a00000->ffffffff83a004b8
(XEN) Xenstore ring: 0000000000000000->0000000000000000
(XEN) Console ring: 0000000000000000->0000000000000000
(XEN) Page tables: ffffffff83a01000->ffffffff83a22000
(XEN) Boot stack: ffffffff83a22000->ffffffff83a23000
(XEN) TOTAL: ffffffff80000000->ffffffff83c00000
(XEN) ENTRY ADDRESS: ffffffff82cbd180
(XEN) Dom0 has maximum 4 VCPUs
(XEN) Initial low memory virq threshold set at 0x4000 pages.
(XEN) Scrubbing Free RAM in background
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) *** Serial input to DOM0 (type 'CTRL-a' three times to switch input)
(XEN) Freed 540kB init memory
(XEN) PCI add device 0000:00:00.0
(XEN) PCI add device 0000:00:00.2
(XEN) PCI add device 0000:00:01.0
(XEN) PCI add device 0000:00:01.1
(XEN) PCI add device 0000:00:01.2
(XEN) PCI add device 0000:00:01.6
(XEN) PCI add device 0000:00:01.7
(XEN) PCI add device 0000:00:08.0
(XEN) PCI add device 0000:00:08.1
(XEN) PCI add device 0000:00:08.2
(XEN) PCI add device 0000:00:14.0
(XEN) PCI add device 0000:00:14.3
(XEN) PCI add device 0000:00:18.0
(XEN) PCI add device 0000:00:18.1
(XEN) PCI add device 0000:00:18.2
(XEN) PCI add device 0000:00:18.3
(XEN) PCI add device 0000:00:18.4
(XEN) PCI add device 0000:00:18.5
(XEN) PCI add device 0000:00:18.6
(XEN) PCI add device 0000:00:18.7
(XEN) PCI add device 0000:01:00.0
(XEN) PCI add device 0000:03:00.0
(XEN) PCI add device 0000:04:00.0
(XEN) PCI add device 0000:05:00.0
(XEN) PCI add device 0000:05:00.1
(XEN) PCI add device 0000:05:00.2
(XEN) PCI add device 0000:05:00.3
(XEN) PCI add device 0000:05:00.4
(XEN) PCI add device 0000:05:00.5
(XEN) PCI add device 0000:05:00.6
(XEN) PCI add device 0000:05:00.7
(XEN) PCI add device 0000:06:00.0
(XEN) HVM d1v0 save: CPU
(XEN) HVM d1v1 save: CPU
(XEN) HVM d1 save: PIC
(XEN) HVM d1 save: IOAPIC
(XEN) HVM d1v0 save: LAPIC
(XEN) HVM d1v1 save: LAPIC
(XEN) HVM d1v0 save: LAPIC_REGS
(XEN) HVM d1v1 save: LAPIC_REGS
(XEN) HVM d1 save: PCI_IRQ
(XEN) HVM d1 save: ISA_IRQ
(XEN) HVM d1 save: PCI_LINK
(XEN) HVM d1 save: PIT
(XEN) HVM d1 save: RTC
(XEN) HVM d1 save: HPET
(XEN) HVM d1 save: PMTIMER
(XEN) HVM d1v0 save: MTRR
(XEN) HVM d1v1 save: MTRR
(XEN) HVM d1 save: VIRIDIAN_DOMAIN
(XEN) HVM d1v0 save: CPU_XSAVE
(XEN) HVM d1v1 save: CPU_XSAVE
(XEN) HVM d1v0 save: VIRIDIAN_VCPU
(XEN) HVM d1v1 save: VIRIDIAN_VCPU
(XEN) HVM d1v0 save: VMCE_VCPU
(XEN) HVM d1v1 save: VMCE_VCPU
(XEN) HVM d1v0 save: TSC_ADJUST
(XEN) HVM d1v1 save: TSC_ADJUST
(XEN) HVM d1v0 save: CPU_MSR
(XEN) HVM d1v1 save: CPU_MSR
(XEN) HVM1 restore: CPU 0
(d1) HVM Loader
(d1) Detected Xen v4.14.0
(d1) Xenbus rings @0xfeffc000, event channel 1
(d1) System requested SeaBIOS
(d1) CPU speed is 1996 MHz
(d1) Relocating guest memory for lowmem MMIO space enabled
(d1) PCI-ISA link 0 routed to IRQ5
(d1) PCI-ISA link 1 routed to IRQ10
(d1) PCI-ISA link 2 routed to IRQ11
(d1) PCI-ISA link 3 routed to IRQ5
(d1) pci dev 01:3 INTA->IRQ10
(d1) pci dev 02:0 INTA->IRQ11
(d1) pci dev 03:0 INTA->IRQ5
(d1) pci dev 05:0 INTD->IRQ5
(d1) No RAM in high memory; setting high_mem resource base to 100000000
(d1) pci dev 02:0 bar 14 size 001000000: 0f0000008
(d1) pci dev 04:0 bar 10 size 001000000: 0f1000008
(d1) pci dev 04:0 bar 30 size 000010000: 0f2000000
(d1) pci dev 03:0 bar 18 size 000002000: 0f2010000
(d1) pci dev 04:0 bar 18 size 000001000: 0f2012000
(d1) pci dev 05:0 bar 10 size 000001000: 0f2013000
(d1) pci dev 03:0 bar 14 size 000000400: 0f2014000
(d1) pci dev 02:0 bar 10 size 000000100: 00000c001
(d1) pci dev 03:0 bar 10 size 000000100: 00000c101
(d1) pci dev 01:1 bar 20 size 000000010: 00000c201
(d1) Multiprocessor initialisation:
(d1) - CPU0 ... 48-bit phys ... fixed MTRRs ... var MTRRs [1/8] ... done.
(d1) - CPU1 ... 48-bit phys ... fixed MTRRs ... var MTRRs [1/8] ... done.
(d1) Writing SMBIOS tables ...
(d1) Loading SeaBIOS ...
(d1) Creating MP tables ...
(d1) Loading ACPI ...
(d1) vm86 TSS at fc00a980
(d1) BIOS map:
(d1) 10000-100e3: Scratch space
(d1) e0000-fffff: Main BIOS
(d1) E820 table:
(d1) [00]: 00000000:00000000 - 00000000:000a0000: RAM
(d1) HOLE: 00000000:000a0000 - 00000000:000e0000
(d1) [01]: 00000000:000e0000 - 00000000:00100000: RESERVED
(d1) [02]: 00000000:00100000 - 00000000:18000000: RAM
(d1) HOLE: 00000000:18000000 - 00000000:fc000000
(d1) [03]: 00000000:fc000000 - 00000001:00000000: RESERVED
(d1) Invoking SeaBIOS ...
(XEN) MMIO emulation failed (1): d1v0 32bit @ 0008:fffeedfd ->
(XEN) d1v0 Triple fault - invoking HVM shutdown action 1
(XEN) *** Dumping Dom1 vcpu#0 state: ***
(XEN) ----[ Xen-4.14.0 x86_64 debug=n Not tainted ]----
(XEN) CPU: 0
(XEN) RIP: 0008:[<00000000fffeedfd>]
(XEN) RFLAGS: 0000000000000046 CONTEXT: hvm guest (d1v0)
(XEN) rax: 0000000000000000 rbx: 0000000000000000 rcx: 00000000fffeedfd
(XEN) rdx: 0000000000000059 rsi: 0000000000000000 rdi: 0000000000000000
(XEN) rbp: 0000000000000000 rsp: 0000000000006fe4 r8: 0000000000000000
(XEN) r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000000
(XEN) r12: 0000000000000000 r13: 0000000000000000 r14: 0000000000000000
(XEN) r15: 0000000000000000 cr0: 0000000000000011 cr4: 0000000000000000
(XEN) cr3: 0000000000000000 cr2: 0000000000000000
(XEN) fsb: 0000000000000000 gsb: 0000000000000000 gss: 0000000000000000
(XEN) ds: 0010 es: 0010 fs: 0010 gs: 0010 ss: 0010 cs: 0008
(XEN) HVM d3v0 save: CPU
(XEN) HVM d3v1 save: CPU
(XEN) HVM d3 save: PIC
(XEN) HVM d3 save: IOAPIC
(XEN) HVM d3v0 save: LAPIC
(XEN) HVM d3v1 save: LAPIC
(XEN) HVM d3v0 save: LAPIC_REGS
(XEN) HVM d3v1 save: LAPIC_REGS
(XEN) HVM d3 save: PCI_IRQ
(XEN) HVM d3 save: ISA_IRQ
(XEN) HVM d3 save: PCI_LINK
(XEN) HVM d3 save: PIT
(XEN) HVM d3 save: RTC
(XEN) HVM d3 save: HPET
(XEN) HVM d3 save: PMTIMER
(XEN) HVM d3v0 save: MTRR
(XEN) HVM d3v1 save: MTRR
(XEN) HVM d3 save: VIRIDIAN_DOMAIN
(XEN) HVM d3v0 save: CPU_XSAVE
(XEN) HVM d3v1 save: CPU_XSAVE
(XEN) HVM d3v0 save: VIRIDIAN_VCPU
(XEN) HVM d3v1 save: VIRIDIAN_VCPU
(XEN) HVM d3v0 save: VMCE_VCPU
(XEN) HVM d3v1 save: VMCE_VCPU
(XEN) HVM d3v0 save: TSC_ADJUST
(XEN) HVM d3v1 save: TSC_ADJUST
(XEN) HVM d3v0 save: CPU_MSR
(XEN) HVM d3v1 save: CPU_MSR
(XEN) HVM3 restore: CPU 0
(d3) HVM Loader
(d3) Detected Xen v4.14.0
(d3) Xenbus rings @0xfeffc000, event channel 1
(d3) System requested SeaBIOS
(d3) CPU speed is 1996 MHz
(d3) Relocating guest memory for lowmem MMIO space enabled
(d3) PCI-ISA link 0 routed to IRQ5
(d3) PCI-ISA link 1 routed to IRQ10
(d3) PCI-ISA link 2 routed to IRQ11
(d3) PCI-ISA link 3 routed to IRQ5
(d3) pci dev 01:3 INTA->IRQ10
(d3) pci dev 02:0 INTA->IRQ11
(d3) pci dev 03:0 INTA->IRQ5
(d3) pci dev 05:0 INTD->IRQ5
(d3) No RAM in high memory; setting high_mem resource base to 100000000
(d3) pci dev 02:0 bar 14 size 001000000: 0f0000008
(d3) pci dev 04:0 bar 10 size 001000000: 0f1000008
(d3) pci dev 04:0 bar 30 size 000010000: 0f2000000
(d3) pci dev 03:0 bar 18 size 000002000: 0f2010000
(d3) pci dev 04:0 bar 18 size 000001000: 0f2012000
(d3) pci dev 05:0 bar 10 size 000001000: 0f2013000
(d3) pci dev 03:0 bar 14 size 000000400: 0f2014000
(d3) pci dev 02:0 bar 10 size 000000100: 00000c001
(d3) pci dev 03:0 bar 10 size 000000100: 00000c101
(d3) pci dev 01:1 bar 20 size 000000010: 00000c201
(d3) Multiprocessor initialisation:
(d3) - CPU0 ... 48-bit phys ... fixed MTRRs ... var MTRRs [1/8] ... done.
(d3) - CPU1 ... 48-bit phys ... fixed MTRRs ... var MTRRs [1/8] ... done.
(d3) Writing SMBIOS tables ...
(d3) Loading SeaBIOS ...
(d3) Creating MP tables ...
(d3) Loading ACPI ...
(d3) vm86 TSS at fc00a980
(d3) BIOS map:
(d3) 10000-100e3: Scratch space
(d3) e0000-fffff: Main BIOS
(d3) E820 table:
(d3) [00]: 00000000:00000000 - 00000000:000a0000: RAM
(d3) HOLE: 00000000:000a0000 - 00000000:000e0000
(d3) [01]: 00000000:000e0000 - 00000000:00100000: RESERVED
(d3) [02]: 00000000:00100000 - 00000000:18000000: RAM
(d3) HOLE: 00000000:18000000 - 00000000:fc000000
(d3) [03]: 00000000:fc000000 - 00000001:00000000: RESERVED
(d3) Invoking SeaBIOS ...
(XEN) MMIO emulation failed (1): d3v0 32bit @ 0008:fffeedfd ->
(XEN) d3v0 Triple fault - invoking HVM shutdown action 1
(XEN) *** Dumping Dom3 vcpu#0 state: ***
(XEN) ----[ Xen-4.14.0 x86_64 debug=n Not tainted ]----
(XEN) CPU: 6
(XEN) RIP: 0008:[<00000000fffeedfd>]
(XEN) RFLAGS: 0000000000000046 CONTEXT: hvm guest (d3v0)
(XEN) rax: 0000000000000000 rbx: 0000000000000000 rcx: 00000000fffeedfd
(XEN) rdx: 0000000000000059 rsi: 0000000000000000 rdi: 0000000000000000
(XEN) rbp: 0000000000000000 rsp: 0000000000006fe4 r8: 0000000000000000
(XEN) r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000000
(XEN) r12: 0000000000000000 r13: 0000000000000000 r14: 0000000000000000
(XEN) r15: 0000000000000000 cr0: 0000000000000011 cr4: 0000000000000000
(XEN) cr3: 0000000000000000 cr2: 0000000000000000
(XEN) fsb: 0000000000000000 gsb: 0000000000000000 gss: 0000000000000000
(XEN) ds: 0010 es: 0010 fs: 0010 gs: 0010 ss: 0010 cs: 0008
Can you confirm that we have the same trouble here?
The very recent Kernel 5.4.62 has gotten a lot of amdgpu-related changes.
The Kernel for QubesOS 4.1 has version 5.4.61 at the moment.
5.4.62 is probably worth trying out.
Looks like Marek fixed this 3 hours ago
Does anyone know how to use the Qubes repo, but explicitly use Marek’s Repo for this specific repo?
Aw that didn’t actually fix the issue, it’s back open again.
it’s fixed soon
If you have a spare drive you could try the latest build until the fix is ready. sys-net & sys-usb did work (until I dared updating with testing repos enabled). I half-expected that this would happen as soon as I saw so many Xen 4.14 updates.
I had noticed other problems, for example “Suspend” didn’t work anymore but does with an earlier version.
Looks like Marek just pushed updates to vmm-xen, I’ll build and see how it goes!
Qubes won’t boot at all unless I’m running Xen 4.14?
Woo! It’s working!
I’m glad it all worked out in the end (of the longest running thread in the forum so far!). Maybe this now deserves an updated Hardware Compatbility List entry? @dylanger