HPE Morpheus VM Essentials
1825552 Members
2584 Online
109681 Solutions
New Discussion

After host goes down, VM does not start automatically.

 
SOLVED
Go to solution
kurotan
Occasional Advisor

After host goes down, VM does not start automatically.

 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?

4 REPLIES 4
kurotan
Occasional Advisor

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

# 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"?

mnavada
HPE Pro
Solution

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

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.



I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo
kurotan
Occasional Advisor

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

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

Thaufique_Mod
Moderator

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

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. 



I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo