Search results

How do I train Bayes as to what is SPAM and what is not? It's producing so many false positives that it may make more sense to just turn it off.

Oh, yeah, this controller is doing a bunch of other stuff, so that won't work.

This might work... https://pve.proxmox.com/wiki/Passthrough_Physical_Disk_to_Virtual_Machine_(VM)

We have added some new disks to our Proxmox servers, and we were just looking for some verification that we've reached the right conclusion. We currently have 2x Dell 2.4TB drives in a mirror with a hot spare. We added two more. Of the four that we added (two each to two hosts), two aren't...

Googling shows that this error message when backing up is most often associated with LXC container permissions. While I do use LXC containers, this error appears to be exclusively on KVM\QEMU VMs. Some of them were freshly created on Proxmox, while others were migrated from VMWare. I am backing...

Found it. I added it to /, and the test user can now get to what it needs. Now, I want to see if I gave it too much. :-)

I don't see that dialog box anywhere. I'm running 8.2.2.

I've read through https://pve.proxmox.com/wiki/User_Management, but it's not very clear. How do I assign a custom-created role to a user?

I'm not sure how to search Google for this. Can someone point me to documentation on how to migrate old Proxmox containers to a modern server? I already have the new one. just looking to shut down the last two machines on the old server. Maybe I should search for OpenVZ to LXC migration?

Okay, I made some amount of breakthrough, though I don't understand why. root@PVE1:~# ls -hal /run/pve/import/esxi/VMware15/mnt/ha-datacenter/RAID10/NickBsmoker/NickBsmoker.vmx ls: cannot access '/run/pve/import/esxi/VMware15/mnt/ha-datacenter/RAID10/NickBsmoker/NickBsmoker.vmx': No such file...

From the PVE Web UI: can't open '/run/pve/import/esxi/VMware15/mnt/ha-datacenter/RAID10/NickBsmoker/NickBsmoker.vmx' - No such file or directory (500) From /var/log/pveproxy/access.log ::ffff:10.1.1.37 - root@pam [16/06/2024:20:35:44 -0500] "GET /api2/extjs/cluster/nextid?_dc=1718588127794...

Recommendations for a low-power and cheap device to put into my Proxmox cluster so that I can have a quorum? I quickly bought stuff last week to move my environment to new hardware. I have three R730s (actually, they sent me R730xds, so I think I got a good deal out of it); two will run PVE...

Has anyone else done this? What are the risks of this change? My problem ended up being that the source VMs had snapshots.

/var/log on the vSphere host doesn't show anything. I determined that by issuing a grep for one of the VMs I was trying to migrate, attempted a migration, grepped again, and then compared the differences.

root@PVE1:~# journalctl -u pve-esxi* Jun 15 13:02:24 PVE1 systemd[1]: Started pve-esxi-fuse-VMWare13.scope. Jun 15 13:02:28 PVE1 esxi-folder-fus[41384]: PVE1 esxi-folder-fuse[41384]: esxi fuse mount ready Jun 15 13:20:52 PVE1 systemd[1]: Started pve-esxi-fuse-VMware15.scope. Jun 15 13:21:03 PVE1...

Where can I find additional logging on "esxi-folder-fuse" or "pve-esxi"? root@PVE1:~# ls -hal /run/pve/import/esxi/VMWare13/mnt/ha-datacenter/NEW/UBNT\ UniFi\ 2/ total 0 -r--r--r-- 1 root root 554 Dec 31 1969 'UBNT UniFi 2.vmdk' That works, so it can assumingly reach the data.

I have had some successful migrations from the same hosts, but on different datastores. The successful datastore is named "RAID10". The unsuccessful datastore is named "NEW". "NEW" doesn't have any special characters, which would cause it to fail. root@PVE1:~# systemctl status pve-esxi* ●...

Thus far, it has worked fine for me on vSphere 5.5.

I started reading this thread and then realized that it was 17 pages. I also don't see the ability to search just within this thread, so pardon me if it's already been asked. I see see the documentation state that VMware versions 6.5 through 8.0 have been tested successfully. Have versions...

I do recall Intel 3600\3700 were recommended for different tasks (one SLOG, the other L2ARC), but it doesn't look like Intel maintained successors to them.