xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: David Erickson <halcyon1981@gmail.com>
Cc: Anthony Perard <anthony.perard@citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	jacek burghardt <jaceksburghardt@gmail.com>,
	Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: LSI SAS2008 Option Rom Failure
Date: Thu, 2 Aug 2012 08:45:20 +0100	[thread overview]
Message-ID: <1343893520.7571.58.camel@dagon.hellion.org.uk> (raw)
In-Reply-To: <CANKx4w9AUuAUWtnW59NL7az8VJ-jLJn984hMqvGVwTEfVAvs1A@mail.gmail.com>

On Wed, 2012-08-01 at 18:52 +0100, David Erickson wrote:
> my assumption is this is because of the error
> in xen-hotplug.log: "RTNETLINK answers: Operation not supported",

That's a benign warning AFAIK.

> and here is my ifconfig while ubuntu is booted (without VMs it doesn't
> have the vifs):

This all looks fine. I think you need to be investigating the network
configuration inside the guest. Does the eth* device exist, is it
configured etc

In your Ubuntu boot log I see:
        [    0.000000] Hypervisor detected: Xen HVM
        [    0.000000] Xen version 4.2.
        [    0.000000] Xen Platform PCI: I/O protocol version 1
        [    0.000000] Netfront and the Xen platform PCI driver have been compiled for this kernel: unplug emulated NICs.
        [    0.000000] Blkfront and the Xen platform PCI driver have been compiled for this kernel: unplug emulated disks.

which means you will need the xen-netfront driver to be loaded, I don't
see any logs to that effect. What does lsmod say? What about "ifconfig
-a". Does the driver even exist on the live cd under /lib/modules
somewhere?

It's a bit odd that you still have vifX.Y-emu in dom0 given that the
emulated device is supposed to have been unplugged. I wonder if that is
a (separate) bug with emu device unplug. Which qemu was this again?

If you added xen_emul_unplug=never to your guest command line then you
would avoid this unplug and you should have an emulated NIC available
instead.

Ian.

  reply	other threads:[~2012-08-02  7:45 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-18 21:02 LSI SAS2008 Option Rom Failure ivo
2012-07-18 23:52 ` David Erickson
2012-07-19  0:18   ` David Erickson
2012-07-19  0:24     ` ivo
2012-07-19  0:56       ` David Erickson
2012-07-19  1:02         ` David Erickson
     [not found]           ` <CAHyyzzTMX4wcg+DNEL91dWmo0R-6oGJLNH5O50bSUeHkmTWAwQ@mail.gmail.com>
2012-07-19  3:56             ` David Erickson
2012-07-19  7:22               ` Ian Campbell
2012-07-19 10:57                 ` Anthony PERARD
2012-07-19 11:07                   ` Ian Campbell
2012-07-19 11:31                     ` Anthony PERARD
2012-07-19 11:38                       ` Ian Campbell
2012-07-19 11:44                         ` Anthony PERARD
2012-07-19 11:48                           ` Ian Campbell
2012-07-19 11:48                         ` Stefano Stabellini
2012-07-19 11:59                           ` Ian Campbell
2012-07-19 12:00                 ` Stefano Stabellini
2012-07-19 15:27                   ` David Erickson
2012-07-31  7:35                     ` David Erickson
2012-07-31  9:04                       ` Ian Campbell
2012-07-31  9:35                         ` Jan Beulich
2012-07-31  9:41                           ` Ian Campbell
2012-07-31  9:47                             ` Jan Beulich
2012-07-31 10:08                               ` Anthony PERARD
2012-07-31 15:32                             ` David Erickson
2012-07-31 10:16                           ` Stefano Stabellini
2012-07-31 15:28                         ` David Erickson
2012-07-31 15:35                           ` Ian Campbell
2012-07-31 16:12                             ` David Erickson
2012-07-31 11:39                       ` Stefano Stabellini
2012-07-31 16:05                         ` David Erickson
2012-08-01 11:13                           ` Stefano Stabellini
2012-08-01 17:52                             ` David Erickson
2012-08-02  7:45                               ` Ian Campbell [this message]
2012-08-02 16:24                                 ` David Erickson
2012-08-02 16:45                                   ` Ian Campbell
2012-08-02 17:10                                     ` David Erickson
2012-08-02 17:12                                       ` David Erickson
2012-08-02 18:39                                         ` Ian Campbell
2012-08-02 17:38                               ` David Erickson
2012-08-03 16:50                                 ` David Erickson
2012-08-06 10:23                                   ` Stefano Stabellini
2012-07-19  0:18   ` ivo
  -- strict thread matches above, loose matches on Subject: below --
2012-07-18  9:47 David Erickson
2012-07-18  9:59 ` Ian Campbell
2012-07-18 17:55   ` David Erickson
2012-07-18 18:19     ` David Erickson
2012-07-18 19:14       ` David Erickson
2012-07-18 20:13         ` James Regan

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=1343893520.7571.58.camel@dagon.hellion.org.uk \
    --to=ian.campbell@citrix.com \
    --cc=Stefano.Stabellini@eu.citrix.com \
    --cc=anthony.perard@citrix.com \
    --cc=halcyon1981@gmail.com \
    --cc=jaceksburghardt@gmail.com \
    --cc=xen-devel@lists.xen.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).