GitHub user shin-kamui closed a discussion: VMs won't start on networks with 
client drive enabled

### problem

Creating an L2 network with client drive and user data enabled, and assigning 
it as the primary Nic network causes the VM to fail to boot.  

`Error
Unable to orchestrate the start of VM instance 
{"instanceName":"i-10-95-VM","uuid":"cf7fe0b5-3aaf-436a-a491-05ff04157b44"}.`

Management logs show the following error:

`[root@cs-mgmt-01 management]# tail -f management-server.log | grep xorriso
2025-05-09 08:18:58,813 DEBUG [o.a.c.s.c.ConfigDriveBuilder] 
(Work-Job-Executor-81:[ctx-e0bbdf57, job-752/job-753, ctx-fb886621]) 
(logid:aafce644) Executing config drive creation command: /usr/bin/xorriso -o 
/tmp/configdrive13732511610698651691/i-10-95-VM.iso -ldots -allow-lowercase 
-allow-multidot -cache-inodes -l -quiet -J -r -V config-2 
/tmp/configdrive13732511610698651691
2025-05-09 08:18:58,813 DEBUG [o.a.c.s.c.ConfigDriveBuilder] 
(Work-Job-Executor-81:[ctx-e0bbdf57, job-752/job-753, ctx-fb886621]) 
(logid:aafce644) Executing command [/usr/bin/xorriso -o 
/tmp/configdrive13732511610698651691/i-10-95-VM.iso -ldots -allow-lowercase 
-allow-multidot -cache-inodes -l -quiet -J -r -V config-2 
/tmp/configdrive13732511610698651691 ].
2025-05-09 08:18:58,819 WARN  [o.a.c.s.c.ConfigDriveBuilder] 
(Work-Job-Executor-81:[ctx-e0bbdf57, job-752/job-753, ctx-fb886621]) 
(logid:aafce644) Execution of process [2527556] for command [/usr/bin/xorriso 
-o /tmp/configdrive13732511610698651691/i-10-95-VM.iso -ldots -allow-lowercase 
-allow-multidot -cache-inodes -l -quiet -J -r -V config-2 
/tmp/configdrive13732511610698651691 ] failed.
2025-05-09 08:18:58,819 DEBUG [o.a.c.s.c.ConfigDriveBuilder] 
(Work-Job-Executor-81:[ctx-e0bbdf57, job-752/job-753, ctx-fb886621]) 
(logid:aafce644) Exit value of process [2527556] for command [/usr/bin/xorriso 
-o /tmp/configdrive13732511610698651691/i-10-95-VM.iso -ldots -allow-lowercase 
-allow-multidot -cache-inodes -l -quiet -J -r -V config-2 
/tmp/configdrive13732511610698651691 ] is [5].
2025-05-09 08:18:58,819 WARN  [o.a.c.s.c.ConfigDriveBuilder] 
(Work-Job-Executor-81:[ctx-e0bbdf57, job-752/job-753, ctx-fb886621]) 
(logid:aafce644) Process [2527556] for command [/usr/bin/xorriso -o 
/tmp/configdrive13732511610698651691/i-10-95-VM.iso -ldots -allow-lowercase 
-allow-multidot -cache-inodes -l -quiet -J -r -V config-2 
/tmp/configdrive13732511610698651691 ] encountered the error: [xorriso 1.5.4 : 
RockRidge filesystem manipulator, libburnia project.xorriso : FAILURE : Not a 
known command:  '-o'xorriso : FAILURE : Not a known command:  
'/tmp/configdrive13732511610698651691/i-10-95-VM.iso'xorriso : FAILURE : Not a 
known command:  '-ldots'xorriso : FAILURE : Not a known command:  
'-allow-lowercase'xorriso : FAILURE : Not a known command:  
'-allow-multidot'xorriso : FAILURE : Not a known command:  
'-cache-inodes'xorriso : FAILURE : Not a known command:  '-l'xorriso : FAILURE 
: Not a known command:  '-quiet'xorriso : FAILURE : Not a known command:  
'-J'xorriso : FAILURE : Not a 
 known command:  '-r'xorriso : FAILURE : Not a known command:  '-V'xorriso : 
FAILURE : Not a known command:  'config-2'xorriso : FAILURE : Not a known 
command:  '/tmp/configdrive13732511610698651691'xorriso : aborting : -abort_on 
'FAILURE' encountered 'FAILURE'].
2025-05-09 08:18:58,820 WARN  [o.a.c.s.c.ConfigDriveBuilder] 
(Work-Job-Executor-81:[ctx-e0bbdf57, job-752/job-753, ctx-fb886621]) 
(logid:aafce644) Unable to create iso file: i-10-95-VM.iso due to gexorriso 
1.5.4 : RockRidge filesystem manipulator, libburnia project.xorriso : FAILURE : 
Not a known command:  '-o'xorriso : FAILURE : Not a known command:  
'/tmp/configdrive13732511610698651691/i-10-95-VM.iso'xorriso : FAILURE : Not a 
known command:  '-ldots'xorriso : FAILURE : Not a known command:  
'-allow-lowercase'xorriso : FAILURE : Not a known command:  
'-allow-multidot'xorriso : FAILURE : Not a known command:  
'-cache-inodes'xorriso : FAILURE : Not a known command:  '-l'xorriso : FAILURE 
: Not a known command:  '-quiet'xorriso : FAILURE : Not a known command:  
'-J'xorriso : FAILURE : Not a known command:  '-r'xorriso : FAILURE : Not a 
known command:  '-V'xorriso : FAILURE : Not a known command:  'config-2'xorriso 
: FAILURE : Not a known command:  '/tmp/configdrive13732511610698651691
 'xorriso : aborting : -abort_on 'FAILURE' encountered 'FAILURE'
2025-05-09 08:18:59,224 ERROR [c.c.v.ClusteredVirtualMachineManagerImpl] 
(Work-Job-Executor-81:[ctx-e0bbdf57, job-752/job-753, ctx-fb886621]) 
(logid:aafce644) Unable to orchestrate start VM instance 
{"id":95,"instanceName":"i-10-95-VM","type":"User","uuid":"cf7fe0b5-3aaf-436a-a491-05ff04157b44"}
 due to [Unable to create iso file: i-10-95-VM.iso due to gexorriso 1.5.4 : 
RockRidge filesystem manipulator, libburnia project.xorriso : FAILURE : Not a 
known command:  '-o'xorriso : FAILURE : Not a known command:  
'/tmp/configdrive13732511610698651691/i-10-95-VM.iso'xorriso : FAILURE : Not a 
known command:  '-ldots'xorriso : FAILURE : Not a known command:  
'-allow-lowercase'xorriso : FAILURE : Not a known command:  
'-allow-multidot'xorriso : FAILURE : Not a known command:  
'-cache-inodes'xorriso : FAILURE : Not a known command:  '-l'xorriso : FAILURE 
: Not a known command:  '-quiet'xorriso : FAILURE : Not a known command:  
'-J'xorriso : FAILURE : Not a known command:  '-r'xorriso : FAILURE :
  Not a known command:  '-V'xorriso : FAILURE : Not a known command:  
'config-2'xorriso : FAILURE : Not a known command:  
'/tmp/configdrive13732511610698651691'xorriso : aborting : -abort_on 'FAILURE' 
encountered 'FAILURE'].`


When I try running the command from the CLI im getting errors about args as 
well.  Is there a specific version of xorriso that I need to get my hands on to 
fix this, or have I made a grave mistake in my lab deployment?  Im new to 
cloudstack, would appreciate any assistance I can get.  Can't find any real 
documentation on the underlying function of client drive, so assuming it's not 
really expected to be a user configurable component.

here's the output of running the command standalone:

`[root@CS-KVM-02 ~]# /usr/bin/xorriso -o 
/tmp/configdrive12482914262195410498/i-10-95-VM.iso -ldots -allow-lowercase 
-allow-multidot -cache-inodes -l -quiet -J -r -V config-2 
/tmp/configdrive12482914262195410498
xorriso 1.5.4 : RockRidge filesystem manipulator, libburnia project.

xorriso : FAILURE : Not a known command:  '-o'

xorriso : FAILURE : Not a known command:  
'/tmp/configdrive12482914262195410498/i-10-95-VM.iso'

xorriso : FAILURE : Not a known command:  '-ldots'

xorriso : FAILURE : Not a known command:  '-allow-lowercase'

xorriso : FAILURE : Not a known command:  '-allow-multidot'

xorriso : FAILURE : Not a known command:  '-cache-inodes'

xorriso : FAILURE : Not a known command:  '-l'

xorriso : FAILURE : Not a known command:  '-quiet'

xorriso : FAILURE : Not a known command:  '-J'

xorriso : FAILURE : Not a known command:  '-r'

xorriso : FAILURE : Not a known command:  '-V'

xorriso : FAILURE : Not a known command:  'config-2'

xorriso : FAILURE : Not a known command:  '/tmp/configdrive12482914262195410498'

xorriso : aborting : -abort_on 'FAILURE' encountered 'FAILURE'
`


### versions

The versions of ACS, hypervisors, storage, network etc..

ACS version 4.20, all hypervisors are KVM running on Oracle Linux 9.5 UEK, 
Primary storage is ceph RBD (same hosts), secondary is CEPHFS via NFS, network 
config on each node is a single 10gig carrying all 4 types of traffic vlan 
separated.  Management server is a separate oracle linux 9.5 based system that 
is also a member of the ceph cluster.  

### The steps to reproduce the bug

1. Create new L2 guest network using "offering for l2 networks with config 
drive user data VLAN"
2. Create new test VM using centos 5.5 included template
3. Attempt to start VM


### What to do about it?

Honestly not sure.  Please help me through this process.  My apologies for the 
burden.  

GitHub link: https://github.com/apache/cloudstack/discussions/10864

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]

Reply via email to