Search results

I want to pass-through an NVME drive, the ID is 1bb1:5013 / 48:00.0 Its in it's own IOMMU group: # find /sys/kernel/iommu_groups/ -type l |grep "53" /sys/kernel/iommu_groups/53/devices/0000:48:00.0 Do I have to add 1bb1:5013 to pci-stub.ids= or vfio-pci.ids= in grub's config? Also, How to add...

For some reason the USB stick I made with PVE (dd mode) errored out ... it's now unformattable so I have to buy a new one tomorrow. Also, with PVE installed on 2 disks (ZFS raid1) - do I have to select any particular disk as the "boot" disk in the bios?

I want to pass-through an NVME drive, the ID is 1bb1:5013 / 48:00.0 Its in it's own IOMMU group: # find /sys/kernel/iommu_groups/ -type l |grep "53" /sys/kernel/iommu_groups/53/devices/0000:48:00.0 Do I have to add 1bb1:5013 to pci-stub.ids= or vfio-pci.ids= in grub's config? Also, How to add...

Turns out the lan cable was at fault here, backup jobs complete normally with another cable. Right now I'm verifying all the backups in PBS, when that's done I'll do the new PVE install and restore VM configs and storage.cfg's entries.

This keeps happening, I can't backup anything... Both PVE and PBS are updated: PVE: 6.4.13 PBS: 2.0-4 Tried rebooting them - no change. Changed the switch - no change. Changed the cable - so far all looks to be normal... 1 vm with a 300G disk backed up normally.. testing more. Hopefully...

After several attempts, the VM got backed up, but... what was causing this? The backup server and PVE are on the same gigabit switch, no troubles there.

Also... this happens one some backups... What is causing this? In PVE: 106: 2021-10-27 21:26:29 INFO: 68% (44.2 GiB of 65.0 GiB) in 6m 26s, read: 111.3 MiB/s, write: 111.3 MiB/s 106: 2021-10-27 21:26:35 INFO: 69% (44.9 GiB of 65.0 GiB) in 6m 32s, read: 111.3 MiB/s, write: 111.3 MiB/s 106...

If I backup /etc/pve/* and simply restore it on the new install, w/o wiping the VM storage disk(s) - will the VMs work? Do I have to backup anything else on the host, just in case? Btw.. PVE tried to backup a non-existing .iso placed in the virtual cd/dvd drive. Maybe undesired behavior ...

I'm running a PBS server on another PC right now. In PVE - 2 separate data stores added from Datacenter -> Storage -> PBS After all VMs are backed up - I'll do a clean install PVE on the 2 SSDs. Question is - how to restore the VMs after that? Is there something specific ?

Does the PVE installer support software raid for the OS itself?

So, if I do backups - the VMs will still exist on the NVME. After new PVE install on SSDs it won't see the storage, but can't I just add the storage back and copy the VM configs folder? There was something about this in the forum but I can't find it. It was about the "storage config" and "vm...

I don't want to move the VM disks storage, they'll stay where they are. It's just the PVE install disk (HDD) that will "go away" and be replaced with 2 SSDs. After the PVE is installed - how will it see the existing VM disks / configs? What do I have to backup from the old install & restore on...

Hello, Few questions guys.. I've been thinking of doing a clean install of PVE (it's currently residing on an old 320 GB HDD) - on 2 250GB SSDs (in raid 1 mode, if possible, just to have some redundancy in case 1 of them fails). The VMs are on 2 disks - 1x 2TB HDD (backups mostly) and 1x 1TB...

Hopefully someone's working on vTPM for PVE, cause Winblows 11 would require it.... Its better to have some type of implementation, instead of all the trickery that would otherwise be required to install W11 w/o TPM.

Then... I don't know why I don't have this on the "stock" 13.0 ...

Did you install something additional or not? Because on FreeBSD 13.0 with qemu-guest-agent (the one from the first post) installed & enabled, I get: # info balloon...

Looks like FreeBSD doesn't have an "info balloon" command.

Hello, Looks like PVE doesn't detect ram usage in FreeBSD properly, example - VM has 700 MB usage, PVE dashboard shows 1924. qemu-guest-agent is installed, however, looks like PVE doesn't use it to get the RAM usage: dommemstat is the command currently implemented in the qemu-guest-agent port...

It interests me more in the context of High-Performance VM, example - my "daily driver" is a Windows 10 VM with PCIe GPU passed through, 32GB ram allocated, the vm disk is on NVME drive. Sometimes it feels sluggish, so I wonder if RT kernel would make any difference ( I also plan to try CPU...

What's the benefit of running a RT kernel, and why isn't there an official build for that type of kernel ? It'd be really convenient to test this by installing it via apt.