Search results

Maybe. The rom-parser tool is not perfect either, but it could be a hint. Oh no, not at all - read through the article I linked in the first post, you just need to put the parameter into the VM config. This does not permanently alter your card, and since there are also hardware safeguards...

I'll keep it in mind, but it also doesn't hurt, I checked the kernel source and any unsupported argument is simply ignored - I think it might actually help to have it in here, it's easier to say "use intel_iommu=on or amd_iommu=on depending on your chip" than it is to make more exceptions of...

This is true, I believe this comes from 'intel_iommu' where it is both valid and often necessary, however, the correct solution AFAICT is to just not add it, 'fullflush' does something different. The 'iommu=pt' line should be enough to enable it. `dmesg | grep iommu` should confirm it, if you...

Is this related to OPs post? If not, please open a new thread the next time. Please also post your '/etc/network/interfaces' config, and describe in more detail: * How you expect it to work * What specifically doesn't work * What and how you tried to configure

We've put a patch on the mailing list also CC'ing the original author: https://lists.proxmox.com/pipermail/pve-devel/2021-August/049690.html You're right in that it should be quite safe to remove it, but we'll still make sure it doesn't break anything before it goes live. Thanks for the report...

Hm, a "Stop" should never fail this way, even if it would, it should end up doing a SIGKILL after a bit, which worked once you did it manually... There might be something wrong in general with your setup then. If "Stop" doesn't work, "Shutdown" is almost guaranteed to fail too. I meant the task...

How did you attempt this? Did you request a "stop" or a "shutdown" from the UI? In the latter case, it's clear that it can't work, as the "shutdown" command is equivalent to just pressing the power button, to which SeaBIOS/OVMF simply don't have a handler installed. As this shutdown task then...

If you have a free PCI slot it fits into, I don't see why it wouldn't work. Most devices are supported natively, without requiring a specific driver, but that depends on the device of course. HP stuff I would assume to work. In general, PVE is just Linux, so anything compatible with Linux will...

It's all or nothing, the actual seperation depends on the motherboard hardware. pcie_acs_override usually helps, but there are scenarios where it doesn't. Are you sure it's active? Check your kernel commandline with 'cat /proc/cmdline' to see if it applied correctly.

The 'status' output and the fact there's nothing in the logs would indicate that QEMU is operating normally, i.e. the VM is running as expected, it just never received the command to shut down. Could you also post your VM config ('qm config <vmid>')? To me this almost looks like ACPI is turned...

Hm, you could try booting from a live restore image and checking the original drive from that, just to see if all the data is in fact correctly restored. Also, compare the checksums (sha1sum /dev/mapper/pve-vm--202--disk--0) of the two disks before and after restore, if they differ, use...

Ein reboot tuts, solange er von PVE Seite ausgelöst wird und nicht aus dem Gast selbst. Es gibt auch die Möglichkeit bulk-stop/-start zu verwenden, auf der node-übersicht rechts oben. Falls zwei nodes verfügbar sind, am besten einfach live-migrieren. Es gab eine relativ lange periode zwischen...

lsusb -t is useful for mapping ports/controllers, but tbh I've always just used trial and error, usually the ports on a mainboard that share a controller are physically grouped together too. It is currently hardcoded into our stack. But as stated before, USB passthrough suffers from rather...

A VM stuck in a "locked" mode means something is fundamentally gone wrong. No, this will always stay as an advanced "yes I know what I'm doing" feature. In your case, the unlock command saw that some other task was still accessing the config file. Stop any other tasks on this VMID (like, a...

USB passthrough has very limited bandwidth and performance in general. Getting a webcam working at all is probably pushing the limits. I'd recommend using PCIe passthrough to assign an entire USB controller directly to your VM. This will give you native performance and should work with any...

Can you post your VM config after restore? ('qm config <vmid>')

Clustering requires at least 3 machines to be reliable, i.e. with two machines it will work and provide migration, but the cluster will not be quorate if you shut one of them down (i.e. you won't be able to change any state, start/stop VMs, etc... with only one online). The correct solution...

There's no such storage pool available. You can, however, attach any regular block device directly to a VM: qm set <vmid> -scsi0 /dev/disk/by-id/xxxxx-partN (or 'sata0', 'virtio0', whatever floats your boat) Note that this will break snapshots, migration and to a degree backups.

Yes. :) Is there anything not working in the pvesr (storage replication) service, or was that just an unrelated question?

What is the error exactly? The log you posted contains only normal messages, there's nothing wrong there... Please describe in more detail what doesn't work, i.e. what do you expect to happen and what happens instead.