Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Qubes running on a dual EPYC 7301 system! #3602

Closed
wilsonk opened this issue Feb 18, 2018 · 1 comment
Closed

Qubes running on a dual EPYC 7301 system! #3602

wilsonk opened this issue Feb 18, 2018 · 1 comment
Labels
R: not applicable E.g., help/support requests, questions, discussions, "not a bug," not enough info, not actionable.

Comments

@wilsonk
Copy link

wilsonk commented Feb 18, 2018

Qubes OS version:

Qubes-4.0-RC4
AMD EPYC 7301 X 2
128 GB of 2666 RAM
240 GB SSD drive in SATA 3 (not SAS)
Radeon onboard graphics

IOMMU enabled in rather new BIOS (Nov 27/17)
SM enabled (Virtualization support)

Affected TemplateVMs:

All VM's affected


Steps to reproduce the behavior:

Try to start VM

Expected behavior:

VM starts

Actual behavior:

VM doesn't start and there are errors in the /var/log/libvirt/libxl/libxl-driver.log that say "PCI device... error. Possibly IOMMU is not enabled?"

General notes:

dmesg seems to indiacate that IOMMUv2 won't start but there are no errors for IOMMU and the device listing shows IOMMU was initialized.

I can gather a little more info on this later, but thought I would post this here quickly in case someone might know a simple fix for this that I am missing.

I can start a VM by disabling networking and not using sys-net/sys-firewall, so it might be somewhat related to 3125?

Related issues:

#3125 might be related

@andrewdavidwong
Copy link
Member

Based on our issue reporting guidelines, this appears to be too localized for qubes-issues, since it depends on a specific hardware configuration. We ask that you please send this to the qubes-users mailing list instead. qubes-users is intended for these sorts of issues and receives much more traffic, which means that your issue is more likely to receive a response there. If, after reading our issue reporting guidelines, you believe we are mistaken, please leave a comment briefly explaining why. We'll be happy to take another look, and, if appropriate, reopen this issue. Thank you for your understanding.

@andrewdavidwong andrewdavidwong added the R: not applicable E.g., help/support requests, questions, discussions, "not a bug," not enough info, not actionable. label Feb 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
R: not applicable E.g., help/support requests, questions, discussions, "not a bug," not enough info, not actionable.
Projects
None yet
Development

No branches or pull requests

2 participants