From: Stefan Bader <stefan.bader@canonical.com>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Cc: Ian Campbell <ian.campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Xen 4.x / Linux 3.x (dom0 and HVM domU) and NIC handling
Date: Thu, 01 Dec 2011 16:09:38 +0100 [thread overview]
Message-ID: <4ED798B2.1040309@canonical.com> (raw)
Moving to public discussion...
This was found with Xen hypervisor version supporting device unplugging and the
domU kernel having net-/blkfront and pci platform built-in (or as module).
The block device is defined as hda and the NIC type=ioemu (so theoretically
guests without pv support would work, too).
Since both drivers are present, the kernel tries to unplug the emulated devices
and succeeds. The blkfront driver detects the xvda device available in parallel
and is working ok.
However the network interface does not work. There are entries present under
sysfs for the xenbus but trying to bring it up fails with errors. And also there
seems to be no mac address set (all zeros in sysfs).
When the type=ioemu is removed in the configuration, this works.
I have not much more debugging information beyond that, yet. But it sounds a bit
like NICs should behave the same as block devices. So if there is an emulated
device defined there will be an alternate paravirt interface for it and after
unplugging the emulated ones we end up with the pv ones.
Is that something that can be seen with newer Xen versions, too (I am using 4.1.1)?
-Stefan
next reply other threads:[~2011-12-01 15:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 15:09 Stefan Bader [this message]
2011-12-01 16:03 ` Xen 4.x / Linux 3.x (dom0 and HVM domU) and NIC handling Ian Campbell
2011-12-01 17:47 ` Stefan Bader
2011-12-02 10:15 ` Ian Campbell
2011-12-01 18:09 ` Pasi Kärkkäinen
2011-12-02 10:09 ` Ian Campbell
2011-12-02 10:11 ` Stefan Bader
2011-12-02 10:41 ` Pasi Kärkkäinen
2011-12-02 16:36 ` Alex Bligh
2011-12-02 16:40 ` Ian Campbell
2011-12-02 17:16 ` Alex Bligh
2011-12-02 17:42 ` Ian Campbell
2011-12-02 18:32 ` Alex Bligh
2011-12-03 10:44 ` Ian Campbell
2011-12-05 15:03 ` Stefan Bader
2011-12-06 22:35 ` Alex Bligh
2011-12-05 14:55 ` Stefan Bader
2011-12-05 16:10 ` Ian Campbell
2011-12-06 22:37 ` Alex Bligh
2011-12-06 22:32 ` Alex Bligh
2011-12-02 21:49 ` Pasi Kärkkäinen
2011-12-05 14:33 ` Stefan Bader
2011-12-05 14:39 ` Stefano Stabellini
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=4ED798B2.1040309@canonical.com \
--to=stefan.bader@canonical.com \
--cc=ian.campbell@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--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.