Anyone else having trouble using iscsi?

Latest response

I seem to be unable to use ISCSI direct attached LUN's with VM's, unless I log onto the hypervisor, and manually add the 'qemu' user to the 'disk'. This is not permanent, so it sucks, but it is enough for testing.

 

This is the error message I get:

 

Thread-1773::DEBUG::2012-11-16 13:29:01,455::vm::607::vm.Vm::(_startUnderlyingVm) vmId=`8b982672-1ca8-488b-a112-dcd0a7f8bc15`::_ongoingCreations released
Thread-1773::ERROR::2012-11-16 13:29:01,458::vm::631::vm.Vm::(_startUnderlyingVm) vmId=`8b982672-1ca8-488b-a112-dcd0a7f8bc15`::The vm start process failed
Traceback (most recent call last):
File "/usr/share/vdsm/vm.py", line 597, in _startUnderlyingVm
File "/usr/share/vdsm/libvirtvm.py", line 1416, in _run
File "/usr/lib64/python2.6/site-packages/vdsm/libvirtconnection.py", line 83, in wrapper
File "/usr/lib64/python2.6/site-packages/libvirt.py", line 2490, in createXML
libvirtError: internal error Process exited while reading console log output: char device redirected to /dev/pts/1
qemu-kvm: -drive file=/dev/mapper/1IET_00010002,if=none,id=drive-virtio-disk1,format=raw,serial=,cache=none,werror=stop,rerror=stop,aio=native: could not open disk image /dev/mapper/1IET_00010002: Permission denied

Thread-1773::DEBUG::2012-11-16 13:29:01,460::vm::969::vm.Vm::(setDownStatus) vmId=`8b982672-1ca8-488b-a112-dcd0a7f8bc15`::Changed state to Down: internal error Process exited while reading console log output: char device redirected to /dev/pts/1
qemu-kvm: -drive file=/dev/mapper/1IET_00010002,if=none,id=drive-virtio-disk1,format=raw,serial=,cache=none,werror=stop,rerror=stop,aio=native: could not open disk image /dev/mapper/1IET_00010002: Permission denied

Thread-1778::DEBUG::2012-11-16 13:29:02,993::BindingXMLRPC::894::vds::(wrapper) client [10.10.10.10]::call vmGetStats with ('8b982672-1ca8-488b-a112-dcd0a7f8bc15',) {}
Thread-1778::DEBUG::2012-11-16 13:29:02,993::BindingXMLRPC::900::vds::(wrapper) return vmGetStats with {'status': {'message': 'Done', 'code': 0}, 'statsList': [{'status': 'Down', 'hash': '0', 'exitMessage': 'internal error Process exited while reading console log output: char device redirected to /dev/pts/1\nqemu-kvm: -drive file=/dev/mapper/1IET_00010002,if=none,id=drive-virtio-disk1,format=raw,serial=,cache=none,werror=stop,rerror=stop,aio=native: could not open disk image /dev/mapper/1IET_00010002: Permission denied\n', 'vmId': '8b982672-1ca8-488b-a112-dcd0a7f8bc15', 'timeOffset': '-1', 'exitCode': 1}]}

 

However, this seems to be a bug the size of Antarctica, so I'd like to file a bug. What product do I file RHEV bugs against in Red Hat Bugzilla. And don't say 'RHEV', because that product doesn't show in the 'Enter new bug' screen... :(

ma

Responses