QEMU 9.2 Released With VirtIO GPU Vulkan Support, AVX10 & Experimental Rust Support

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • qarium
    replied
    Originally posted by akarypid View Post
    So with the VritIO vulkan-based driver, will we even be able to assign the same GPU to multiple VMs and have them share it? Or did I not understand this correctly?
    yes but right now only if you have linux as a host and linux as a guest.

    right now it does not work if you have linux as a host and windows as a guest...

    Leave a comment:


  • amity
    replied
    My understanding is the virtio vulkan support still requires linux, or anything that works with virgl currently, as I don't think there's a stable windows virtio/virgl driver.

    There is https://gitlab.freedesktop.org/max8rr8/virglrenderer (from this PR) but it hasn't been updated in 1.5 years and still has tons of show-stopper bugs.
    Last edited by amity; 14 December 2024, 04:45 PM.

    Leave a comment:


  • MillionToOne
    replied
    Originally posted by iustinp View Post
    "Future versions of QEMU will begin to require a Rust compiler." - yay! But very surprised there's no anti-Rust comments on the first page (so far). What are the usual naysayers doing?
    Spraying WD40 on rust

    Leave a comment:


  • wertigon
    replied
    Originally posted by akarypid View Post
    So with the VritIO vulkan-based driver, will we even be able to assign the same GPU to multiple VMs and have them share it? Or did I not understand this correctly?
    The way I understand it, the VirtIO is basically making the VM into a Vulkan client on the host system. There is some overhead but pretty much no need to pass through the GPU anymore.

    Leave a comment:


  • iustinp
    replied
    "Future versions of QEMU will begin to require a Rust compiler." - yay! But very surprised there's no anti-Rust comments on the first page (so far). What are the usual naysayers doing?

    Leave a comment:


  • zaps166
    replied
    Originally posted by gustavoar View Post
    Please just give me a easy way to passthrough resizable BAR in VFIO
    On AMD Ryzen platform I have to enable Above 4G decoding and disable RE-BAR in UEFI - in this configuration it works in Windows VMs when passing-through the GPU (CPU can see whole VRAM). Also the RE-BAR UEFI setting doesn't affect Linux host - it also work there regardless of this UEFI setting.

    For me it looks like the "RE-BAR" UEFI setting affects only Windows (real, not VM).

    Leave a comment:


  • pgoetz
    replied
    Originally posted by akarypid View Post
    So with the VritIO vulkan-based driver, will we even be able to assign the same GPU to multiple VMs and have them share it? Or did I not understand this correctly?
    I think this is a hardware/video driver issue? Dealing with sharing the GPU memory in a coherent fashion would likely require Nvidia MIG, or something similar. Currently these features are not available on consumer grade cards.

    Leave a comment:


  • Quackdoc
    replied
    Originally posted by akarypid View Post
    So with the VritIO vulkan-based driver, will we even be able to assign the same GPU to multiple VMs and have them share it? Or did I not understand this correctly?
    kinda, the perf isn't 1:1 but it is really high, so it could in effect act like that. but in reality, all it is, is vulkan passthrough in a sense.

    Leave a comment:


  • akarypid
    replied
    So with the VritIO vulkan-based driver, will we even be able to assign the same GPU to multiple VMs and have them share it? Or did I not understand this correctly?

    Leave a comment:


  • gustavoar
    replied
    Originally posted by Quackdoc View Post

    is that not solved yet? and here I thought it was able to do a static resize at vm start time.
    Well, that works for some and not for others. I couldn't get it to work for me. Setting a static value is also kind of a workaround, would be nice to have proper support.

    Leave a comment:

Working...
X