Search results

" post-up iptables -t nat -A POSTROUTING -s '10.0.0.0/24' -o enp31s0 -j MASQUERADE post-down iptables -t nat -D POSTROUTING -s '10.0.0.0/24' -o enp31s0 -j MASQUERADE " Try with converting yours iptables rules into a nftables rules. Proxmox doesn't use iptables natively. They...

Hey, Thanks for your dmesg file. Open -it, and search in this key: 1125.098434 At this time boot, you gonna found seg fault error. 2 thinks: - Reboot on previous running kernel. If he boot, go to dmesg, and do the same search with keywords: "segfault" and "BUG". If no entry with them, update...

hum .... this is xaclty that mapped device do ? :'p

OK, hi again, i've not really more idea, but go investiguate... Network thinks: - Is you PVE hosts with problem have maybe a duplicated IP by another VM/hardware on the same network. - Same thinks with MAC @. Firewall/ SecureLogin thinks: - Did you have done any specific changes on FW of...

OK - Sorry, was onjly able to help you diagnose the source problem with aggregation, when this duplicated @ mas error in your log file come. I've not tested with lacp, no switch lv2 to home ^^

sry, haven't more idea @ this moment :/

Did you have installed on yours guests the guest agent ? This is a needed prerequisites for hotpluging. I think you've saw this documentation Proxmox: https://pve.proxmox.com/wiki/Hotplug_(qemu_disk,nic,cpu,memory) But, you only have the manipulation for pve 4.5 and older. Check the real...

Don't forguet to update yours masquerading rules for the updated network name. For your routing problem: 1 Deactivate your enp31s0 gateway. Make it on your vmbr1 declaration. 2 Apply configuration 3 Check routing table (ip -c r) 4 modify your iptables rule for masquerade to vmbr1 interface...

OK. The first reason for my question is i found the vm import tool so hard to use, with frequents fails like yours. My solution used in professional environnement (40TBs VMs import from another production site): Take hand via ssh on your(s) vmware datastore. Then, use this tool...

OK :) If you do not plan to use ZFS FS, you're good. Proxmox is extremely flexible for hardware. But technologies like ZFS need professionnal stuf prerequists. Did you have precises questions for your lab ?

Hey, it's smell a binding problem. Which mode are you using for bonding ? On your GUI, -> PVE Host -> System -> System Log: Check if you haven't messages calling duplicated @mac on your bonded interfaces.If so, try to modify your bonding mode on failove mod, apply your configuration, then retry...

What's calling "dmesg" return ?

In directory view of your vmware datastores, did you see yours disk ? which format did they have now ? Which kind of PVE datastores did you have created ? lvm? zfs ? other think ?

did you enabled NUMA on your guest CPU?

I think you've tried too hard configuration so fastly. 1) Why use a interface not bridged for your PVE? 2) WHY WHY another interface, breidged, on the SAME network ? What's your goal with this ? 3) Begin by place good your post-up rules: ADD them only on your vmbr2 4) Review yours network...

Yes. No VM without AES instruction in 2024 .... Or you gonna loose much of operation time

Be extremely attentive to that you wanna do. Consummer stuff + zfs isn't a really good idea, many post on this forum can confirm this. Be optimist: For zfs in your situation, if a small clients of your installation, you can discover ZFS. But you canno't compare performance stats with...

Did you tried to, in hardware section of your VM, to reallocate the GPU? it may be change og iommu group after update

i woul d suggest you to turn of secures boot in UEFI guest Bios, but if you're not in UEFI mode .... Did you tried to passthrough "Mapped Device" option ? Then with your card, you can use the GPU ressources with yours two VM at the same time. BUT, this only can work if using "Mapped Device"...

I d'ont have any other idea, maybe found in logs why before they failed to communicate :/ Happy to see that 's solved :)