Boot Error for Imported OVA - A start job is running ...

learnedbyerror

Active Member
Feb 15, 2018
3
0
41
60
I've run into a thorny problem with trying to install an OVA for SAP's HANA Express Edition. I am not able to successfully boot the VM when installed on Proxmox 5-1.43. I received to alternating boot messages:

(1 of 2) A start job is running for dev-disk-...b7\x2df9f73ba820c5.device (xxs / no limit)
(2 of 2) A start job is running for dev-sda1.device (xxs / 1 min 30s)


I have created the VM two different ways with the same result. They are:
  1. Untarred the OVA file, gunzipped the vmdk.gz, and then imported with qm importovf
  2. Untarred the OVA file, gunzipped the vmdk.gz, created the VM using the Proxmox Web Interface, converted the vmdk to a cow2 using qemu-img
I can use the same OVA file with VMWare Fusion (importing the OVA and letting Fusion build the VM) and with VirtualBox (lImport Appliance). In both of these cases, the image boots up immediately. I have reviewed and matched the configuration between Fusion and Virtualbox but can't find anything that I recognize as a difference between the configs.

Lastly, I have read through a "lot" of posts on the web searching using the error message and any combination of SAP HANA, SLES, Suse, grub2 ... No joy there. Most of the time the error message seemed to be caused by misconfiguration between the disk UUID, /etc/fstab and grub. I cannot find anything inconsistent with the config (see below for details).

Any help on this will be greatly appreciated!

Thanks,

lbe

Details below:

My config file for option 2 is:
bootdisk: scsi0
cores: 2
ide2: none,media=cdrom
memory: 8192
name: HXE1
net0: e1000=9A:E9:A4:64:EF:41,bridge=vmbr0
numa: 0
ostype: l26
scsi0: local-dir:122/vm-122-disk-1.qcow2,cache=writethrough,size=70000M
scsihw: virtio-scsi-pci
smbios1: uuid=dd0af3d1-4ec6-45aa-ae09-010cefae859b
sockets: 1


I have tried variations of both the virtio-scsi-pci and lsilogic controllers.

Additionally, I have mounted the qcow2 file using nbd.

fdisk -l /dev/nbd0 output:
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0002740e

Device Boot Start End Sectors Size Id Type
nbd0p1 2048 8402943 8400896 4G 82 Linux swap / Solaris
nbd0p2 * 8402944 143359999 134957056 64.4G 83 Linux


blkid /dev/nbd0p(1|2)
/dev/nbd0p1: UUID="1d16032a-ec49-4925-9c5c-4919a6c69abc" TYPE="swap" PARTUUID="0002740e-01"
/dev/nbd0p2: UUID="d2fd1fd0-9563-4b5e-9eb7-f9f73ba820c5" TYPE="xfs" PARTUUID="0002740e-02"


The UID for the xfs partition matches the fragment shown in the error msg​

/etc/fstab content from nbd0p2 when mounted
/dev/sda1 swap swap defaults 0 0
/dev/sda2 / xfs defaults 1 1
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!