Search results

Re: GlusterFS & Proxmox Future & Issues Just a followup: Using this command: qemu-img create -f qcow2 gluster://server.domain.com:24007/testvol/images/100/vm-100-disk-1.qcow2 50G Crates a 193KB disk image. 100% sparse, 100% thin. What the heck is making Proxmox's GUI make large disk images...

Hey gents, I just want to know what the outlook is on more/better GlusterFS support in updated versions of Proxmox. I've run into a few usability issues that basically make GlusterFS support almost unusable in Proxmox. For example, the simple creation of a QCOW2 image makes Proxmox timeout...

One thing I've noticed is that Gluster doesnt like the way Proxmox makes .qcow2 disk images. If I make a 500GB QCOW2 disk - Proxmox actually makes and populates a 500GB disk image on the Gluster cluster - therefor timing out the Create VM Process - yet Gluster/Proxmox are still sitting there...

Locations? I'm looking for a literal step by step. >.<

Oh, it totally will not be live. Servers and VMs can go down/offline.

Heya Gents I plan to do an overhaul of our server nework - and one of the things I wanted to do was re-do our cluster. The node names are whacked, and I want to move the primary node to a totally different machine. I have four servers with VMs on them. What steps would I need to take to move...

Ugh. It was rrDNS. As soon as I went back to not using rrDNS, it works fine. Close thread. :(

I made the same mistake. Proxmox installs GRUB to the MBR, so the correct choice would have been your RAID6. The above link worked for me perfectly.

Can anyone tell me why we cannot use more than a single IP for a GlusterFS storage device? Isn't that one of the central aspects of GlusterFS - that its multiple servers and not just one? I have a two-node GlusterFS 3.4.1 cluster running. I can only add one of the two node's IPs to Proxmox. If...