[ovirt-devel] "Could not find working O_DIRECT alignment. Try cache.direct=off"
Christopher Pereira
kripper at imatronix.cl
Thu Apr 30 06:40:10 UTC 2015
virDomainCreateXML() is returning "Could not find working O_DIRECT
alignment. Try cache.direct=off".
This image was working some days ago with a previous version.
Did the image get corrupted or could this be related to a recent change
in oVirt?
--- Logs ---
Thread-694::INFO::2015-04-30 03:32:49,512::vm::1765::vm.Vm::(_run)
vmId=`bc99ded7-edc9-4bc5-bca5-a61a286757d2`::<?xml version="1.0"
encoding="utf-8"?>
<domain type="kvm">
<name>Test 31</name>
<uuid>bc99ded7-edc9-4bc5-bca5-a61a286757d2</uuid>
<memory>12582912</memory>
<currentMemory>12582912</currentMemory>
<vcpu current="4">16</vcpu>
<devices>
<channel type="unix">
<target name="com.redhat.rhevm.vdsm"
type="virtio"/>
<source mode="bind"
path="/var/lib/libvirt/qemu/channels/bc99ded7-edc9-4bc5-bca5-a61a286757d2.com.redhat.rhevm.vdsm"/>
</channel>
<channel type="unix">
<target name="org.qemu.guest_agent.0"
type="virtio"/>
<source mode="bind"
path="/var/lib/libvirt/qemu/channels/bc99ded7-edc9-4bc5-bca5-a61a286757d2.org.qemu.guest_agent.0"/>
</channel>
<input bus="ps2" type="mouse"/>
<sound model="ich6"/>
<memballoon model="virtio">
<address bus="0x00" domain="0x0000"
function="0x0" slot="0x06" type="pci"/>
</memballoon>
<controller index="0" ports="16" type="virtio-serial">
<address bus="0x00" domain="0x0000"
function="0x0" slot="0x04" type="pci"/>
</controller>
<video>
<address bus="0x00" domain="0x0000"
function="0x0" slot="0x02" type="pci"/>
<model heads="1" type="cirrus" vram="32768"/>
</video>
<graphics autoport="yes" listen="0" passwd="*****"
passwdValidTo="1970-01-01T00:00:01" port="-1" type="vnc"/>
<interface type="bridge">
<address bus="0x00" domain="0x0000"
function="0x0" slot="0x03" type="pci"/>
<mac address="00:1a:4a:16:01:51"/>
<model type="virtio"/>
<source bridge=";vdsmdummy;"/>
<filterref filter="vdsm-no-mac-spoofing"/>
<link state="up"/>
</interface>
<disk device="cdrom" snapshot="no" type="file">
<address bus="1" controller="0" target="0"
type="drive" unit="0"/>
<source file="" startupPolicy="optional"/>
<target bus="ide" dev="hdc"/>
<readonly/>
<serial/>
</disk>
<disk device="disk" snapshot="no" type="file">
<address bus="0x00" domain="0x0000"
function="0x0" slot="0x05" type="pci"/>
<source
file="/rhev/data-center/00000001-0001-0001-0001-00000000007e/3233144b-7be1-445f-9ea6-6aebbacbb93f/images/5a7db80d-f037-4dcb-8059-6706a2b62b19/db63659c-c9a9-4f4f-887f-3443a008a27e"/>
<target bus="virtio" dev="vda"/>
<serial>5a7db80d-f037-4dcb-8059-6706a2b62b19</serial>
<boot order="1"/>
<driver cache="none" error_policy="stop"
io="threads" name="qemu" type="raw"/>
</disk>
</devices>
<os>
<type arch="x86_64" machine="rhel6.5.0">hvm</type>
<smbios mode="sysinfo"/>
</os>
<sysinfo type="smbios">
<system>
<entry name="manufacturer">oVirt</entry>
<entry name="product">oVirt Node</entry>
<entry
name="version">7-1.1503.el7.centos.2.8</entry>
<entry
name="serial">4C4C4544-0042-4B10-8058-B2C04F5A5A31</entry>
<entry
name="uuid">bc99ded7-edc9-4bc5-bca5-a61a286757d2</entry>
</system>
</sysinfo>
<clock adjustment="3600" offset="variable">
<timer name="rtc" tickpolicy="catchup"/>
<timer name="pit" tickpolicy="delay"/>
<timer name="hpet" present="no"/>
</clock>
<features>
<acpi/>
</features>
<cpu match="exact">
<model>SandyBridge</model>
<topology cores="1" sockets="16" threads="1"/>
</cpu>
</domain>
Thread-694::ERROR::2015-04-30
03:32:49,978::vm::741::vm.Vm::(_startUnderlyingVm)
vmId=`bc99ded7-edc9-4bc5-bca5-a61a286757d2`::The vm start process failed
Traceback (most recent call last):
File "/usr/share/vdsm/virt/vm.py", line 689, in _startUnderlyingVm
self._run()
File "/usr/share/vdsm/virt/vm.py", line 1800, in _run
self._connection.createXML(domxml, flags),
File "/usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py",
line 126, in wrapper
ret = f(*args, **kwargs)
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 3427, in
createXML
if ret is None:raise libvirtError('virDomainCreateXML() failed',
conn=self)
libvirtError: internal error: process exited while connecting to
monitor: 2015-04-30T06:32:49.783554Z qemu-kvm: -drive
file=/rhev/data-center/00000001-0001-0001-0001-00000000007e/3233144b-7be1-445f-9ea6-6aebbacbb93f/images/5a7db80d-f037-4dcb-8059-6706a2b62b19/db63659c-c9a9-4f4f-887f-3443a008a27e,if=none,id=drive-virtio-disk0,format=raw,serial=5a7db80d-f037-4dcb-8059-6706a2b62b19,cache=none,werror=stop,rerror=stop,aio=threads:
could not open disk image
/rhev/data-center/00000001-0001-0001-0001-00000000007e/3233144b-7be1-445f-9ea6-6aebbacbb93f/images/5a7db80d-f037-4dcb-8059-6706a2b62b19/db63659c-c9a9-4f4f-887f-3443a008a27e:
Could not find working O_DIRECT alignment. Try cache.direct=off.
---
Related BZ : https://bugzilla.redhat.com/show_bug.cgi?id=1184363
More information about the Devel
mailing list