Search results

  1. N

    OVMF / UEFI doesn't see migrated VM disk

    Greetings. I could use some guidance in getting Proxmox VE's OVMF (UEFI) to see a Debian 11 VM I've migrated over from a VMware vSphere cluster. Migration of other VMs that use BIOS went fine using "qm importovf". For this VM, which used EFI in vSphere, I completed the migration, changed the...
  2. N

    Best practices: Hardware vs software RAID

    Leaving things alone, then, at least until I lay hands on a new controller and SSDs. Thanks all for your guidance.
  3. N

    Best practices: Hardware vs software RAID

    My knowledge of storage would fill a thimble, but if it's at all like network benchmarking, where I have a bit of experience, then (a) different tools can measure different things and (b) all benchmarks are broken in some way. The question here: Is anything with this setup or these results...
  4. N

    Best practices: Hardware vs software RAID

    OK, thanks. I ran each test five times and saw very consistent results. I'm pasting the full output below of iteration 1 from each test. I've also pasted the result from a pveperf test run after both sets of fio benchmarks. Let me know if anyone wants to see the output of all five iterations...
  5. N

    Best practices: Hardware vs software RAID

    Thanks for these. Both commands want a --size parameter. Just checking: Are you looking for "--size=4K" here? If not, what other value?
  6. N

    Best practices: Hardware vs software RAID

    Pardon my ignorance, but I'm unfamiliar with the fio tool. Which of these fio tests would offer a meaningful check of pveperf's fsync numbers? random reads file random read/writes random read/writes sequential reads And are we looking to measure IOPS or throughput or latency?
  7. N

    Best practices: Hardware vs software RAID

    The before and after numbers are correct as observed. On subsequent runs of pveperf with caching disabled, FSYNCs dropped a bit, down to the high 1600s. My RAID controller does not have a BBU. This host has redundant power supplies and resides in a data center that has had 100.00 percent...
  8. N

    Best practices: Hardware vs software RAID

    Update: Reconfigured the RAID controller only to learn it doesn't support JBOD. After some misadventures with PXE boot (this host is remote), I set up RAID6 again, this time without caching enabled. Performance is much improved. BEFORE: FSYNCS/SECOND: 185.26 AFTER: FSYNCS/SECOND: 1946.91...
  9. N

    Proxmox installation via PXE: solution

    Answering my own question: What finally worked was formatting the opts variable in the form of PHP options, starting with a question mark and using ampersands instead of spaces as delimiters: set opts ?vga=791&video=vesafb:ywrap,mtrr&ramdisk_size=16777216&rw&quiet&initrd=initrd&splash=silent...
  10. N

    Proxmox installation via PXE: solution

    Help! Picking up this old thread: I'm getting a file-not-found error when executing @morph027's iPXE bootscript to install Proxmox VE 7.1 via PXE Boot. With iPXE method, the client complains like this: http://172.31.5.25/proxmox/7.1/initrd... ok...
  11. N

    Best practices: Hardware vs software RAID

    Greetings. I'm new to Proxmox, and am looking for config recommendations to ensure the best balance of performance and data integrity. On a Supermicro server with a LSI 9260-i4 RAID controller and no battery backup with 4 HDDs attached, is it better to use software RAID with ZFS over hardware...
  12. N

    VMware vSphere -> Proxmox migration "Windows failed to start"

    Changing from BIOS to UEFI did not resolve the problem. UEFI returns a mapping error, which makes sense because the VMware VM used BIOS and did not have an EFI disk. I tried deleting the network adapter from the VM in vSphere and re-exporting, converting to qcow2, and re-importing the image...
  13. N

    VMware vSphere -> Proxmox migration "Windows failed to start"

    Update: All of the v. 173 variants won't complete because the VdService (spice) fails to start. Thanks in advance for further clues on migrating Windows VMs from VMware to Proxmox.
  14. N

    VMware vSphere -> Proxmox migration "Windows failed to start"

    Thanks for your reply. I had not tried installing the VirtIO driver on the VM while it was still in vSphere. The current release of the driver fails to install because it needs Win8 or later. I found a link stating that v. 173-4 was the last known good version for Windows 7. But ... that...
  15. N

    VMware vSphere -> Proxmox migration "Windows failed to start"

    Greetings. I am evaluating Proxmox VE 7.0-8 for possible use as an alternative to an existing VMware vSphere cluster. Linux, FreeBSD, and OpenBSD machines all migrated OK but there's an issue with Windows VMs. After exporting a Windows 7 VM [1] from vSphere and importing to qcow2 format using...
  16. N

    Installed under ESXi

    FWIW I had to enable not only promiscuous mode but also forged transmits in a vSphere distributed switch to allow the Proxmox VE "guest" to see the rest of the network. I could NOT ping any other host or the gateway with only promiscuous mode enabled.