- Users - oVirt List Archives

Re: [Users] could not add iscsi disk in ovirt.
by Dafna Ron 29 Sep '13

29 Sep '13

you don't have to reconfigure engine to create iscsi pool. you can create multiple pools, the only limitation is that you will need a host for the each of the DCs. but you can move one host from one DC to another... so if you have 2 hosts just create a new DC and move one of the hosts there. I think that the direct lun is only for iscsi and fiber but I can give you a 100% certainty answer on Monday. I don't think its supported for NFS... I can check for you on Monday for sure. On 09/27/2013 03:28 PM, Saurabh wrote: > On 27/09/13 19:52, Dafna Ron wrote: >> wait :) >> >> the first screen shot was of local storage and internal disk type - >> not related at all to the direct lun feature. >> >> the second screen shot is for iscsi storage pool. >> it shows a current connected lun that you have. >> >> try this: >> >> create a new target lun. >> log in to the webadmin -> disks tab -> new disk >> select the Default DC (which is your iscsi storage type) -> expend >> the "discover tartest" >> put in your storage server (where you created the lun) -> discover >> you should than see a list of targets -> log in >> select the target and press OK. >> >> >> On 09/27/2013 03:11 PM, Saurabh wrote: >>> On 27/09/13 19:14, Dafna Ron wrote: >>>> the output is empty in both your outpit and the logs. >>>> >>>> This is the part in the log that shows that you do not have any >>>> devices: return: [] >>>> >>>> when you create a new disk and select the NFS DC- can you please >>>> send me the screen shot of that? >>>> >>>> >>>> On 09/27/2013 02:41 PM, Saurabh wrote: >>>>> On 27/09/13 18:40, Dafna Ron wrote: >>>>>> I am not sure direct lun will be supported for an NFS pool... can >>>>>> you try the same from iscsi pool? >>>>>> >>>>>> is this lun being used somewhere else or did you create a new one? >>>>>> you can run vdsClient -s 0 getDeviceList to see the list of the >>>>>> available luns and if the status is free or not. >>>>>> (it should also in the logs (engine and vdsm) when you discover >>>>>> the luns from the webadmin. >>>>>> >>>>>> >>>>>> On 09/27/2013 01:43 PM, Saurabh wrote: >>>>>>> >>>>>>> Hi guys, I am running ovirt with NFS as storage pool. Everything >>>>>>> is working quite fine for me. The only problem is I could not >>>>>>> add the a new iscsi disk in Disk tab. When I go to the Disk tab >>>>>>> there is an option of adding new disk from internal storage and >>>>>>> another option is add External (Direct Lun). When I opt for the >>>>>>> External (Direct LUN), I am able to discover the Lun but could >>>>>>> not log in to that lun using the ovirt web console. Whereas when >>>>>>> I try to login to that lun using the isciadm in command line I >>>>>>> am able to login. Any help?? >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Users mailing list >>>>>>> Users(a)ovirt.org >>>>>>> http://lists.ovirt.org/mailman/listinfo/users >>>>>> >>>>>> >>>>> I have created a new Lun for this purpose only and it is not being >>>>> used anywhere. >>>>> In order to try an iscsi pool I will have to reconfigure the >>>>> engine, because during the engine setup I opted for nfs. >>>>> >>>>> This is the output when I run this command. >>>>> >>>>> [root@ovirt ~]# vdsClient -s 0 getDeviceList >>>>> [] >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> this is log snippet from engine.log when I discover and try to >>>>> login to that lun. >>>>> >>>>> >>>>> ################################################################################################# >>>>> >>>>> 013-09-27 14:34:55,592 INFO >>>>> [org.ovirt.engine.core.vdsbroker.vdsbroker.DiscoverSendTargetsVDSCommand] >>>>> (ajp--127.0.0.1-8702-11) START, >>>>> DiscoverSendTargetsVDSCommand(HostName = 192.168.100.59, HostId = >>>>> 168842b9-071b-4c64-a22d-07ae1e63830b, connection={ id: null, >>>>> connection: 192.168.100.160, iqn: null, vfsType: null, >>>>> mountOptions: null, nfsVersion: null, nfsRetrans: null, nfsTimeo: >>>>> null };), log id: 2e12b97 >>>>> 2013-09-27 14:34:55,653 INFO >>>>> [org.ovirt.engine.core.vdsbroker.vdsbroker.DiscoverSendTargetsVDSCommand] >>>>> (ajp--127.0.0.1-8702-11) FINISH, DiscoverSendTargetsVDSCommand, >>>>> return: [{ id: null, connection: 192.168.100.160, iqn: >>>>> iqn.2013.26.ovirt.techblue.lv001, vfsType: null, mountOptions: >>>>> null, nfsVersion: null, nfsRetrans: null, nfsTimeo: null };], log >>>>> id: 2e12b97 >>>>> 2013-09-27 14:36:25,877 INFO >>>>> [org.ovirt.engine.core.bll.storage.ConnectStorageToVdsCommand] >>>>> (ajp--127.0.0.1-8702-2) Running command: >>>>> ConnectStorageToVdsCommand internal: false. Entities affected : >>>>> ID: aaa00000-0000-0000-0000-123456789aaa Type: System >>>>> 2013-09-27 14:36:25,880 INFO >>>>> [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand] >>>>> (ajp--127.0.0.1-8702-2) START, >>>>> ConnectStorageServerVDSCommand(HostName = 192.168.100.59, HostId = >>>>> 168842b9-071b-4c64-a22d-07ae1e63830b, storagePoolId = >>>>> 00000000-0000-0000-0000-000000000000, storageType = ISCSI, >>>>> connectionList = [{ id: null, connection: 192.168.100.160, iqn: >>>>> iqn.2013.26.ovirt.techblue.lv001, vfsType: null, mountOptions: >>>>> null, nfsVersion: null, nfsRetrans: null, nfsTimeo: null };]), log >>>>> id: 5fca13a4 >>>>> 2013-09-27 14:36:26,012 INFO >>>>> [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand] >>>>> (ajp--127.0.0.1-8702-2) FINISH, ConnectStorageServerVDSCommand, >>>>> return: {00000000-0000-0000-0000-000000000000=0}, log id: 5fca13a4 >>>>> 2013-09-27 14:36:26,098 INFO >>>>> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetDeviceListVDSCommand] (ajp--127.0.0.1-8702-12) >>>>> START, GetDeviceListVDSCommand(HostName = 192.168.100.59, HostId = >>>>> 168842b9-071b-4c64-a22d-07ae1e63830b, storageType=ISCSI), log id: >>>>> 20fb893b >>>>> 2013-09-27 14:36:29,376 INFO >>>>> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetDeviceListVDSCommand] (ajp--127.0.0.1-8702-12) >>>>> FINISH, GetDeviceListVDSCommand, return: [], log id: 20fb893b >>>>> >>>>> ###################################################################################################### >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>> Here I am sending you the two screenshots, one is when I am adding >>> the disk from the Local-storage that is NFS, and another is the >>> Direct lun. >>> You can see that I am able to discover it but could not log into it. >>> >> >> > ok so there is no means we can use an iscsi disk in a Data center > whoose default storage is NFS? -- Dafna Ron

3 2

[Users] 500 Internal Server Error when provisioning via Foreman (using nightly build)
by Andrew Timmes 29 Sep '13

29 Sep '13

All, I'm using oVirt 3.4.0-0.2.master.20130925104201.git8ab6304.el6 on CentOS 6.4 as a compute resource for Foreman (1.2.2, also running on CentOS 6.4). When I attempt to provision a machine, I get a 500 server error. Logs are posted below: https://gist.github.com/andrew-timmes/d41f465d2c25af5905c8 It looks similar to the issue that Andrew Lau reported in August ( http://lists.ovirt.org/pipermail/users/2013-August/015693.html) but I'm still seeing the issue in the nightly build. Any ideas? Thanks, Andrew Timmes

3 2

[Users] oVirt 3.3 and Neutron
by Riccardo Brunetti 29 Sep '13

29 Sep '13

Dear oVirt users. I'm trying to setup oVirt 3.3 using an OpenStack Neutron existing service as network provider. It works pretty well: I can use the networks defined in Neutron, import them and when I launch VM instances from oVirt they get an internal-IP address from Neutron. A can also associate a floating IP to the Neutron port and get inbound connectivity for the virtual machine. The problem is that if I shutdown the VM (both from inside the VM itself and from the oVirt WEB GUI) the association port/internal-IP/floating-IP is lost and when the VM is booted again It will get a different internal-IP on a different port and I have to manually re-associate the floating-IP. Is there a way to keep the IP addresses when the VM is simply shutted down and not deleted? This is the behavior when using OpenStack: if I poweroff the VM, the IPs are kept for the future. Moreover: can you confirm that in oVirt 3.3 there is still no support for the Neutron security rules? Thank you very much Best Regards Riccardo

4 3

[Users] Bottleneck writing to a VM w/ mounted GlusterFS
by Stefano Stagnaro 28 Sep '13

28 Sep '13

Hello, I'm testing oVirt 3.3 with GlusterFS libgfapi back-end. I'm using a node for engine and one for VDSM. From the VMs I'm mounting a second GlusterFS volume on a third storage server. I'm experiencing very bad transfer rates (38MB/s) writing from a client to a VM on the mounted GlusterFS. On the other hand, from the VM itself I can move a big file from the root vda (libgfapi) to the mounted GlusterFS at 70MB/s. I can't really figure out where the bottleneck could be. I'm using only the default ovirtmgmt network. Thank you for your help, any hint will be appreciated. Regards, -- Stefano Stagnaro IT Manager Prisma Engineering S.r.l. Via Petrocchi, 4 20127 Milano – Italy Tel. 02 26113507 int 339 e-mail: stefanos(a)prisma-eng.com skype: stefano.stagnaro

2 1

[Users] Gluster NFS Replicate bricks different size
by Andrew Lau 28 Sep '13

28 Sep '13

I've mounted a gluster 1x2 replica through NFS in oVirt. The NFS share holds the qcow images of the VMs. I recently nuked a whole replica brick in an 1x2 array (for numerous other reasons including split-brain), the brick self healed and restored back to the same state as its partner. 4 days later, they've become inbalanced. The direct `du` of the /brick are showing different sizes by around 20GB. I can see at brick level how some images are not the same size. I don't think this is normal, but I can't see anything to point what could be the issue. gluster volume heal STORAGE info gluster volume heal STORAGE info split-brain Shows no issues. Any suggestions? Cheers, Andrew.

1 0

Re: [Users] could not add iscsi disk in ovirt.
by Dafna Ron 27 Sep '13

27 Sep '13

the output is empty in both your outpit and the logs. This is the part in the log that shows that you do not have any devices: return: [] when you create a new disk and select the NFS DC- can you please send me the screen shot of that? On 09/27/2013 02:41 PM, Saurabh wrote: > On 27/09/13 18:40, Dafna Ron wrote: >> I am not sure direct lun will be supported for an NFS pool... can you >> try the same from iscsi pool? >> >> is this lun being used somewhere else or did you create a new one? >> you can run vdsClient -s 0 getDeviceList to see the list of the >> available luns and if the status is free or not. >> (it should also in the logs (engine and vdsm) when you discover the >> luns from the webadmin. >> >> >> On 09/27/2013 01:43 PM, Saurabh wrote: >>> >>> Hi guys, I am running ovirt with NFS as storage pool. Everything is >>> working quite fine for me. The only problem is I could not add the a >>> new iscsi disk in Disk tab. When I go to the Disk tab there is an >>> option of adding new disk from internal storage and another option >>> is add External (Direct Lun). When I opt for the External (Direct >>> LUN), I am able to discover the Lun but could not log in to that lun >>> using the ovirt web console. Whereas when I try to login to that lun >>> using the isciadm in command line I am able to login. Any help?? >>> >>> _______________________________________________ >>> Users mailing list >>> Users(a)ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/users >> >> > I have created a new Lun for this purpose only and it is not being > used anywhere. > In order to try an iscsi pool I will have to reconfigure the engine, > because during the engine setup I opted for nfs. > > This is the output when I run this command. > > [root@ovirt ~]# vdsClient -s 0 getDeviceList > [] > > > > > > this is log snippet from engine.log when I discover and try to login > to that lun. > > > ################################################################################################# > > 013-09-27 14:34:55,592 INFO > [org.ovirt.engine.core.vdsbroker.vdsbroker.DiscoverSendTargetsVDSCommand] > (ajp--127.0.0.1-8702-11) START, DiscoverSendTargetsVDSCommand(HostName > = 192.168.100.59, HostId = 168842b9-071b-4c64-a22d-07ae1e63830b, > connection={ id: null, connection: 192.168.100.160, iqn: null, > vfsType: null, mountOptions: null, nfsVersion: null, nfsRetrans: null, > nfsTimeo: null };), log id: 2e12b97 > 2013-09-27 14:34:55,653 INFO > [org.ovirt.engine.core.vdsbroker.vdsbroker.DiscoverSendTargetsVDSCommand] > (ajp--127.0.0.1-8702-11) FINISH, DiscoverSendTargetsVDSCommand, > return: [{ id: null, connection: 192.168.100.160, iqn: > iqn.2013.26.ovirt.techblue.lv001, vfsType: null, mountOptions: null, > nfsVersion: null, nfsRetrans: null, nfsTimeo: null };], log id: 2e12b97 > 2013-09-27 14:36:25,877 INFO > [org.ovirt.engine.core.bll.storage.ConnectStorageToVdsCommand] > (ajp--127.0.0.1-8702-2) Running command: ConnectStorageToVdsCommand > internal: false. Entities affected : ID: > aaa00000-0000-0000-0000-123456789aaa Type: System > 2013-09-27 14:36:25,880 INFO > [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand] > (ajp--127.0.0.1-8702-2) START, ConnectStorageServerVDSCommand(HostName > = 192.168.100.59, HostId = 168842b9-071b-4c64-a22d-07ae1e63830b, > storagePoolId = 00000000-0000-0000-0000-000000000000, storageType = > ISCSI, connectionList = [{ id: null, connection: 192.168.100.160, iqn: > iqn.2013.26.ovirt.techblue.lv001, vfsType: null, mountOptions: null, > nfsVersion: null, nfsRetrans: null, nfsTimeo: null };]), log id: 5fca13a4 > 2013-09-27 14:36:26,012 INFO > [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand] > (ajp--127.0.0.1-8702-2) FINISH, ConnectStorageServerVDSCommand, > return: {00000000-0000-0000-0000-000000000000=0}, log id: 5fca13a4 > 2013-09-27 14:36:26,098 INFO > [org.ovirt.engine.core.vdsbroker.vdsbroker.GetDeviceListVDSCommand] > (ajp--127.0.0.1-8702-12) START, GetDeviceListVDSCommand(HostName = > 192.168.100.59, HostId = 168842b9-071b-4c64-a22d-07ae1e63830b, > storageType=ISCSI), log id: 20fb893b > 2013-09-27 14:36:29,376 INFO > [org.ovirt.engine.core.vdsbroker.vdsbroker.GetDeviceListVDSCommand] > (ajp--127.0.0.1-8702-12) FINISH, GetDeviceListVDSCommand, return: [], > log id: 20fb893b > > ###################################################################################################### > > > > -- Dafna Ron

2 2

[Users] could not add iscsi disk in ovirt.
by Saurabh 27 Sep '13

27 Sep '13

Hi guys, I am running ovirt with NFS as storage pool. Everything is working quite fine for me. The only problem is I could not add the a new iscsi disk in Disk tab. When I go to the Disk tab there is an option of adding new disk from internal storage and another option is add External (Direct Lun). When I opt for the External (Direct LUN), I am able to discover the Lun but could not log in to that lun using the ovirt web console. Whereas when I try to login to that lun using the isciadm in command line I am able to login. Any help??

2 2

[Users] vdsm live migration errors in latest master
by Dead Horse 27 Sep '13

27 Sep '13

Seeing failed live migrations and these errors in the vdsm logs with latest VDSM/Engine master. Hosts are EL6.4 Thread-1306::ERROR::2013-09-23 16:02:42,422::BindingXMLRPC::993::vds::(wrapper) unexpected error Traceback (most recent call last): File "/usr/share/vdsm/BindingXMLRPC.py", line 979, in wrapper res = f(*args, **kwargs) File "/usr/share/vdsm/BindingXMLRPC.py", line 211, in vmDestroy return vm.destroy() File "/usr/share/vdsm/API.py", line 323, in destroy res = v.destroy() File "/usr/share/vdsm/vm.py", line 4326, in destroy response = self.releaseVm() File "/usr/share/vdsm/vm.py", line 4292, in releaseVm self._cleanup() File "/usr/share/vdsm/vm.py", line 2750, in _cleanup self._cleanupDrives() File "/usr/share/vdsm/vm.py", line 2482, in _cleanupDrives drive, exc_info=True) File "/usr/lib64/python2.6/logging/__init__.py", line 1329, in error self.logger.error(msg, *args, **kwargs) File "/usr/lib64/python2.6/logging/__init__.py", line 1082, in error self._log(ERROR, msg, args, **kwargs) File "/usr/lib64/python2.6/logging/__init__.py", line 1082, in error self._log(ERROR, msg, args, **kwargs) File "/usr/lib64/python2.6/logging/__init__.py", line 1173, in _log self.handle(record) File "/usr/lib64/python2.6/logging/__init__.py", line 1183, in handle self.callHandlers(record) File "/usr/lib64/python2.6/logging/__init__.py", line 1220, in callHandlers hdlr.handle(record) File "/usr/lib64/python2.6/logging/__init__.py", line 679, in handle self.emit(record) File "/usr/lib64/python2.6/logging/handlers.py", line 780, in emit msg = self.format(record) File "/usr/lib64/python2.6/logging/__init__.py", line 654, in format return fmt.format(record) File "/usr/lib64/python2.6/logging/__init__.py", line 436, in format record.message = record.getMessage() File "/usr/lib64/python2.6/logging/__init__.py", line 306, in getMessage msg = msg % self.args File "/usr/share/vdsm/vm.py", line 107, in __str__ if not a.startswith('__')] File "/usr/share/vdsm/vm.py", line 1344, in hasVolumeLeases if self.shared != DRIVE_SHARED_TYPE.EXCLUSIVE: AttributeError: 'Drive' object has no attribute 'shared' - DHC

3 7

[Users] importing VM from ESXI
by emitor＠gmail.com 26 Sep '13

26 Sep '13

Hi, I'm not being able to import a VM from ESXI: [root@ovirt-mgmt ~]# LIBGUESTFS_TRACE=1 LIBGUESTFS_DEBUG=1 virt-v2v -ic esx://10.11.12.123/?no_verify=1 -o rhev -os 10.11.12.222:/var/lib/exports/export --network ovirtmgt MultiDektec MultiDektec_MultiDektec: 100% [======================================================================================================================================================]D 0h36m54s libguestfs: trace: set_verbose true libguestfs: trace: set_verbose = 0 libguestfs: trace: set_backend "appliance" libguestfs: trace: set_backend = 0 libguestfs: create: flags = 0, handle = 0x4431d30, program = perl libguestfs: trace: set_attach_method "appliance" libguestfs: trace: set_backend "appliance" libguestfs: trace: set_backend = 0 libguestfs: trace: set_attach_method = 0 libguestfs: trace: add_drive "/tmp/KxIoJI50Pc/2872ac3e-7340-4dfa-9801-0a1bd052b3a3/v2v._ApSlRZG/387a5113-bbc2-45a2-9c55-5dc3dade31a9/01c899de-131e-4407-a16c-8c5484ccb8bd" "format:raw" "iface:ide" "name:sda" libguestfs: trace: add_drive = 0 libguestfs: trace: add_drive "/tmp/to3mfS2mtB" "readonly:true" "format:raw" "iface:ide" libguestfs: trace: add_drive = 0 libguestfs: trace: set_network true libguestfs: trace: set_network = 0 libguestfs: trace: launch libguestfs: trace: get_tmpdir libguestfs: trace: get_tmpdir = "/tmp" libguestfs: trace: get_backend libguestfs: trace: get_backend = "direct" libguestfs: launch: backend=direct libguestfs: launch: tmpdir=/tmp/libguestfsbaJ32y libguestfs: launch: umask=0022 libguestfs: launch: euid=36 libguestfs: command: run: supermin-helper libguestfs: command: run: \ --verbose libguestfs: command: run: \ -u 36 libguestfs: command: run: \ -g 36 libguestfs: command: run: \ -f checksum libguestfs: command: run: \ /usr/lib64/guestfs/supermin.d libguestfs: command: run: \ x86_64 supermin helper [00008ms] whitelist = (not specified), host_cpu = x86_64, kernel = (null), initrd = (null), appliance = (null) supermin helper [00009ms] inputs[0] = /usr/lib64/guestfs/supermin.d checking modpath /lib/modules/3.10.10-200.fc19.x86_64 is a directory checking modpath /lib/modules/3.11.1-200.fc19.x86_64 is a directory checking modpath /lib/modules/3.10.11-200.fc19.x86_64 is a directory picked vmlinuz-3.11.1-200.fc19.x86_64 supermin helper [00010ms] finished creating kernel supermin helper [00010ms] visiting /usr/lib64/guestfs/supermin.d supermin helper [00010ms] visiting /usr/lib64/guestfs/supermin.d/base.img supermin helper [00055ms] visiting /usr/lib64/guestfs/supermin.d/daemon.img supermin helper [00057ms] visiting /usr/lib64/guestfs/supermin.d/hostfiles supermin helper [00419ms] visiting /usr/lib64/guestfs/supermin.d/init.img supermin helper [00440ms] visiting /usr/lib64/guestfs/supermin.d/udev-rules.img supermin helper [00468ms] adding kernel modules supermin helper [00528ms] finished creating appliance libguestfs: checksum of existing appliance: 096bf8833aed53a33f7c0da2a5e685ad430bba5b50ae20a7e0325bca32cca6d2 libguestfs: trace: get_cachedir libguestfs: trace: get_cachedir = "/var/tmp" libguestfs: [00718ms] begin testing qemu features libguestfs: command: run: /usr/bin/qemu-kvm libguestfs: command: run: \ -nographic libguestfs: command: run: \ -help libguestfs: command: run: /usr/bin/qemu-kvm libguestfs: command: run: \ -nographic libguestfs: command: run: \ -version libguestfs: qemu version 1.4 libguestfs: command: run: /usr/bin/qemu-kvm libguestfs: command: run: \ -nographic libguestfs: command: run: \ -machine accel=kvm:tcg libguestfs: command: run: \ -device ? libguestfs: [01607ms] finished testing qemu features [01608ms] /usr/bin/qemu-kvm \ -global virtio-blk-pci.scsi=off \ -nodefconfig \ -nodefaults \ -nographic \ -machine accel=kvm:tcg \ -m 500 \ -no-reboot \ -no-hpet \ -kernel /var/tmp/.guestfs-36/kernel.52160 \ -initrd /var/tmp/.guestfs-36/initrd.52160 \ -device virtio-scsi-pci,id=scsi \ -drive file=/tmp/KxIoJI50Pc/2872ac3e-7340-4dfa-9801-0a1bd052b3a3/v2v._ApSlRZG/387a5113-bbc2-45a2-9c55-5dc3dade31a9/01c899de-131e-4407-a16c-8c5484ccb8bd,cache=none,format=raw,id=hd0,if=ide \ -drive file=/tmp/to3mfS2mtB,snapshot=on,format=raw,id=hd1,if=ide \ -drive file=/var/tmp/.guestfs-36/root.52160,snapshot=on,id=appliance,if=none,cache=unsafe \ -device scsi-hd,drive=appliance \ -device virtio-serial \ -serial stdio \ -device sga \ -chardev socket,path=/tmp/libguestfsbaJ32y/guestfsd.sock,id=channel0 \ -device virtserialport,chardev=channel0,name=org.libguestfs.channel.0 \ -netdev user,id=usernet,net=169.254.0.0/16 \ -device virtio-net-pci,netdev=usernet \ -append 'panic=1 console=ttyS0 udevtimeout=600 no_timer_check acpi=off printk.time=1 cgroup_disable=memory root=/dev/sdc selinux=0 guestfs_verbose=1 TERM=screen' qemu-system-x86_64: -drive file=/tmp/KxIoJI50Pc/2872ac3e-7340-4dfa-9801-0a1bd052b3a3/v2v._ApSlRZG/387a5113-bbc2-45a2-9c55-5dc3dade31a9/01c899de-131e-4407-a16c-8c5484ccb8bd,cache=none,format=raw,id=hd0,if=ide: could not open disk image /tmp/KxIoJI50Pc/2872ac3e-7340-4dfa-9801-0a1bd052b3a3/v2v._ApSlRZG/387a5113-bbc2-45a2-9c55-5dc3dade31a9/01c899de-131e-4407-a16c-8c5484ccb8bd: Permission denied libguestfs: child_cleanup: 0x4431d30: child process died libguestfs: sending SIGTERM to process 52793 libguestfs: trace: launch = -1 (error) virt-v2v: Failed to launch guestfs appliance. Try running again with LIBGUESTFS_DEBUG=1 for more information libguestfs: trace: close libguestfs: closing guestfs handle 0x4431d30 (state 0) libguestfs: command: run: rm libguestfs: command: run: \ -rf /tmp/libguestfsbaJ32y I've followed this link to do it: http://www.hacktheory.org/index.php/projects/projects-by-eureka/migrate-esx… And these to try to fix the error: https://bugzilla.redhat.com/show_bug.cgi?id=921292 http://superuser.com/questions/298426/kvm-image-failed-to-start-with-virsh-… But it's still happening the same I'm running: qemu-kvm-1.4.2-9.fc19.x86_64 libvirt-1.1.2-1.fc19 vdsm-4.12.1-2.fc19 libguestfs-tools-c-1.22.6-1.fc19.x86_64 libguestfs-1.22.6-1.fc19.x86_64 virt-v2v-0.9.0-3.fc19.x86_64 Could you give me a hint on this? Thanks! -- *Emiliano Tortorella* +598 98941176 emitor(a)gmail.com

2 3

Re: [Users] Disk state - Illegal?
by SULLIVAN, Chris (WGK) 26 Sep '13

26 Sep '13

Thanks for posting that Andrew. I had the same problem removing disks from a Gluster volume (disk state changed to Illegal and the actual disk file was not removed from the volume) and your method worked fine for me. Cheers, Chris Message: 3 Date: Thu, 26 Sep 2013 12:53:04 +1000 From: Andrew Lau <andrew(a)andrewklau.com> To: Dan Ferris <dferris(a)prometheusresearch.com> Cc: "Users(a)ovirt.org" <Users(a)ovirt.org> Subject: Re: [Users] Disk state - Illegal? Message-ID: <CAD7dF9droPuPGxqjM-9aTyE7_qLLhDnYxLLVVB_FtWQdkH0srw(a)mail.gmail.com> Content-Type: text/plain; charset="iso-8859-1" I noticed that too, I wasn't sure if it was a bug or just how I had setup my NFS share.. There were three steps I did to remove the disk images, I'm sure there's a 100% easier solution..: I found the easiest way (graphically) was go to your https://ovirtengine/api/disks and so a search for the illegal disk. Append the extra ID eg. <disk href="/api/disks/lk342-dfsdf... into your URL this'll give you your image ID. Go to your storage share: cd /data/storage-id/master/vms/storage-id grep -ir 'vmname' * You'll find the image-id reference here too. Then the image you will want to remove is in the /data/storage-id/images/image-id I assume you could safely remove this whole folder if you wanted to delete the disk. To remove the illegal state I did it through the API so again with the URL above https://ovirtengine/disks/disk-id send a DELETE using HTTP/CURL Again, this was a poor mans solution but it worked for me. On Thu, Sep 26, 2013 at 4:04 AM, Dan Ferris <dferris(a)prometheusresearch.com>wrote: > Hi, > > I have another hopefully simple question. > > One VM that I am trying to remove says that it's disk state is "illegal" > and when I try to remove the disk it says that it failed to initiate > the removing of the disk. > > Is there an easy way to get rid of these illegal disk images? > > Dan > PLEASE CONSIDER THE ENVIRONMENT, DON'T PRINT THIS EMAIL UNLESS YOU REALLY NEED TO. This email and its attachments may contain information which is confidential and/or legally privileged. If you are not the intended recipient of this e-mail please notify the sender immediately by e-mail and delete this e-mail and its attachments from your computer and IT systems. You must not copy, re-transmit, use or disclose (other than to the sender) the existence or contents of this email or its attachments or permit anyone else to do so. ----------------------------- ______________________________**_________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/**mailman/listinfo/users<http://lists.ovirt.org > /mailman/listinfo/users> > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.ovirt.org/pipermail/users/attachments/20130926/7b7ac24b/attach…> ------------------------------ Message: 4 Date: Thu, 26 Sep 2013 08:35:07 +0100 From: "Richard W.M. Jones" <rjones(a)redhat.com> To: "emitor(a)gmail.com" <emitor(a)gmail.com> Cc: users(a)ovirt.org Subject: Re: [Users] importing VM from ESXI Message-ID: <20130926073507.GE1887(a)redhat.com> Content-Type: text/plain; charset=us-ascii On Wed, Sep 25, 2013 at 06:10:00PM -0300, emitor(a)gmail.com wrote: > could not open disk image > /tmp/KxIoJI50Pc/2872ac3e-7340-4dfa-9801-0a1bd052b3a3/v2v._ApSlRZG/387a5113-bbc2-45a2-9c55-5dc3dade31a9/01c899de-131e-4407-a16c-8c5484ccb8bd: > Permission denied The error comes from qemu and indicates qemu cannot open this temporary disk image. I've no idea why it cannot open it, but possibilities include: SELinux, file permissions (eg on /tmp), setting of TMPDIR, relative path to a backing file, and more ... I'd suggest that you 'strace -f' the whole set of processes to see what precise system call fails. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming blog: http://rwmj.wordpress.com Fedora now supports 80 OCaml packages (the OPEN alternative to F#) ------------------------------ _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users End of Users Digest, Vol 24, Issue 140 **************************************

1 0