VM creation failure on XEN host

jojo · July 6, 2016, 3:28pm

Hi Hector,
thanks so much for your post. This clarifies a lot!!!

And because you mentioned a manual edit of deployment file:

I recently tried to edit deployment files manually (actually because of another issue) and could not figure out how I should actually do it without having OpenNebula write a new deyployment file and change it back to the original contents (iterations of file deployment.0 deployment.1 .2… after shutting off and on the VM)

I don’t have a system at hand at the moment to try it out again, but may I ask you to confirm that it should work in this order:

First, edit the currently used deployment.X file, then destroy the original one vm:

virsh destroy one-xxx
virsh undefine one-xxx

then

virsh define /var/lib/one/...../deployment.X
virsh start one-xxx

then recover the failed vm (using which version of recover? --retry?):

onevm recover --????? one-xxx

And BTW do you know where exactely the deployment.X file is coming from?
Obviously it is once generated from information in the onetemplate, oneimage, etc., ok.

Is it then copied into the database? And on every fresh VM start/define it is pulled from the database and depyloyment.X is regenerated from there?

It is definitely never again pulled out of the onetemplate, etc informations again. That’s what I already found out.

Maybe you can shed some light on this as well. I am curious.

Thanks again!
all the best
Jojo

hsanjuan · July 6, 2016, 4:28pm

I recently tried to edit deployment files manually (actually because of another issue) and could not figure out how I should actually do it without having OpenNebula write a new deyployment file and change it back to the original contents (iterations of file deployment.0 deployment.1 .2… after shutting off and on the VM)

Right… The quick-dirty way I have thought of to achieve a fix without needing manual intervention every time would be to patch the remote/vmm/xen/deploy script and do a sed -i in the deployment file right before the xl create command is called. This would be a way to fix the deployment file every time it is used to create the VMs which does not require the recompile OpenNebula and can be distributed easily (onehost sync --force if I remember well). I haven’t tried it though, it’s just a solution I have in mind.

And BTW do you know where exactely the deployment.X file is coming from?

From XenDriver.cc (deployment_description()) function it seems. If you feel like rolling out your own custom-built OpenNebula, then you can change the relevant line on that file to make all context disks in HVM writeable.

I don’t have a system at hand at the moment to try it out again, but may I ask you to confirm that it should work in this order:

I haven’t used virsh in a long time, and OpenNebula Xen drivers use xl or xm directly. They run xl create path/to/deployment.X but this fails, so the manual fix is editing deployment.X and then running xl create manually. Then onevm recover $id --success for the VM, which then turns from FAILED to RUNNING state correctly.

atodorov_storpool · July 6, 2016, 10:03pm

Hi,

hsanjuan:

I recently tried to edit deployment files manually (actually because of another issue) and could not figure out how I should actually do it without having OpenNebula write a new deyployment file and change it back to the original contents (iterations of file deployment.0 deployment.1 .2… after shutting off and on the VM)

Right… The quick-dirty way I have thought of to achieve a fix without needing manual intervention every time would be to patch the remote/vmm/xen/deploy script and do a sed -i in the deployment file right before the xl create command is called. This would be a way to fix the deployment file every time it is used to create the VMs which does not require the recompile OpenNebula and can be distributed easily (onehost sync --force if I remember well). I haven’t tried it though, it’s just a solution I have in mind.

I can confirm that patching the deploy script and adding custom tweaking is working.

For more advanced editing you can use more complicated scripts. For example, here is my work to enable virtio-blk-data-plane on KVM hosts:

github.com

OpenNebula/addon-storpool/blob/master/vmm/kvm/vmTweakVirtioBlkDataPlane.py

#!/usr/bin/env python

# -------------------------------------------------------------------------- #
# Copyright 2015-2022, StorPool (storpool.com)                               #
#                                                                            #
# Licensed under the Apache License, Version 2.0 (the "License"); you may    #
# not use this file except in compliance with the License. You may obtain    #
# a copy of the License at                                                   #
#                                                                            #
# http://www.apache.org/licenses/LICENSE-2.0                                 #
#                                                                            #
# Unless required by applicable law or agreed to in writing, software        #
# distributed under the License is distributed on an "AS IS" BASIS,          #
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.   #
# See the License for the specific language governing permissions and        #
# limitations under the License.                                             #
#--------------------------------------------------------------------------- #

# vmTweakVirtioBlkDataPlane.py <XMLfile>

This file has been truncated. show original

Kind Regards,
Anton Todorov

jojo · July 7, 2016, 8:12am

Hi Hector

sorry for the confusion, actually i tried editing deployment files by hand on a kvm system recently! that’s why I mentioned the virsh commands. my experience though was that after the recovery of the vm the settings in the deployment file where changed back to the original state. perhaps I should experiment with this once more and also use the --success option.

thanks for the hint to the xendriver function, i will try to find the similar function in the kvm driver.

I actually did a lot of testing with Xen Hypervisors but then found a way to migrate my customers existing xen vms to kvm with minimal effort and decided to go this way. that’s why i am mixing things up a little here

Hi Anton,
I’ll read your code later today! Thanks!

all the best
Jojo

Topic		Replies	Views
[SOLVED] Failure running VM on new Host Machine Community Support	2	1908	November 5, 2015
Create Virtual Machine Failed Community Support	5	5346	August 17, 2015
VM creation failed on opennebula cloud on the top of another opennebula clod Community Support	1	847	April 26, 2016
Cannot create VM on ESX Community Support	1	997	August 12, 2015
OpenNebula failed to provision VM General	1	375	July 29, 2020

VM creation failure on XEN host

Related topics