Xen devel - Dec 2011 - linux-3.1.5 and xen-4.0.3

Hello,

I try to run xen-4.0.3 (and 4.0.2) with linux-3.1.5.
I''ve all beckends and frontends build in kernel, but the system
can''t
bring up vif and vbd devices.

Error message:

Internal error: Device 769 (vbd) could not be connected. Hotplug scripts
not working..

Where can i look for a failure?

Regards,
Stefan Kuhne



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

On Sat, 2011-12-31 at 23:29 +0000, Stefan Kuhne wrote:
> Hello,
> 
> I try to run xen-4.0.3 (and 4.0.2) with linux-3.1.5.
> I''ve all beckends and frontends build in kernel, but the system
can''t
> bring up vif and vbd devices.
> 
> 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 .


Wei.

On Sun, Jan 01, 2012 at 12:29:57AM +0100, Stefan Kuhne
wrote:
> Hello,
> 
> I try to run xen-4.0.3 (and 4.0.2) with linux-3.1.5.
What is the distro?
> I''ve all beckends and frontends build in kernel, but the system
can''t
> bring up vif and vbd devices.
> 
> Error message:
> 
> Internal error: Device 769 (vbd) could not be connected. Hotplug scripts
> not working..
> 
> Where can i look for a failure?
> 
> Regards,
> Stefan Kuhne
> 

> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

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



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel