FileSR does indeed require files to be named as <uuid>.vhd or <uuid>.raw, otherwise the sr-scan will indeed fail. I'd therefore delete all of the .json files and rename them to be called <uuid>.vhd.
I don't know whether an older version of FFS will work with the new XAPI, but I don't think there are plans to re-introduce VHD support in FFS due to differences in the new SMAPIv3 which it now uses (long story short, if VHD support was re-introduced it would not perform as well as we'd hope). Bob ________________________________ From: Dawid Kowalski [dkad...@gmail.com] Sent: 11 February 2015 11:26 To: Bob Ball; Xen API mailing list Subject: Re: [Xen-API] ffs missing Hi Bob, Thanks for reply. I've tried to use FileSR prior sending original question but /*for some reason it does not discover VMs sitting in the folder. Worth noting is that VMs under ffs were created as: <VMNAME> <VMNAME>.json Creating VM using "file" SR results in "<VM>.vhd" file. Symlinking or renaming original file created using FFS to VMNAME.VHD results in following message when running SR-SCAN: Error code: SR_BACKEND_FAILURE_40 Error parameters: , The SR scan failed [opterr=['UUID_INVALID', 'VDI', 'XenBuilder']], */ Which version of FFS supports VHDs in the old way? I've been setting up system in question around Xmass time and before Jan 10th. How can I pull and build proper FFS version for me with VHD support? I'll downgrade version, restore VMs, pull out data and then can create new ones using qcow2 format. Thanks, Dawid On 11/02/15 11:42, Bob Ball wrote: Hi David, The list of SR options are a pre-defined list for Bash tab completion. Have you tried creating an SR with type FFS and using it? Note, in recent builds, FFS only supports qcow2 disks. xe sr-create type=ffs name-label=qcow2 device-config:uri=file:///root/qcow2 host-uuid=<uuid> If you want to use VHDs then use FileSR in a very similar way, but setting device-config:path and device-config:location both to the same directory. Bob ________________________________ From: xen-api-boun...@lists.xen.org<mailto:xen-api-boun...@lists.xen.org> [xen-api-boun...@lists.xen.org<mailto:xen-api-boun...@lists.xen.org>] on behalf of Dawid Kowalski [dkad...@gmail.com<mailto:dkad...@gmail.com>] Sent: 11 February 2015 10:28 To: Xen API mailing list Subject: Re: [Xen-API] ffs missing Hi Guys, Further tests did show that FFS is missing not only on Ubuntu based system but also on Centos based system. Package itself is installed however FFS type doesn't show on the SR types list. Any help will be more than appreciated as I've couple of VMs in down state as ffs based SR can't be used at the moment. Thanks, Dawid On 06/02/15 02:40, Dawid Kowalski wrote: Hi Guys, I'm looking for your help again. I've successfully created Xenhost, created FFS based SRs and everything worked ok. I've had some issues but had some basics running and was happy. (Ubuntu 14.04.1 LTS). Than due to other circumstances had to restart server. During restart it did hang up. After powercycle I can't get FFS working. Everything else works fine. Seems like FFS is not registering to XAPI. /etc/init.d/ffs doesn't start ffs as there's no /usr/sbin/ffs. I've checked deb package and ffs is not included there. Going through my troubleshooting steps, I did setup to other systems from scratch, one of them based on xenserver git and other based on BobBall repository with Xen. Both of them behave the same way - FFS is not registered. Symlinks under /opt/xensource didn't help: ls -l /opt/xensource/ sm -> /usr/lib/xapi/sm Having said all of it, I do remember that when setting up server I've had some problems with FFS which finally did sort out by adding some links or something similar. Unfortunately my all notes were on SSD drive which failed miserably the day after I did setup Xen and copy is within one of Xen VMs to make it even more funny. Therefore, any help from your side would be more appreciated. btw. I've tried to add "file" type SR but for some reason it does not discover VMs sitting in the folder. Worth noting is that VMs under ffs were created as: <VMNAME> <VMNAME>.json Creating VM using "file" SR results in "<VM>.vhd" file. Symlinking or renaming original file created using FFS to VMNAME.VHD results in following message when running SR-SCAN: Error code: SR_BACKEND_FAILURE_40 Error parameters: , The SR scan failed [opterr=['UUID_INVALID', 'VDI', 'XenBuilder']], # command to create ffs - doesn't work xe sr-create content-type=user host-uuid=0d83e699-df0b-40db-9934-b5cbc9e5eafe type=ffs device-config:path=/mnt/images name-label=test username=root password=(omitted) # syslog Feb 6 02:11:13 silver xapi: [ info|silver|6062 UNIX /var/lib/xcp/xapi||cli] xe sr-create content-type=user host-uuid=0d83e699-df0b-40db-9934-b5cbc9e5eafe type=ffs device-config:path=/mnt/images name-label=test username=root password=(omitted) Feb 6 02:11:13 silver xapi: [ info|silver|6062 UNIX /var/lib/xcp/xapi|session.login_with_password D:d1bafb363b96|xapi] Session.create trackid=fe419c0ab3f1a7f668a0cf4979113666 pool=false uname=root originator=cli is_local_superuser=true auth_user_sid= parent=trackid=9834f5af41c964e225f24279aefe4e49 Feb 6 02:11:13 silver xapi: [debug|silver|6062 UNIX /var/lib/xcp/xapi|session.login_with_password D:d1bafb363b96|mscgen] xapi=>xapi [label="session.get_uuid"]; Feb 6 02:11:13 silver xapi: [debug|silver|6063 UNIX /var/lib/xcp/xapi||dummytaskhelper] task dispatch:session.get_uuid D:5afb28575cda created by task D:d1bafb363b96 Feb 6 02:11:13 silver xapi: [debug|silver|6062 UNIX /var/lib/xcp/xapi|SR.create R:515cc6d49889|audit] SR.create: name label = 'test' Feb 6 02:11:13 silver xapi: [debug|silver|6062 UNIX /var/lib/xcp/xapi|SR.create R:515cc6d49889|xapi] SR.create name_label=test sm_config=[ ] Feb 6 02:11:13 silver xapi: [debug|silver|6062 UNIX /var/lib/xcp/xapi|SR.create R:515cc6d49889|mux] register SR 43e2eb28-2803-06bf-c9fc-aff45ed7e4d1 (currently-registered = [ 5b245868-00c6-dcd1-3cc9-c590f8f2c502, 7d2ad721-9bbc-be93-6ed0-1040eb1361e9, c0384c67-d7bf-a12e-430b-d6bb1569ec8c, 995f3d5d-e698-4f41-88a0-e0bb2edeeef1, f29722df-7c21-47cc-858a-c06c700cec91, 43e2eb28-2803-06bf-c9fc-aff45ed7e4d1, 06260f45-4ab0-44f8-b9b9-c184886c5619, 4b73fdd7-06a6-c5ea-2205-dd1e5a5b3a0d ]) Feb 6 02:11:13 silver xapi: [debug|silver|6062 UNIX /var/lib/xcp/xapi|SR.create R:515cc6d49889|xapi] Called from file \"lib/pervasiveext.ml<http://pervasiveext.ml>\", line 22, characters 2-9\n Feb 6 02:11:13 silver xapi: [error|silver|6062 UNIX /var/lib/xcp/xapi|SR.create R:515cc6d49889|storage_access] Re-raising as MISSING_URI [ Please include a URI in the device-config ] Feb 6 02:11:13 silver xapi: [debug|silver|6062 UNIX /var/lib/xcp/xapi|SR.create R:515cc6d49889|backtrace] Raised at file \"xapi_sr.ml<http://xapi_sr.ml>\", line 223, characters 9-10\nCalled from file \"message_forwarding.ml<http://message_forwarding.ml>\", line 233, characters 25-44\nCalled from file \"server.ml<http://server.ml>\", line 21875, characters 82-267\nCalled from file \"rbac.ml<http://rbac.ml>\", line 227, characters 16-23\n Feb 6 02:11:13 silver xapi: [20150206T01:11:13.071Z|audit|silver|6062 UNIX /var/lib/xcp/xapi|SR.create R:515cc6d49889|audit] ('trackid=fe419c0ab3f1a7f668a0cf4979113666' 'LOCAL_SUPERUSER' 'root' 'ALLOWED' 'ERROR:MISSING_URI: [ Please include a URI in the device-config ]' 'API' 'SR.create' (('host' 'silver' '0d83e699-df0b-40db-9934-b5cbc9e5eafe' 'OpaqueRef:0d0d7bf7-4d03-afc4-4280-8724014224ba') ('name_label' 'test' '' '') ('name_description' '' '' ''))) Feb 6 02:11:13 silver xapi: [debug|silver|6062 UNIX /var/lib/xcp/xapi|SR.create R:515cc6d49889|backtrace] Raised at file \"rbac.ml<http://rbac.ml>\", line 236, characters 10-15\nCalled from file \"server_helpers.ml<http://server_helpers.ml>\", line 75, characters 11-41\n Feb 6 02:11:13 silver xapi: [debug|silver|6062 UNIX /var/lib/xcp/xapi|SR.create R:515cc6d49889|dispatcher] Server_helpers.exec exception_handler: Got exception MISSING_URI: [ Please include a URI in the device-config ] Feb 6 02:11:13 silver xapi: [debug|silver|6062 UNIX /var/lib/xcp/xapi|SR.create R:515cc6d49889|dispatcher] Raised at file \"rbac.ml<http://rbac.ml>\", line 236, characters 10-15\nCalled from file \"server_helpers.ml<http://server_helpers.ml>\", line 75, characters 11-41\n Feb 6 02:11:13 silver xapi: [debug|silver|6062 UNIX /var/lib/xcp/xapi|SR.create R:515cc6d49889|backtrace] Raised at file \"rbac.ml<http://rbac.ml>\", line 236, characters 10-15\nCalled from file \"server_helpers.ml<http://server_helpers.ml>\", line 75, characters 11-41\n Feb 6 02:11:13 silver xapi: [debug|silver|6062 UNIX /var/lib/xcp/xapi|SR.create R:515cc6d49889|xapi] Raised at file \"server_helpers.ml<http://server_helpers.ml>\", line 90, characters 14-15\nCalled from file \"lib/pervasiveext.ml<http://pervasiveext.ml>\", line 22, characters 2-9\n Feb 6 02:11:13 silver xapi: [debug|silver|6062 UNIX /var/lib/xcp/xapi|dispatch:SR.create D:a74592cb8e0e|xapi] Raised at file \"lib/pervasiveext.ml<http://pervasiveext.ml>\", line 26, characters 22-25\nCalled from file \"lib/debug.ml<http://debug.ml>\", line 57, characters 17-20\nRe-raised at file \"lib/debug.ml<http://debug.ml>\", line 62, characters 10-11\nCalled from file \"lib/pervasiveext.ml<http://pervasiveext.ml>\", line 22, characters 2-9\n Feb 6 02:11:13 silver xapi: [debug|silver|6062 UNIX /var/lib/xcp/xapi|dispatch:SR.create D:a74592cb8e0e|backtrace] Raised at file \"lib/pervasiveext.ml<http://pervasiveext.ml>\", line 26, characters 22-25\nCalled from file \"lib/debug.ml<http://debug.ml>\", line 57, characters 17-20\nRe-raised at file \"lib/debug.ml<http://debug.ml>\", line 62, characters 10-11\nCalled from file \"lib/pervasiveext.ml<http://pervasiveext.ml>\", line 22, characters 2-9\nRe-raised at file \"lib/pervasiveext.ml<http://pervasiveext.ml>\", line 26, characters 22-25\nCalled from file \"server_helpers.ml<http://server_helpers.ml>\", line 136, characters 10-106\nCalled from file \"server.ml<http://server.ml>\", line 21876, characters 23-161\nCalled from file \"server_helpers.ml<http://server_helpers.ml>\", line 115, characters 4-7\n Feb 6 02:11:13 silver xapi: [debug|silver|6062 UNIX /var/lib/xcp/xapi||xapi] Raised at file \"client.ml<http://client.ml>\", line 6, characters 37-75\nCalled from file \"client.ml<http://client.ml>\", line 18, characters 55-110\nCalled from file \"client.ml<http://client.ml>\", line 9501, characters 6-154\nCalled from file \"cli_operations.ml<http://cli_operations.ml>\", line 1423, characters 8-161\nCalled from file \"xapi_cli.ml<http://xapi_cli.ml>\", line 119, characters 18-58\nCalled from file \"lib/pervasiveext.ml<http://pervasiveext.ml>\", line 22, characters 2-9\n Feb 6 02:11:13 silver xapi: [ info|silver|6062 UNIX /var/lib/xcp/xapi|session.logout D:786e245b403e|xapi] Session.destroy trackid=fe419c0ab3f1a7f668a0cf4979113666 Feb 6 02:11:13 silver xapi: [debug|silver|6062 UNIX /var/lib/xcp/xapi||backtrace] Raised at file \"lib/pervasiveext.ml<http://pervasiveext.ml>\", line 26, characters 22-25\nCalled from file \"xapi_cli.ml<http://xapi_cli.ml>\", line 118, characters 2-139\nCalled from file \"xapi_cli.ml<http://xapi_cli.ml>\", line 221, characters 7-44\nCalled from file \"xapi_cli.ml<http://xapi_cli.ml>\", line 273, characters 4-23\n Feb 6 02:11:13 silver xapi: [debug|silver|6062 UNIX /var/lib/xcp/xapi||cli] Xapi_cli.exception_handler: Got exception MISSING_URI: [ Please include a URI in the device-config ] Feb 6 02:11:13 silver xapi: [debug|silver|6062 UNIX /var/lib/xcp/xapi||cli] Raised at file \"lib/pervasiveext.ml<http://pervasiveext.ml>\", line 26, characters 22-25\nCalled from file \"xapi_cli.ml<http://xapi_cli.ml>\", line 118, characters 2-139\nCalled from file \"xapi_cli.ml<http://xapi_cli.ml>\", line 221, characters 7-44\nCalled from file \"xapi_cli.ml<http://xapi_cli.ml>\", line 273, characters 4-23\n Feb 6 02:11:13 silver xapi: [debug|silver|72|xapi events D:88c60758dbbb|xenops] Event on VM 4f1cbed7-eba5-4591-bc12-313612a9ecfe; resident_here = true Feb 6 02:11:13 silver xapi: [debug|silver|72|xapi events D:88c60758dbbb|mscgen] xapi=>xapi [label="event.from"]; Feb 6 02:11:13 silver xapi: [debug|silver|6064 UNIX /var/lib/xcp/xapi||dummytaskhelper] task dispatch:event.from D:1cd29e53d99d created by task D:88c60758dbbb Thanks in advance, Dawid
_______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
