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

RE: [Xen-users] xentop blocked

To: bruno taranto <btaranto@xxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-users] xentop blocked
From: Maxim Rozin <maxim@xxxxxxxxxxxxxxxxxx>
Date: Wed, 14 Jun 2006 17:16:20 +0200
Delivery-date: Wed, 14 Jun 2006 07:19:10 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1f00da1c0606140646t5bf0beabx23c732bc8fd276c1@xxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcaPwUBk21gvL4ZLSZK5CNzR+RhOPAAA7xFQ
Thread-topic: [Xen-users] xentop blocked

Bruno,

 

As you can see in xm manual, this is what "blocked" state means:

           b - blocked

               The domain is blocked, and not running or runable.  This can

               be caused because the domain is waiting on IO (a traditional

               wait state) or has gone to sleep because there was nothing

               else for it to do.

So "blocked" state is a normal state for a domain and it has nothing to do with the network problem.

 

Have a nice day,

 

Maxim Rozin

BenefIT-technologies

Mobile: +972-54-5409444

Tel: +972-3-9238888

 


From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of bruno taranto
Sent: Wednesday, June 14, 2006 3:47 PM
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] xentop blocked

 

i would like to know why my domU is blocked at xentop monitor.
thats why i can't ping each other?

dcgs0058:/etc/xen# xm list
Name                              ID Mem(MiB) VCPUs State  Time(s)
Domain-0                           0     1894     4 r-----    38.6
basic_debian_sarge                 7       64     1 -b----     9.5

dcgs0058:/etc/xen# xentop
xentop - 10:43:10   Xen 3.0.2-2
2 domains: 1 running, 1 blocked, 0 paused, 0 crashed, 0 dying, 0 shutdown
Mem: 2096512k total, 2033024k used, 63488k free    CPUs: 4 @ 3192MHz
      NAME  STATE   CPU(sec) CPU(%)     MEM(k) MEM(%)  MAXMEM(k) MAXMEM(%) VCPUS NETS NETTX(k) NETRX(k) SSID
basic_debian_sarge --b---          9    0.0      65280    3.1      65536       3.1     1    1        0        0    0
  Domain-0 -----r         38    0.1    1939456   92.5   no limit       n/a     4    8        0        0    0

dom0 ifconfig --------
dcgs0058:/etc/xen# ifconfig
dummy0    Link encap:Ethernet  HWaddr 2E:0F:35:5C:63:F6
          inet addr:192.168.0.1  Bcast:192.168.0.255  Mask: 255.255.255.0
eth0      Link encap:Ethernet  HWaddr 00:13:72:4E:7E:B3
          inet addr:172.28.0.200  Bcast:172.28.0.255  Mask: 255.255.255.0
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
vif7.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet addr:172.28.0.200  Bcast:172.28.255.255  Mask:255.255.255.255
dcgs0058:/etc/xen#
dom0 ifconfig --------
domU ifconfig --------
debian:~# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:16:3E:5D:3C:82
          inet addr:192.168.0.2  Bcast:192.168.0.255   Mask:255.255.255.0
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
debian:~#
domU ifconfig --------

bruno taranto

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>