![]() |
John VanDyk has been innovating with information technology for more than 20 years. Read more... |
Solved: internal error boot orders have to be contiguous and starting from 1
Submitted by John on Wed, 2013-01-30 19:16
I exported a VM from RHEV 3.0 to an export domain. Then I imported the VM into RHEV 3.1.
I was surprised that the VM would not start. Instead, I got this message:
Exit message: internal error boot orders have to be contiguous and starting from 1
Upon further inspection, the boot order information was completely missing from the imported KVM definition:
<disk device="disk" snapshot="no" type="block">
<source dev="/rhev/data-center/a1f867a3-237a-4be3-8e07-bf61f5b95280/71051d89-b9bd-4db5-8fe1-7c4499114874/images/d543a66c-4dd6-4d49-a8ea-7d65c137ce41/39bbb768-13d0-4bb8-ae93-a2c8611da655"/>
<target bus="virtio" dev="vda"/>
<serial>d543a66c-4ef6-4d49-a8ea-7d65c137ce41</serial>
<driver cache="none" error_policy="stop" io="native" name="qemu" type="raw"/>
</disk>
I solved this by just editing the imported VM's disk in the RHEV UI. I changed the disk's properties from bootable to nonbootable and saved the change. Then I changed it back to bootable again. This wrote in the boot order:
<disk device="disk" snapshot="no" type="block">
<source dev="/rhev/data-center/a1f867a3-237a-4be3-8e07-bf61f5b95280/71051d89-b9bd-4db5-8fe1-7c4499114874/images/d543a66c-4dd6-4d49-a8ea-7d65c137ce41/39bbb768-13d0-4bb8-ae93-a2c8611da655"/>
<target bus="virtio" dev="vda"/>
<serial>d543a66c-4ef6-4d49-a8ea-7d65c137ce41</serial>
<boot order="1"/>
<driver cache="none" error_policy="stop" io="native" name="qemu" type="raw"/>
</disk>
I think this happened because the VM had a CD mounted in the RHEV 3.0 data center that was unavailable in the RHEV 3.1 data center.
See also: https://bugzilla.redhat.com/show_bug.cgi?id=874952
- Log in to post comments
Comments
RHEV upgrade from 3.0 to 3.1
Hi,
I had this same issue during the upgrade from 3.0 to 3.1. This solution worked for me...
Thank you!!!
This is known issue and has
This is known issue and has been fixed through this errata : http://rhn.redhat.com/errata/RHSA-2013-0888.html
bug that caused this issue is : https://bugzilla.redhat.com/show_bug.cgi?id=888642