Say I have two GlusterFS nodes - 10.0.0.220 and 10.0.0.221 - If I simply add the 10.0.0.220 node in as a Gluster Storage type, the glusterfs api intelligently finds the other node. You dont need to tell Proxmox about both. Just one. Works great!
Oh, I'm sure it works fine with Linux. Problem is, all of my major VMs that are moving tons of data are Windows Server VM's. CPU is not an issue at all. I'm just surprised that the Virtio drivers clearly say theyre connected at 10GBE - but do not perform anywhere close. Why even have it as an...
Gentlemen,
I have a Proxmox node directly connected to a GlusterFS cluster via Infiniband. I installed two Windows 7 VM's to the Proxmox node. Running HD Tune on the Win7 VM's, I'm seeing CRAZY good throughputs and high IOPS. :D
I then created a bridge device (vmbr1) that did not bridge to any...
Re: GlusterFS & Proxmox Future & Issues
Yes yes, this works perfectly fine for a new VM. I've done it that way, too.
Problems still exist for restoring a VM from a backup. I'm looking to move all of my current VMs off a QNAP NAS device to a more hearty GlusterFS solution - and the only way to...
Re: GlusterFS & Proxmox Future & Issues
FYI - restore the backup to an NFS share, then Move Disk to GlusterFS and change it from QCOW2 to VMDK causes windows VM's to fail upon boot.
Attempting to then use qemu-img convert to convert the vmdk to qcow2.
qemu-img convert -f vmdk...
Re: GlusterFS & Proxmox Future & Issues
Yep, thats exactly it. This renders QCOW2 with Proxmox basically unusable when creating or making qcow2 disk images with the Proxmox GUI.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.