A couple of bugs in the new qemu 1.4.0 package in Rawhide
by Richard W.M. Jones
Firstly the %if condition here doesn't work for me. For some reason
it still wants me to install perl-podlators (which doesn't exist on
Fedora 18):
%if 0%{?fedora} > 18
BuildRequires: perl-podlators
%endif
I don't understand why it doesn't work, since on the same machine:
$ rpm --eval '%{?fedora}'
18
Is "018" treated as an impossible octal number? My suggestion is to
just BR the programs directly. The upstream code seems to need
pod2man, so:
BuildRequires: /usr/bin/pod2man
Secondly, /usr/bin/qemu-kvm is now a script:
$ cat /usr/bin/qemu-kvm
#!/bin/sh
exec /usr/bin/qemu-system-x86 -machine accel=kvm "$@"
The problem is that /usr/bin/qemu-system-x86 doesn't appear to exist.
Did you mean /usr/bin/qemu-system-x86_84, or is there a missing
runtime Requires in the package?
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW
10 years, 7 months
Fedora 18, virt-manager & libguestfs SELinux relabelling problem
by Richard W.M. Jones
I just want to bring everyone's attention this important bug in
Fedora 18. It looks like people are now starting to upgrade to F18
and are hitting this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=912499
In brief, when virt-manager runs, it starts some libguestfs instances
in the background to inspect guests. Starting with Fedora 18 these
use libvirt and because of a bad interaction between libguestfs &
libvirt this causes the guest disks to get [SELinux] relabelled which
suddenly prevents the guests from accessing their own disks.
This will only affect you if SELinux is set to Enforcing.
You may also see the same problem if you use read-only tools on
running guests, such as virt-df, virt-inspector, virt-cat, etc.,
as root.
There are two workarounds possible in the short term:
(1) To continue using libguestfs to inspect disks, ensure the
following environment variable is set everywhere:
export LIBGUESTFS_ATTACH_METHOD=appliance
(eg. by putting that line into /etc/profile.d/local.sh and logging
out).
Note that this disables sVirt protection in libguestfs, even if
SELinux is enabled.
(2) OR do:
yum uninstall python-libguestfs
This will disable the inspection features of virt-manager.
I intend to fix the bug by modifying how it uses libvirt, and to push
an updated libguestfs package to Fedora 18, but that will take a few weeks.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine. Supports Linux and Windows.
http://people.redhat.com/~rjones/virt-df/
10 years, 7 months
Re: [fedora-virt] Network Manager and Routed Mode in Fedora 18?
by Dario Faggioli
(Adding the list back, please, don't drop it :-))
On gio, 2013-02-14 at 06:56 -0600, Dean Hunter wrote:
> On Thu, 2013-02-14 at 00:47 +0100, Dario Faggioli wrote:
> > On mer, 2013-02-13 at 17:13 -0600, Dean Hunter wrote:
> > > Does Network Manager work with libvirt on Fedora 18?
> > >
> > I only have experience with Xen and libvirt on Fedora, but I guess that
> > does not makes much difference when talking about interactions between
> > libvirt and NetworkManager, right?
> >
> > Well, this experience of mine is that, as soon as I install
> > libvirt-daemon-config-network, a bridge called 'virbr0' is automatically
> > created and all my guests can and actually use it by default.
> >
> Thank you for your response. I have checked that
> libvirt-daemon-config-network is installed, but no virtual bridge
> (virbr0 or any other name) has been created.
>
Well, no idea then. I have it, without touching any config file, either
libvirt or NM related, so I never investigated more... Perhaps someone
else can give some more useful information.
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
10 years, 7 months
No SPICE console over remote libvirt
by Ian Pilcher
Is anyone else unable to get a SPICE console over a remote libvirt
(qemu+ssh) connection? I am able to connect and start VMs remotely, but
when I try to display a SPICE console, it just sits there at "Connecting
to graphical console for guest".
Both hosts are fully-updated Fedora 18 (but virt-preview is *not*
enabled), and local SPICE consoles work just fine in virt-manager.
--
========================================================================
Ian Pilcher arequipeno(a)gmail.com
Sometimes there's nothing left to do but crash and burn...or die trying.
========================================================================
10 years, 7 months
Network Manager and Routed Mode in Fedora 18?
by Dean Hunter
All the documentation I have found for building virtual machines using
virt-manager talks about first disabling the new Network Manager and
enabling the old networking service. But all of that documentation is
written against much older version of Fedora. Does Network Manager work
with libvirt on Fedora 18?
I have found the Virtualization Administration Guide in the Fedora
Draft Documentation, but it does not specifically installation. I am
trying to use Fedora 18 to host several virtual machine servers for
LAMP, IPA/Samba, etc. in a very small development network. I need access
to the VM servers from the developers' hosts. This seems to be described
in section 18.5.1, Routed mode of the guide, but the sections that
follow only describe configuring Isolated mode.
10 years, 7 months
sparc?
by Tom Horsley
I see qemu-system-sparc installed in fedora 18, so I'm now
curious:
If I DDed the disk from an old sun workstation we have
could I go into virt-manager and create a new virtual
machine pointing at that disk image and saying it is
a sparc architecture?
Or is it still more complicated than that to get
anything other than x86 architectures to run? (Yes,
I know it would be slow even if it did work :-).
10 years, 7 months
Fedora virt status January 2013
by Cole Robinson
Hi all, here's highlights of Fedora virt ongoings for January:
Fedora 19 Features
==================
The Fedora 19 feature freeze was January 29th, and there are a handful of virt
relevant features:
https://fedoraproject.org/wiki/Features/Virtio_RNG
- paravirt RNG device for VMs
https://fedoraproject.org/wiki/Features/Virt_Storage_Migration
- Migrate a running VM and storage to a new host, no shared storage required
https://fedoraproject.org/wiki/Features/Virt_Device_Failover
- Migrate a guest with an assigned physical device, transparently degrading to
use of an emulated device.
https://fedoraproject.org/wiki/Features/QXLKMSSupport
- KMS support for QXL, gives us plymouth in guests, stepping stone to spice 3D
https://fedoraproject.org/wiki/Features/NetworkManagerBridging
- Native bridge support in NetworkManager, and make it play nice with virt.
https://fedoraproject.org/wiki/Features/oVirtEngine_3.2
- Update to oVirt Engine 3.2
http://fedoraproject.org/wiki/Features/OpenStack_Grizzly
- Openstack Grizzly release
For the curious, these two pages contain all the proposed features:
https://fedoraproject.org/wiki/Category:FeatureAnnounced
https://fedoraproject.org/wiki/Category:FeatureAcceptedF19
As of now there still isn't a Fedora 19 schedule, but my guess is that the GA
release will at least be after May.
Virt Preview now for F18
========================
virt-preview, the optional repo providing latest virt packages from rawhide
for the current stable Fedora release, is now building packages against Fedora
18. F17 support is discontinued. For more info on virt-preview, see:
http://fedoraproject.org/wiki/Virtualization_Preview_Repository
Libvirt 1.0.2 released
======================
Libvirt 1.0.2 was released on January 30. Featured items from the changelog:
* LXC improvements (Daniel P. Berrange)
* S390 architecture improvement (Viktor Mihajlovski)
* Power architecture improvement (Li Zhang)
* large Coverity report cleanups and associated bug fixes (John Ferlan)
* virTypedParams* APIs to helps with those data structures (Jiri Denemark)
libvirt-1.0.2 is in virt-preview and rawhide now, however this release broke
the python bindings, and a fix is still pending:
https://lists.fedoraproject.org/pipermail/virt/2013-February/003576.html
Additionally, there were new libvirt maintenance releases for F16, F17, and
F18 libvirt versions, primarily to fix a nasty CVE. Please update ASAP:
https://admin.fedoraproject.org/updates/libvirt-0.10.2.3-1.fc18
https://admin.fedoraproject.org/updates/libvirt-0.9.11.9-1.fc17
https://admin.fedoraproject.org/updates/libvirt-0.9.6.4-1.fc16
Bug stats
=========
Bug count on Jan 06 2013: 248
Bug count on Feb 03 2013: 264
Not surprisingly, with F18 hitting the streets there's been a sizable uptick
in F18 bugs:
By release:
* Fedora 16 : 36
* Fedora 17 : 96
* Fedora 18 : 105
* Fedora rawhide : 27
However with F16 going EOL this month, that will 'fix' a big handful. Of
course, if anyone out there has any bugs filed against F16 that they are still
hitting on F17 and F18, please change the version soon or they will be mass
closed.
Package breakdown:
By package:
* gnome-boxes : 16
* gtk-vnc : 3
* ipxe : 2
* libcacard : 2
* libguestfs : 2
* libosinfo : 11
* libseccomp : 1
* libvirt : 51
* libvirt-cim : 3
* libvirt-glib : 2
* libvirt-qmf : 1
* libvirt-sandbox : 12
* netcf : 4
* qemu : 77
* spice-gtk : 4
* spice-vdagent : 1
* usbredir : 1
* virt-dmesg : 1
* virt-manager : 24
* virt-v2v : 4
* virt-viewer : 6
* virt-what : 2
* xen : 12
* xorg-x11-drv-cirrus: 4
* xorg-x11-drv-qxl : 18
Bugs of note
============
- https://bugzilla.redhat.com/show_bug.cgi?id=873845
- https://bugzilla.redhat.com/show_bug.cgi?id=892075
Couple common crashes in qemu related to spice, that accumulated quite a few
duplicates. Fixed with current F18 packages as of last week, so make sure
you're up to date!
- https://bugzilla.redhat.com/show_bug.cgi?id=875348
Another spice related crash, this one affecting clients like boxes,
virt-viewer, and virt-manager. There's a known fix, just not pushed yet.
- https://bugzilla.redhat.com/show_bug.cgi?id=810040
fprintd would crash GDM if a VM didn't have a USB bus, as is the default in
hyper-v and xen PV. Had the dubious honor of being the last fix accepted into F18!
Thanks,
Cole
10 years, 7 months
