From Fedora Project Wiki
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 194: | Line 194: | ||
| Dell_Optiplex_790 (F19 with Preview Repo) | | Dell_Optiplex_790 (F19 with Preview Repo) | ||
| {{result|pass}} | | {{result|pass}} | ||
| {{result|fail||873468}}<ref | | {{result|fail||873468}}<ref>Encountered the issue described in this bug ("Nothing Selected" in Software Selection). The workaround mentioned solved the issue. After that, I was able to start installation but while I was creating a user the installation aborted (error populatint transaction: failure: ntfsprogs...). Could be network issue.</ref> | ||
| | | | ||
| {{result|pass}} | | {{result|pass}} | ||
Line 227: | Line 227: | ||
| [[User:dustymabe|dustymabe]] | | [[User:dustymabe|dustymabe]] | ||
| Nested Virt - F19(L0) F20(L1) F20(L2) | | Nested Virt - F19(L0) F20(L1) F20(L2) | ||
| {{result|pass}} <ref | | {{result|pass}} <ref># F20 iso image was attached to cdrom of L1 guest | ||
# Following command was run to create and install L2 guest | # Following command was run to create and install L2 guest | ||
Line 233: | Line 233: | ||
virt-install --name nest1 --ram 2048 --disk /guests/nest1.img,size=10,bus=scsi --controller=scsi,model=virtio-scsi --accelerate --location /dev/sr0</ref> | virt-install --name nest1 --ram 2048 --disk /guests/nest1.img,size=10,bus=scsi --controller=scsi,model=virtio-scsi --accelerate --location /dev/sr0</ref> | ||
| | | | ||
| {{result|pass||1016715}}<ref | | {{result|pass||1016715}}<ref>PXE and network components worked fine (used virt-install --pxe...). Only issue came at the end of install when I had to force reboot the guest. This may be a result of my odd nested virt setup. </ref> | ||
| | | | ||
| <references/> | | <references/> | ||
Line 256: | Line 256: | ||
| HP EliteBook 8530p | | HP EliteBook 8530p | ||
| {{result|pass||1016657}}<ref>The install via virt-manager's 'New VM' wizard was smooth, apart from the issue described in the bug report.</ref> | | {{result|pass||1016657}}<ref>The install via virt-manager's 'New VM' wizard was smooth, apart from the issue described in the bug report.</ref> | ||
| {{result|fail||1016606}}<ref | | {{result|fail||1016606}}<ref>After working around the first bug, I didn't manage to install via URL due to mirror problems (a needed several retries to get the initial image, later anaconda failed in the middle of install due to a missing rpm package).</ref> | ||
| | | | ||
| | | | ||
Line 299: | Line 299: | ||
| [[User:Jorge_Fabregas|Jorge_Fabregas]] | | [[User:Jorge_Fabregas|Jorge_Fabregas]] | ||
| Dell_Optiplex_790 (F19 with Preview Repo) | | Dell_Optiplex_790 (F19 with Preview Repo) | ||
| {{result|warn}} <ref | | {{result|warn}} <ref>After installing Fedora-20-Beta-TC2-x86_64-DVD.iso, I can't see the mouse pointer on the Desktop (this VM was installed with virt-install ...--os-variant fedora20)</ref>{{result|pass}} | ||
| {{result|pass}} <ref | | {{result|pass}} <ref>Found out that once you open the console thru virt-manager...no matter if you close the viewer window you can't use the virsh line. You have to close virt-manager completely in order to use virsh console...</ref>{{result|warn}} <ref>It worked thru virt-manager. With "virsh console test-day-vm" I received: | ||
Connected to domain test-day-vm | Connected to domain test-day-vm | ||
Line 307: | Line 307: | ||
This was using Fedora-20-Beta-TC2-x86_64-DVD.iso | This was using Fedora-20-Beta-TC2-x86_64-DVD.iso | ||
</ref>{{result|warn}} <ref | </ref>{{result|warn}} <ref>It worked thru virt-manager. With "virsh console test-day-vm" I received: | ||
Connected to domain test-day-vm | Connected to domain test-day-vm | ||
Line 336: | Line 336: | ||
| Nested Virt - F19(L0) F20(L1) F20(L2) | | Nested Virt - F19(L0) F20(L1) F20(L2) | ||
| | | | ||
| {{result|pass}} <ref | | {{result|pass}} <ref>Install guest with --os-variant fedora20 and verified guest xml has serial console device and can login using virsh console and virt-manager. </ref> | ||
| | | | ||
| | | | ||
Line 350: | Line 350: | ||
| {{result|warn}} <ref>Exact behavior as Jorge_Fabregas mentioned in his comments</ref> | | {{result|warn}} <ref>Exact behavior as Jorge_Fabregas mentioned in his comments</ref> | ||
| | | | ||
| {{result|pass}} <ref>Failed the first time - testcase didn't mentione "nested=1" to kvm_intel</ref>{{result|fail}} <ref | | {{result|pass}} <ref>Failed the first time - testcase didn't mentione "nested=1" to kvm_intel</ref>{{result|fail}} <ref>Launched L1 using virt-manager (CPU copy host). Verified that qemu on host has -cpu SandyBridge,+pdpe1gb,+osxsave,+dca,+pcid,+pdcm,+xtpr,+tm2,+est,+smx,+vmx,+ds_cpl,+monitor,+dtes64,+pbe,+tm,+ht,+ss,+acpi,+ds,+vme. Inside guest, cpuinfo shows SandyBridge but no vmx flags found.</ref> | ||
| | | | ||
| {{result|warn}} <ref>For VFIO, after adding <driver name='vfio' /> to the config, I couldn't run the guest at all. I am guessing it's a syntax issue.</ref>{{result|pass}} <ref>I tested with a Intel 82599 controller. | | {{result|warn}} <ref>For VFIO, after adding <driver name='vfio' /> to the config, I couldn't run the guest at all. I am guessing it's a syntax issue.</ref>{{result|pass}} <ref>I tested with a Intel 82599 controller. | ||
Line 373: | Line 373: | ||
| HP EliteBook 8530p | | HP EliteBook 8530p | ||
| {{result|pass}} | | {{result|pass}} | ||
| {{result|warn||1016488}}<ref | | {{result|warn||1016488}}<ref>Same thing as observed by atodorov. However, if I manually add the Console Device via "Add Hardware" option, I get a working console in virt-manager. 'virsh console vm-name' still doesn't work though.</ref> | ||
| {{result|fail||1016511}}<ref>Similar to what mrezanina observed.</ref> | | {{result|fail||1016511}}<ref>Similar to what mrezanina observed.</ref> | ||
| | | | ||
Line 384: | Line 384: | ||
| [[User:rhn-support-jrodrigu|rhn-support-jrodrigu]] | | [[User:rhn-support-jrodrigu|rhn-support-jrodrigu]] | ||
| Lenovo T430s | | Lenovo T430s | ||
| {{result|pass}} <ref>In save VM after doing three times it has been successful.</ref>{{result|fail}} <ref | | {{result|pass}} <ref>In save VM after doing three times it has been successful.</ref>{{result|fail}} <ref>Error saving domain: internal error: unexpected migration status in setup | ||
Traceback (most recent call last): | Traceback (most recent call last): | ||
Line 396: | Line 396: | ||
if ret == -1: raise libvirtError ('virDomainManagedSave() failed', dom=self) | if ret == -1: raise libvirtError ('virDomainManagedSave() failed', dom=self) | ||
libvirtError: internal error: unexpected migration status in setup</ref> | libvirtError: internal error: unexpected migration status in setup</ref> | ||
| {{result|warn}} <ref | | {{result|warn}} <ref>Finally I have been able to add a virtio console and it works fine from virt-manager. From command line I have been able to connect but login didn't appear and I haven't been able to login.</ref>{{result|fail}} <ref>My Guest didn't have a virtio console. After add it guest doesn't start and in /var/log/libvirt/qemu/fedora20.log I have: | ||
... | ... | ||
Line 405: | Line 405: | ||
2013-10-09 13:33:50.918+0000: shutting down | 2013-10-09 13:33:50.918+0000: shutting down | ||
</ref> | </ref> | ||
| {{result|warn}} <ref | | {{result|warn}} <ref>I have been able to attach USB pen-drive from my Lenovo to my first Fedora 20 VM. When I try to attach this pen-drive to my nested Fedora 20 nested VM I receive this error: | ||
Path '/dev/bus/usb/000/000' is not accessible: No such file or directory | Path '/dev/bus/usb/000/000' is not accessible: No such file or directory | ||
Line 495: | Line 495: | ||
Should you encounter any problem while using the web application, please contact jskladan on #fedora-qa channel at freenode, or send an email to jskladan@fedoraproject.org --> | Should you encounter any problem while using the web application, please contact jskladan on #fedora-qa channel at freenode, or send an email to jskladan@fedoraproject.org --> | ||
[[Category:Test Days]] [[Category:Fedora 20 Test Days]] [[Category:Virtualization]] | |||