How to run virt-sysprep / How to troubleshoot template creation failure
When attempting to create a template the process fails. It has been suggested to run virt-sysprep manually and see why it it failed. Specifically, I have an Ubuntu 20.04 machine that doesn't boot properly even if the the template process does finish without error. I have tried creating the template several times as a test. about 80% of the time the template creation fails outright for qemu errors. The other 20% "appear" to work but the system boots to a grub emergency prompt Can someone clarify the process? I know you can run the command: virt-sysprep -d <name_of_vm> 1. Where do you run it from? The hypervisor host or the management engine? 2. What account do you need to use? What is the authentication username and password? I also think I read somewhere that you should refrain from using root. Anything else to know? Anything else to try regarding the grub prompt? Thanks.
On Wed, May 25, 2022 at 01:04:11AM -0000, jeremy_tourville@hotmail.com wrote:
When attempting to create a template the process fails. It has been suggested to run virt-sysprep manually and see why it it failed. Specifically, I have an Ubuntu 20.04 machine that doesn't boot properly even if the the template process does finish without error.
I wonder if that something tells about the template itself. How did you create the template? Did the original VM work fine?
I have tried creating the template several times as a test. about 80% of the time the template creation fails outright for qemu errors. The other 20% "appear" to work but the system boots to a grub emergency prompt
Can someone clarify the process? I know you can run the command: virt-sysprep -d <name_of_vm>
This works for powered off libvirt domains but is not usable in oVirt environment.
1. Where do you run it from? The hypervisor host or the management engine?
It's not completely trivial to run manually and may not be the best approach (just yet). If you have NFS domains you may be able to figure out paths to all disks of your newly created VM and run virt-sysprep on it. If you have block storage you need to prepare the disk images first. For start, please provide vdsm.log. You should also see a log file for the virt-sysprep run in /var/log/vdsm/commands/, please provide that too.
2. What account do you need to use? What is the authentication username and password?
I also think I read somewhere that you should refrain from using root. Anything else to know?
I beleve we run all virt-* commands as vdsm user.
Anything else to try regarding the grub prompt?
Is the template worth fixing or would it make more sense to recreate it? If the original VM/template is broken it may explain the virt-sysprep failures. Tomas
Thanks. _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/ICWANF6XMXTBHX...
-- Tomáš Golembiovský <tgolembi@redhat.com>
Tomas, thank you for your input. I am creating the template from a new Ubuntu VM that I have created. I have noted that generally my centos/rocky VMs can be created from VMs without issue. It has only been Ubuntu that is giving me grief. That being said, I only have one Ubuntu VM in my environment that needs to be made into a template. Fix the template or recreate it makes no difference to me. As long as the template is usable that's all that matters. I have block storage, not NFS. You mention needing to prepare the disk images first... how? In my experience I didn't need to do that for any centos VMs. I just clicked make template in GUI, selected QCOW image type and seal VM option. In a few minutes everything was done and I could use the new template.
I was able to gather a VDSM log. Would you still like the VDSM logs? The template creation process seems to be working in the sense that the template always gets created. Now my problem has changed to having trouble with the system booting to a grub prompt as mentioned in the first post. Would the logs be of any use if the template creation process finishes? I don't understand why any VMs created from the template boot to the grub prompt.
On Sun, Jun 05, 2022 at 12:11:47AM -0000, jeremy_tourville@hotmail.com wrote:
I was able to gather a VDSM log. Would you still like the VDSM logs? The template creation process seems to be working in the sense that the template always gets created.
I don't expect to find there much if the process finishes ok, but feel free to send it to me. You don't have to post it to the mailing list.
Now my problem has changed to having trouble with the system booting to a grub prompt as mentioned in the first post. Would the logs be of any use if the template creation process finishes?
I don't understand why any VMs created from the template boot to the grub prompt.
Could you please confirm that the VM that you use to create the template works fine? * Does the original VM boot *before* creating the template? * Does the original VM boot *after* creating the template? * If you clone the VM, does the clone boot? Tomas
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/UB2ZO7TQK2DIIU...
-- Tomáš Golembiovský <tgolembi@redhat.com>
I'll send you the VDSM log. To answer you questions: Yes Yes No, the cloned VM boots to the grub prompt.
participants (2)
-
jeremy_tourville＠hotmail.com -
Tomáš Golembiovský