<div dir="ltr">Please help. I'm having some recurring errors after VM is deploy PROLOG and then powered on BOOT. At the BOOT phase I suspect there is something going on ... because as soon as I *reboot* the VM I get "Boot failed: could not read the boot disk"<div>
<br></div><div>Upon further inspection the libvirt qemu log files for the specified VM(s) produce "block I/O error in device" as seen below:</div><div><br></div><div><div>[root@shelf3-node2 ~]# tail -f /var/log/libvirt/qemu/one-41.log</div>
<div>2014-06-18 15:47:22.708+0000: starting up</div><div>LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin HOME=/root USER=root LOGNAME=root QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -name one-41 -S -M rhel6.5.0 -enable-kvm -m 512 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 0c282fe0-a689-c92d-1be7-198bddb4e0c0 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/one-41.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/var/lib/one//datastores/0/41/disk.0,if=none,id=drive-virtio-disk0,format=qcow2,cache=none,aio=native -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive file=/var/lib/one//datastores/0/41/disk.1,if=none,media=cdrom,id=drive-ide0-0-0,readonly=on,format=raw -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -netdev tap,fd=29,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=02:00:80:7b:00:35,bus=pci.0,addr=0x3 -vnc <a href="http://0.0.0.0:41">0.0.0.0:41</a> -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5</div>
<div>block I/O error in device 'drive-virtio-disk0': Invalid argument (22)</div><div>block I/O error in device 'drive-virtio-disk0': Invalid argument (22)</div><div>^C</div><div>[root@shelf3-node2 ~]# tail -f /var/log/libvirt/qemu/one-40.log</div>
<div>block I/O error in device 'drive-ide0-0-0': Invalid argument (22)</div><div>block I/O error in device 'drive-ide0-0-0': Invalid argument (22)</div><div>block I/O error in device 'drive-ide0-0-0': Invalid argument (22)</div>
<div>block I/O error in device 'drive-ide0-0-0': Invalid argument (22)</div><div>block I/O error in device 'drive-ide0-0-0': Invalid argument (22)</div><div>block I/O error in device 'drive-ide0-0-0': Invalid argument (22)</div>
<div>block I/O error in device 'drive-ide0-0-0': Invalid argument (22)</div><div>block I/O error in device 'drive-ide0-0-0': Invalid argument (22)</div><div>block I/O error in device 'drive-ide0-0-0': Invalid argument (22)</div>
<div>block I/O error in device 'drive-ide0-0-0': Invalid argument (22)</div><div>block I/O error in device 'drive-ide0-0-0': Invalid argument (22)</div><div>^C</div><div>[root@shelf3-node2 ~]# tail -f /var/log/libvirt/qemu/one-41.log</div>
<div>2014-06-18 15:47:22.708+0000: starting up</div><div>LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin HOME=/root USER=root LOGNAME=root QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -name one-41 -S -M rhel6.5.0 -enable-kvm -m 512 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 0c282fe0-a689-c92d-1be7-198bddb4e0c0 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/one-41.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/var/lib/one//datastores/0/41/disk.0,if=none,id=drive-virtio-disk0,format=qcow2,cache=none,aio=native -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive file=/var/lib/one//datastores/0/41/disk.1,if=none,media=cdrom,id=drive-ide0-0-0,readonly=on,format=raw -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -netdev tap,fd=29,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=02:00:80:7b:00:35,bus=pci.0,addr=0x3 -vnc <a href="http://0.0.0.0:41">0.0.0.0:41</a> -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5</div>
<div>block I/O error in device 'drive-virtio-disk0': Invalid argument (22)</div><div>block I/O error in device 'drive-virtio-disk0': Invalid argument (22)</div><div>block I/O error in device 'drive-virtio-disk0': Invalid argument (22)</div>
<div><br></div><div>Any idea why my configuration deploys the VM(s) to specified hosts in my cluster just fine BUT then upon a reboot produces these block I/O errors??</div><div><br></div><div>I don't suspect that it's my gluster config:</div>
<div><div>Volume Name: GLUSTERFS-ONE</div><div>Type: Distribute</div><div>Volume ID: d40e6dcb-435d-47d5-b575-edfe1eec5b62</div><div>Status: Started</div><div>Number of Bricks: 2</div><div>Transport-type: tcp</div><div>Bricks:</div>
<div>Brick1: storage1:/BRICK0/ONE</div><div>Brick2: storage3:/BRICK0/ONE</div><div>Options Reconfigured:</div><div>storage.owner-gid: 9869</div><div>storage.owner-uid: 9869</div><div>server.allow-insecure: on</div></div><div>
<br></div><div>Or Datastore config:</div><div><div>[oneadmin@shelf3-node1 ~]$ onedatastore list</div><div> ID NAME SIZE AVAIL CLUSTER IMAGES TYPE DS TM</div><div> 0 system 2T 92% TESTCLUSTER 0 sys - shared</div>
<div> 1 default 131T 73% TESTCLUSTER 6 img fs shared</div><div> 2 files 59.1G 94% TESTCLUSTER 0 fil fs ssh</div><div> 103 GlusterFS KVM 131T 73% TESTCLUSTER 3 img fs shared</div>
</div><div><br></div><div>ANY IDEA. THIS HAS STUMPED ME. Going onto a couple of days now ... everything else seems to function as expected.</div><div><br></div>-- W<div dir="ltr"><div><br></div></div>
</div></div>