search for: adminvm

...9.6 and 10.5. If we switch from QEMU RAW to QCOW2, the problem disappears. The problem is not reproduced when we take gluster out of the equation (meaning, pointing QEMU at a local disk image instead of gluster-hosted one ? that works fine). The problem can be reproduced this way: * Assume /adminvm/images on a gluster sharded volume * rm /adminvm/images/adminvm.img * qemu-img create -f raw /adminvm/images/adminvm.img 50M Now start the virtual machine that refers to the above adminvm.img file * Boot up a rescue environment or a live mode or similar * sgdisk --zap-all /dev/sda...

...QEMU RAW to QCOW2, the problem disappears. > ? > The problem is not reproduced when we take gluster out of the > equation (meaning, pointing QEMU at a local disk image instead of > gluster-hosted one ? that works fine). > ? > The problem can be reproduced this way: > * Assume /adminvm/images on a gluster sharded volume > * rm /adminvm/images/adminvm.img > * qemu-img create -f raw /adminvm/images/adminvm.img 50M > ? > Now start the virtual machine that refers to the above adminvm.img > file > * Boot up a rescue environment or a live mode or similar > * sgdisk...

...would be welcome news. <devices> <emulator>/usr/libexec/qemu-kvm</emulator> <disk type='network' device='disk'> <driver name='qemu' type='raw' cache='none'/> <source protocol='gluster' name='adminvm/images/adminvm.img' index='2'> <host name='localhost' port='24007'/> </source> <backingStore/> <target dev='sdh' bus='scsi'/> <alias name='scsi1-0-0-0'/> <address type...

...g bricks out of space by accident. We would like to avoid the kludge of calling qemu-img 10 times (or more) to make a larger fallocated image. If there are suggested methods or tunings, please let me know! We are currently at gluster 9.3 Volume setup: [root at nano-1 images]# gluster volume info adminvm Volume Name: adminvm Type: Replicate Volume ID: e09122b9-8bc4-409b-a423-7596feebf941 Status: Started Snapshot Count: 0 Number of Bricks: 1 x 3 = 3 Transport-type: tcp Bricks: Brick1: 172.23.254.181:/data/brick_adminvm Brick2: 172.23.254.182:/data/brick_adminvm Brick3: 172.23.254.183:/data/brick_ad...