vendor-reset
pyznap
vendor-reset | pyznap | |
---|---|---|
143 | 9 | |
703 | 198 | |
- | - | |
4.0 | 0.0 | |
17 days ago | about 1 month ago | |
C | Python | |
GNU General Public License v3.0 only | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
vendor-reset
-
Problems with single GPU passthrough | AMD 5700 XT
I have the vendor-reset fix. I have disabled resizable bar, and I have added the fix for the AMD driver detecting the VM in the XML file.
-
Windows 11 VM not shutting down fully
Credit to the fine people in this github issue:https://github.com/gnif/vendor-reset/issues/46
-
VirGL
I’m not sure what you mean by forwarding, but if you mean regular gpu passthrough and the reset bugs with amd gpus, then for the rx580 vendor-reset should typically work: https://github.com/gnif/vendor-reset
Does not work with the lower 6000 (below 6800) and 7000 series that can also have reset issues.
- Supported methods of using DKMS kernel modules; GPGPU virtualization
- swtpm_setup: Not overwriting existing state file.
- Worried about vbios size and hash (single gpu passthrough).
-
AMD GPU Passthrough Black Screen on VM Boot
Just an update installing vendor-reset to counteract the amd gpu reset bug fixed my issues completely. Are you running an amd gpu by chance, it may be worth a shot to try it. https://github.com/gnif/vendor-reset
-
[HELP] AMD REST BUG
1) download https://github.com/gnif/vendor-reset/archive/refs/tags/v0.1.0.zip
- Did anyone using windows 10 VM with an AMD GPU have issues installing the proprietary drivers in windows? Win 10 VM just gets BSOD once they start installing
- GPU Passthrough errors: BAR 0, Error 43, vendor-reset
pyznap
- Python Port of 600 Line Bash Script: rsync-time-machine.py for Rsync Backups
-
Should I be using zfs replicate, mirror, or something else entirely?
Sanoid/syncoids been mentioned but honestly for once a week learning by doing . Pyznap also excellent when you want to automate. https://github.com/yboetz/pyznap
-
Vdevs and snapshots?
In contrast, zfs snapshots are immutable, and thus anything short of a hardware failure can be addressed with a simple zfs rollback command. This includes deliberate, accidental, and malicious actions. They can also be automated (I personally use pyznap but syncoid is also quite popular), creating what is effectively an incremental backup. I maintain - for each dataset - 24 hourly, 7 daily, 6 monthly, and 1 yearly snapshot. Additionally, I have a wholly separate server that wakes up once a day to ingest these snapshots via zfs send/recv, so even if I made a horrible mistake or suffered a catastrophic hardware failure, I could completely restore from the other server. This last point brings snapshots firmly into the realm of backups, IMO.
-
Sanoid for snapshots management?
Another favorite option is Pyznap, which is python based and originally created to have have a few features and changes compared to sanoid. The author is also active here on reddit. I and not sure what the differences are anymore, it'll come down to trying them and preference.
- Advice on settings for spin-down (Ubuntu Server)
-
A small script to wake up a node that doesn't like to boot
I have two Supermicro X9 2Us, each with Proxmox. One has allegedly existed solely as a backup target, which wakes up daily to ingest ZFS snapshots using pyznap. Unfortunately, for reasons which are unclear, this particular node doesn't always like to see its boot device, which is an NVMe drive. It's the exact same board as my primary, with the exact same modified BIOS to allow booting from NVMe. It usually takes 2-3 cycles before it'll see it and boot.
-
Pros/cons of visible dataset for backups vs. only snapshots
I have two nearly identical systems, both running Proxmox, with Debian VMs. One is a backup, which (once this is worked out) will wake up daily to ingest incremental backups. I'm using pyznap to handle the backup strategy.
-
Ubuntu server 21.04 native encrypted root on zfs zfsbootmenu pyznap
https://github.com/yboetz/pyznap/issues/1#issuecomment-351015432
- Don't do VFIO to save money...or time (opinion piece)
What are some alternatives?
vfio-single-amdgpu-passthrough - This repo is a tutorial for single amd gpu passthrough to various qemu VMs
sanoid - These are policy-driven snapshot management and replication tools which use OpenZFS for underlying next-gen storage. (Btrfs support plans are shelved unless and until btrfs becomes reliable.)
single-gpu-passthrough
zfsbackup-go - Backup ZFS snapshots to cloud storage such as Google, Amazon, Azure, etc. Built with the enterprise in mind.
Single-GPU-Passthrough
cv4pve-autosnap - Automatic snapshot tool for Proxmox VE
OSX-KVM - Run macOS on QEMU/KVM. With OpenCore + Monterey + Ventura + Sonoma support now! Only commercial (paid) support is available now to avoid spammy issues. No Mac system is required.
Vault - A tool for secrets management, encryption as a service, and privileged access management
KVM-Opencore - OpenCore disk image for running macOS VMs on Proxmox/QEMU
zfs - OpenZFS on Linux and FreeBSD
vfio
barrier - Open-source KVM software