4:09 a.m.
Hi all,
The XML description of a network does not contain information of the
Domains (VMs) plugged into a network. For example, there is a network named
'default' and there are two domains named: domainA and domainB. The Network
XML description of 'default' network cannot tell what domains are plugged
into it (in this scenario: domainA and domainB). What reasons could be
behind this Network XML format convention?
Thanks,
Fawad
10:52 a.m.
On 12/17/2012 05:09 AM, Fawad Khaliq wrote:
Hi all,
The XML description of a network does not contain information of the
Domains (VMs) plugged into a network. For example, there is a network
named 'default' and there are two domains named: domainA and domainB.
The Network XML description of 'default' network cannot tell what
domains are plugged into it (in this scenario: domainA and domainB).
What reasons could be behind this Network XML format convention?
While not as simple to retrieve as it would be if a copy of that
information were saved in each network's status, it is available by
listing all networks, then retrieving the XML for each domain and
looking at all the <interface> elements for each.
11:26 a.m.
On Mon, Dec 17, 2012 at 9:52 PM, Laine Stump <laine(a)laine.org> wrote:
On 12/17/2012 05:09 AM, Fawad Khaliq wrote:
> Hi all,
>
> The XML description of a network does not contain information of the
> Domains (VMs) plugged into a network. For example, there is a network
> named 'default' and there are two domains named: domainA and domainB.
> The Network XML description of 'default' network cannot tell what
> domains are plugged into it (in this scenario: domainA and domainB).
> What reasons could be behind this Network XML format convention?
While not as simple to retrieve as it would be if a copy of that
information were saved in each network's status, it is available by
listing all networks, then retrieving the XML for each domain and
looking at all the <interface> elements for each.
--
libvir-list mailing list
libvir-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
Isnt it similar as to when we want to retrieve the xml of domains on a
local hypervisor... We query to list all functioning domains on a
hypervisor. Then we take their id from the list and get the corresponding
xml files to those ids...
is that right?
--
Regards,
Arslan Waqar.
11:34 a.m.
Thank you Laine. That makes good sense for not including it in the XML.
On Mon, Dec 17, 2012 at 9:52 PM, Laine Stump <laine(a)laine.org> wrote:
On 12/17/2012 05:09 AM, Fawad Khaliq wrote:
> Hi all,
>
> The XML description of a network does not contain information of the
> Domains (VMs) plugged into a network. For example, there is a network
> named 'default' and there are two domains named: domainA and domainB.
> The Network XML description of 'default' network cannot tell what
> domains are plugged into it (in this scenario: domainA and domainB).
> What reasons could be behind this Network XML format convention?
While not as simple to retrieve as it would be if a copy of that
information were saved in each network's status, it is available by
listing all networks, then retrieving the XML for each domain and
looking at all the <interface> elements for each.
--
libvir-list mailing list
libvir-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
4393
days inactive
4393
days old
3 comments
3 participants
participants (3)
-
Arslan Waqar -
Fawad Khaliq -
Laine Stump