WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 		  
Home Products Support Community News
 
   
 

xen-users

[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: [Xen-users] block-attach crashes domU

from [Tracy Reed] [Permanent Link][Original]
To: Pasi Kärkkäinen <pasik@xxxxxx>
Subject: Re: [Xen-users] block-attach crashes domU
From: Tracy Reed <treed@xxxxxxxxxxxxxxx>
Date: Fri, 22 Jan 2010 13:05:32 -0800
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 22 Jan 2010 13:06:21 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100122080018.GL2861@xxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <20100122062126.GV8056@xxxxxxxxxxxxx> <20100122080018.GL2861@xxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.20 (2009-06-14) 
On Fri, Jan 22, 2010 at 10:00:18AM +0200, Pasi Kärkkäinen spake thusly:
> Does it work if you attach some local LVM volume or file image (non-AOE) as 
> xvdd? 
> 
> Do you get errors in dom0 "dmesg"? How about dom0 /var/log/messages? 
> Do you get errors in dom0 "xm log" ? How about "xm dmesg"?

Nothing in dom0 dmesg or /var/log/messages

xm dmesg contains many things like:

(XEN) mm.c:625:d172 Non-privileged (172) attempt to map I/O space
000000f0
(XEN) mm.c:625:d53 Non-privileged (53) attempt to map I/O space
000000f0
(XEN) mm.c:625:d72 Non-privileged (72) attempt to map I/O space
000000f0
(XEN) mm.c:625:d90 Non-privileged (90) attempt to map I/O space
000000f0
(XEN) mm.c:625:d172 Non-privileged (172) attempt to map I/O space
000000f0

Not sure if this indicates a problem or is related to my current
problem or not. Hard to tell since it isn't time-stamped.

In xm log I see things like:

[2010-01-21 21:51:30 xend 8993] INFO (image:137) buildDomain os=linux
dom=178 vc
pus=4
[2010-01-21 21:51:30 xend 8993] DEBUG (image:206) domid          = 178
[2010-01-21 21:51:30 xend 8993] DEBUG (image:207) memsize        =
2048
[2010-01-21 21:51:30 xend 8993] DEBUG (image:208) image          =
/var/lib/xen/
boot_kernel.CkgrHX
[2010-01-21 21:51:30 xend 8993] DEBUG (image:209) store_evtchn   = 1
[2010-01-21 21:51:30 xend 8993] DEBUG (image:210) console_evtchn = 2
[2010-01-21 21:51:30 xend 8993] DEBUG (image:211) cmdline        =  ro
root=/dev
/md0 console=xvc0
[2010-01-21 21:51:30 xend 8993] DEBUG (image:212) ramdisk        =
/var/lib/xen/
boot_ramdisk.UfCwIK
[2010-01-21 21:51:30 xend 8993] DEBUG (image:213) vcpus          = 4
[2010-01-21 21:51:30 xend 8993] DEBUG (image:214) features       = 
[2010-01-21 21:51:30 xend 8993] DEBUG (blkif:27) exception looking up
device num
ber for xvda: [Errno 2] No such file or directory: \047/dev/xvda\047
[2010-01-21 21:51:30 xend 8993] DEBUG (DevController:110)
DevController: writing
 {\047virtual-device\047: \04751712\047, \047device-type\047:
 \047disk\047, \047
protocol\047: \047x86_64-abi\047, \047backend-id\047: \0470\047,
\047state\047: 
\0471\047, \047backend\047:
\047/local/domain/0/backend/vbd/178/51712\047} to /l
ocal/domain/178/device/vbd/51712.
[2010-01-21 21:51:30 xend 8993] DEBUG (DevController:112)
DevController: writing
 {\047domain\047: \047db2\047, \047frontend\047:
 \047/local/domain/178/device/vb
d/51712\047, \047format\047: \047raw\047, \047dev\047: \047xvda\047,
\047state\0
47: \0471\047, \047params\047: \047/dev/etherd/e1.12\047,
\047mode\047: \047w\04
7, \047online\047: \0471\047, \047frontend-id\047: \047178\047,
\047type\047: \0
47phy\047} to /local/domain/0/backend/vbd/178/51712.
[2010-01-21 21:51:30 xend 8993] DEBUG (blkif:27) exception looking up
device num
ber for xvdb: [Errno 2] No such file or directory: \047/dev/xvdb\047
[2010-01-21 21:51:30 xend 8993] DEBUG (DevController:110)
DevController: writing
 {\047virtual-device\047: \04751728\047, \047device-type\047:
 \047disk\047, \047
protocol\047: \047x86_64-abi\047, \047backend-id\047: \0470\047,
\047state\047: 
\0471\047, \047backend\047:
\047/local/domain/0/backend/vbd/178/51728\047} to /l
ocal/domain/178/device/vbd/51728.
[2010-01-21 21:51:30 xend 8993] DEBUG (DevController:112)
DevController: writing
 {\047domain\047: \047db2\047, \047frontend\047:
 \047/local/domain/178/device/vb
d/51728\047, \047format\047: \047raw\047, \047dev\047: \047xvdb\047,
\047state\0
47: \0471\047, \047params\047: \047/dev/etherd/e2.12\047,
\047mode\047: \047w\04
7, \047online\047: \0471\047, \047frontend-id\047: \047178\047,
\047type\047: \0
47phy\047} to /local/domain/0/backend/vbd/178/51728.
[2010-01-21 21:51:30 xend 8993] DEBUG (blkif:27) exception looking up
device num
ber for xvdc: [Errno 2] No such file or directory: \047/dev/xvdc\047

and also:

[2010-01-21 21:51:06 xend 8993] DEBUG (DevController:496)
hotplugStatusCallback 
/local/domain/0/backend/vif/177/0/hotplug-status.
[2010-01-21 21:51:06 xend 8993] DEBUG (DevController:510)
hotplugStatusCallback 
1.
[2010-01-21 21:51:06 xend 8993] DEBUG (DevController:154) Waiting for
devices us
b.
[2010-01-21 21:51:06 xend 8993] DEBUG (DevController:154) Waiting for
devices vb
d.
[2010-01-21 21:51:06 xend 8993] DEBUG (DevController:160) Waiting for
51712.
[2010-01-21 21:51:06 xend 8993] DEBUG (DevController:496)
hotplugStatusCallback 
/local/domain/0/backend/vbd/177/51712/hotplug-status.
[2010-01-21 21:51:07 xend 8993] DEBUG (DevController:496)
hotplugStatusCallback 
/local/domain/0/backend/vbd/177/51712/hotplug-status.
[2010-01-21 21:51:07 xend 8993] DEBUG (DevController:510)
hotplugStatusCallback 
1.
[2010-01-21 21:51:07 xend 8993] DEBUG (DevController:160) Waiting for
51728.
[2010-01-21 21:51:07 xend 8993] DEBUG (DevController:496)
hotplugStatusCallback 
/local/domain/0/backend/vbd/177/51728/hotplug-status.
[2010-01-21 21:51:07 xend 8993] DEBUG (DevController:496)
hotplugStatusCallback 
/local/domain/0/backend/vbd/177/51728/hotplug-status.
[2010-01-21 21:51:07 xend 8993] DEBUG (DevController:510)
hotplugStatusCallback 
1.
[2010-01-21 21:51:07 xend 8993] DEBUG (DevController:160) Waiting for
51744.
[2010-01-21 21:51:07 xend 8993] DEBUG (DevController:496)
hotplugStatusCallback 
/local/domain/0/backend/vbd/177/51744/hotplug-status.
[2010-01-21 21:51:07 xend 8993] DEBUG (DevController:496)
hotplugStatusCallback 
/local/domain/0/backend/vbd/177/51744/hotplug-status.
[2010-01-21 21:51:07 xend 8993] DEBUG (DevController:510)
hotplugStatusCallback 
1.
[2010-01-21 21:51:07 xend 8993] DEBUG (DevController:160) Waiting for
0.
[2010-01-21 21:51:07 xend 8993] DEBUG (DevController:496)
hotplugStatusCallback 
/local/domain/0/backend/vbd/177/0/hotplug-status.
[2010-01-21 21:51:07 xend 8993] DEBUG (DevController:510)
hotplugStatusCallback 
1.
[2010-01-21 21:51:07 xend 8993] DEBUG (DevController:154) Waiting for
devices ir
q.
[2010-01-21 21:51:07 xend 8993] DEBUG (DevController:154) Waiting for
devices vk
bd.
[2010-01-21 21:51:07 xend 8993] DEBUG (DevController:154) Waiting for
devices vf
b.
[2010-01-21 21:51:07 xend 8993] DEBUG (DevController:154) Waiting for
devices pc
i.
[2010-01-21 21:51:07 xend 8993] DEBUG (DevController:154) Waiting for
devices io
ports.
[2010-01-21 21:51:07 xend 8993] DEBUG (DevController:154) Waiting for
devices ta
p.
[2010-01-21 21:51:07 xend 8993] DEBUG (DevController:154) Waiting for
devices vt
pm.
[2010-01-21 21:51:12 xend.XendDomainInfo 8993] WARNING
(XendDomainInfo:965) Doma
in has crashed: name=db2 id=177.
[2010-01-21 21:51:12 xend.XendDomainInfo 8993] DEBUG
(XendDomainInfo:832) Storin
g domain details: {\047console/ring-ref\047: \0475339667\047,
\047console/port\0
47: \0472\047, \047cpu/3/availability\047: \047online\047,
\047name\047: \047db2
\047, \047console/limit\047: \0471048576\047,
\047cpu/2/availability\047: \047on
line\047, \047vm\047:
\047/vm/f253cab5-c3de-c1f7-e735-5d4f0bfcd3ff\047, \047domi
d\047: \047177\047, \047cpu/0/availability\047: \047online\047,
\047memory/targe
t\047: \0472097152\047, \047store/ring-ref\047: \0475973074\047,
\047cpu/1/avail
ability\047: \047online\047, \047store/port\047: \0471\047}
[2010-01-21 21:51:12 xend.XendDomainInfo 8993] ERROR
(XendDomainInfo:1896) VM db
2 restarting too fast (8.055686 seconds since the last restart).
Refusing to re
start to avoid loops.

I'm pretty sure these are related to the crashes I saw. 

-- 
Tracy Reed
http://tracyreed.org

Attachment: pgp7fMzfVuivV.pgp
Description: PGP signature

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  RE: [Xen-users] Extremely poor iSCSI performance, Joseph Coleman
Next by Date:  Re: [Xen-users] x64 hvm linux very slow on a x64 xen host, Matthieu Patou
Previous by Thread:  Re: [Xen-users] block-attach crashes domU, Pasi Kärkkäinen
Next by Thread:  [Xen-users] XCP 0.1.1 xe source code?, Gémes Géza
Indexes:  [Date] [Thread] [Top] [All Lists]
 
   

Copyright , Citrix Systems Inc. All rights reserved. Legal and Privacy