On Fri, 2007-03-09 at 19:38 +, Daniel P. Berrange wrote:
> On Fri, Mar 09, 2007 at 07:17:04PM +, Mark McLoughlin wrote:
> > On Fri, 2007-03-09 at 18:52 +, Daniel P. Berrange wrote:
> > > On Fri, Mar 09, 2007 at 04:44:17PM +, Mark McLoughlin wrote:
> >
> > > > Rather you sug
On Fri, Mar 09, 2007 at 07:17:04PM +, Mark McLoughlin wrote:
> On Fri, 2007-03-09 at 18:52 +, Daniel P. Berrange wrote:
> > On Fri, Mar 09, 2007 at 04:44:17PM +, Mark McLoughlin wrote:
>
> > > Rather you suggest that if people want to use bridging, then they
> > > should modify the d
On Fri, 2007-03-09 at 18:52 +, Daniel P. Berrange wrote:
> On Fri, Mar 09, 2007 at 04:44:17PM +, Mark McLoughlin wrote:
> > Rather you suggest that if people want to use bridging, then they
> > should modify the default network XML config by hand and not have the
> > latter option in t
On Fri, Mar 09, 2007 at 04:44:17PM +, Mark McLoughlin wrote:
> On Fri, 2007-03-09 at 14:40 +, Daniel P. Berrange wrote:
> > On Fri, Mar 09, 2007 at 02:27:02PM +, Mark McLoughlin wrote:
> > >
> > > As I said in another mail, the way I'd imagined virt-install working
> > > would be tha
On Fri, 2007-03-09 at 14:57 +, Daniel P. Berrange wrote:
> On Fri, Mar 09, 2007 at 01:52:31PM +, Mark McLoughlin wrote:
> > Another way you could imagine would be for the your router to act as an
> > IPv6 router for a delegated prefix, but I'm not sure how the ISP would
> > communicate
Mark McLoughlin wrote:
Hi Rich,
Minor point from a glance ...
On Fri, 2007-03-09 at 15:22 +, Richard W.M. Jones wrote:
$ virsh -c test:///default capabilities | tidy -xml -i -q
test
I find this a bit weird because I'd guess to be a domain
description, as in
Hi Rich,
Minor point from a glance ...
On Fri, 2007-03-09 at 15:22 +, Richard W.M. Jones wrote:
> $ virsh -c test:///default capabilities | tidy -xml -i -q
>
>
> test
>
I find this a bit weird because I'd guess to be a domain
description, as in the root element
On Fri, 2007-03-09 at 14:40 +, Daniel P. Berrange wrote:
> On Fri, Mar 09, 2007 at 02:27:02PM +, Mark McLoughlin wrote:
> > On Fri, 2007-03-09 at 03:03 +, Daniel P. Berrange wrote:
> >
> > > Anyway, we now have two different syntaxes in the XML for defining what
> > > is more or less t
Richard W.M. Jones wrote:
Daniel P. Berrange wrote:
On Fri, Mar 09, 2007 at 03:22:08PM +, Richard W.M. Jones wrote:
This patch:
* Adds virConnectGetCapabilities which returns an XML description of
the capabilities of the driver or hypervisor under this connection
(see below for more abou
Daniel P. Berrange wrote:
On Fri, Mar 09, 2007 at 03:22:08PM +, Richard W.M. Jones wrote:
This patch:
* Adds virConnectGetCapabilities which returns an XML description of the
capabilities of the driver or hypervisor under this connection (see
below for more about the XML format).
+/
On Fri, Mar 09, 2007 at 04:20:58PM +, Mark McLoughlin wrote:
> On Fri, 2007-03-09 at 14:32 +, Daniel P. Berrange wrote:
> > On Fri, Mar 09, 2007 at 02:27:02PM +, Mark McLoughlin wrote:
> > > On Fri, 2007-03-09 at 03:03 +, Daniel P. Berrange wrote:
>
> > > > For the reverse Xen wil
On Fri, 2007-03-09 at 14:32 +, Daniel P. Berrange wrote:
> On Fri, Mar 09, 2007 at 02:27:02PM +, Mark McLoughlin wrote:
> > On Fri, 2007-03-09 at 03:03 +, Daniel P. Berrange wrote:
> > > For the reverse Xen will tell us what bridge device a
> > > guest is using, and we can reverse
On Fri, 2007-03-09 at 04:44 -0500, Daniel Veillard wrote:
> In general I really prefer restartable daemons especially if the client can
> auto restart them if they are gone missing, it makes users and sysadmins
> life so much easier (and avoid the need to start the daemon at bootup, which
> is y
On Fri, Mar 09, 2007 at 03:22:08PM +, Richard W.M. Jones wrote:
> This patch:
>
> * Adds virConnectGetCapabilities which returns an XML description of the
> capabilities of the driver or hypervisor under this connection (see
> below for more about the XML format).
+/* 32 or 64 bit host?
On Fri, Mar 09, 2007 at 03:22:08PM +, Richard W.M. Jones wrote:
> This patch:
>
> * Adds virConnectGetCapabilities which returns an XML description of the
> capabilities of the driver or hypervisor under this connection (see
> below for more about the XML format).
>
> * Adds virsh capabilit
Daniel Veillard wrote:
[...]
Let me come back with a modified patch which fixes those issues ...
Rich.
--
Emerging Technologies, Red Hat http://et.redhat.com/~rjones/
64 Baker Street, London, W1U 7DF Mobile: +44 7866 314 421
"[Negative numbers] darken the very whole doctrines of the equat
On Fri, Mar 09, 2007 at 03:22:08PM +, Richard W.M. Jones wrote:
> This patch:
>
> * Adds virConnectGetCapabilities which returns an XML description of the
> capabilities of the driver or hypervisor under this connection (see
> below for more about the XML format).
>
> * Adds virsh capabilit
On Fri, 2007-03-09 at 03:32 +, Daniel P. Berrange wrote:
> The UUID for the default network is not included in the example default
> config. So every time you restart the libvirt_qemud we get a randomly
> generated UUID. This isn't really in keeping with the idea of having a
> permanent UID :-)
Daniel P. Berrange wrote:
And the "Stateless autoconfiguration" diagram seems to be exactly what
I think we'd want. Every guest has a MAC addr so that deals with the
lower 64-bits of the adress, but how do we choose the upper 64-bits to
form our 'router advertisment'... Perhaps that's the bit th
This patch:
* Adds virConnectGetCapabilities which returns an XML description of the
capabilities of the driver or hypervisor under this connection (see
below for more about the XML format).
* Adds virsh capabilities command.
* Checks the Python binding works.
Caveats:
* Xen implementation
On Fri, Mar 09, 2007 at 01:52:31PM +, Mark McLoughlin wrote:
> On Wed, 2007-03-07 at 18:15 +, Daniel P. Berrange wrote:
> > Do link-local addreses
> > let the guest communicate with outside world, or is only enablling the
> > VM-to-VM and VM-to-Host communications ?
>
> link-local ad
On Fri, Mar 09, 2007 at 02:29:08PM +, Mark McLoughlin wrote:
> On Fri, 2007-03-09 at 03:17 +, Daniel P. Berrange wrote:
> > Currently we launch dnsmasq with a command line looking like:
> >
> >dnsmasq --keep-in-foreground
> >--bind-interfaces
> >--pid-file
> >
On Fri, Mar 09, 2007 at 02:27:02PM +, Mark McLoughlin wrote:
> On Fri, 2007-03-09 at 03:03 +, Daniel P. Berrange wrote:
>
> > Anyway, we now have two different syntaxes in the XML for defining what
> > is more or less the same thing which is a real PITA for the tools. It
> > is useful to h
On Fri, 2007-03-09 at 03:25 +, Daniel P. Berrange wrote:
> Thinking about later RPM upgrades I think we need to think about whether it
> will be possible to restart the libvirt_qemud while guests & networks are
> running.
If I had time, I'd give some serious thought as to whether we ne
On Fri, Mar 09, 2007 at 02:27:02PM +, Mark McLoughlin wrote:
> On Fri, 2007-03-09 at 03:03 +, Daniel P. Berrange wrote:
> > To improve life for the tools though I'd like to do two things as a high
> > priority
> >
> > - Support managed networks in Xen - we can simply lookup the bridge
>
On Fri, 2007-03-09 at 03:17 +, Daniel P. Berrange wrote:
> Currently we launch dnsmasq with a command line looking like:
>
>dnsmasq --keep-in-foreground
>--bind-interfaces
>--pid-file
>--conf-file
>--except-interface lo
>--liste
On Fri, 2007-03-09 at 03:03 +, Daniel P. Berrange wrote:
> Anyway, we now have two different syntaxes in the XML for defining what
> is more or less the same thing which is a real PITA for the tools. It
> is useful to have the distinct representations - one is for 'managed'
> bridges, and the
On Fri, 2007-03-09 at 01:42 +, Daniel P. Berrange wrote:
> I was about to make use of the new networking APIs in
> virt-manager/virt-install
> when I discovered we don't have any python binding for it. Attached is the
> quickest patch I could write to support it
I've only glanced at i
On Fri, Mar 09, 2007 at 02:02:55PM +, Richard W.M. Jones wrote:
> Richard W.M. Jones wrote:
> >Daniel P. Berrange wrote:
> >>On Fri, Mar 09, 2007 at 10:47:18AM +, Richard W.M. Jones wrote:
> >>>Daniel P. Berrange wrote:
> Thinking about later RPM upgrades I think we need to think about
Richard W.M. Jones wrote:
Daniel P. Berrange wrote:
On Fri, Mar 09, 2007 at 10:47:18AM +, Richard W.M. Jones wrote:
Daniel P. Berrange wrote:
Thinking about later RPM upgrades I think we need to think about
whether it
will be possible to restart the libvirt_qemud while guests &
networks a
On Wed, 2007-03-07 at 18:15 +, Daniel P. Berrange wrote:
> On Tue, Mar 06, 2007 at 09:37:46AM +, Mark McLoughlin wrote:
> > However, with IPv6, the combination of link-local addresses, address
> > auto-configuration and network renumbering should largely eliminate
> > these problems.
>
Daniel P. Berrange wrote:
On Fri, Mar 09, 2007 at 10:47:18AM +, Richard W.M. Jones wrote:
Daniel P. Berrange wrote:
Thinking about later RPM upgrades I think we need to think about whether it
will be possible to restart the libvirt_qemud while guests & networks are
running. There's a couple
On Fri, Mar 09, 2007 at 04:24:34AM -0500, Daniel Veillard wrote:
> On Fri, Mar 09, 2007 at 01:42:29AM +, Daniel P. Berrange wrote:
> > I was about to make use of the new networking APIs in
> > virt-manager/virt-install
> > when I discovered we don't have any python binding for it. Attached is
On Fri, Mar 09, 2007 at 10:47:18AM +, Richard W.M. Jones wrote:
> Daniel P. Berrange wrote:
> >Thinking about later RPM upgrades I think we need to think about whether it
> >will be possible to restart the libvirt_qemud while guests & networks are
> >running. There's a couple of issues:
> >
> >
Daniel P. Berrange wrote:
Thinking about later RPM upgrades I think we need to think about whether it
will be possible to restart the libvirt_qemud while guests & networks are
running. There's a couple of issues:
- We do waitpid() to cleanup qemu & dnsmasq processes when we stop domains
& ne
On Fri, Mar 09, 2007 at 03:25:44AM +, Daniel P. Berrange wrote:
> Thinking about later RPM upgrades I think we need to think about whether it
> will be possible to restart the libvirt_qemud while guests & networks are
> running. There's a couple of issues:
>
> - We do waitpid() to cleanup qem
On Fri, Mar 09, 2007 at 01:42:29AM +, Daniel P. Berrange wrote:
> I was about to make use of the new networking APIs in
> virt-manager/virt-install
> when I discovered we don't have any python binding for it. Attached is the
> quickest patch I could write to support it - I basically copied all
37 matches
Mail list logo
