🔗 Virtualization
In this section, we cover discussion on the @et-mgmnt-tools-list, @fedora-xen-list, @libvirt-list and @ovirt-devel-list of Fedora virtualization technologies.
Contributing Writer: Dale Bewley
🔗 Enterprise Management Tools List
This section contains the discussion happening on the et-mgmt-tools list
🔗 Fedora Virtualization List
This section contains the discussion happening on the fedora-virt list.
🔗 New Fedora Virtualization List
On @fedora-xen, Daniel Veillard announced[1] the creation of the new @fedora-virt list.
"As the initiator for [the fedora-xen] list, I must admit I made a mistake 3 years ago, I should have picked a list name agnostic from the hypervisor name. With the current state of Xen in Fedora recent releases it really make sense to try to correct that mistake ... it's never too late ! So http://www.redhat.com/mailman/listinfo/fedora-virt is born, I don't want to mass-subscribe people, especially as I think the current list should survive with its Xen centric focus. You can subscribe directly to the new URL above.
The topic is everything concerning Fedora and virtualization including Xen.
I think the [fedora-xen] list would be a good place for people still using Fedora <= 8 with Xen, but it's just a suggestion :-)"
[1] http://www.redhat.com/archives/fedora-xen/2009-January/msg00014.html
🔗 Fedora Xen List
This section contains the discussion happening on the fedora-xen list.
🔗 Libvirt List
This section contains the discussion happening on the libvir-list.
🔗 Interface Bandwidth Controls
Max Zhen described[1] a goal of enabling
to configure bandwidth rate limits for the network interface of virtual machines, and asked for comments on implementation ideas.
libvirt
[1] http://www.redhat.com/archives/libvir-list/2008-December/msg00644.html
🔗 RHEL 5 Support
Markus Armbruster posted[1] a
"patch series attempts to make
just work on RHEL-5. Right
now it doesn't, mostly because libvirt
libvirt
relies on version number checks
in a couple of places, and RHEL-5's version numbers aren't the whole
truth due to various backports of later stuff." Adding
"I'm not proposing this for immediate commit, as I'm still testing.
But I'd appreciate review: is this the right way to do it?"
[1] http://www.redhat.com/archives/libvir-list/2008-December/msg00629.html
🔗 Choice of Private Network Range
Peter Anvin was[1] "kind of wondering why
defaults to
192.168.122.0/24". Refering to RFCs 2544 and 3330. Peter suggested the following alternative ranges:
libvirt
- 192.0.2.0/24 - reserved as "test and example network"
- 198.18.0.0/15 - reserved as "benchmark test network"
[1] http://www.redhat.com/archives/libvir-list/2008-December/msg00545.html
🔗 Guest-Safe libvirtd Restarts
A restart of libvirtd
will necessarily also restart KVM
virtual machine guests.
Guido Günther sought[1] to rectify this with a submission of several patches.
[1] http://www.redhat.com/archives/libvir-list/2008-December/msg00346.html
[2] http://fedoraproject.org/wiki/FWN/Issue146#Maintaining_VM_State_While_Restarting_libvirtd_Needed
🔗 oVirt Devel List
This section contains the discussion happening on the ovirt-devel list.