From Fedora Project Wiki

< FWN‎ | Beats

(reset for 183)
Line 12: Line 12:
[ et-mgmt-tools list]
[ et-mgmt-tools list]
==== Remote virt-manager VM Wizard ====
==== ====
[[CraigMiskell|Craig Miskell]]
"running {{package|virt-manager}} 0.7.0 on Ubuntu, connecting using SSH to [a remote] {{package|libvirt}} running on Debian Lenny Xen-3.2.1", and when attempting to create a new guest found "no install options are available because:"
* "Network install" is not available unless the connection is local, and
* Local install media and Network boot (PXE) are not available because of the following line in (around line 340):
is_pv = (self.capsguest.os_type == "xen")
[[ColeRobinson|Cole Robinson]] pointed out the latter has been fixed upstream,
and explained the former fails "Because a network install has to fetch a boot kernel and initrd from the URL, and we have no way to tell the remote machine to fetch these locations."
<references />
<references />
Line 30: Line 18:
This section contains the discussion happening on the
This section contains the discussion happening on the
[ fedora-virt list].
[ fedora-virt list].
==== F12 Feature: Host Information ====
[[RichardJones|Richard Jones]]
an RFC for a feature<ref></ref> he's working on for [[Releases/12|Fedora 12]]. 
The feature will "Allow a virtual machine to see information and statistics from the
host operating system."
For example, it will "Allow a virtual machine to look at host information (such as number of
physical, not just virtual CPUs), and statistics like the load on the
[[DanielBerrange|Daniel Berrange]]
that "a core goal of this
hostinfo service is to avoid any use of networking. We don't want to
presume that a guest has a NIC, nor that the host has a configured
NIC on the same LAN as the guest." So this feature will make use of serial
ports to pass queries and responses between the guest and the host.
<references />
==== libguestfs Super-minimized Appliance ====
[[RichardJones|Richard Jones]]
a set of "very experimental" patches to {{package|libguestfs}}
"which allow you to build a so-called 'supermin (super-minimized) appliance'."
Within <code>libguestfs</code>, "The normal appliance is a self-contained Linux operating system, based
on the Fedora/RHEL/CentOS Linux distro.  So it contains a complete
copy of all the libraries and programs needed, like kernel, libc,
bash, coreutils etc etc."
"The supermin appliance removes the kernel and all the executable
libraries and programs from the appliance.  That just leaves a
skeleton of config files and some data files, which is obviously
massively smaller than the normal appliance.  At runtime we rebuild
the appliance on-the-fly from the libraries and programs on the host
(eg. pulling in the real /lib/, the real /bin/bash etc.)"
"The new appliance is a mere 500K, so <code>libguestfs</code> RPMs will be a lot
smaller.  Of course that just means they will have many more
dependencies, so the amount pulled down will be the same or greater."
<references />
==== A guest fish in the pipes ====
[[RichardJones|Richard Jones]]
{{package|libguestfs|guestfish}}. "This patch adds support for pipes to guestfish, so you can pipe output
from a <code>guestfish</code> command through a command on the host.  The canonical
example is:
><fs> hexdump /bin/ls | less
Another example, looking for root backdoors in the password file:
><fs> cat /etc/passwd | awk -F: '$3 == 0 { print }' | grep -v ^root:
Anything right of the first pipe symbol gets passed to the local
shell, thus expansion, redirection and so on work on that."
<references />
=== Libvirt List ===
=== Libvirt List ===
Line 100: Line 23:
[ libvir-list].
[ libvir-list].
==== Safe PCI Device Passthrough ====
==== ====
[[MirkoRaasch|Mirko Raasch]]
"How can i start my guest with three pci devices passed through and {{package|libvirt}}?" Starting <code>qemu</code> by hand appeared to work.
But virsh start produced an error:
libvirtd: 15:44:55.459: warning : pciTrySecondaryBusReset:483 : Other
devices on bus with 0000:05:01.0, not doing bus reset
[[DanielBerrange|Daniel Berrange]]
"what <code>libvirt</code> is complaining about is that there are other devices
in the PCI bus which are not associated with this guest, and thus there
is no way to safely reset the device you are trying to assign, without
endangering the host OS or other guest OS."
Adding "when you launch QEMU manually there is no
checking for whether the PCI devices are in use by other guests,
or by the host OS. So while it may launch QEMU, it is not running
safely, and eg, if your guest  OS does a PCI bus reset it could
kill/harm your host OS."
PCI device passthrough is a new feature<ref></ref> in Fedora 11.
<references />
==== VMware ESX driver status update ====
[[MatthiasBolte|Matthias Bolte]]
continued<ref></ref> work (FWN #177<ref></ref>) to create a VMware ESX driver for <code>libvirt</code>.
Matthias is currently "working on the VMX config to domain XML mapping for
dump/create XML" using the VMware Infrastructure API<ref></ref>.
<references />
<references />

Revision as of 23:35, 1 July 2009


In this section, we cover discussion of Fedora virtualization technologies on the @et-mgmnt-tools-list, @fedora-xen-list, @libvirt-list and @ovirt-devel-list lists.

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.

Libvirt List

This section contains the discussion happening on the libvir-list.