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

Add Proxmox installation steps #12

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

joshuataylor
Copy link

I also have screenshots, unsure where to place them?

Happy for this to be edited as you see fit.

@electrikjesus
Copy link
Member

For some docs, I add an assets or images folder to the document folder. Then place the images in there and link them in the markdown.

@Quackdoc
Copy link
Collaborator

Quackdoc commented Apr 30, 2024

Ill review this when I get s chance later tonight. I did take a quick glance, however. Does Proxmox not support EGL Headless? I thought it got support for that.

@joshuataylor
Copy link
Author

joshuataylor commented Apr 30, 2024 via email

@Quackdoc
Copy link
Collaborator

Yeah but if it's not exposed in a user friendly way people may not be able to use it nicely. Using virtio-gpu or QXL would be ideal for no gpu acceleration still. With acceleration we would use virtio-gpu + egl-headless. This is still compatible with VNC and Spice and should be better then the vmware gpu implementation.

@joshuataylor
Copy link
Author

joshuataylor commented Apr 30, 2024 via email

@joshuataylor
Copy link
Author

Promox (8.2, latest, not sure of exact offerings of earlier versions) offers the following options for Display:

Default
Standard VGA
VMware compatible
SPICE
SPICE dual monitor
SPICE three monitors
SPICE four monitors
Serial terminal 0
Serial terminal 1
Serial terminal 2
Serial terminal 3
VirtIO-GPU
VirtGL-GPU
none

You can also configure QEMU options via VM configuration files, which I know folks who do VFIO/IOMMU/PCI passthrough/etc sometimes have to use if the option isn't supported "officially" by the Proxmox UI yet.

I'm also happy to play with/test GPU passthrough options with Proxmox, it's not my usecase, but still happy to help others.

My cards I have in this machine:

  1. AMD RX550, 4gb
  2. MSI GeForce RTX3080 VENTUS 3X 10GB GDDR6X

I also have a couple of random cards of unknown working status I can try, but these should be a good start.

I'll have a play and let you know.

@Quackdoc
Copy link
Collaborator

Quackdoc commented May 1, 2024

Unfortunately, I don't know what those "Displays" are since they seem to be mixing display and gpu into one category... you will have to look into the documentation for that

Passing through the rx550 should work. passing through the 3080 will work as well, but we only use nouveau

@joshuataylor
Copy link
Author

👍 Understood - all good - just wanted to share my progress/findings. I've played a fair bit around for VFIO with ArchLinux(btw), not much with Proxmox, so far VirGL works with the RX550. I use Proxmox primarily for few containers/VMs.

My primary use-case for BlissOS is not passthrough, but it's an interesting topic that others seem to struggle with, due to inexperience with Linux. Proxmox is a good starting point for that, agreed about giving them a good experience -- from what I've been using BlissOS for (notification forwarding to my devices, random app testing, etc) it's been pretty rock solid with VMware compatible, I didn't realise virtio-gpu was supported so well 😍.

I tried to make the initial tutorial easy to follow, as Proxmox offers a console view which is a good way of ensuring you can actually boot into BlissOS before advancing into more advanced topics.

Console view, for those interested:
image

I think creating a more advanced guide, after we sort this PR, would be useful, as the notes could then be used in tandem with the QEMU notes.

If I need a hand with anything, I'll reach out. Cheers.

@Quackdoc
Copy link
Collaborator

Quackdoc commented May 7, 2024

I think creating a more advanced guide, after we sort this PR, would be useful, as the notes could then be used in tandem with the QEMU notes.

If I need a hand with anything, I'll reach out. Cheers.

I would not be opposed to this. We would likely want to restructure the documentation since I also want to do xcp-ng related instructions at some point as well

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants