[libvirt] [PATCH 0/5] Add virConnectListDefinedInterfaces/NumOfDefinedInterfaces
by Laine Stump
This patch adds everything but the backend implementation of two APIs
that were requested during review of my patch to add virsh commands
that expose the virInterface* API. These count and list interfaces on
the host that are currently inactive (ie "down").
virConnectListInterfaces and virConnectNumOfInterfaces will list/count
*only* those interfaces that are currently active.
With these functions in place, I'll be able to add the "--inactive"
and "--all" flags to iface-list, as suggested by danpb.
Implementation of the backend of these two functions is waiting for
two things: 1) supporting code in libnetcf, and 2) implementation of
the rest of the backend driver functions for virInterface* (ready in
the wings and waiting to go).
15 years, 5 months
[libvirt] More then one pci device possible with libvirt and pci passthrough?
by Mirko Raasch
Hi,
i want to use more then one pci card in my debian guest.
But when i start the guest, the log says:
libvirtd: 15:44:55.459: warning : pciTrySecondaryBusReset:483 : Other
devices on bus with 0000:05:01.0, not doing bus reset
With "/usr/bin/qemu-system-x86_64 -m 512 -name test -hda
/media/vm/test.img -boot c -vnc :2 -k de -pcidevice host=05:01.0
-pcidevice host=05:02.0 -pcidevice host=05:03.0" there seems to be no
problems.
How can i start my guest with three pci devices passed through and libvirt?
My hostdev section in the xml looks like this:
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain='0x0000' bus='0x05' slot='0x01' function='0x0'/>
</source>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain='0x0000' bus='0x05' slot='0x02' function='0x0'/>
</source>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain='0x0000' bus='0x05' slot='0x03' function='0x0'/>
</source>
</hostdev>
Greetings
Mirko
15 years, 5 months
[libvirt] kernel summit topic - 'containers end-game'
by Serge E. Hallyn
A topic on ksummit agenda is 'containers end-game and how do we
get there'.
So for starters, looking just at application (and system) containers, what do
the libvirt and liblxc projects want to see in kernel support that is currently
missing? Are there specific things that should be done soon to make containers
more useful and usable?
More generally, the topic raises the question... what 'end-games' are there?
A few I can think of off-hand include:
1. resource control
2. lightweight virtual servers
3. (or 2.5) unprivileged containers/jail-on-steroids
(lightweight virtual servers in which you might, just
maybe, almost, be able to give away a root account, at
least as much as you could do so with a kvm/qemu/xen
partition)
4. checkpoint, restart, and migration
For each end-game, what kernel pieces do we think are missing? For instance,
people seem agreed that resource control needs io control :) Containers imo
need a user namespace. I think there are quite a few network namespace
exploiters who require sysfs directory tagging (or some equivalent) to
allow us to migrate physical devices into network namespaces. And
checkpoint/restart needs... checkpoint/restart.
thanks,
-serge
15 years, 5 months
[libvirt] [PATCH] Power Hypervisor Support for libvirt - minimum set of features
by Eduardo Otubo
Hello all,
This is the initial patch for the driver for IBM Power Hypervisors. The
minimum set of features are now implemented: list, list --all and
dumpxml. Here is the Changeset since last PATCH I sent:
* The URI has changed to: phyp://user@[hmc|ivm]/managed_system. If the
system is a HMC+VIOS based, only an HMC authentication will be required.
Commands will be sent to VIOS trough HMC command line. And if the system
is an IVM based, then just provide the username and password for IVM.
* Since the Power Hypervisor has no information about UUID's, I built a
little database (uuid_db) to store and associate LPAR ID's with UUID
randomly generated by the API.
* The command dumpxml is implemented, but there are some informations
missing. Fetching informations like fstab, os type, uptime, IP addr and
so on, will only be available in a future versions of the HMC system.
* The TODO list is now set to implement life cycle functions.
Thanks in advance,
[]'s
--
Eduardo Otubo
Software Engineer
Linux Technology Center
IBM Systems & Technology Group
Mobile: +55 19 8135 0885
otubo(a)linux.vnet.ibm.com
15 years, 5 months
[libvirt] PATCH: 0/3: Run QEMU guests within a CGroup
by Daniel P. Berrange
Recent Linux kernels have a new concept of 'CGroups' which is a way to
group tasks on the system and apply policy to them as a whole. We already
use this in the LXC container driver, to control total memory usage of
things runing within a container.
This patch series is a proof of concept to make use of CGroups in the
QEMU driver. The idea is that we have a 3 level cgroup hierarchy
- Top level; contains the libvirtd daemon itself
- 2nd level: one per libvirt driver, but dos not contain any
processes.
- 3rd level: one per guest VM. Contains the QEMU process
The host admin can do control on the top level and 2nd level to set an
overall system policy. libvirt will then provide APIs / capabilities to
control individual VMs policy.
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
15 years, 5 months
[libvirt] vTPM support in libvirt
by Andreas Sommer
I'm wondering if there will be vTPM support in libvirt in the near
future?! Xen does support it already with the configuration "vtpm =
['instance=1,backend=0']", for example.
So it would be great if the libvirt XML format supported it, too... For
example like this:
<devices>
<vtpm instance="1" backend="xxx" />
</devices>
Both attributes are optional. The backend attribute is a VM ID (on Xen,
only zero for dom0 is supported) and could be implemented as a UUID?!
What do you think? Are there any efforts to introducing that?
Cheers
Andreas
15 years, 5 months
[libvirt] [Patch] Fix network driver not to forget to save <domain/> in network XML file
by Satoru SATOH
It seems that libvirt network driver can understand /network/domain
element but it does not save this configuration into the network
definition XML file correctly (looks completely forgetting about it).
Here is a fix for this problem.
(see also: rhbz#505720)
---
src/network_conf.c | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/src/network_conf.c b/src/network_conf.c
index 1e0cbb8..1b50b84 100644
--- a/src/network_conf.c
+++ b/src/network_conf.c
@@ -592,6 +592,9 @@ char *virNetworkDefFormat(virConnectPtr conn,
def->stp ? "on" : "off",
def->delay);
+ if (def->domain)
+ virBufferVSprintf(&buf, " <domain name='%s'/>\n", def->domain);
+
if (def->ipAddress || def->netmask) {
virBufferAddLit(&buf, " <ip");
--
1.6.3.2
15 years, 5 months
[libvirt] [Patch] Network schema fixes and updates
by Satoru SATOH
This is a patch to make network schema (network.rng) to support some
neat features (/netowrk/domain, //dhcp/host/*).
---
docs/schemas/network.rng | 14 ++++++++++++++
1 files changed, 14 insertions(+), 0 deletions(-)
diff --git a/docs/schemas/network.rng b/docs/schemas/network.rng
index 34c0163..a4281a5 100644
--- a/docs/schemas/network.rng
+++ b/docs/schemas/network.rng
@@ -1,6 +1,7 @@
<!-- A Relax NG schema for the libvirt network XML format -->
<element name="network" xmlns="http://relaxng.org/ns/structure/1.0"
datatypeLibrary="http://www.w3.org/2001/XMLSchema-datatypes">
+ <interleave>
<!-- The name of the network, used to refer to it through the API
and in virsh -->
<element name="name"><text/></element>
@@ -43,6 +44,11 @@
</element>
</optional>
<optional>
+ <element name="domain">
+ <attribute name="name"><text/></attribute>
+ </element>
+ </optional>
+ <optional>
<!-- The IP element sets up NAT'ing and an optional DHCP server
local to the host. -->
<!-- FIXME: address, netmask and the start and end of the ranges
@@ -63,7 +69,15 @@
<attribute name="end"><text/></attribute>
</element>
</zeroOrMore>
+ <zeroOrMore>
+ <element name="host">
+ <attribute name="mac"><text/></attribute>
+ <attribute name="name"><text/></attribute>
+ <attribute name="ip"><text/></attribute>
+ </element>
+ </zeroOrMore>
</element>
</element>
</optional>
+ </interleave>
</element>
--
1.6.3.2
15 years, 5 months
