From: Anthony Wright <anthony@overnetdata.com>
To: Todd Deshane <todd.deshane@xen.org>
Cc: xen-devel@lists.xensource.com
Subject: Re: phy disks and vifs timing out in DomU
Date: Thu, 28 Jul 2011 17:00:13 +0100 [thread overview]
Message-ID: <4E31878D.7020508@overnetdata.com> (raw)
In-Reply-To: <CAMrPLWLdY7HwDBaASCGbH=22vOkZCExKh2P_4CPsFs2YZuQ5fg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1653 bytes --]
On 28/07/2011 16:46, Todd Deshane wrote:
> On Thu, Jul 28, 2011 at 3:36 PM, Anthony Wright <anthony@overnetdata.com> wrote:
>> On 28/07/2011 16:01, Todd Deshane wrote:
>>> On Thu, Jul 28, 2011 at 7:24 AM, Anthony Wright <anthony@overnetdata.com> wrote:
>>>> I have a 32 bit 3.0 Dom0 kernel running Xen 4.1. I am trying to run a 32 bit PV DomU with two tap:aio disks, two phy disks & 1 vif. The two tap:aio disks are working fine, but the phy disks and the vif don't work and I get the following error messages from the DomU kernel during boot:
>>>>
>>>> [ 1.783658] Using IPI No-Shortcut mode
>>>> [ 11.880061] XENBUS: Timeout connecting to device: device/vbd/51729 (state 3)
>>>> [ 11.880072] XENBUS: Timeout connecting to device: device/vbd/51745 (state 3)
>>>> [ 11.880079] XENBUS: Timeout connecting to device: device/vif/0 (state 0)
>>>> [ 11.880146] md: Waiting for all devices to be available before autodetect
>>>>
>>>> The DomU VM runs linux version 2.6.30.1 and has worked perfectly on other systems running a 2.6.18 kernel under Xen 3.4.
>>>>
>>>> Any ideas?
>>>>
>>> You should post your domU config file. Maybe the problem is some
>>> syntax change from Xen 3.4 to Xen 4.1 or from 2.6.18 kernel to 3.0
>>> kernel.
>>>
>>> Thanks,
>>> Todd
>> I've attached the Dom0 & the DomU kernel configs. Dom0 is running linux
>> 3.0, DomU is running linux 2.6.30.1.
> I meant the domU guest configuration file (the xm/xl one). I meant
> that you might be specifying the disk line incorrectly.
I've attached the startup config. I've tried more RAM, but that doesn't
help, and I can't find anything useful in the xen logs.
thanks,
Anthony.
[-- Attachment #2: xen-startup --]
[-- Type: text/plain, Size: 625 bytes --]
name = '1-2'
kernel = '/workspace/agent/appliances/XenFileServer-3.18/kernel'
disk = [
'tap:aio:/workspace/agent/appliances/XenFileServer-3.18/rootfs,xvda1,r'
,'tap:aio:/var/agent/running/1/sysconfig,xvda2,r'
,'phy:/dev/Master/Workspace-1,xvdb1,w'
,'phy:/dev/Master/Filesystem,xvdc1,w'
]
pci = [
]
root = '/dev/xvda1'
memory = 128
vif = [ 'bridge=br-internal,mac=02:95:8a:d7:d0:48' ]
vcpus = 1
extras = ''
on_poweroff = 'destroy'
on_reboot = 'destroy'
on_crash = 'destroy'
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-07-28 16:00 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <29902981.10.1311837224851.JavaMail.root@zimbra.overnetdata.com>
2011-07-28 7:24 ` phy disks and vifs timing out in DomU Anthony Wright
2011-07-28 15:01 ` Todd Deshane
2011-07-28 15:36 ` Anthony Wright
2011-07-28 15:46 ` Todd Deshane
2011-07-28 16:00 ` Anthony Wright [this message]
2011-07-29 15:55 ` Konrad Rzeszutek Wilk
2011-07-29 18:40 ` Anthony Wright
2011-07-29 20:01 ` Konrad Rzeszutek Wilk
2011-07-30 17:05 ` Anthony Wright
2011-08-01 11:03 ` Anthony Wright
2011-07-28 16:28 ` Ian Campbell
2011-07-29 7:53 ` Kernel bug from 3.0 (was phy disks and vifs timing out in DomU) Anthony Wright
2011-08-03 15:28 ` Konrad Rzeszutek Wilk
2011-08-09 16:35 ` Konrad Rzeszutek Wilk
2011-08-19 10:22 ` Anthony Wright
2011-08-19 12:56 ` Konrad Rzeszutek Wilk
2011-08-22 11:02 ` Anthony Wright
2011-08-25 20:31 ` Anthony Wright
2011-08-26 14:26 ` Konrad Rzeszutek Wilk
2011-08-26 14:44 ` Konrad Rzeszutek Wilk
2011-08-29 12:13 ` Anthony Wright
2011-08-31 16:58 ` David Vrabel
2011-08-31 17:07 ` Konrad Rzeszutek Wilk
2011-09-01 7:42 ` Ian Campbell
2011-09-01 14:23 ` Konrad Rzeszutek Wilk
2011-09-01 15:12 ` David Vrabel
2011-09-01 15:37 ` Konrad Rzeszutek Wilk
2011-09-01 15:43 ` Ian Campbell
2011-09-01 16:07 ` Konrad Rzeszutek Wilk
2011-09-07 12:57 ` Anthony Wright
2011-09-07 18:35 ` Konrad Rzeszutek Wilk
2011-09-01 15:12 ` Ian Campbell
2011-09-01 15:38 ` Konrad Rzeszutek Wilk
2011-09-01 15:44 ` Ian Campbell
2011-09-01 17:34 ` Jeremy Fitzhardinge
2011-09-01 19:19 ` Ian Campbell
2011-09-01 17:32 ` Jeremy Fitzhardinge
2011-09-01 19:21 ` Ian Campbell
2011-09-01 20:34 ` Jeremy Fitzhardinge
2011-09-02 7:17 ` Ian Campbell
2011-09-02 20:26 ` Jeremy Fitzhardinge
2011-09-03 10:27 ` Ian Campbell
2011-09-23 12:35 ` Anthony Wright
2011-09-23 12:49 ` David Vrabel
2011-08-29 17:33 ` Anthony Wright
2011-08-25 21:11 ` Anthony Wright
2011-08-26 7:10 ` Sander Eikelenboom
2011-08-26 11:23 ` Pasi Kärkkäinen
2011-08-26 12:16 ` Stefano Stabellini
2011-08-26 12:15 ` Anthony Wright
2011-08-26 12:32 ` Stefano Stabellini
2011-07-29 15:48 ` phy disks and vifs timing out in DomU (only on certain hardware) Anthony Wright
2011-07-29 16:06 ` Konrad Rzeszutek Wilk
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=4E31878D.7020508@overnetdata.com \
--to=anthony@overnetdata.com \
--cc=todd.deshane@xen.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 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).