Latest revision |
Your text |
Line 42: |
Line 42: |
| || Install F12 (you can install it inside a virtual machine if you want, but it'll run a bit slower). Then: | | || Install F12 (you can install it inside a virtual machine if you want, but it'll run a bit slower). Then: |
| yum install libguestfs guestfish perl-libguestfs \ | | yum install libguestfs guestfish perl-libguestfs \ |
| virt-cat virt-df virt-inspector virt-v2v | | virt-cat virt-df virt-inspector |
| If there are any installation errors or dependency problems, these are serious bugs and should be reported. | | If there are any installation errors or dependency problems, these are serious bugs and should be reported. |
| |- | | |- |
Line 50: |
Line 50: |
| This should take a few seconds (perhaps up to a minute or two on a slow machine). It shouldn't print any error messages. You don't need to be root. | | This should take a few seconds (perhaps up to a minute or two on a slow machine). It shouldn't print any error messages. You don't need to be root. |
|
| |
|
| Edit: Although it "shouldn't print any error messages", if KVM is unavailable then you may see the following harmless warnings, and it'll also be a lot slower:
| | If that fails, please run: |
| | |
| open /dev/kvm: No such file or directory
| |
| Could not initialize KVM, will disable KVM support
| |
| | |
| If the short test above fails, please run: | |
| libguestfs-test-tool | | libguestfs-test-tool |
| If it doesn't print "== TEST FINISHED OK== " at the end, copy the complete, unedited output into a bug report, along with details of your test machine. You can also ask about problems in the IRC channel. | | If it doesn't print "TEST FINISHED OK" at the end, copy the complete, unedited output into a bug report, along with details of your test machine. You can also ask about problems in the IRC channel. |
| |- | | |- |
| | Inspector | | | Inspector |
Line 94: |
Line 89: |
| guestfish -a output.img -m /dev/sda1 | | guestfish -a output.img -m /dev/sda1 |
| ><fs> ls / | | ><fs> ls / |
| |-
| |
| | virt-snapshot
| |
| || Snapshot, rollback and commit an existing virtual machine. Ensure the guest is shut down, then do:
| |
| virt-snapshot <guest>
| |
| Make some changes (including changing/adding/removing virtual hardware), shutdown the guest again, then do:
| |
| virt-snapshot --rollback <guest>
| |
| Check the guest is back in its original state.
| |
| Shutdown, snapshot the guest again, make some more changes and shutdown again. Commit the changes with:
| |
| virt-snapshot --commit <guest>
| |
| Check the changes have persisted.
| |
| |-
| |
| | virt-v2v
| |
| || If you have any Xen Fedora/RHEL guests around, copy them their images over to the test box and export their libvirt domain XML on the remote box with:
| |
| virsh dumpxml <guest> > <guest>.xml
| |
| Make sure you copy the images to the same location on the test box as they were in on the origin box. Alternatively do some path surgery on the domain xml. Create the following basic virt-v2v.conf:
| |
| [libvirtxml]
| |
| bridge.xenbr1=virbr0
| |
| If the guest has a PV kernel, obtain an FV kernel relevant to the target OS and add something like the following to your virt-v2v.conf:
| |
| [aliases]
| |
| rhel.kernel-xen=kernel
| |
| rhel.kernel-xenU=kernel
| |
| fedora.kernel-xen=kernel
| |
| fedora.kernel-xenU=kernel
| |
|
| |
| [files]
| |
| rhel.5.kernel=/path/to/kernel.arch.el5.rpm
| |
| See virt-v2v.conf(5) for more. Snapshot the images and convert them to run on KVM with:
| |
| virt-snapshot -o <guest>-snapshot.xml -i libvirtxml <guest>.xml
| |
| virt-v2v -s virt-v2v.conf -i libvirtxml <guest>-snapshot.xml
| |
| Does the resulting guest boot? Does it give any errors on boot? Are the VirtIO drivers enabled? If anything looks wrong, please report any error messages, along with any config files in the guest which look broken.
| |
| |- | | |- |
| | Advanced | | | Advanced |
Line 141: |
Line 106: |
| |} | | |} |
|
| |
|
| [[Category:Fedora_12_Test_Days]] | | [[Category:Test Days]] |
| [[Category:Virtualization]] | | [[Category:Virtualization]] |