Recent content by spirit

  1. spirit

    AD Smartcard Authentication for web GUI

    is it possible to use oidc with your AD/entra ? I'm not sure about smartcard with browser, but it's working fine with our security keys.
  2. spirit

    Frr update to 10.4.1-1 broke external routing?

    they an issue on their github about evpn and their new unified startup script (race between zebra daemon not 100% started before bgpd daemon is starting , so some routes are not registered in kernel , until you restart manually the bgp daemon again) https://github.com/FRRouting/frr/issues/19756
  3. spirit

    Server load graph

    1= 1 core, 2= cores, ... the load average shouldn't be more than the total number of cores of your host.
  4. spirit

    VMware CPU Ready equivalent in Proxmox

    you have the new pressure stats in pve9, which is almost the same than CPU readyness. (0 is ok, over 0 mean than your vm cpu need to wait ). Same for storage && memory pressure. no alerting is available in pve yet, you need to use external monitoring tool
  5. spirit

    HA migration time

    this is strange, the vm should be started directly after the move. You don't have added start delay in vm options ?
  6. spirit

    Bad experience on Window Server running SQL on PVE 9.1

    They are still optimisation not yet implemented in qcow2 on lvm share (mainly the cache size), it could impact the performance with disk > 300Gb. But it should impact so much the performance. do you have tried with raw format to compare instead qcow2? also, windows virtio driver could have...
  7. spirit

    NTFS drive, mounted & passthrough simultaneously

    because you can't mount a ntfs filesystem on 2 machines at the same time....you are going to kill it if you do this...
  8. spirit

    Feature request: VM configuration toggle for 4k block device sector size

    what is your cpu usage during the bench ? currently iothread use only 1core, so you could be cpu limited in rand4k. (I'm working on it to add support for the new multithreading feature ). It could explain the difference, if hyper-v is able to use multiple cores by disk.
  9. spirit

    Proxmox VE - disaster recovery (equivalent to VMware's SRM)

    It should come in the future with proxmox datacenter manager. (2 differents cluster + storage replication ). Not sure It'll be ready for 1.0 , but I'm pretty sure that the feature will be available in 2016. For now, you need to replicate the storage yourself (depending of the storage techno...
  10. spirit

    strange issues with snapshot backups

    if your fleecing storage is full, sure, you'll got io-error. But it's helping too to avoid slowdown during backup if your pbs is slow. for example, production is on nvme, and pbs is on hdd. You'll have slowdown when backup is running if write occur on a block not yet saved. With fleecing, if...
  11. spirit

    Proxmox 9.1.1 FC Storage via LVM

    The lock is managed by proxmox code directly. (through pmxcfs/corosync). You can't delete 2 lvm volumes at the same time.
  12. spirit

    strange issues with snapshot backups

    you can also use a fleecing device in schedule backups advanced option, to define a temp buffer disk. (could be local storage)
  13. spirit

    [TUTORIAL] Inside Proxmox VE 9 SAN Snapshot Support

    I'm not sure, as it's using an ioctl ioctl(fd, BLKZEROOUT) , to tell to the storage to write 0 from a begin sector to a end sector . (Some kind of offloading, a little bit like discard). So, I don't think that O_DIRECT , CACHE_NONE,... apply here, as we don't really write zeroes through the...
  14. spirit

    Snapshots as Volume-Chain Creates Large Snapshot Volumes

    Maybe because if the space is allocate again to a new vm, if the vm is doing a discard, it should remove the zeroed block yes, it's zeroing by security, to avoid to have old datas when you'll create a new vm on the old allocated space of previous vm.. but of course this zerroed space is...
  15. spirit

    Snapshots as Volume-Chain Creates Large Snapshot Volumes

    for secure delete, the new blkdiscard here, is not using discard, but zeroing feature (blkdiscard -z). It's a little bit different, because it's really writing zeroes (telling to the storage to writing zeroes by range from this begin sector - end sectore), that t's it's faster than cstream...