Bug #1630
closed
oVirt hosts cannot boot after they are built
Description
The boot order for VM's looks like it gets set to Network first and then Hard Disk.
The problem is that even after they are done being built the file and next-server options get left in the lease. Having only the config missing causes the boot to fail outright, rather than passing the pxe boot and proceeding with boot from disk.
So, either the lease needs to be rewritten without those options after the host has completed building and/or you need to swap the boot order at that time, otherise you are left with vm's that don't boot properly.
This is using RHEV 3.0 if it makes a difference.
Updated by Ohad Levy almost 12 years ago
- Status changed from New to Resolved
please use the default tftp (more --> provisioning templates --> default tftp button) to generate the default behaivour you desire (e.g. boot from disk).
it might be an option to update dhcp attributes as well, but for the moment, it is implemented as tftp based solution (as your dhcp options might fall back to a more generic option).