Recent content by Gilberto Ferreira

  1. G

    Proxmox VE 7 is vulnerable to some type of 0day/RCE non auth

    In any case, I don't think this is a 0day vulnerability, because on this is happen due to out date servers and bad servers administration, to say the least. Many of this vulnerabilities are well-know documented, such as kernel and ssh vulnerabilities. So, your job is do not exposed a weak server...
  2. G

    Proxmox VE 7 is vulnerable to some type of 0day/RCE non auth

    I got reports from Proxmox VE 8.0.3, 8.2 and 8.4 as well... And here is a compromissed server:
  3. G

    Proxmox VE 7 is vulnerable to some type of 0day/RCE non auth

    Hi guys... Anybody can confirm if PVE 8 is also affected???
  4. G

    PVE VM replication standalone host to 3 node PVE cluster with CEPH shared storage

    Perhaps you sould take a look in PVE-Zsync. One doesn't need to have the node in cluster, I guess. https://pve.proxmox.com/wiki/PVE-zsync Just an idea.
  5. G

    Proxmox Virtual Environment now available for 64-bit ARM (arm64)!

    This an excelent news... It's just show how owesome Proxmox is... Go go Proxmox... :)
  6. G

    Migration from VMware

    Starwind has a nice tools as well... https://www.starwindsoftware.com/starwind-v2v-converter I never used, but got friends that did it... I rather use clonezilla or redorescue as I pointed out... Redorescue always work for me... But, go ahead, and try others... Best regards.
  7. G

    Migration from VMware

    Try http://redorescue.com/ Works 100% for me. And, first, remove vmware tools, if installed.!
  8. G

    Problem with PVE 8.1 and OCFS2 shared storage with io_uring

    yeah... that's what I am doing since use ocfs2 for the first time. Thanks for the advice.
  9. G

    Problem with PVE 8.1 and OCFS2 shared storage with io_uring

    Oh! My mistake! I just set cache = none and get those nasty errors. Put cache = writeback and it's work fine. Sorry
  10. G

    Problem with PVE 8.1 and OCFS2 shared storage with io_uring

    But I used the writeback cache in the Proxmox 8.4 as well I got bugged! So, still, I can't explain why works on newest version of kernel and PVE. Anyway... It's works.... That what's matter.
  11. G

    Problem with PVE 8.1 and OCFS2 shared storage with io_uring

    Or perhaps, this is has to do with new QEMU? We need some expert explanation here.
  12. G

    Problem with PVE 8.1 and OCFS2 shared storage with io_uring

    just to validate this process, I create a 2 node cluster with Proxmox VE 8.4.19 and with the very same storage, created with Debian 13 and TargetCLI. Now I got that error: With Proxmox VE 9 and newer kernels, no error so far, at least here for me. Best regards.
  13. G

    Problem with PVE 8.1 and OCFS2 shared storage with io_uring

    So... I went ahead and create a quick and simple target iscsi with Debian and targetcli. I've created the backstore, target and luns with sinble IP. After that, I create the device in proxmox with: iscsiadm -m discovery -t st -p 172.18.100.120 iscsiadm -m node -L all lsscsi [7:0:0:0] disk...
  14. G

    [SOLVED] Resize Ubuntu VM disk

    In your case, or better, in any case, it's needs to use growpart first. Before use it, perhaps is need to install cloud-guest-utils
  15. G

    pve 9.2 fails to install

    Try to append this options in the grub: pcie_aspm=off intel_iommu=off intel_idle.max_cstate=0 acpi_power_meter=off nomodeset This options has save me for a lot of issue. pcie_aspm=off What it does: Disables Active State Power Management for PCI Express (ASPM). What it is for: Prevents PCIe...
Top Bottom
Back