11–19 of 19 posts
Solid product, solid team. Really a nice polished product at this point.
Edit: just for clarification this looks really neat for GPU pci switching? Back in 2012 ish we tried to build a 8 GPU bitcoin mining beast group thread over on bitcointalk on proxmox and we could never get more than 6 GPU's working IIRC. Things were different then.
I'm familiar with proxmox, and I think I'm a fairly technical person, but I can't decipher what this means:
"Switch among Guest VMs organized by Resource Pool"
This readme does not seem very well written.
What does this actually do? I'm familiar with proxmox, and I think I'm a fairly technical person, but I can't decipher what this means: "Switch among Guest VMs organized by Resource Pool" This readme does not seem very well written.
Earlier quoted context omitted.
It looks like it's a tool to help manage hardware passthrough, specifically to pass through a single resource (GPU most often) and have the UI know that all the guests sharing it are mutually exclusive and you can only have one running at a time.
Thanks, I see (I think). So some use cases would be for gaming (where you really need dedicated graphics performance), and also for MacOS as a guest OS (as otherwise the user interface is really slow)?
Is this something specific to proxmox or non-mac hosted virtualization? I ask because I regularly run MacOS without GPU passthrough without any UI slowdowns at all. In fact, at one point I ran macOS in a VM as the primary UI on my MacBook for several years..
Earlier quoted context omitted.
Thanks, I see (I think). So some use cases would be for gaming (where you really need dedicated graphics performance), and also for MacOS as a guest OS (as otherwise the user interface is really slow)?
> for MacOS as a guest OS (as otherwise the user interface is really slow) Is this something specific to proxmox or non-mac hosted virtualization? I ask because I regularly run MacOS without GPU passthrough without any UI slowdowns at all. In fact, at one point I ran macOS in a VM as the primary UI on my MacBook for several years..
This was on a late 2013 though, so the experience may be very different now, in fact now that I've replaced it with a 2020 iMac, I'll give it another go and see.
I use (and love!) Proxmox but as a way to virtualise dedicated servers (eg from OVH / Hetzner) and avoid having to pay hosts like DO everytime I need a new VPS for a project. I'm completely confused by what this ("Proxmox PCI Switcher") is – and the readme isn't helping very much. Can someone explain?
It looks like it's a tool to help manage hardware passthrough, specifically to pass through a single resource (GPU most often) and have the UI know that all the guests sharing it are mutually exclusive and you can only have one running at a time.
I have a lot of difficult to explain this. I will improve the docs... maybe record a video.
What does this actually do? I'm familiar with proxmox, and I think I'm a fairly technical person, but I can't decipher what this means: "Switch among Guest VMs organized by Resource Pool" This readme does not seem very well written.
This tool handler this kind of "lock" like a switch button.
Earlier quoted context omitted.
Thanks, I see (I think). So some use cases would be for gaming (where you really need dedicated graphics performance), and also for MacOS as a guest OS (as otherwise the user interface is really slow)?
> for MacOS as a guest OS (as otherwise the user interface is really slow) Is this something specific to proxmox or non-mac hosted virtualization? I ask because I regularly run MacOS without GPU passthrough without any UI slowdowns at all. In fact, at one point I ran macOS in a VM as the primary UI on my MacBook for several years..
If you don't know, screen sharing is done very well - it does very intelligent things, such as drag and drop files from desktop to desktop or rich-text copy/paste between systems. It will also pass keys correctly, so command-q will quit a remote app instead of quitting the screen sharing app itself. same with alt-tab.
I used to use screen sharing with the macbook itself, but it kept going to sleep with the lid closed at inopportune times even with caffeinate, so I just cut to the chase.
I also was able to migrate the macos vm when I upgraded my proxmox machine hardware. "vzdump ", copy the dumpfile, "qmrestore ", voila
Earlier quoted context omitted.
It looks like it's a tool to help manage hardware passthrough, specifically to pass through a single resource (GPU most often) and have the UI know that all the guests sharing it are mutually exclusive and you can only have one running at a time.
nice words, thanks! I have a lot of difficult to explain this. I will improve the docs... maybe record a video.