Search results

I would still test as above. to VMs both attched to bmvr6 with static address, to see if they can ping each other. I'm still leaning towards the swtich not forwarding/allowing tagged/untagged packets into the right places.

To test, add another virtual with the same setup and set a static address on both virtuals, in the same address space as your normal network. Make sure they are on the same VLAN in proxmox and the same network bridge. See if they can talk/ping each other (windows blocks ping responses by...

Quick reply, have you made sure that VLAN aware on the network device of the host is ticked ? also make sure your tagging is sent on the VLAN for the virtual interface being passed to the virtual machine. Also check that your switch is not a managed one (if it is you might need to enable VLANs...

My local storage was not fast enough to validate the backups as they finish and were just killing my storage. I removed "Verify new backups immediately after completion" from Datastore.

Think i've worked it out, will report back shortly.

So i'm getting the above error, however it's always after the back has got to 100% (see below logs) If i check in the backup location i can see that the backup has been saved and even verified. If i run and the backup manually it also completes fine. Any ideas ? INFO: Starting Backup of VM...

So from my understanding the 4000G are really 3000 chips with Vega graphics in them, and for OEMs. Do report back on what you go with as i've been waiting to pull the trigger on upgrading my Intel i5 4690K as it's got far too many PCI cards to not cause bottlenecks :(

I might have forgotten that we don't log into the web console as root, so that might have been why we didn't see the migration task. Not a huge amount, when it happens the journald service inside the container is in an error state. There is also a message in dmesg stating it couldn't remount...

I suspect the qcow2 backed disk was trying to expand/grow the virtual disk as you were filling it up. I remember hyper-v dynamic expanding disks causing issues when growing, most noticeable on databases being wirtten out.

sorry, came from another thread and just skimmed it.

just posted about trying to pin the cpu cores, might help ?

have you tried pinning the cpu cores ? i did this in my old virtual gaming rig and it helped a bit, but that was just qemu on ubuntu https://forum.proxmox.com/threads/cpu-pinning.67805/

I thought setting that just sets the presented rotation speed to 0 so the guest flags it as an SSD in the OS. Also try enabling "IO Thread" Tho you are only using one controller so prob not much help I like to enable "Write back (unsafe)" on my guests disks (all this is my own home server...

I couldn't see a stop, as i had set it through a crontab job. It's always a diffrent contaier that locks up on shutdown, the logs show the container can't remount root, so some kind of race in journald i think. After going down a rabbit hole i think it has to do with CentOS 7 being systemd 219...

To answer my second questions, Yes if you change the option in the GUI then it will reflect the next items in the queue to the actioned Weather it would allow you to increse from one to two to allow getting through the list i have yet to test (i suspect not as a worker submits jobs to process...

So two questions really. Is is possible to cancel stop migrations once they are in the queue ? i.e i run pvenode migrateall ProxMoxNode2 --maxworkers 1 but after a few containers it stops, due to one container failing to shutdown, but there is 30 behind that locked one. is it possible to...

Had this error on my test unit and this fixed my issue of this !

I was looping through a list from pct list, then submitting each one to pct move, which then queued it for HA worker... this way is MUCH better !

If you can't remember what you added try looking at the guide and working out what the default was. Hope that helps

From grub i selected an old kernel that would boot, then i edited /etc/lvm/lvm.conf again and removed what i added (cause i made a copy of the old file and called it lvm.conf.bak)