libvirt users - Dec 2013 - gentoo linux, problem starting vm´s when cache=none

hello mailinglist,

on gentoo system with qemu-1.6.1, libvirt 1.1.4, libvirt-glib-0.1.7, 
virt-manager 0.10.0-r1

when i set on virtual machine "cache=none" in the disk-menu, the
machine
faults to start with:

<<
Fehler beim Starten der Domain: Interner Fehler: Prozess während der 
Verbindungsaufnahme zum Monitor beendet :qemu-system-x86_64: -drive 
file=/raid6/virtual/debian-kaspersky.img,if=none,id=drive-virtio-disk0,format=qcow2,cache=none,aio=native:
could not open disk image /raid6/virtual/debian-kaspersky.img: Invalid 
argument


Traceback (most recent call last):
   File "/usr/share/virt-manager/virtManager/asyncjob.py", line 100,
in
cb_wrapper
     callback(asyncjob, *args, **kwargs)
   File "/usr/share/virt-manager/virtManager/asyncjob.py", line 122,
in
tmpcb
     callback(*args, **kwargs)
   File "/usr/share/virt-manager/virtManager/domain.py", line 1210, in
startup
     self._backend.create()
   File "/usr/lib64/python2.7/site-packages/libvirt.py", line 708, in 
create
     if ret == -1: raise libvirtError ('virDomainCreate() failed', 
dom=self)
libvirtError: Interner Fehler: Prozess während der Verbindungsaufnahme 
zum Monitor beendet :qemu-system-x86_64: -drive 
file=/raid6/virtual/debian-kaspersky.img,if=none,id=drive-virtio-disk0,format=qcow2,cache=none,aio=native:
could not open disk image /raid6/virtual/debian-kaspersky.img: Invalid 
argument
>> 
when i switch back to cache=default, the machine start like a charm.

any ideas why? i cant find anything in logs, only  this "invalid 
argument".

the machine is created with profile "linux / debian squeeze" cause its
a
debian 6

marko

On Tue, Dec 10, 2013 at 11:20:35AM +0100, Marko Weber | ZBF
wrote:
> 
> hello mailinglist,
> 
> on gentoo system with qemu-1.6.1, libvirt 1.1.4, libvirt-glib-0.1.7,
> virt-manager 0.10.0-r1
> 
> when i set on virtual machine "cache=none" in the disk-menu, the
> machine faults to start with:
> 
> <<
> Fehler beim Starten der Domain: Interner Fehler: Prozess während der
> Verbindungsaufnahme zum Monitor beendet :qemu-system-x86_64: -drive
file=/raid6/virtual/debian-kaspersky.img,if=none,id=drive-virtio-disk0,format=qcow2,cache=none,aio=native:
> could not open disk image /raid6/virtual/debian-kaspersky.img:
> Invalid argument
> 
> 
> Traceback (most recent call last):
>   File "/usr/share/virt-manager/virtManager/asyncjob.py", line
100,
> in cb_wrapper
>     callback(asyncjob, *args, **kwargs)
>   File "/usr/share/virt-manager/virtManager/asyncjob.py", line
122,
> in tmpcb
>     callback(*args, **kwargs)
>   File "/usr/share/virt-manager/virtManager/domain.py", line
1210,
> in startup
>     self._backend.create()
>   File "/usr/lib64/python2.7/site-packages/libvirt.py", line 708,
in
> create
>     if ret == -1: raise libvirtError ('virDomainCreate() failed',
> dom=self)
> libvirtError: Interner Fehler: Prozess während der
> Verbindungsaufnahme zum Monitor beendet :qemu-system-x86_64: -drive
file=/raid6/virtual/debian-kaspersky.img,if=none,id=drive-virtio-disk0,format=qcow2,cache=none,aio=native:
> could not open disk image /raid6/virtual/debian-kaspersky.img:
> Invalid argument
> >>
> 
> when i switch back to cache=default, the machine start like a charm.
> 
> any ideas why? i cant find anything in logs, only  this "invalid
> argument".
cache=none uses O_DIRECT flag. if you get "Invalid argument" it
usually
means that your filesystem is bad and does not support O_DIRECT

Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

On Tue, Dec 10, 2013 at 03:21:59PM +0100, Marko Weber | ZBF
wrote:
> Hello Daniel,
> 
> Am 2013-12-10 11:23, schrieb Daniel P. Berrange:
> >On Tue, Dec 10, 2013 at 11:20:35AM +0100, Marko Weber | ZBF wrote:
> >>
> >>hello mailinglist,
> >>
> >>on gentoo system with qemu-1.6.1, libvirt 1.1.4,
libvirt-glib-0.1.7,
> >>virt-manager 0.10.0-r1
> >>
> >>when i set on virtual machine "cache=none" in the
disk-menu, the
> >>machine faults to start with:
> >>
> >><<
> >>Fehler beim Starten der Domain: Interner Fehler: Prozess während
der
> >>Verbindungsaufnahme zum Monitor beendet :qemu-system-x86_64:
> >>-drive
file=/raid6/virtual/debian-kaspersky.img,if=none,id=drive-virtio-disk0,format=qcow2,cache=none,aio=native:
> >>could not open disk image /raid6/virtual/debian-kaspersky.img:
> >>Invalid argument
> >>
> >>
> >>Traceback (most recent call last):
> >>  File "/usr/share/virt-manager/virtManager/asyncjob.py",
line 100,
> >>in cb_wrapper
> >>    callback(asyncjob, *args, **kwargs)
> >>  File "/usr/share/virt-manager/virtManager/asyncjob.py",
line 122,
> >>in tmpcb
> >>    callback(*args, **kwargs)
> >>  File "/usr/share/virt-manager/virtManager/domain.py",
line 1210,
> >>in startup
> >>    self._backend.create()
> >>  File "/usr/lib64/python2.7/site-packages/libvirt.py",
line 708, in
> >>create
> >>    if ret == -1: raise libvirtError ('virDomainCreate()
failed',
> >>dom=self)
> >>libvirtError: Interner Fehler: Prozess während der
> >>Verbindungsaufnahme zum Monitor beendet :qemu-system-x86_64:
> >>-drive
file=/raid6/virtual/debian-kaspersky.img,if=none,id=drive-virtio-disk0,format=qcow2,cache=none,aio=native:
> >>could not open disk image /raid6/virtual/debian-kaspersky.img:
> >>Invalid argument
> >>>>
> >>
> >>when i switch back to cache=default, the machine start like a
charm.
> >>
> >>any ideas why? i cant find anything in logs, only  this
"invalid
> >>argument".
> >
> >cache=none uses O_DIRECT flag. if you get "Invalid argument"
it usually
> >means that your filesystem is bad and does not support O_DIRECT
> 
> i use vanilla-kernel 3.10.23 and xfs on the partition where the vm
> .img is lying.
> 
> the mount options i use:    /raid6 type xfs
> (rw,noatime,nodiratime,largeio,nobarrier,logbsize=256k)
> 
> any wrong here?
XFS should support O_DIRECT, but possibly one of the mount option is
causing trouble. I don't know enough about XFS to answer for sure.

BTW, please keep your replies on the mailing list...

Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|