Search results

Solved now, coming back with cause later.

Looks like I managed to free up a bit. But still wonder why this happened.. but that I need to analyze later. It stills shows yellow on my vms on zfs in the GUI for some reason... root@p1:/etc/pve# kill -9397049 -bash: kill: 9397049: invalid signal specification root@p1:/etc/pve# kill -9...

root@p1:/etc/pve# zfs destroy -f rpool/data/vm-125-disk-0 cannot destroy 'rpool/data/vm-125-disk-0': dataset is busy root@p1:/etc/pve# qm destroy 125 can't remove VM 125 - protection mode enabled

But how :) The GUI doesn't let me and rm -Rf rpool/data/vm-304-state-BeforeCpanel doesn't delete them either. root@p1:/etc/pve# qm delsnapshot 304 BeforeCpanel unable to create output file '/var/log/pve/tasks/0/UPID:p1:001ACB8D:0E364084:65687DE0:qmdelsnapshot:304:root@pam:' - No space left...

I have VMs in both pools, it is my zfs-vm's that are in trouble... I could even delete "Virtual Machine 125" that are in that pool with 300 GB disks, but I can't even remove it's protection due to no storage space. So can't delete anything either. I couldn't find any big files in the "/" root...

oot@p1:/etc/pve# zpool list -v NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT rpool 888G 861G 27.4G - - 57% 96% 1.00x ONLINE -...

Under different places, it says my two pools have lot of space. But see here, system is full! I have a zfs pool and a raid pool. It shows status OK on both and free space in giu with several TB free space. But all my vms on zfs volume has yellow mark and I can't do anything with them. I have...

Haven't found a way around it yet unfortunately, since there isn't any devices in between.

Thanks for the reply. I'm using FQDN for the public IP using one ISP, while I use an local/internal backup-server at a seperate fiber line between two data centers (for backups only). Maybe I can solve this by some routing, but that's my initial issue. Have local private IP at proxmox and...

I just found out that the reason why my proxmox-backups fails over time is because I use Let's encrypt certificate is renewed from time to time (I used the fingerprint): https://forum.proxmox.com/threads/pbs-error-fetching-datastores-fingerprint-xx-not-verified-abort-500.90342/ The work-around...

Yes, of course there are different needs, but in most threads I found it seemed to match what I was looking for (except the one I quoted of course):confused: But it might just be me misunderstanding the questions in those cases. How do I add that command, is it as simple as create a new file in...

It has been asked many times and I have tried so many different solutions. The most common answer from Proxmox-members or staff seems to be like this (in this quote, a fw thing- but still): "You would configure the IP for proxmox in the bridge instead of the NIC, then pass the bridge through to...

This is from the syslog - repeated message tons of time (7.4-3). Is this something I should ignore? I have disabled ipv6 (on os-level) both on the host and on all vms and the suggested fix in the error message seems to indicate the error is related to ipv6 - maybe just a dependency that is...

Only issue now is that most of my LXC containers doesn't work any more.. Console doest say anything, just black and shows status Running - without actually running. I can't even stop them I can pct mount 102 for instance... So weird. And that was apparently the cgroup issue, haven't rebooted...

Fixed: Didn't want to, but did a reboot just in hope and it worked afterwards. Don't know why. Firewall has started failing and I don't know why. I get this error in the log: Apr 29 00:16:17 pve-firewall[1442]: status update error: ipset_restore_cmdlist: Try `ipset help' for more information...

From time to time, I have to boot into Windows Recovery inside a VM (kvm) and I have to provide some files to be available to that Windows Recovery system. For instance Windows Backup Restore. I would need to place those files on an USB or a network share. These are often really big files, many...

For later referanse to help others - I have working vms so I couldn't just take down the entire host. I solved it finally after lot of threads here giving no help. The method of using "Third remove the disk:" also suggested above didn't work, as it gave the same error message that it...

I experienced exact same issue with both RockyLinux 9 and AlmaLinux 9 on all the ProxMox-host I had. Struggled so much to figure it out. By changing the CPU type to Host like suggested earlier in this thread, instead of the default one, it worked. It is the first time ever (after 10 years or...

I have v7.2.7 running in a cluster or what this is called. Have both Proxmox in same WEB GUI. Usually, I have been able to move the vms from one Proxmox-server to the other. I have recently upgraded to 7.2.7 (both hosts rebooted). When I try to migrate a live kvm-machine, I get these kinds of...