Search results

yes, snapshots on san are coming (with qcow2 on top of lvm, like ovirt indeed) . I'm working on it, I hope to finish it for pve9.

don't use zfs or ceph on consumer ssd/nvme without plp , performance will always be bad.

For this specific case, I think this is normal to have random slow ops error, as your pg and replicats can be on different slorage speed. (so, a primary write on fast sdd, will always wait for replicat on slow hdd), and for read, it's really russian roulette. (Personally, I'll do 2...

you have mixed ssd and hdd in the same pool ???

ok make sense. I'll try to see if we could implement it.

maybe you are cpu limited in the vm (currently 1disk can use only 1core with iothread). BTW, cache=writeback don't make too much sense with local nvme. It can even slowdown result. better to use cache=none.

the main reason is that current evpn implementation is done to use the anycast gateway distributed (and do l3rougint)on each node, but I'll not work if you use vlan behind. (Or maybe do you plan to use evpn to transport L2 only witout any routing ?)

https://pve.proxmox.com/wiki/Serial_Terminal#Add_a_virtual_serial_port_to_the_VM (then you can use the alternative xterm console, where copy/paste is working). but you can't have display, until you configure some config in the guest

xterm console allow copy paste, but you need to redirect output first to the serial. (maybe copy/paste could work blindly, no sure)

you should first restart pve-cluster service, to mount the /etc/pve directory . (it's used /var/lib/pve-cluster/config.db as backend, and expose it like a fs in /etc/pve)

mv /etc/pve/ha/resources.cfg /tmp/ ;) then move back the file again Note than you need to close watchdog too to avoid fencing, the currently only is it to 1) stop pve-ha-lrm on all nodes, node by node 2) stop pve-ha-crm on all nodes, node by node then, do the reverse when on have...

I have see some similar problem with migration from vmware, seem than rocky don't have virtio drivers by default in initramfs when it's deployed first on different hypervistor maybe try to boot with ide, then sudo dracut -f --regenerate-all --add-drivers "virtio_blk virtio_scsi virtio_net"...

shouldn't be a problem, but if you use HA, you really to disable it before.

don't use wal/db disk on separated drive, simply use your enterprise ssd as osd with wal/db disk inside

ah ok ! ^_^ for the restart, I really don't known (maybe it's an option of fortigate side), but you can use "/usr/lib/frr/frr-reload.py /etc/frr/frr.conf --reload" to reload config without restarting the frr process

(just to be sure, your frr.conf is on fortigate ? forgate use frr ? )

you need to announce a default type5 route from your fortigate, and it should already by done with your address-family l2vpn evpn default-originate ipv4 default-originate ipv6 exit-address-family "neighbor VTEP activate" need to be in "address-family l2vpn evpn", like in your config...

this message looks strange. what is the content of /etc/frr/daemons ?

what is your nvme model ? seem unrelated, icmp is network, slow storage can't impact it. but slow network between the osd could impact io. (do you have tried some icmp test between your proxmox nodes directly ?) should be investigated

you can use " qm disk import <vmid> yourexportedfile.qcow2 <targetstorage> --format raw|qcow2", it'll import the disk, do the format converstion and add the disk to vm configuration .