From: "Daniel P. Berrange" <berrange@redhat.com>
To: John Levon <levon@movementarian.org>
Cc: xen-devel@lists.xensource.com, david.edmondson@sun.com
Subject: Re: [Xen-changelog] [xen-3.1-testing] xend: fix server/netif.py so that it respects type=None.
Date: Fri, 5 Oct 2007 01:38:40 +0100 [thread overview]
Message-ID: <20071005003839.GA15791@redhat.com> (raw)
In-Reply-To: <20071005002124.GM3751@totally.trollied.org.uk>
On Fri, Oct 05, 2007 at 01:21:24AM +0100, John Levon wrote:
> On Thu, Oct 04, 2007 at 08:40:16AM -0700, Xen patchbot-3.1-testing wrote:
>
> > xend: fix server/netif.py so that it respects type=None.
> > Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
> > xen-unstable changeset: 15972:3a799196ff69d3a3d5e4a891c13434aa61ce60a9
> > xen-unstable date: Thu Sep 27 17:44:03 2007 +0100
> >
> > - if not typ:
> > - typ = xoptions.netback_type
> > -
>
> Grumble, this makes xoptions.netback_type now clearly unused. I'm not
> sure whether this breaks us yet, but certainly there's either cleanup
> needed or it needs fixing.
It shouldn't break anything unless it was already broken.
Basically with type=None, then the in-memory VM would be booted with type
of None, but at the same time the VM config would be written out to disk
with type of 'netfront'. You could stop & start the HVM guest many times
and XenD would always use a type of None when configuring qemu/netback.
The moment you restarted XenD (or rebooted the machine), then it would read
the config in from disk & now see type=netfront. So your config which had
been working fine, suddenly changes when XenD is restarted & your qemu
NICs disappear. So if this breaks anything for Solaris, then it must have
been broken all along, because this only changes the config written to disk,
not the in-memory one XenD is actuall using to start off with.
> What does type=None do?
The behaviour is
- type == netfront -> setup netback only
- type == ioemu -> setup qemu-dm only
- type is None -> setup netback & qemu-dm
The latter is the preferred behavour because it means the same VM config works
whether the guest is using the RTL8139 emulated NIC, or PV drivers.
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
next prev parent reply other threads:[~2007-10-05 0:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200710041540.l94FeHjC015059@xenbits.xensource.com>
2007-10-05 0:21 ` [Xen-changelog] [xen-3.1-testing] xend: fix server/netif.py so that it respects type=None John Levon
2007-10-05 0:38 ` Daniel P. Berrange [this message]
2007-10-05 1:22 ` Daniel P. Berrange
2007-10-05 13:41 ` David Edmondson
2007-10-05 14:00 ` Keir Fraser
2007-10-05 14:33 ` David Edmondson
2007-10-05 15:29 ` Daniel P. Berrange
2007-10-05 15:31 ` David Edmondson
2007-10-05 15:56 ` Keir Fraser
2007-10-05 16:06 ` Daniel P. Berrange
2007-10-05 16:09 ` Keir Fraser
2007-10-05 16:17 ` David Edmondson
2007-10-06 6:41 ` Keir Fraser
2007-10-08 8:20 ` David Edmondson
2007-10-05 16:16 ` David Edmondson
2007-10-05 17:30 ` Daniel P. Berrange
2007-10-05 17:36 ` David Edmondson
2007-10-05 17:57 ` Daniel P. Berrange
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071005003839.GA15791@redhat.com \
--to=berrange@redhat.com \
--cc=david.edmondson@sun.com \
--cc=levon@movementarian.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.