Attempting to Start a VM through the VM Manager GUI fails with "OVMAPI_5001E" - "Async command failed Server error: Command: ['xm', 'create' ] stderr: Error: Unable to open config file
(Doc ID 2086485.1)
Last updated on AUGUST 04, 2018
Oracle VM - Version 3.0.1 and later Linux x86-64
On Oracle VM, when attempting to start a virtual machine in the VM Manager Graphical User Interface (GUI), the job first starts, then lists "child running" and then fails with the following kind of error message :
OVMAPI_5001E Job: 1449552161671/QueuedVmStartDbImpl_1449552161670/Start/resume vm: OLinux67.0, on server: dell-ppr1, failed. Job Failure Event: 1449552162525/Server Async Command Failed/OVMEVT_00C014D_001 Async command failed on server: dell-ppr1. Object: OLinux67.0, PID: 12720, Server error: Command: ['xm', 'create', '/OVS/Repositories/0004fb000003000077007d6d557cc20f/VirtualMachines/0004fb000006000039c6ed93e780c330/vm.cfg'] failed (1): stderr: Error: Unable to open config file: /OVS/Repositories/0004fb000003000077007d6d557cc20f/VirtualMachines/0004fb000006000039c6ed93e780c330/vm.cfg stdout: Usage: xm create <ConfigFile> [options] [vars] Create a domain based on <ConfigFile>. Options: -h, --help Print this help. --help_config Print the available configuration variables (vars) for the configuration script. -q, --quiet Quiet. --path=PATH Search path for configuration scripts. The value of PATH is a colon-separated directory list. -f=FILE, --defconfig=FILE Use the given Python configuration script.The configuration script is loaded after arguments have been processed. Each command-line option sets a configuration variable named after its long option name, and these variables are placed in the environment of the script before it is loaded. Variables for options that may be repeated have list values. Other variables can be set using VAR=VAL on the command line. After the script is loaded, option values that were not set on the command line are replaced by the values set in the script. -F=FILE, --config=FILE Domain configuration to use (SXP). SXP is the underlying configuration format used by Xen. SXP configurations can be hand-written or generated from Python configuration scripts, using the -n (dryrun) option to print the configuration. -n, --dryrun Dry run - prints the resulting configuration in SXP but does not create the domain. -x, --xmldryrun XML dry run - prints the resulting configuration in XML but does not create the domain. -s, --skipdtd Skip DTD checking - skips checks on XML before creating. Experimental. Can decrease create time. -p, --paused Leave the domain paused after it is created. -c, --console_autoconnect Connect to the console after the domain is created. --vncviewer Connect to the VNC display after the domain is created. --vncviewer-autopass Pass VNC password to viewer via stdin and -autopass. [options] [vars] Create a domain. Domain creation parameters can be set by command-line switches, from a python configuration script or an SXP config file. See documentation for --defconfig, --config. Configuration variables can be set using VAR=VAL on the command line. For example vmid=3 sets vmid to 3. , on server: dell-ppr1, associated with object: 0004fb000006000039c6ed93e780c330... [Tue Dec 08 06:22:42 CET 2015]
When looking at the manager Graphical User Interface, no other virtual machines from the repository are reported as "running" - Some may even be listed with the "critical" event severity.
After identifying the mount point the repository should have using note "How to determine which /dev/mapper entry a repository corresponds to from the manager's GUI" (Doc ID 2084919.1),
And comparing that /dev/mapper entry with the output of the mount command :
[root@dell-ppr1 ~]# mount /dev/sda2 on / type ext4 (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw) /dev/sda1 on /boot type ext4 (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) nodev on /sys/kernel/debug type debugfs (rw) configfs on /sys/kernel/config type configfs (rw) xenfs on /proc/xen type xenfs (rw) none on /var/lib/xenstored type tmpfs (rw) ocfs2_dlmfs on /dlm type ocfs2_dlmfs (rw) /dev/mapper/3600144f0560e58220000144f81b80c00 on /poolfsmnt/0004fb0000050000d1d733cd98f00af7 type ocfs2 (rw,_netdev,heartbeat=global)
The mount point appears to be missing from the output returned by the mount command.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!