From: Dominik Csapak <d.csapak@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Cc: moddingfox <moddingfox@gmail.com>, Tyst Marin <moddingfox@foxtek.us>
Subject: Re: [pve-devel] [PATCH] Add UI option for boot optional mapped usb device
Date: Wed, 4 Dec 2024 10:40:04 +0100 [thread overview]
Message-ID: <77f8faaf-db60-4ee0-8354-1ff83c870416@proxmox.com> (raw)
In-Reply-To: <mailman.694.1732617417.391.pve-devel@lists.proxmox.com>
Hi,
thanks for wanting to contribute!
First, did you already see https://pve.proxmox.com/wiki/Developer_Documentation ?
(especially the CLA part at the end?)
Just a few high level comments/questions to the approach (did not look too much at the code yet).
Please correct me if I'm wrong, but my guess why you want this is to emulate
the behavior for 'raw' USB passed through devices? (since those don't have to
be there for the vm to start?)
I think maybe such a setting would be better suited on the mapping itself?
I say this because the mapping defines which devices can/should be used, so
there is IMHO the right part to decide if it should be used in a guest
when it's missing.
Also I'm not very sure if we'd need a setting for this at all, since
the 'raw' passthrough also simply pass it through.
Just for your understanding, the reason it's currently implemented this way
is to prevent booting a VM with a wrong device (at least when using the path),
or a without one since that can have bad consequences (depending on what the
guest does with the device and what devices are connected)
Additionally we currently don't properly track the use of usb devices on our
side (which can have weird side effects, e.g. if you try to pass the same
device to multiple running vms at the same time) but this is not really
possible when using vendor/device ids since there could be mulitple such devices.
with kind regards
Dominik
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2024-12-04 9:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-26 1:51 moddingfox via pve-devel
2024-12-04 9:40 ` Dominik Csapak [this message]
2024-12-04 21:50 ` Tyst Marin
2024-12-12 8:19 ` Dominik Csapak
2024-12-13 0:23 ` Tyst Marin
2024-12-13 8:34 ` Dominik Csapak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=77f8faaf-db60-4ee0-8354-1ff83c870416@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=moddingfox@foxtek.us \
--cc=moddingfox@gmail.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox