Created attachment 937289 [details] engine vdsm and qemu log files Description of problem: When trying to install OS on VM , it is paused . Probably related to RHEL7 , because when switched to RHEL6.5 host, the problem disappeared ! Version-Release number of selected component (if applicable): Red Hat Enterprise Virtualization Manager Version: 3.5.0-0.11.beta.el6ev vdsm-4.16.3-3.el7.beta.x86_64 libvirt-client-1.1.1-29.el7_0.1.x86_64 How reproducible: Happens sometime. Steps to Reproduce: setup: I've tested it on 2 setups: - 1 RHEL7 host, 1 iSCSI SD, and 1 VM - 1 RHEL7 host, 1 nfs SD, and 1 VM 1. Create new VM with a thin provisioning disk. 2. Run it . 3. open consol , and chose RHEL 6.5 on cobller menue . 4. continue with the installation. Actual results: 5. the console freeze at some point (12% of package installation for me). 6. On Admin GUI , the VM is paused. 7. errors on logs, see in additional info below Expected results: 5. in the console, the installation should end correctly with an active login to the server. Additional info: On engine log : 2014-09-14 08:53:45,636 ERROR [org.ovirt.engine.core.dal.db broker.auditloghandling.AuditLogDirector] (DefaultQuartzSch eduler_Worker-99) Correlation ID: null, Call Stack: null, C ustom Event ID: -1, Message: VM VM1 has paused due to stora ge I/O problem. on VDSM log : Thread-36::ERROR::2014-09-14 08:51:56,923::vm::373::vm.Vm::(_sampleCpuTune) vmId=`44aa0fa8-a9a3-437c-baaf-3385ee92fddc`::libvirt does not support metadata in qemu VM1.log: red_dispatcher_set_cursor_peer: block I/O error in device 'drive-virtio-disk0': Input/output error (5) block I/O error in device 'drive-virtio-disk0': Input/output error (5)
Nir, don't we already have a BZ for this issue (an LVM issue, IIRC)?
*** This bug has been marked as a duplicate of bug 1127460 ***
Gal, what would help to solve the original bug, is to get the selinux lable of the volume, when you start the installation, and after the error. Please do this: 1. Create the vm disk 2. Find the the directory where the volume lives 3. Start the vm 4. Run this command while true; do ls -lZ /path/to/directory >> ls-lz.out; sleep 30; done When the vm pauses, stop this command and upload the ls-lz.out file to the original bug.