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 publish the changes below to finish undoing the edit.

Latest revision Your text
Line 212: Line 212:
| [[User:lersek|lersek]]
| [[User:lersek|lersek]]
| HP Z400
| HP Z400
| {{result|pass}}  <ref group="long">Probably should file a bunch of bugs but no time for it now. This was the
| {{result|pass}}  <ref>Probably should file a bunch of bugs but no time for it now. This was the
whole process:
whole process:


Line 267: Line 267:
actually shut off.)
actually shut off.)
</ref>
</ref>
| {{result|warn}}  <ref group="long">Problem #6: the virt-manager Text Console login test works, but after that,
| {{result|warn}}  <ref>Problem #6: the virt-manager Text Console login test works, but after that,
even when switching back to the Graphical Console VNC, the virsh console
even when switching back to the Graphical Console VNC, the virsh console
test fails with
test fails with
Line 278: Line 278:
|  
|  
|  
|  
| {{result|fail}}  <ref group="long">Connecting the first ISO worked alright (showed up in guest, both on the GNOME 3 GUI and under /run/media/user), but it could not be disconnected. First, I encountered BZ#967914. After that, the first ISO was not unmounted in the guest, even though virt-manager implied so at the second attempt; listing the /run/media/user/CD_ROM_NAME directory corresponding to the ISO image produced IO errors, the CD_ROM_NAME directory was not removed. The "virsh change-media" reported success on the host side, but again its effect was not visible in the guest (same IO errors and the first ISO's name, as above).</ref>
| {{result|fail}}  <ref>Connecting the first ISO worked alright (showed up in guest, both on the GNOME 3 GUI and under /run/media/user), but it could not be disconnected. First, I encountered BZ#967914. After that, the first ISO was not unmounted in the guest, even though virt-manager implied so at the second attempt; listing the /run/media/user/CD_ROM_NAME directory corresponding to the ISO image produced IO errors, the CD_ROM_NAME directory was not removed. The "virsh change-media" reported success on the host side, but again its effect was not visible in the guest (same IO errors and the first ISO's name, as above).</ref>
| <references/>
| <references/>
|-
|-
Line 289: Line 289:
| {{result|pass}}  <ref>I tested only booting LIVE.iso in the nested VM</ref>
| {{result|pass}}  <ref>I tested only booting LIVE.iso in the nested VM</ref>
|  
|  
| {{result|fail}}  <ref group="long">Does not work with my network card - it throws exception "Unable to read from monitor on start", but the card is removed from host for a short while.
| {{result|fail}}  <ref>Does not work with my network card - it throws exception "Unable to read from monitor on start", but the card is removed from host for a short while.
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04)</ref>
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04)</ref>
|  
|  
Line 311: Line 311:
| Lenovo T500
| Lenovo T500
| {{result|pass}}  <ref>F19 guest from DVD</ref>
| {{result|pass}}  <ref>F19 guest from DVD</ref>
| {{result|fail}}  <ref group="long">The very first reboot after the guest install,  
| {{result|fail}}  <ref>The very first reboot after the guest install,  
there are boot messages on the console. Then
there are boot messages on the console. Then
the console activities stopped.  No login  
the console activities stopped.  No login  
Line 327: Line 327:
|  
|  
|  
|  
| {{result|fail||967914}}<ref group="long">CDROM in the guest mostly worked.
| {{result|fail||967914}}<ref>CDROM in the guest mostly worked.
The only problem is already reported by BZ 967914: the first "Disconnect" operation from virt-manager would fail with an error "These changes will take effect after the next guest sutdown". In the Details section, there is the
The only problem is already reported by BZ 967914: the first "Disconnect" operation from virt-manager would fail with an error "These changes will take effect after the next guest sutdown". In the Details section, there is the
message "internal error unable to execute QEMU command 'eject': Device drive-ide0-0-1 is locked".  
message "internal error unable to execute QEMU command 'eject': Device drive-ide0-0-1 is locked".  
Line 336: Line 336:
| [[User:JustinClift|JustinClift]]
| [[User:JustinClift|JustinClift]]
| Dell Inspiron 7720-4578
| Dell Inspiron 7720-4578
| {{result|pass}}  <ref group="long">Installed guest (F19 Beta RC4 64-bit DVD).
| {{result|pass}}  <ref>Installed guest (F19 Beta RC4 64-bit DVD).


Installation went fine.  The only weirdness was artifacts in the display of the banner like "I'm sorry Dave, I can't do that".  May be related to the Nvidia GT 650M graphics card + nouveau drivers on host, with the VNC code in Virtual Machine Manager.</ref>
Installation went fine.  The only weirdness was artifacts in the display of the banner like "I'm sorry Dave, I can't do that".  May be related to the Nvidia GT 650M graphics card + nouveau drivers on host, with the VNC code in Virtual Machine Manager.</ref>
|  
|  
| {{result|warn}}  <ref group="long">Only got part way through testing this before I had to leave (for airport).
| {{result|warn}}  <ref>Only got part way through testing this before I had to leave (for airport).


Pausing a running guest (F19 Beta RC4 x64 with 4GB ram) worked using VMM, but had problems.  The "Run" option in VMM never became enabled in either the high level VMM overview window (in buttons toolbar), nor in the VNC console (buttons, menu structure).
Pausing a running guest (F19 Beta RC4 x64 with 4GB ram) worked using VMM, but had problems.  The "Run" option in VMM never became enabled in either the high level VMM overview window (in buttons toolbar), nor in the VNC console (buttons, menu structure).
Line 368: Line 368:
| [[User:sagarun|sagarun]]
| [[User:sagarun|sagarun]]
| HP Desktop - Intel Core2duo
| HP Desktop - Intel Core2duo
| {{result|pass}}  <ref>FreeBSD 7 works fine!</ref>{{result|warn}}  <ref>Works fine with a RHEL 6 guest - First time i had to restart libvirtd to make it working!</ref>{{result|warn}}  <ref group="long">Works fine except, On a freshly installed Fedora 19 - Beta TC4 the libvirtd needs to be restarted once.
| {{result|pass}}  <ref>FreeBSD 7 works fine!</ref>{{result|warn}}  <ref>Works fine with a RHEL 6 guest - First time i had to restart libvirtd to make it working!</ref>{{result|warn}}  <ref>Works fine except, On a freshly installed Fedora 19 - Beta TC4 the libvirtd needs to be restarted once.




Line 404: Line 404:
| [[User:jasonbrooks|jasonbrooks]]
| [[User:jasonbrooks|jasonbrooks]]
| Lenovo X220
| Lenovo X220
| {{result|warn}}  <ref group="long">virt-install argument "--os-distro" specified in the directions turned up the error "virt-install: error: no such option: --os-distro"
| {{result|warn}}  <ref>virt-install argument "--os-distro" specified in the directions turned up the error "virt-install: error: no such option: --os-distro"


I used --os-variant instead.
I used --os-variant instead.
Line 439: Line 439:
| [[User:SlowJet|SlowJet]]
| [[User:SlowJet|SlowJet]]
| Intel G865BGF(3G-PreviewRepo)
| Intel G865BGF(3G-PreviewRepo)
| {{result|warn}}  <ref group="long">Created new VM from Hurd/Debain img in Downloads.
| {{result|warn}}  <ref>Created new VM from Hurd/Debain img in Downloads.
A message said it would take care of the access issues, after running a bit, I did a clone vm (not pased).
A message said it would take care of the access issues, after running a bit, I did a clone vm (not pased).
The clone booted and ran.
The clone booted and ran.
Line 463: Line 463:
|  
|  
|  
|  
| {{result|fail}}  <ref group="long">Tried with:
| {{result|fail}}  <ref>Tried with:
  * 0d:00.0 SD Host controller: Ricoh Co Ltd MMC/SD Host Controller (rev 01)
  * 0d:00.0 SD Host controller: Ricoh Co Ltd MMC/SD Host Controller (rev 01)
  * 00:19.0 Ethernet controller: Intel Corporation 82577LM Gigabit Network Connection (rev 06)
  * 00:19.0 Ethernet controller: Intel Corporation 82577LM Gigabit Network Connection (rev 06)
Line 501: Line 501:
| [[User:knoel|knoel]]
| [[User:knoel|knoel]]
| IBM x3550 M4
| IBM x3550 M4
| {{result|pass}}  <ref group="long">Messy debug output:
| {{result|pass}}  <ref>Messy debug output:


3 clients want entropy
3 clients want entropy
Line 539: Line 539:
| [[User:JustinClift|JustinClift]]
| [[User:JustinClift|JustinClift]]
| Dell Inspiron 7720-4578
| Dell Inspiron 7720-4578
| {{result|pass}}  <ref group="long">Tested both /dev/random and egd.pl in guest after configuring virtio rng.  Worked perfectly.  egd.pl debug showed client requesting entropy, etc.</ref>
| {{result|pass}}  <ref>Tested both /dev/random and egd.pl in guest after configuring virtio rng.  Worked perfectly.  egd.pl debug showed client requesting entropy, etc.</ref>
|  
|  
|  
|  
Line 548: Line 548:
|  
|  
|  
|  
| {{result|fail}}  <ref group="long">Not sure if this is a bug; dmesg | grep -e DMAR -e IOMMU shows 3 entries, but there's no vfio in /dev and issuing VM start outputs "Error starting domain: internal error Invalid device 0000:00:19.0 iommu_group file /sys/bus/pci/devices/0000:00:19.0/iommu_group is not a symlink".</ref>
| {{result|fail}}  <ref>Not sure if this is a bug; dmesg | grep -e DMAR -e IOMMU shows 3 entries, but there's no vfio in /dev and issuing VM start outputs "Error starting domain: internal error Invalid device 0000:00:19.0 iommu_group file /sys/bus/pci/devices/0000:00:19.0/iommu_group is not a symlink".</ref>
| <references/>
| <references/>
|}
|}
Line 555: Line 555:


== Debugging ==
== Debugging ==
== Long comments ==
<references group="long" />


* https://fedoraproject.org/wiki/How_to_debug_Libvirt_problems
* https://fedoraproject.org/wiki/How_to_debug_Libvirt_problems
Please note that all contributions to Fedora Project Wiki are considered to be released under the Attribution-Share Alike 4.0 International (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)