Search results

It's my problem to deal with. Upgrading with LXC's to v7 seems painful (especially when I checked a month or two ago with CT's getting broken), and I am using a host that only workings with GPU stuff with 5.4 kernel.

How is live restore better/improvement in this case?

I've never had this happen - what disks are you using? Are the VM's and PBS backup disks separate? FYI, I do not use RAID (speed increase) - nor SSD's and I have yet to experience a VM hang during backup - almost never.

That's a bit gross then. At least Windows 11 isn't production yet. :/

Another question I have is that I am still on PVE 6.4 - with no plans to upgrade until EOL - if secure boot/vTPM is implemented (in v7) - will it be ported to 6.4 as it is not EOL yet?

I do not know much about bridges, but either do TFA on PVE host for better password security, or get a new network switch firewall capabilities to block traffic from all ips, except XYZ, get the vm's on a different network switch, , or tweak around with Proxmox bridges and firewall.

Networking like this is a big beyond me too, I recommend Two Factor Auth if you can't isolate them on a different subnet/network that can't talk with your PVE host.... And if they're escaping the VM/QUEM, there's other problems...

When I migrate an LXC I get: ERROR: migration aborted (duration 00:00:00): storage 'Seagate1TBDriveThree' is not available on node 'pve' Why can't I not choose a disk on remote? The GUI doesn't even show disks that I can select on the remote node/host. proxmox-ve: 6.4-1 (running kernel...

How would I do this? I need to have a spare disk lying around? Create an NFS/SMB store, of of the disk I wish to migrate to on the target server node? - won't work Can someone at Proxmox chime in on this issue?

I think seeing how much time it takes to hash is pointless, because it's not going to take that time every time a backup is ran with dirty bitmaps?

UI is mostly the same, and I have to stay on 6.4 PVE - so upgrading is a no go for me. Turns out the issue is resolved, after I saw issues with the .chunks/vms/ct/ folders that needed to be correctly purged I believe.

Executed the follow lines: proxmox-backup-manager datastore list proxmox-backup-manager datastore remove StoragePool proxmox-backup-manager datastore create StoragePool /storage Note, same as it was setup before I removed Output of last command: Result...

Hmm. Not working on 6.4-8. proxmox-ve: 6.4-1 (running kernel: 5.4.119-1-pve) pve-manager: 6.4-8 (running version: 6.4-8/185e14db) pve-kernel-5.4: 6.4-3 pve-kernel-helper: 6.4-3 pve-kernel-5.4.119-1-pve: 5.4.119-1 pve-kernel-5.4.106-1-pve: 5.4.106-1 pve-kernel-5.4.34-1-pve: 5.4.34-2 ceph-fuse...

Never have this happen. Any backups to an earlier point where this doesn't happen?

When i migrate an LXC I get: ERROR: migration aborted (duration 00:00:00): storage 'Seagate1TBDriveThree' is not available on node 'pve' Why can't I not choose a disk on remote?

Seems interesting. I've come across an issue where the SAN (HP MSA 2012i) will format any drives and create a pool. Formatting my drives is a no go for me, as I would need to get 45+ TB's right now to copy it off so I can "start" this procedure. Asking online, it was suggested to look at Ceph...

I've been digging around for a SAN. ISCSI seems okay - the 1GbE (or x4) is acceptable for media streaming under 4K. I am utilising MergerFS to group several disks into one pool, but looking at a high availability disk shelf, I was wondering if anyone new if it might be possible to add the ISCSI...

I ran sgdisk --zap-all /dev/sdb vgdisplay/lvdisplay shows nothing about the disk. The storage entry loads no size info- I removed it from storage as well. I can't seem to remove the disk from Proxmox.

VM's are isolated - you need to login to view information. My advice is to install a monitoring agent (E.G. Zabbix) on the VM/guest.

I use otherwise: pvecm add xxxx