From: "Stefan Kuhne" <stefan.kuhne@gmx.net>
To: Wei Liu <wei.liu2@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: linux-3.1.5 and xen-4.0.3
Date: Tue, 03 Jan 2012 23:41:41 +0100 [thread overview]
Message-ID: <4F038425.70905@access.denied> (raw)
In-Reply-To: <1325420264.24422.53.camel@liuw-desktop>
[-- Attachment #1.1: Type: text/plain, Size: 4094 bytes --]
Am 01.01.2012 13:17, schrieb Wei Liu:
> On Sat, 2011-12-31 at 23:29 +0000, Stefan Kuhne wrote:
Hello,
>> Error message:
>>
>> Internal error: Device 769 (vbd) could not be connected. Hotplug scripts
>> not working..
>>
>> Where can i look for a failure?
>
> Xen logs are stored in /var/log/xen by default. And judging from you
> log, you're probably using xend, right? You can start with xend.log .
>
I found in xend.log:
[2012-01-04 00:29:58 2055] DEBUG (XendDomain:464) Adding Domain: 0
[2012-01-04 00:29:58 2055] DEBUG (XendDomain:398) number of vcpus to use
is 0
[2012-01-04 00:29:58 2055] DEBUG (XendDomainInfo:1891)
XendDomainInfo.handleShutdownWatch
[2012-01-04 00:29:58 2055] WARNING (XendAPI:705) API call:
VBD.set_device not found
[2012-01-04 00:29:58 2055] WARNING (XendAPI:705) API call: VBD.set_type
not found
[2012-01-04 00:29:58 2055] WARNING (XendAPI:705) API call:
session.get_all_records not found
[2012-01-04 00:29:58 2055] WARNING (XendAPI:705) API call:
event.get_record not found
[2012-01-04 00:29:58 2055] WARNING (XendAPI:705) API call: event.get_all
not found
[2012-01-04 00:29:58 2055] WARNING (XendAPI:705) API call:
VIF.set_device not found
[2012-01-04 00:29:58 2055] WARNING (XendAPI:705) API call: VIF.set_MAC
not found
[2012-01-04 00:29:58 2055] WARNING (XendAPI:705) API call: VIF.set_MTU
not found
[2012-01-04 00:29:58 2055] WARNING (XendAPI:705) API call: debug.get_all
not found
And:
root@eisxen:~# cat /var/log/xen/xend-debug.log
Xend started at Wed Jan 4 00:29:57 2012.
cat: /sys/bus/scsi/devices/host0/vendor: No such file or directory
cat: /sys/bus/scsi/devices/host0/model: No such file or directory
cat: /sys/bus/scsi/devices/host0/type: No such file or directory
cat: /sys/bus/scsi/devices/host0/rev: No such file or directory
cat: /sys/bus/scsi/devices/host0/scsi_level: No such file or directory
cat: /sys/bus/scsi/devices/host1/vendor: No such file or directory
cat: /sys/bus/scsi/devices/host1/model: No such file or directory
cat: /sys/bus/scsi/devices/host1/type: No such file or directory
cat: /sys/bus/scsi/devices/host1/rev: No such file or directory
cat: /sys/bus/scsi/devices/host1/scsi_level: No such file or directory
cat: /sys/bus/scsi/devices/host2/vendor: No such file or directory
cat: /sys/bus/scsi/devices/host2/model: No such file or directory
cat: /sys/bus/scsi/devices/host2/type: No such file or directory
cat: /sys/bus/scsi/devices/host2/rev: No such file or directory
cat: /sys/bus/scsi/devices/host2/scsi_level: No such file or directory
cat: /sys/bus/scsi/devices/host3/vendor: No such file or directory
cat: /sys/bus/scsi/devices/host3/model: No such file or directory
cat: /sys/bus/scsi/devices/host3/type: No such file or directory
cat: /sys/bus/scsi/devices/host3/rev: No such file or directory
cat: /sys/bus/scsi/devices/host3/scsi_level: No such file or directory
cat: /sys/bus/scsi/devices/host4/vendor: No such file or directory
cat: /sys/bus/scsi/devices/host4/model: No such file or directory
cat: /sys/bus/scsi/devices/host4/type: No such file or directory
cat: /sys/bus/scsi/devices/host4/rev: No such file or directory
cat: /sys/bus/scsi/devices/host4/scsi_level: No such file or directory
cat: /sys/bus/scsi/devices/target0:0:0/vendor: No such file or directory
cat: /sys/bus/scsi/devices/target0:0:0/model: No such file or directory
cat: /sys/bus/scsi/devices/target0:0:0/type: No such file or directory
cat: /sys/bus/scsi/devices/target0:0:0/rev: No such file or directory
cat: /sys/bus/scsi/devices/target0:0:0/scsi_level: No such file or directory
cat: /sys/bus/scsi/devices/target2:0:0/vendor: No such file or directory
cat: /sys/bus/scsi/devices/target2:0:0/model: No such file or directory
cat: /sys/bus/scsi/devices/target2:0:0/type: No such file or directory
cat: /sys/bus/scsi/devices/target2:0:0/rev: No such file or directory
cat: /sys/bus/scsi/devices/target2:0:0/scsi_level: No such file or directory
root@eisxen:~#
I think that doesn't look good.
Thanks. a happy new year and Regards,
Stefan Kuhne
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 552 bytes --]
[-- Attachment #2: 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:[~2012-01-03 22:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-31 23:29 linux-3.1.5 and xen-4.0.3 Stefan Kuhne
2012-01-01 12:17 ` Wei Liu
2012-01-03 22:41 ` Stefan Kuhne [this message]
2012-01-03 17:57 ` 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=4F038425.70905@access.denied \
--to=stefan.kuhne@gmx.net \
--cc=wei.liu2@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 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).