virsh Segfault after creation of guest [with virt-preview repo; F17 guest on F17 host]
by Kashyap Chamarthy
Heya,
I'm just trying to create a minimal(@core) Fedora 17 guest on F17 host, using Virt- preview.
So, once I create the minimal guest (using the attached script), the guest attempts to
reboot, and it's just hung there, I could see that on the serial console. I tried to do a
'virsh list', it's just hung there too, When I tried to look into logs, I see a virsh
segfault:
=> Version Info: <=
I'm using the packages from 'virt-preview' repo
#-----------------------------------------------------------#
[root@moon ~]# uname -r ; arch ; rpm -q qemu-kvm libvirt
3.4.6-2.fc17.x86_64
x86_64
qemu-kvm-1.1.0-9.fc17.x86_64
libvirt-0.9.13-3.fc17.x86_64
[root@moon ~]#
[root@moon qemu]# cat /etc/fedora-release
Fedora release 17 (Beefy Miracle)
[root@moon qemu]#
#-----------------------------------------------------------#
=> From /var/log/messages <=
#-----------------------------------------------------------#
.
.
.
Jul 28 18:26:08 moon libvirtd[18901]: 2012-07-28 12:56:08.066+0000: 18901: error :
virNetSocketReadWire:1006 : End of file while reading data: Input/output error
Jul 28 18:26:15 moon kernel: [296929.644578] virsh[20063]: segfault at 96 ip
00007f4d5100ff31 sp 00007fffd7978688 error 4 in libc-2.15.so[7f4d50f8a000+1ac000]
Jul 28 18:26:15 moon libvirtd[18901]: 2012-07-28 12:56:15.176+0000: 18901: error :
virNetSocketReadWire:1006 : End of file while reading data: Input/output error
.
.
.
.
Jul 28 18:53:09 moon libvirtd[21293]: 2012-07-28 13:23:09.037+0000: 21293: warning :
virDriverLoadModule:72 : Module /usr/lib64/libvirt/connection-d
river/libvirt_driver_libxl.so not accessible
Jul 28 18:53:09 moon libvirtd[21293]: 2012-07-28 13:23:09.656+0000: 21379: error :
qemuMonitorOpenUnix:308 : failed to connect to monitor socket: No such process
.
.
.
Jul 28 18:54:36 moon libvirtd[21293]: 2012-07-28 13:24:36.640+0000: 21293: error :
daemonStreamHandleAbort:622 : stream aborted at client request
#-----------------------------------------------------------#
To avoid this, I have to stop libvirtd service (here, it takes a little while to stop the
service. Then, again start the libvirtd service). Now, I can use virsh, and start the
guest and see the boot progress via serial console.
Just wondering if it's a known issue, before I file a bug.
If needed, I can provide further debugging info by enabling LIBVIRT_DEBUG=1 on the shell
when it hangs. Just let me know.
/kashyap
10 years, 10 months
Bridged Networking - Virtual Environments
by Jorge Fábregas
Hello everyone,
I'm learning about bridged networking and how it is applied to virtual
environments (bypassing all the automation provided by libvirtd etc) .
I have a question regarding ip configuration for the virtual bridge.
Let's say I have a host (my machine) where I want to run 3 VMs bridged
to my home network (thru eth0). I have a DHCP server running on my DSL
router, and I have dhcp enabled on my 3 VMs so they all should get a
lease from the DHCP.
As far as a I know these are the raw steps needed to accomplish this:
1- create br0
2- remove current ip address from eth0
3- enslave eth0 to br0
4- create tap devices
5- attach tap devices to br0
6- assign tap devices to every VM
As you can see I haven't assigned an ip address to the virtual bridge
(br0). Why is it that (on almost any site that I visit with this setup)
they always end up assigning an ip address to br0?
Thanks in advance!
Jorge
10 years, 10 months
Xorg input focus problem with virt-manager guest VNC window
by Chuck Anderson
I just did a yum update and reboot on Fedora 16, and since then I've
been having input focus issues (outside of guests). Whenever I move
the mouse over a virt-manager guest console window (VNC), I can't
right click title bars of windows that are stacked on top of the
virt-manager guest. Additionally, often the input focus gets stuck
such that even after moving the mouse to other areas of the desktop
and other windows, I can't type into them at all, nor click anything.
Cutting and pasting with the left/middle mouse buttons in
gnome-terminal still seems to work, though. The text cursor in
gnome-terminal windows blinks very quickly and erratically while stuck
in this state.
When this happens, I have to mouse back into the virt-manager guest
VNC console and back out again, which usually clears the issue.
I realize this might not be caused by virt-manager itself, but I
thought I'd start here in case others have seen this issue, and also
to learn what virt-manager/VNC might be doing differently to the X
server to trigger this issue vs. other X clients. Many packages were
updated, including:
NVIDIA binary driver (unfortunately required to use the 4 displayport
outputs on the nVidia Quadro NVS 420 card I have)
1:akmod-nvidia-295.59-1.fc16.x86_64
1:kmod-nvidia-295.59-1.fc16.4.x86_64
1:kmod-nvidia-3.3.1-3.fc16.x86_64-295.40-2.fc16.x86_64
1:kmod-nvidia-3.4.5-1.fc16.x86_64-295.59-1.fc16.4.x86_64
1:xorg-x11-drv-nvidia-295.59-1.fc16.x86_64
1:xorg-x11-drv-nvidia-libs-295.59-1.fc16.x86_64
Kernel:
kernel-3.4.5-1.fc16.x86_64
kernel-devel-3.4.5-1.fc16.x86_64
kernel-headers-3.4.5-1.fc16.x86_64
Virt-related:
libvirt-0.9.6.1-1.fc16.x86_64
libvirt-client-0.9.6.1-1.fc16.x86_64
libvirt-python-0.9.6.1-1.fc16.x86_64
python-virtinst-0.600.2-1.fc16.noarch
virt-manager-0.9.3-1.fc16.noarch
virt-manager-common-0.9.3-1.fc16.noarch
I'm also using Gnome 3 in fallback mode.
Thanks.
10 years, 10 months
Fwd: Call for Test Days for Fedora 18
by Richard W.M. Jones
I guess we need to organize some F18 virt test days?
Rich.
----- Forwarded message from Adam Williamson -----
Date: Tue, 17 Jul 2012 11:15:45 -0700
Subject: Call for Test Days for Fedora 18
Hey, folks. It's that time again - time to start thinking about Test
Days for Fedora 18.
For anyone who isn't aware, a Test Day is an event usually focused
around IRC for interaction and a Wiki page for instructions and results,
with the aim being to get a bunch of interested users and developers
together to test a specific feature or area of the distribution. You can
run a Test Day on just about anything for which it would be useful to do
some fairly focused testing in 'real time' with a group of testers; it
doesn't have to be code, for instance we often run Test Days for
l10n/i18n topics. For more information on Test Days, see
https://fedoraproject.org/wiki/QA/Test_Days .
Anyone who wants to can host their own Test Day, or you can request that
the QA group helps you out with organization, or any combination of the
two. To propose a Test Day, just file a ticket in QA trac - full details
are at https://fedoraproject.org/wiki/QA/Test_Days/Create . For
instructions on hosting a Test Day, see
https://fedoraproject.org/wiki/QA/SOP_Test_Day_management .
You can see the schedule at
https://fedoraproject.org/wiki/QA/Fedora_18_test_days . There are many
slots open right now, with the earliest on 2012-08-09 and the latest
2012-11-01. Consider the development schedule, though, in deciding when
you want to run your Test Day - for some topics you may want to avoid
the time before the Alpha release or the time after the feature freeze
or the Final freeze.
We normally aim to schedule Test Days on Thursdays; however, if you want
to run a series of related Test Days, it's often a good idea to do
something like Tuesday / Wednesday / Thursday of the same week (this is
how we usually run the X Test Week, for instance). If all the Thursday
slots fill up but more people want to run Test Days, we will open up
Tuesday slots as overflows. And finally, if you really want to run a
Test Day in a specific timeframe due to the development schedule, but
the Thursday slot for that week is full, we can add a slot on another
day. We're flexible! Just put in your ticket the date or timeframe you'd
like, and we'll figure it out from there.
If you have any questions about the Test Day process, please don't
hesitate to contact me or any other member of the QA team on test@ or in
#fedora-qa on IRC. Thanks!
--
Adam Williamson
----- End forwarded message -----
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://et.redhat.com/~rjones/virt-top
10 years, 10 months
virsh start --console "some-guest" booting options F17 host
by Frank Murphy
Q1:
virsh start --console "some-guest"
How can a different kernel be booted from?
If kernel=0 won't complete boot.
Q2:
On one Guest, cannot enter luks pw.
It shows where to enter it,
just no asterisks.
even though all console=tty*
is in last position on grub2 cmd line.
--
Regards,
Frank
"Jack of all, fubars"
10 years, 10 months
qemu updated to 1.1 and libvirt to 0.9.13 : nothing works!
by Frédéric Grelot
Hi all,
I updated my vm server yesterday with the latest packages from virt-preview : qemu 1.1, libvirt 0.9.13, and virt-manager 0.9.3
Unfortunately, I couldn't connect using virsh anymore (nor using virt-manager). I had the same problem a few days earlier when I forced installation of those packages from rawhide for testing purposes, but I hadn't time to report.
yesterday, I increased the log verbosity, so here it is :
#virsh -d 4 list
erreur :Failed to reconnect to the hypervisor
erreur :pas de connexion valide
erreur :no connection driver available for No connection for URI qemu:///system
erreur :Failed to reconnect to the hypervisor
in /var/log/messages :
with loglevel = 2 :
(libvirtd startup, nothing especially wrong)
Jul 20 21:12:14 vmserver libvirtd[3387]: 2012-07-20 19:12:14.583+0000: 3387: info : libvirt version: 0.9.13, package: 2.fc17 (Fedora Project, 2012-07-20-10:09:35, x86-01.phx2.fedoraproject.org)
Jul 20 21:12:14 vmserver libvirtd[3387]: 2012-07-20 19:12:14.583+0000: 3387: warning : virDriverLoadModule:72 : Module /usr/lib64/libvirt/connection-driver/libvirt_driver_network.so not accessible
Jul 20 21:12:14 vmserver libvirtd[3387]: 2012-07-20 19:12:14.583+0000: 3387: warning : virDriverLoadModule:72 : Module /usr/lib64/libvirt/connection-driver/libvirt_driver_storage.so not accessible
Jul 20 21:12:14 vmserver libvirtd[3387]: 2012-07-20 19:12:14.583+0000: 3387: warning : virDriverLoadModule:72 : Module /usr/lib64/libvirt/connection-driver/libvirt_driver_nodedev.so not accessible
Jul 20 21:12:14 vmserver libvirtd[3387]: 2012-07-20 19:12:14.583+0000: 3387: warning : virDriverLoadModule:72 : Module /usr/lib64/libvirt/connection-driver/libvirt_driver_secret.so not accessible
Jul 20 21:12:14 vmserver libvirtd[3387]: 2012-07-20 19:12:14.583+0000: 3387: warning : virDriverLoadModule:72 : Module /usr/lib64/libvirt/connection-driver/libvirt_driver_nwfilter.so not accessible
Jul 20 21:12:14 vmserver libvirtd[3387]: 2012-07-20 19:12:14.583+0000: 3387: warning : virDriverLoadModule:72 : Module /usr/lib64/libvirt/connection-driver/libvirt_driver_qemu.so not accessible
Jul 20 21:12:14 vmserver libvirtd[3387]: 2012-07-20 19:12:14.583+0000: 3387: warning : virDriverLoadModule:72 : Module /usr/lib64/libvirt/connection-driver/libvirt_driver_lxc.so not accessible
Jul 20 21:12:14 vmserver libvirtd[3387]: 2012-07-20 19:12:14.583+0000: 3387: warning : virDriverLoadModule:72 : Module /usr/lib64/libvirt/connection-driver/libvirt_driver_uml.so not accessible
Jul 20 21:12:14 vmserver libvirtd[3387]: 2012-07-20 19:12:14.583+0000: 3387: warning : virDriverLoadModule:72 : Module /usr/lib64/libvirt/connection-driver/libvirt_driver_xen.so not accessible
Jul 20 21:12:14 vmserver libvirtd[3387]: 2012-07-20 19:12:14.583+0000: 3387: warning : virDriverLoadModule:72 : Module /usr/lib64/libvirt/connection-driver/libvirt_driver_libxl.so not accessible
Jul 20 21:12:14 vmserver libvirtd: Could not find keytab file: /etc/libvirt/krb5.tab: Aucun fichier ou dossier de ce type
(when I try virsh list)
Jul 20 21:12:21 vmserver libvirtd[3387]: 2012-07-20 19:12:21.662+0000: 3395: error : do_open:1174 : no connection driver available for No connection for URI (null)
Jul 20 21:12:21 vmserver libvirtd[3387]: 2012-07-20 19:12:21.663+0000: 3387: error : virNetSocketReadWire:1003 : End of file while reading data: Erreur d'entrée/sortie
Jul 20 21:12:21 vmserver libvirtd[3387]: 2012-07-20 19:12:21.666+0000: 3393: error : do_open:1174 : no connection driver available for No connection for URI (null)
Jul 20 21:12:21 vmserver libvirtd[3387]: 2012-07-20 19:12:21.667+0000: 3387: error : virNetSocketReadWire:1003 : End of file while reading data: Erreur d'entrée/sortie
I also have a log with loglevel=1, but it is far longer... However, the section corresponding to the virsh list is short :
Jul 20 21:03:05 vmserver libvirtd[3133]: 2012-07-20 19:03:05.546+0000: 3140: info : remoteDispatchAuthList:2193 : Bypass polkit auth for privileged client pid:3153,uid:0
Jul 20 21:03:05 vmserver libvirtd[3133]: 2012-07-20 19:03:05.550+0000: 3137: error : do_open:1174 : no connection driver available for No connection for URI qemu:///system
Jul 20 21:03:05 vmserver libvirtd[3133]: 2012-07-20 19:03:05.551+0000: 3133: error : virNetSocketReadWire:1003 : End of file while reading data: Erreur d'entrée/sortie
Jul 20 21:03:05 vmserver libvirtd[3133]: 2012-07-20 19:03:05.553+0000: 3143: info : remoteDispatchAuthList:2193 : Bypass polkit auth for privileged client pid:3153,uid:0
Jul 20 21:03:05 vmserver libvirtd[3133]: 2012-07-20 19:03:05.556+0000: 3140: error : do_open:1174 : no connection driver available for No connection for URI qemu:///system
Jul 20 21:03:05 vmserver libvirtd[3133]: 2012-07-20 19:03:05.557+0000: 3133: error : virNetSocketReadWire:1003 : End of file while reading data: Erreur d'entrée/sortie
I'm not sure why in this latest log, the URI is qemu:///system while it seems to be "null" in the first one... However, none of them worked.
Precision : virsh list was entered in root. By the way, virt-manager (not working either, but I haven't kept the logs) was run by a non-privileged user which is asked a password when connecting.
Currently, I managed to go back to a working state by yum removing qemu*, libvirt* and then "yum install --disablerepo=fedora-virt-preview qemu* libvirt* virt-*" (or similar : I did not really installed all subpackages of libvirt* and virt-*). But if you were to push those packages to the main repos, that'll become problematic...
If necessary, it is quite easy to go back to the non-working state (yum update actually...), so tell me if it's needed for tests.
Frederic.
10 years, 10 months
Different cpu usage between Fedora and SL6 guests
by Orion Poplawski
While staring at top on my SL6 kvm server waiting for it to crash, I noticed
that my idle Fedora kvm guests appear to be consuming between 8-12% cpu while
my idle SL6 guests appear to be consuming between 0.3-2% cpu as shown in the
qemu-kvm processes in top. In fact I have a Fedora 17 instance running now
with nothing but kernel processes and the qemu-kvm process still shows it
using 7-8% cpu.
Does anyone have any insight as to why this would be the case?
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA, Boulder Office FAX: 303-415-9702
3380 Mitchell Lane orion(a)nwra.com
Boulder, CO 80301 http://www.nwra.com
10 years, 10 months
Fedora virt status June 2012
by Cole Robinson
Fere's some status bits about virt happenings in Fedora for last month (and a
bit of July):
Fedora 18
=========
In the next coming month, we will start hitting the first important Fedora 18
dates:
July 27: Feature submission deadline
August 07: Feature freeze (majority of the feature is in fedora)
August 14: Alpha change deadline
Take a look at some of the virt features that Red Hatters are working on for F18:
https://fedoraproject.org/wiki/Features/Syscall_Filters
https://fedoraproject.org/wiki/Features/Virt_Live_Snapshots
https://fedoraproject.org/wiki/Features/Virt_Storage_Motion
https://fedoraproject.org/wiki/Features/Virt_Guest_Suspend_Hibernate
https://fedoraproject.org/wiki/Features/Virt_CPU_Memory_Hotplug
Lot's of cool stuff approaching! The current idea is that the F18 feature
freeze should line up nicely with the QEMU 1.2 feature freeze, so the F18
Alpha release should have lot's of good stuff queued up.
QEMU 1.1 release
================
QEMU 1.1 was released on June 2nd. Highlights from the release announcement:
- Support for passing a DTB on ARM platforms when using -kernel
- Support for PCI emulation on -M pseries on PPC
- KVM support for in-kernel APIC and PIC and Hyper-V support
- A new paravirtual SCSI device (virtio-scsi)
- Image streaming support in the block layer
- A new bridge device that can be used without root privileges
- Guest agent support for Windows
- Restored ARM host support
A much more detailed changelog can be found here:
http://wiki.qemu.org/ChangeLog/1.1
In Fedora, our QEMU package is actually based on the qemu-kvm releases, which
carry a shrinking number of kvm specific patches. qemu-kvm 1.1 was released
on July 2nd, and is currently in rawhide thanks to the quick work of Hans De
Goede and Rich Jones!
Libvirt 0.9.13 release
======================
Libvirt's monthly release also came out on July 2nd and promptly landed in
rawhide. Changelog highlights:
- S390: support for s390(x)
- snapshot: implement new APIs for esx and vbox
- snapshot: new query APIs and many improvements
- virsh: Allow users to reedit rejected XML
- nwfilter: add DHCP snooping
- Enable driver modules in libvirt RPM
- Default to enable driver modules for libvirtd
- storage backend: Add RBD (RADOS Block Device) support
- sVirt support for LXC domains inprovement
Libvirt 0.9.6.1 and 0.9.11.4 maintenance releases
=================================================
Another F17 libvirt maintenance release was done, and a first release for the
F16 version. Both releases fix a number of reported issues, as detailed in the
update report:
https://admin.fedoraproject.org/updates/FEDORA-2012-10098/libvirt-0.9.11....
https://admin.fedoraproject.org/updates/FEDORA-2012-9913/libvirt-0.9.6.1-...
Those updates have both made it to stable, so they are only a yum update away!
Bug stats
==========
Bug count on June 06 2012: 296 (gulp!)
Bug count on July 10 2012: 184 (wooo!)
Dramatic drop was due to a few things:
- F15 going EOL let us close a bunch of bugs. There were still a bunch of F14
bugs lingering around as well, now closed.
- I did a brief sweep of the whole list which turned up a lot of dups, fixed
issues, or abandoned reports
- libvirt stable releases closed out a good number of issues
Breakdown of the stats:
By release:
* Fedora 16 : 82
* Fedora 17 : 80
* Fedora rawhide : 22
By package:
* gnome-boxes : 9
* gtk-vnc : 3
* libguestfs : 5
* libosinfo : 2
* libvirt : 38
* libvirt-cim : 3
* libvirt-sandbox : 3
* netcf : 3
* python-virtinst : 3
* qemu : 57
* spice-gtk : 7
* virt-dmesg : 1
* virt-manager : 15
* virt-v2v : 3
* virt-viewer : 6
* virt-what : 2
* xen : 12
* xorg-x11-drv-cirrus: 2
* xorg-x11-drv-qxl : 10
Bugs of note
============
* https://bugzilla.redhat.com/show_bug.cgi?id=714271
libvirt pinned to single CPU after suspend/resume cycle ->
all VMs running on the same single core
Not fixed in Fedora yet, but the fix is upstream, and heading to us via kernel
stable releases.
https://bugzilla.redhat.com/show_bug.cgi?id=836913
qemu < 1.1 with qcow2 can occasionally cause data loss on shutdown.
Rich put in an heroic effort tracking this down, and determining it's fixed in
qemu 1.1 in rawhide. Still to determine what we need to backport for F17, if
that's an option.
Thanks,
Cole
10 years, 10 months
ANNOUNCE: virt-manager 0.9.2 and virtinst 0.600.2 released
by Cole Robinson
I'm happy to announce two new releases:
virt-manager 0.9.2: virt-manager is a desktop application for managing
KVM and Xen virtual machines via libvirt.
virtinst 0.600.2: virtinst is a collection of command line tools for
provisioning libvirt virtual machines, including virt-install and
virt-clone.
The releases can be downloaded from:
http://virt-manager.org/download.html
The direct download links are:
http://virt-manager.org/download/sources/virt-manager/virt-manager-0.9.2....
http://virt-manager.org/download/sources/virtinst/virtinst-0.600.2.tar.gz
The virt-manager release includes:
- Convert to gtkbuilder: UI can now be edited with modern glade tool
- virt-manager no longer runs on RHEL5, but can manage a remote RHEL5
host
- Option to configure spapr net and disk devices for pseries (Li Zhang)
- Many bug fixes and improvements
The virtinst release includes:
- virt-install: New --memballoon option (Eiichi Tsukata)
- virt-install: Improved qemu/kvm pseries support (Li Zhang, Qing Lin)
- virt-install: Support setting BIOS path using -boot loader=PATH
- Various bug fixes and improvements
Also, unless there are serious snags, the next virt-manager release will have
some major organizational changes: port to GTK3, virtinst will no longer be a
public API, merging virtinst and virt-manager git repos, maybe even converting
to python3. While this will facilitate a ton of future improvements, the
downside is that a much more recent distro will be required to run
virt-manager. More info forthcoming on virt-tools-list
Thanks,
Cole
10 years, 11 months
Upgrading qemu to 1.1 in rawhide
by Hans de Goede
Hi all,
This is just a heads-up that I intend to upgrade qemu to 1.1 for rawhide,
dropping about a 100 spice/usb patches which are upstream now :)
If you do not want me to do this please protest loud and quickly, because
I expect to build the new qemu before the end of today.
Regards.
Hans
10 years, 11 months
