[Date Prev][Date Next] [Thread Prev][Thread Next]
[fedora-virt] Fedora virt status
- From: Mark McLoughlin <markmc redhat com>
- To: Fedora Virtualization List <fedora-virt redhat com>
- Subject: [fedora-virt] Fedora virt status
- Date: Wed, 25 Feb 2009 21:15:26 +0000
2009-03-03 Feature freeze (6 days)
2009-03-10 Beta Freeze (13 days)
2009-04-14 Final freeze (48 days)
An early report this week because I'm about to disappear for three
weeks. Just before the feature/beta freeze ... nice timing, I know! :-)
Dale Bewley provides a timely reminder that all but one of the F11
virt features have not yet been approved by FESCo:
This weeks Fedora Weekly News is out with another great virtualization
Dan Berrange did some experimentation with making Fedora be able to
sanely handle a tablet pointer without extra configuration and filed
these two bugs:
Add a HAL FDI file for the QEMU tablet device
Default to using the table in python-virtinst for F11 guests:
The idea here is that if we use the tablet pointer with F11 guest by
default it will fix the screwiness with mouse pointers in guests by
using absolute pointer positioning rather than relative positioning.
High Resolution in QEMU
In order to use a higher resolution when running Fedora on qemu/kvm,
we're planning on using the PCI subvendor ID to allow the Xorg cirrus
driver to detect that it's a QEMU emulated card and use 1024x768.
Dan Berrange filed two bugs to track this:
Need to add subsystem vendor ID for kvm/qemu cirrus card
xorg should use 1024x768 for kvm/qemu cirrus card
Several libvirt patch sets were posted to add device dettach,
re-attach and reset support:
Also, Chris Wright posted the patch for "remove_id" in sysfs:
Rumour has it that there may be an upstream release Real Soon Now.
The package reviews for the three new BIOS packages are still in
A bug was filed about headless installs:
KVM Having problem In fedora 10 With no-gui
This prompted a new tip to be added to:
In order to gain access to a serial console during the install,
you can use -x "console=ttyS0". Using a serial console combined
with a VNC install can be very useful for debugging e.g.
<code>--nographics -x "console=ttyS0 vnc".
Perhaps it might make sense for Fedora to use any available serial
console if there is no graphics card? Probably not, though, since you
have no idea whether anything is connected to the other end of the
serial line - on a bare-metal headless server, such a policy would
have us pointlessly driving unused serial lines.
The recently released kvm-84 has hit rawhide. Avi's release
announcement is here:
Tom London reports that qemu-kvm segaults for him when using the SDL
graphics frontend. It appears the issue may be related to SDL's use of
SSE/MMX instructions for bit blitting.
Segfault with kvm-84-1.fc11.x86_64.rpm (SDL related)
libvirt-0.6.0-3.fc10 was pushed to f10-updates-testing this week.
Another issue with libvirt-0.6.0 was reported:
virsh setvcpus hangs with libvirt-0.6.0
This turns out to be a recursive locking bug introduced
by the major threading changes in the release.
Jeff Garzik reports that he sees x86_64 F10 installs hangs at
"installing bootloader" under KVM:
This problem went away when he used 1Gb RAM instead of 512Mb. There is
already another similar, but not identical bug, detailing an issue
with x86_64 installs on 512Mb:
Fabian Deutsch also reports some F11 alpha installer issues under
KVM. The first looks like a generic anaconda bug that also existed in
The second seems to be an anaconda hang during a LiveCD install:
Neither of Fabian's issues look related to known pvmmu related crash
in F11 alpha:
However, Mark Bidewell reported an issue with F11 Alpha installs to
kvm vger and this did turn out to likely be pvmmu related:
Also, James Laska previously reported a kernel oops during install
that may well be yet another pvmmu related issue:
Marcelo's pvmmu fix first made it in 2.6.26-rc5.git, so hopefully the
world has been a better place since then.
Rawhide Rebuild Failures
Matt Domsch rebuilt all of rawhide in mock and found that etherboot,
ruby-libvirt, gnome-applet-vm and xen failed to build:
Michael Young completed the first dom0 build in Koji:
These are really for development and debugging purposes only, as I
am still having problems getting them to boot, but others have
reported more success at getting kernels based on this git
repository working, so you might be lucky.
Michael found an interesting issue where recently built F11 RPMs
wouldn't install on F10 because F11 RPMs use SHA-256 checksums. F10
updates now contains a version of RPM which can handle these
Packages built with rpm-4.6.0-8.fc11 won't install on Fedora 10 x86_64
Some discussion on fedora-kernel-list about the need to fix anaconda
to install kernel-PAE on any machine which supports PAE:
Michael Young also reported a lockdep warning during DomU boot which
Jeremy has fixed in his Dom0 tree:
kernel/lockdep.c warning in xen guest boot dmesg
DOOM-O-METER: 188 open bugs last week, 192 this week. Baa!
virt-manager has hardcoded Requires: PolicyKit-gnome
Does virt-manager really require PolicyKit-gnome? The
KDE spin doesn't ship it.
Looks like PolicyKit was fixed in 0.7 to allow us to
only require PolicyKit itself.
Virtual network won't work until restart
It appears that ip_forward was being set to zero because
the NetworkManager and libvirtd services were incorrectly
The "reporting virt bugs" wiki page has some details on
how to diagnose the problem in future:
[Date Prev][Date Next] [Thread Prev][Thread Next]