topic Re: After host goes down, VM does not start automatically. in HPE Morpheus VM Essentials

After host goes down, VM does not start automatically.

kurotan — Thu, 12 Jun 2025 00:49:03 GMT

I tried to start it manually but it did not start.

When I executed

virsh start <vm name>

I got the following

-------------------------

error: Failed to start-domain 'vm name'

Error:Cannot access storage file `/mnt/XXXX/vm name/hpevm-15-disk-0-snap-xxxxxxxxxx'(as uid:0 gid108):No such file or directory

---------------------------

There was no file in ”/mnt/XXXX/vm name/hpevm-15-disk-0-snap-xxxxxxxxxx”,

but ”/mnt/XXXX/vm name/hpevm-15-disk-0” did exist.

Is there a way to start the VM?

Re: After host goes down, VM does not start automatically.

kurotan — Wed, 11 Jun 2025 07:39:13 GMT

# I tried to start the VM,

root@ucs-2:~#vrish
virsh # start CentOS9-XCP02
error: Failed to start domain 'CentOS9-XCP02'
error: Cannot access storage file '/mnt/f9a16a99-546e-4697-aba2-dfa57be1674a/CentOS9-XCP02/hpevm_15-disk-0-snap-1748736070773' (as uid:0, gid:108): No such file or directory

# There is no file "hpevm_15-disk-0-snap-1748736070773" but there is "hpevm_15-disk-0".
root@ucs-2:~# ls /mnt/f9a16a99-546e-4697-aba2-dfa57be1674a/CentOS9-XCP02/
hpevm_15-disk-0

#Edited the XML
root@ucs-2:~#vrish
virsh # edit CentOS9-XCP02
---------------
<disk type='file' device='disk'>
<driver name='qemu' type='qcow2' cache='none' io='io_uring' discard='unmap'/>
<source file='/mnt/f9a16a99-546e-4697-aba2-dfa57be1674a/CentOS9-XCP02/hpevm_15-disk-0-snap-1748736070773'/>
---------------
To
---------------
<disk type='file' device='disk'>
<driver name='qemu' type='qcow2' cache='none' io='io_uring' discard='unmap'/>
<source file='/mnt/f9a16a99-546e-4697-aba2-dfa57be1674a/CentOS9-XCP02/hpevm_15-disk-0'/>
---------------
virsh # edit CentOS9-XCP02
Domain 'CentOS9-XCP02' XML configuration edited.

＃Started the VM
virsh # start CentOS9-XCP02
Domain 'CentOS9-XCP02' started

＃Started

Is this the correct way?

What is the file "hpevm_15-disk-0-snap-1748736070773"?

Re: After host goes down, VM does not start automatically.

mnavada — Wed, 11 Jun 2025 07:52:38 GMT

Hi,

Thanks for contacting HPE via community forum and sharing detailed information.

## The VM didn't start since it couldn't find the boot device. In the configuration of VM, snapshot path ( hpevm-15-disk-0-snap-xxxxxxxxxx”) was defined. Since there was no snapshot disk path in the datastore ( /mnt/XXXX/<vm name > , booting or starting of VM failed.

## The correct boot device for the VM was ”/mnt/XXXX/vm name/hpevm-15-disk-0”. Since you have edited the "xml" file and updated the correct "boot path" for VM, you could start the VM correctly.

## Here issue occured due to missing of boot disk. I suspect that there might be some inconsistancy occured or someone might have modified the boot device.

## Yes, the procedure that you followed to fix the issue is correct.

Re: After host goes down, VM does not start automatically.

kurotan — Thu, 12 Jun 2025 00:46:56 GMT

Thanks for the reply and I understand that my solution is correct.

Re: After host goes down, VM does not start automatically.

Thaufique_Mod — Thu, 12 Jun 2025 06:49:19 GMT

Hello @kurotan,

That's great!
We are happy to hear that you were able to find the solution, and we appreciate you keeping us updated.