From Fedora Project Wiki

(Fix testday app-generated results to use {{result}} template for bug references)
(Move long comments to a separate section at end of page)
Line 212: Line 212:
| [[User:lersek|lersek]]
| [[User:lersek|lersek]]
| HP Z400
| HP Z400
| {{result|pass}}  <ref>Probably should file a bunch of bugs but no time for it now. This was the
| {{result|pass}}  <ref group="long">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>Problem #6: the virt-manager Text Console login test works, but after that,
| {{result|warn}}  <ref group="long">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>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 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>
| <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>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 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.
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>The very first reboot after the guest install,  
| {{result|fail}}  <ref group="long">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>CDROM in the guest mostly worked.
| {{result|fail||967914}}<ref group="long">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>Installed guest (F19 Beta RC4 64-bit DVD).
| {{result|pass}}  <ref group="long">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>Only got part way through testing this before I had to leave (for airport).
| {{result|warn}}  <ref group="long">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>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 group="long">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>virt-install argument "--os-distro" specified in the directions turned up the error "virt-install: error: no such option: --os-distro"
| {{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"


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>Created new VM from Hurd/Debain img in Downloads.
| {{result|warn}}  <ref group="long">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>Tried with:
| {{result|fail}}  <ref group="long">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>Messy debug output:
| {{result|pass}}  <ref group="long">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>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 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>
|  
|  
|  
|  
Line 548: Line 548:
|  
|  
|  
|  
| {{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>
| {{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>
| <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

Revision as of 06:24, 26 December 2014

Fedora Test Days
Virtualization Test Day
Date 2013-05-28
Time all day
Website Virtualization
IRC #fedora-test-day

(webirc IRC logs)

Mailing list virt


Can't make the date?
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.

What to test?

Today's installment of Fedora Test Day will focus on Virtualization in Fedora 19. Test cases will basic virtualization workflow, some cool functionality, as well as new features introduced in Fedora 19.

Who's available

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...

Known issues

Before you begin testing, there are a few known bugs that should be taken into account:

  • running libvirtd inside a guest can break that guests networking. you can work around this by using 'sudo virsh net-edit default' inside the VM, and change all instances of 192.168.122 to 192.168.123 and restarting the VM: bug 811967
  • saving (migrate to file) a guest using spice is crashy bug 962954
  • /dev/vfio/vfio has wrong default permissions. bug 967230
  • Storage migration can fail at the end of the process bug 967242
  • Fedora 19 isn't listed as an OS option in virt-manager bug 950230
  • VM's can hang when trying to destroy: bug 961665
  • QXL + VNC has graphical corruption: bug 948717
  • On initial install, wrong /dev/kvm permissions cause weird libvirt error reporting: hda-duplex not supported by this binary. Reboot should fix it: bug 967836
  • Bad guest performance using virt-install --location install: bug 967780

What's needed to test

For starters, your physical machine should have:

  • Hardware virtualization support (e.g. Intel VT or AMD-V) (see 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.
  • Get the packages with: yum groupinstall virtualization

As for getting the latest virt packages, you have a few options:

Virt Test Day Live CD

There's a Fedora 19 live CD image that already has all the required virtualization packages installed (though you should still yum update after booting). You will probably want a good amount of RAM if using this option (greater than 4G) since you'll be using RAM for both a VM and running the live OS.

Fedora 19 on a physical machine

The preferred testing platform is a fully updated Fedora 19 machine. You have a few options for getting the Fedora 19 bits:

Install with CD/DVD

You can download the Fedora 19 Beta in various formats here. Note: the Beta will be officially released on 2013-05-28, the day of the Test Day; if you wish to download it ahead of time, the images can be found here.

Upgrade from Fedora 18

Run Fedora 19 in a VM with nested virtualization

Do you have a new machine with a ton of ram and storage space, running Fedora 18? Nested virt might be an option! This allows you to create KVM guests inside a Fedora 19 VM.

Use the virt-preview instructions below, install a guest using one of the install test cases, and follow the [[nested virt test case to finish the setup and verify things are working correctly.

Fedora 19 virt packages on Fedora 18

If you aren't ready to make the jump to Fedora 19, this is the next best thing! Run latest virt packages on Fedora 18 from the virt-preview repo:

http://fedoraproject.org/wiki/Virtualization_Preview_Repository

At present, some of the packages in virt-preview are actually newer than what's in Fedora 19 (qemu 1.4 vs. qemu 1.5), but testing is still useful.

Areas to test

All these tests have an entry in the Test Results table, please record them there.

VM Install

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!

Standard features

These are recurring tests of standard virt features, they ensure nothing obvious is broken.

New features

New or improved features in Fedora 19:


Extra tests

These tests aren't listed in the 'test results' table, but consider giving them a spin and reporting any issues on IRC or bugzilla.

libguestfs and tools

You will need Fedora 19 (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

Previous test cases

Some test cases used in previous test days. Still useful to test for regressions!

Fedora 18 features:

Misc tests:

All tests:

Test Results

We are tracking test results in a web application over here

Results from this web application will be automatically transferred to the Wiki on 2013-06-11 and the reporting system will be shutdown. Feel free to continue testing and filling the wiki even after this date.

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

Basic

User Hardware VM-Install Serial login VM Lifecycle Host USB Nested virt Live migration PCI passthrough Change CDROM References
knoel IBM x3550 M4
Pass pass
Pass pass
Pass pass
knoel Lenovo T500
Fail fail [1]
[2]
  1. ↑ RHBZ #968062
  2. ↑ Installed F19 Beta from DVD. Couldn't create a bridge. No libvirtd.log file.
mrezanin HP Z400
Pass pass
[1]
Pass pass
Pass pass
Pass pass
  1. ↑ Tested with RHEL6/RHEL7 guest
lersek HP Z400
Pass pass
[long 1]
Warning warn
[long 2]
Pass pass
[1]
Fail fail
[long 3]
  1. ↑ works fine
tassadar Lenovo T420s (Intel i5-2540M)
Pass pass
[1]
Warning warn [2] [3] [4]
[5]
Warning warn
[6]
Pass pass
Pass pass
Pass pass
[7]
Fail fail
[long 4]
  1. ↑ Everything else in the cast case works as expected.
  2. ↑ RHBZ #965101
  3. ↑ RHBZ #967800
  4. ↑ RHBZ #967740
  5. ↑ Tested on Fedora 19 x86_64 host.
  6. ↑ virsh console fails: Active console session exists for this domain
  7. ↑ I tested only booting LIVE.iso in the nested VM
ignatenkobrain i7-3520m (Lenovo ThinkPad X230)
Pass pass [1]
[2]
Pass pass
[3]
Fail fail
[4]
Fail fail
[5]
Pass pass [6]
[7]
Pass pass
[8]
Fail fail
[9]
  1. ↑ RHBZ #967780
  2. ↑ bad performance in virt-install (network boot)
  3. ↑ need press enter to load form login
  4. ↑ Failed. Try again? [y,n,f,?]: error: XML error: unknown target type 'model' specified for character device
  5. ↑ it isn't switched off when clicking button
  6. ↑ RHBZ #883556
  7. ↑ one crash. not reproducible. abrt couldn't send bug
  8. ↑ works fine
  9. ↑ Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz
hhuang Lenovo T500
Pass pass
[1]
Fail fail
[long 5]
Pass pass
[2]
Pass pass
Pass pass
[3]
Fail fail [4]
[long 6]
  1. ↑ F19 guest from DVD
  2. ↑ Basic guest VM lifecycle operations worked as expected.
  3. ↑ USB drive works correctly in the guest. Add and remove USB drive via the virt-manager work correctly as expected.
  4. ↑ RHBZ #967914
JustinClift Dell Inspiron 7720-4578
Pass pass
[long 7]
Warning warn
[long 8]
jakob_lundberg Dell Optiflex 960
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
sagarun HP Desktop - Intel Core2duo
Pass pass
[1]
Warning warn
[2]
Warning warn
[long 9]
Pass pass
[3]
Pass pass
[4]
  1. ↑ FreeBSD 7 works fine!
  2. ↑ Works fine with a RHEL 6 guest - First time i had to restart libvirtd to make it working!
  3. ↑ libguestfs works fine. Opened up a raw disk image and modified the guest's files!
  4. ↑ Start, Stop, Delete works both on RHEL 6 and freebsd7
jasonbrooks Lenovo X220
Warning warn
[long 10]
Fail fail [1]
[2]
Pass pass
Pass pass
[3]
Pass pass
[4]
  1. ↑ RHBZ #967961
  2. ↑ hit this previously reported bug
  3. ↑ Used a usb optical mouse
  4. ↑ I <3 nested kvm!
kashyapc Intel(R) Xeon(R) CPU E5520
Pass pass
[1]
Pass pass
[2]
Pass pass
[3]
  1. ↑ I used an unattended script like this -- https://github.com/kashyapc/virt-scripts/blob/master/create-guest-qcow2.bash
  2. ↑ $ virsh dumpxml nguest-03 | egrep pty -A 4 $ virsh console nguest-03
  3. ↑ Initial tests - https://github.com/kashyapc/nvmx-haswell/tree/master/tests There are always more to be done.
SlowJet Intel G865BGF(3G-PreviewRepo)
Warning warn
[long 11]
fskola Lenovo T410
Pass pass
[1]
Fail fail [2]
Fail fail [3]
Pass pass
[4]
Fail fail
[long 12]
  1. ↑ Installed from remote URL using virt-install.
  2. ↑ RHBZ #967961
  3. ↑ RHBZ #967968
  4. ↑ Yubikey appeared in the guest (lsusb) but didn't work. Mass storage works perfectly.
pschindl Lenovo T520 Intel i7-2620M
Pass pass
Pass pass
[1]
  1. ↑ virsh console can connect only when no other console session exists for the domain

! References |-

New Features

User Hardware virtio-rng Storage migration VFIO References
knoel IBM x3550 M4
Pass pass
[long 13]
mrezanin HP Z400
Pass pass
[1]
  1. ↑ Device visible, reqeust recorded by egd
lersek HP Z400
Pass pass
[1]
  1. ↑ works fine (tested with EGD too)
tassadar Lenovo T420s (Intel i5-2540M)
Pass pass
[1]
  1. ↑ Tested with egd
JustinClift Dell Inspiron 7720-4578
Pass pass
[long 14]
fskola Lenovo T410
Fail fail
[long 15]

Debugging

Long comments

  1. ↑ Probably should file a bunch of bugs but no time for it now. This was the whole process: Host: physical F19 installation (XFCE spin) on my workstation, first installed as Alpha TC5, but upgraded right before testing. Package versions: - kernel-3.9.4-300.fc19.x86_64 - qemu-kvm-1.4.2-2.fc19.x86_64 - seabios-bin-1.7.2-1.fc19.noarch - libvirt-1.0.5.1-1.fc19.x86_64 - virt-viewer-0.5.6-1.fc19.x86_64 - virt-manager-0.10.0-0.4.gitb68faac8.fc19.noarch Guest: followed instructions in <https://fedoraproject.org/wiki/QA:Testcase_Virtualization_URL_Guest_Install>, version "16:32, 28 May 2013". The non-default parameters I used were: - the VCPU count, I set it to 4; - I pre-created the 8GB image file with qemu-img, format qcow2; - RAM set to 4096 MB. Auto-recognition in virt manager reports Fedora 18 for <http://download.fedoraproject.org/pub/fedora/linux/development/19/x86_64/os/>. Problem #1: pixel garbage visible even with Cirrus + VNC, <https://bugzilla.redhat.com/show_bug.cgi?id=948717>. Maybe important: the virt-manager / virt-viewer windows are X11-forwarded to my RHEL-6 laptop over ssh. Problem #2: when trying to make a screenshot about the pixel garbage, using virt-manager's function, the file selection dialog comes up, but no file is written. Problem #3: when trying to make the same with virt-viewer, the results are worse: we don't even reach the file selection dialog, and virt-viewer seems to hang (doesn't refresh shadowed and redisplayed areas of the window). Took a screenshot finally using "gnome-screenshot" on my RHEL-6 laptop. Problem #4: when entering the root password, I specified "redhat". The warning message says that the password is weak (OK so far), and that it contains the user name in some form (which is incorrect). Pixel garbage resurfaces in installed guest. After reboot: Problem #5: Clicking the Shut Down button in the virt-manager guest window seems to suspend the guest only (the virt-manager main window says Suspended), but it cannot be woken / restarted from either window. Powering down the VM from the inside (using the GNOME 3 button) hangs virt-manager with keyboard grabbed. (Restarting virt-manager works OK, and the guest is actually shut off.)
  2. ↑ 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 test fails with error: operation failed: Active console session exists for this domain
  3. ↑ 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).
  4. ↑ 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)
  5. ↑ The very first reboot after the guest install, there are boot messages on the console. Then the console activities stopped. No login prompt interactions on the console. However, the console is working correctly after subsequent reqboots. Encountered the above with Fedora 19 Alpha and Beta.
  6. ↑ 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 message "internal error unable to execute QEMU command 'eject': Device drive-ide0-0-1 is locked". Issuing another "Disconnect" operation from the virt-manager will successfully disconnect the CDROM.
  7. ↑ 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.
  8. ↑ 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). Was able to work around this using virsh, where "resume 2" started the guest back up again fine. VMM was able to use the guest fine then. At this point I had to leave for airport.
  9. ↑ Works fine except, On a freshly installed Fedora 19 - Beta TC4 the libvirtd needs to be restarted once. [saga@airplanering-dl freevm]$ sudo service libvirtd status Redirecting to /bin/systemctl status libvirtd.service libvirtd.service - Virtualization daemon Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled) Active: active (running) since Tue 2013-05-28 09:51:09 IST; 2h 2min ago Main PID: 1071 (libvirtd) CGroup: name=systemd:/system/libvirtd.service └─1071 /usr/sbin/libvirtd May 28 09:51:09 airplanering-dl.eglbp.corp.yahoo.com systemd[1]: Started Virtualization daemon. May 28 09:51:16 airplanering-dl.eglbp.corp.yahoo.com libvirtd[1071]: libvirt version: 1.0.5.1, package: 1.fc19 (Fedora Project, 2013-05-19-22:57:15, buildvm-11.phx2.fedoraproject.org) May 28 09:51:16 airplanering-dl.eglbp.corp.yahoo.com libvirtd[1071]: Module /usr/lib64/libvirt/connection-driver/libvirt_driver_xen.so not accessible May 28 09:51:16 airplanering-dl.eglbp.corp.yahoo.com libvirtd[1071]: Module /usr/lib64/libvirt/connection-driver/libvirt_driver_libxl.so not accessible May 28 09:51:16 airplanering-dl.eglbp.corp.yahoo.com libvirtd[1071]: Module /usr/lib64/libvirt/connection-driver/libvirt_driver_lxc.so not accessible May 28 09:51:16 airplanering-dl.eglbp.corp.yahoo.com libvirtd[1071]: Module /usr/lib64/libvirt/connection-driver/libvirt_driver_uml.so not accessible May 28 09:51:17 airplanering-dl.eglbp.corp.yahoo.com libvirtd[1071]: open("/var/run/libvirt/network/nwfilter.ltmp"): No such file or directory libguestfs-1.22.0-1.fc19.x86_64 qemu-system-x86-1.4.2-2.fc19.x86_64 virt-install-0.10.0-0.4.gitb68faac8.fc19.noarch libguestfs-1.22.0-1.fc19.x86_64
  10. ↑ 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. Needed to preface virt-install w/ sudo to create the storage. After that, VM created as expected.
  11. ↑ 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). The clone booted and ran. But the shutdown -h now did not work in hurd , neither did any menu shutdown or poweroff, so I had to force power off. I thoht the img had been copied to /var but no, so the selinux tags were worg for Downloads. Also Ctrl-Alt-L to frre mouse is also the host screen saver keys, not good.
  12. ↑ Tried with: * 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) but guest didn't start with "Error starting domain: Unable to read from monitor: Connection reset by peer".
  13. ↑ Messy debug output: 3 clients want entropy 1 clients want entropy do_command HASH(0x1faa480): 0x%02x 2total_bytes_sucked: 5587 0 clients want entropy do_command HASH(0x1faa480): 0x%02x 2total_bytes_sucked: 5651
  14. ↑ Tested both /dev/random and egd.pl in guest after configuring virtio rng. Worked perfectly. egd.pl debug showed client requesting entropy, etc.
  15. ↑ 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".
Retrieved from "https://fedoraproject.org/w/index.php?title=Test_Day:2013-05-28_Virtualization&oldid=399523"