From: Dominik Csapak <d.csapak@proxmox.com>
To: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] vGPU scheduling
Date: Thu, 25 May 2023 09:53:53 +0200 [thread overview]
Message-ID: <44a4c34c-6b17-6b1e-b54b-3b0dff7c3d59@proxmox.com> (raw)
In-Reply-To: <mailman.252.1685000179.348.pve-user@lists.proxmox.com>
On 5/25/23 09:36, Eneko Lacunza via pve-user wrote:
> Hi Dominik,
>
>
> El 25/5/23 a las 9:24, Dominik Csapak escribió:
>>
>>> 2.12.0 (qemu-kvm-2.12.0-64.el8.2.27782638)
>>> * Microsoft Windows Server with Hyper-V 2019 Datacenter edition
>>> * Red Hat Enterprise Linux Kernel-based Virtual Machine (KVM) 9.0 and 9.1
>>> * Red Hat Virtualization 4.3
>>> * Ubuntu Hypervisor 22.04
>>> * VMware vSphere Hypervisor (ESXi) 7.0.1, 7.0.2, and 7.0.3
>>>
>>> Is there any effort planned or on the way to have Proxmox added to the above list?
>>
>> We'd generally like to be on the supported hypervisor list, but currently
>> none of our efforts to contact NVIDIA regarding this were successful,
>> but i hope we can solve this sometime in the future...
>
> I can try to report this via customer request to nvidia, where should I refer them to?
You can refer them directly to me (d.csapak@proxmox.com) or our office mail (office@proxmox.com).
Maybe it helps if the request comes also from the customer side.
>
>>
>>>
>>> As Ubuntu 22.04 is in it and the Proxmox kernel is derived from it, the technical effort may not
>>> be so large.
>>
>> Yes, their current Linux KVM package (15.2) should work with our 5.15 kernel,
>> it's what i use here locally to test, e.g. [0]
>
> We had varying success with 5.15 kernels, some versions work but others do not (refused to work
> after kernel upgrade and had to pin older kernel). Maybe it would be worth to keep a list of known
> to work/known not to work kernels?
Normally i have my tests running with each update of the 5.15 kernel and i did not see
any special problems there. The only recent thing was that we had to change how we
clean up the mediated devices for their newer versions [0]
Note that i only test the latest supported GRID version though (Currently 15.2)
Regards
Dominik
0: https://git.proxmox.com/?p=qemu-server.git;a=commit;h=49c51a60db7f12d7fe2073b755d18b4d9b628fbd
prev parent reply other threads:[~2023-05-25 7:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.190.1684933430.348.pve-user@lists.proxmox.com>
2023-05-24 13:47 ` Dominik Csapak
2023-05-25 7:32 ` DERUMIER, Alexandre
2023-05-25 7:43 ` Dominik Csapak
2023-05-25 9:03 ` Thomas Lamprecht
2024-05-31 7:59 ` Eneko Lacunza via pve-user
[not found] ` <cbb9c11d-5b8e-4f1a-98dd-b3e1cf4be45c@binovo.es>
2024-05-31 8:08 ` Dominik Csapak
[not found] ` <mailman.193.1684936457.348.pve-user@lists.proxmox.com>
[not found] ` <mailman.222.1684948008.348.pve-user@lists.proxmox.com>
[not found] ` <0e48cb4a-7fa0-2bd7-9d4e-f18ab8e03d20@proxmox.com>
[not found] ` <mailman.252.1685000179.348.pve-user@lists.proxmox.com>
2023-05-25 7:53 ` Dominik Csapak [this message]
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=44a4c34c-6b17-6b1e-b54b-3b0dff7c3d59@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=pve-user@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