Red Hat Bugzilla – Bug 621914
virt-v2v does not configure host and guest clock settings optimally
Last modified: 2016-04-26 11:49:50 EDT
Description of problem:
A converted RHEL 4 SMP x86_64 guest will hang during boot during udev initialisation. This is due to its clock configuration.
See here for a table of recommended clock configurations for various guests:
libvirt-related notes from danpb:
danpb1: -no-pit-reinjection is equivalent to
danpb1: <clock offset='utc'> <timer name='pit' tickpolicy='delay'/>
danpb1: in libvirt XML
danpb1: and -rtc-td-hack should be possible with
danpb1: <timer name='rtc' tickpolicy='catchup' track='wall'/>
danpb1: (also within the <clock> element)
Bug 621880 (F13 qemu) may or may not be applicable to RHEL 6. I haven't checked.
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
Virt-v2v needs to run on the latest Red Hat Enterprise Linux release
to ensure it can correctly read and modify new guest filesystem
features. A new version of virt-v2v is now available for RHEL 7.1.
Before RHEL 7.1 is released, follow the instructions here to
install unsupported preview packages on top of RHEL 7.0:
After RHEL 7.1 is released, virt-v2v will be available in
You can run virt-v2v in a single virtual machine. Other
requirements are covered here:
If you find a missing feature or bug in the new version of virt-v2v
please file a bug using the following link: