spirit's latest activity

  • spirit
    spirit replied to the thread Vmware to proxmox (windows VM).
    try to boot on ide first Then, you can convert to virtio-scsi - change your controller to virtio-scsi instead lsi - add a second temporary small disk in scsi0 install virtio-win drivers in windows stop the vm delete the temporary disk switch...
  • spirit
    spirit replied to the thread iothread-vq-mapping support.
    I'll try to get it for pve9 https://lists.proxmox.com/pipermail/pve-devel/2025-July/072194.html
  • spirit
    spirit replied to the thread Proxmox fencing.
    I can confirm that I had tried with Dell idrac some year ago , and I had a lot of bug with unexpected reboot. Never had problem with softdog. (The only benefit was to have log of the watchdog in the idrac log)
  • spirit
    yes, it's a known bug, snat rules management should be improve. (currently they are put as post-up in /etc/network/intefaces , so applied multiple times). It should need some kind of service to manage it. (maybe in new proxmox firewall for...
  • spirit
    mmm, it's possible that some value are not applied at reload. btw, "static auto" is invalid, it's static or auto ifupdown is able to detect inet|inet6 or static|auto automatically, so it should work if you put accept_ra && autoconf 1 directly...
  • spirit
    the flow is like : vm(103.204.193.X)---->vnet(103.204.193.1)------- default route to exit-node ----->proxmoxnode01(exit-node)---------default gw------------->upstream routeur then in the reverse direction upstream routeur-----route to...
  • spirit
    do you have done a reload or a restart of networking service after change ? (a reload shouldn't break you vm, but a restart with detach all vms interfaces, as they are not defined in /etc/network/interfaces)
  • spirit
    spirit replied to the thread Compatibility Matrix.
    yes sure, you need to expose a big lun on both side, configure multipath, and add a lvm shared storage on top. (No snapshot && no thin provisioning yet, it should be available in pve9) Just be carefull, you need a third node to keep quorum...
  • spirit
    I don't known what kind of cpu redhat is using, but it's really scaling across multiple threads (around x2~x4 from baselineà. Personnally, I really want to test it on ceph rbd, because it's currently really cpu limited client side around 70k...
  • spirit
    Yes, I known this can increase latency. I need to look to add an option to pin iothread on specific cpu, like for the vm cpu cores. (ideally iothread have dedicated cores and vm cpus other cores, on same numa node than nvme drive)...