From Fedora Project Wiki

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 48: Line 48:
 
* Hardware virtualization support (e.g. Intel VT or AMD-V) (see [[How_to_debug_Virtualization_problems#Is_My_Guest_Using_KVM.3F|Is My Guest Using KVM?]]).  If unavailable, you can still help with testing QEMU support.
 
* Hardware virtualization support (e.g. Intel VT or AMD-V) (see [[How_to_debug_Virtualization_problems#Is_My_Guest_Using_KVM.3F|Is My Guest Using KVM?]]).  If unavailable, you can still help with testing QEMU support.
 
* Up to 10-20Gb free disk space. Guest images take up a lot of space.
 
* Up to 10-20Gb free disk space. Guest images take up a lot of space.
* Get the packages with <br><pre>yum groupinstall virtualization</pre>
 
  
 
As for getting the latest virt packages, you have a few options:
 
As for getting the latest virt packages, you have a few options:
Line 73: Line 72:
  
 
Do you have a new machine with a ton of ram and storage space, running Fedora 17? Nested virt might be an option!
 
Do you have a new machine with a ton of ram and storage space, running Fedora 17? Nested virt might be an option!
This allows you to create KVM guests _inside_ a Fedora 18 VM.
+
This allows you to create KVM guests _inside_ a Fedora 18 VM. You'll want to install the latest virt packages from
 
+
virt-preview (linked above). Install a Fedora 18 guest (there are test cases below that walk you through it).
# Install the latest virt packages from virt-preview using the instructions above.
+
Then use virt-manager to 'copy host CPU' for your VM. Boot the VM, yum groupinstall @virtualization, and
# Install a Fedora 18 guest using one of the test cases below.
+
verify that nested virt is working (sudo virt-host-validate).
# Use virt-manager to 'copy host CPU' for your VM. Boot the VM, install virtualization packages, and verify that nested virt is working by running the following command as root: <br><pre>virt-host-validate</pre>
 
  
 
Some notes on nested virt with AMD and Intel:
 
Some notes on nested virt with AMD and Intel:
Line 87: Line 85:
 
== Areas to test ==
 
== Areas to test ==
  
=== '''VM Install''' ===
+
=== VM Install (Do these first!) ===
 
 
Record your results for these test cases in the '''[[#Test Results |Test Results]]''' section.
 
  
 
If you don't already have a VM available, run through one of these test cases. A fully functioning VM is required for every other test case!
 
If you don't already have a VM available, run through one of these test cases. A fully functioning VM is required for every other test case!
Line 96: Line 92:
 
* [[QA:Testcase Virtualization URL Guest Install| Guest install via URL]]
 
* [[QA:Testcase Virtualization URL Guest Install| Guest install via URL]]
  
Next give this a run through, which should ensure things aren't broken in some obvious manner:
+
Next give this a run through, which should ensure things aren't broken in some obvious manner
  
 
* [[QA:Testcase Virtualization Virt Manager Lifecycle|VM Lifecycle (start, stop, save, delete, ...)]]
 
* [[QA:Testcase Virtualization Virt Manager Lifecycle|VM Lifecycle (start, stop, save, delete, ...)]]
  
=== '''New tests and features''' ===
+
=== New tests and features ===
 
 
Record your results for these test cases in the '''[[#Test Results|Test Results]]''' section.
 
  
 
* [[QA:Testcase Virtualization Live Backup|Live VM disk backup]]
 
* [[QA:Testcase Virtualization Live Backup|Live VM disk backup]]
Line 111: Line 105:
 
* [[QA:Testcase Virtualization USB3 Device Passthrough|USB3 device assignment]]
 
* [[QA:Testcase Virtualization USB3 Device Passthrough|USB3 device assignment]]
 
* [[QA:Testcase Virtualization USB Redirection|USB Redirection]]
 
* [[QA:Testcase Virtualization USB Redirection|USB Redirection]]
 
=== libguestfs and tools ===
 
 
You will need Fedora 18 (host) and at least one guest (but the more the merrier).
 
 
Install libguestfs:
 
 
# yum install '*guestf*'
 
 
and run through the tests here: http://libguestfs.org/guestfs-testing.1.html
 
 
In Fedora 18, we are using [http://libvirt.org libvirt] to launch the appliance, and [http://selinuxproject.org/page/SVirt sVirt] + SELinux to make everything [http://libguestfs.org/guestfs.3.html#security much more secure].  Therefore it's better (though not required) if you can run these tests with SELinux set to enforcing.
 
  
 
=== Previous test cases ===
 
=== Previous test cases ===
Line 143: Line 125:
 
* [[QA:Testcase Virtualization Virtio SCSI Install|Virtio SCSI install]]
 
* [[QA:Testcase Virtualization Virtio SCSI Install|Virtio SCSI install]]
 
* [[QA:Testcase Virtualization Virtio SCSI Hotplug|Virtio SCSI hotplug]]
 
* [[QA:Testcase Virtualization Virtio SCSI Hotplug|Virtio SCSI hotplug]]
 +
 +
==== libguestfs and tools ====
 +
 +
You will need Fedora 18 (host) and at least one guest (but the more the merrier).
 +
 +
Install libguestfs:
 +
 +
# yum install '*guestf*'
 +
 +
and run through the tests here: http://libguestfs.org/guestfs-testing.1.html
 +
 +
In Fedora 18, we are using [http://libvirt.org libvirt] to launch the appliance, and [http://selinuxproject.org/page/SVirt sVirt] + SELinux to make everything [http://libguestfs.org/guestfs.3.html#security much more secure].  Therefore it's better (though not required) if you can run these tests with SELinux set to enforcing.
 +
 +
==== GuestOS compatibility ====
 +
 +
* [[Test_Day:2012-04-12_Virtualization_Test_Day-GuestOS | GuestOS compatibility]] <br>&mdash; test installation of as many different guest operating system as as possible. (You will need a KVM bare metal host & lots of disk space)
  
  

Please note that all contributions to Fedora Project Wiki are considered to be released under the Attribution-Share Alike 3.0 Unported (see Fedora Project Wiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To edit this page, please solve the following task below and enter the answer in the box (more info):

Cancel Editing help (opens in new window)