PVH doesn't work. PV does.

mfp20 commented 4 years ago

(see below for HW/SW info)

I installed both 4.0.1 and 4.0.2-rc1 but the end result is always the same: 1) sys-firewall creation fails at configuration (after 1st reboot). Error message is about an internal error, "libxenlight failed to create" or alike. 2) VMs fail to start unless I change PVH to PV. 3) appmenus fail to update, untill I update the template VMs.

I've spotted similar issues, without clear solution (example).

The same system, rebooted into another linux distro (kernel 5.2.17), runs properly a KVM/Qemu4 Win10 system with dedicated GPU passtrough. So VT-d and VT-x are properly enabled in bios.

As the pcie ethernet device is part of a wider IOMMU group, I tried to remove the ethernet device from the sys-net VM, but didn't change anything: sys-net in PVH mode doesn't start.

I tried to update both dom0 and the TemplateVMs but problem persist: no PVH (and HVM).

Feel free to ask for logs, install upgraded packages or applying patches.

layout: 'hcl'
type: 'desktop'
hvm: 'yes'
iommu: 'yes'
slat: 'yes'
tpm: 'unknown'
remap: 'yes'
brand: ASUSTeK COMPUTER INC.
model: SABERTOOTH 990FX R3.0
bios: 0212
cpu-short: AMD FX-9590
chipset-short: 990FX
gpu-short:
  RX550
  RX580
network: Intel Corporation I211 Gigabit Network Connection (rev 03)
memory: 32660
scsi: none
usb: 10
versions:
- works: partial
  qubes: 4.0.2-rc1
  xen: 4.8.5-7.fc25
  kernel: 4.19.71-1
  remark: sys-firewall creation fails. Starting VMs fails. Can be fixed
  changing the virtualization mode from PVH to PV.
  credit: mfp
  link: github mfp20

fepitre commented 4 years ago

Have you tried to configure pci strict reset option in devices tab (sys-net HVM)?

marmarek commented 4 years ago

sys-net in PVH mode doesn't start.

You meant HVM, no? (PVH doesn't support PCI passthrough yet, although you should get clearer error).

mfp20 commented 4 years ago

@fepitre

Have you tried to configure pci strict reset option in devices tab (sys-net HVM)?

I didn't, but I will give it a go as soon as I am able to access the qubes system. I can't manage to boot it with refind nor direct mobo's uefi loader.

@marmarek

sys-net in PVH mode doesn't start.

You meant HVM, no? (PVH doesn't support PCI passthrough yet, although you should get clearer error).

The default I've found after the configuration reboot, was PVH. Then I tried HVM too. Both don't work, the only working mode is PV. Isn't a problem for sys-net only. No VM works in PVH (nor in HVM); I mean, even the ones without PCIe devices passtrough.

It must be some problem in dom0 or the TemplateVM; probably the configure step (after first reboot) didn't complete ("can't create sys-firewall", something about libxenlight), so all the machines came out unconfigured.

The only VM having a PCI device is sys-net; what about passing the whole iommu group?

IOMMU Group 15:
        00:15.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] SB700/SB800/SB900 PCI to PCI bridge (PCIE port 0) [1002:43a0]
        00:15.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] SB700/SB800/SB900 PCI to PCI bridge (PCIE port 1) [1002:43a1]
        08:00.0 USB controller [0c03]: ASMedia Technology Inc. ASM1143 USB 3.1 Host Controller [1b21:1343]
        09:00.0 Ethernet controller [0200]: Intel Corporation I211 Gigabit Network Connection [8086:1539] (rev 03)

I don't know about current Xen status, but KVM require for the whole group to be passed to the guest.

Maybe similar to #1393 ?

See above: I can't confirm looking at libvirt's logs as I can't boot the system using rEFInd.

iamahuman commented 4 years ago

Posting the usual logs (xenlight driver, xl dmesg, qubesd journal log and /var/log/qubes) would be appreciated.

How about testing whether Xen/libvirt actually works or not via creating VMs directly with xl or virsh? Trying switching to another version of Xen might also help.

github-actions[bot] commented 1 year ago

This issue is being closed because:

This issue is on the "Release 4.0 updates" milestone.
Qubes OS 4.0 reached EOL (end-of-life) over one year ago.
There has not been any activity on this issue in over one year.

If anyone believes that this issue should be reopened and reassigned to an active milestone, please leave a brief comment. (For example, if a bug still affects Qubes OS 4.1, then the comment "Affects 4.1" will suffice.)

HeyImAngeel commented 4 months ago

affects 4.1.2 same exact problem, i tried everything, for hvm when i boot it opens seabios withv4 Lines and the last Is “Probing EDD (edd=off to disable!… ok”

tried fix from https://www.qubes-os.org/doc/hvm-troubleshooting/ (qvm-prefs kernel "") but now After that seabios, now GRUB boot starts, After GRUB menu close (1/2 seconds) on Fedora another 2 lines seabios opens with writed "setting up swapspace version 1" and the shutdowning the vm but in Fedora After the seabios then the GRUB menu It Will open a GRUB minimal bash-like terminal sometimes in certain vms After GRUB menu It opens the GRUB terminal

in whonix workstation hvm seabios stays stucked in "Booting from Hard Disk"

instead when i use pvh mode (After manually installing grub2 pvh kernel) Debian Will start and After like 5 seconds It Will shutdown, but on Fedora and whonix workstation they starts without shutdowning but no programs or terminal Will open

like that user i got sys-firewall problem during installation and all the programs wasn't installed default (i had to put VMs in PV mode and refreshing softwares)

i want to say that i installed qubes on USB (465GB) booted installation ISO from virtual box and After First boot installation finished fixed uefi problems with tty2 (following https://www.qubes-os.org/doc/uefi-troubleshooting/ and https://forum.qubes-os.org/t/fom-s-giant-list-of-qubes-os-workarounds-tweaks-and-shenanigans/15162)

when i use PV mode VMs seems to work fine (connecting to internet too)

QubesOS / qubes-issues

PVH doesn't work. PV does. #5360