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-devel

[Xen-devel] Dom0 reboot when several VM reboot at the same time

To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, xen-users <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Dom0 reboot when several VM reboot at the same time
From: tsk <aixt2006@xxxxxxxxx>
Date: Fri, 25 Jun 2010 11:40:24 +0800
Cc:
Delivery-date: Thu, 24 Jun 2010 20:41:46 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=rKnFMnnUdlYtTq60fOBtMcWAmkgKNt8oq7YkxtBplns=; b=EBJZ487Gx9TN0Sf3j2/AUjrAN8ra9tjXVN+9vl/PZTA9mVOdIHMojMgC7Hc2pJLtSB WHfRrkdKRDuk6JamND0fxf7DlvkUjrFwxiwD1ja4xtEBeK/cWw5VFNPNpgmaXsrOVQeN 2XmtofsAOeNKcdk4LPUgofsC0J8ELH5KzrVik=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=tggt0P1MyJdaCEjn4J0yW3DD+WUOENrLOUMtWpovz6OdwbHEyD9tJe1agMS8f9ln9i +sNTwIBdCuBaHZPRNhKexgDoZ+yxcTMZv4hQZZYa+VbDAeIT7SxQgAmQhEGMajj99lCW eljgalXx0nwRPILmmqEvEODE4V2+dUs2p3rOU=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi folks,

  I met a problem: when 6 VM reboot at the same time, 3:00 morning, the Dom0 reboot it self:
Xen version is 4.0.0, VMs are windows 2003 with redhat pv, they will update and reboot itself every 3:00 AM.

# last
... ...
admin    pts/0        10.247.1.1       Fri Jun 25 03:40 - 04:30  (00:50)    
reboot   system boot  2.6.31.13        Fri Jun 25 11:16          (00:-3)    
admin    pts/0        10.247.1.1       Fri Jun 18 03:30 - 03:31  (00:01)
... ...

/var/log/xen/xend.log:
... ...
[2010-06-25 03:10:41 4409] DEBUG (DevController:139) Waiting for devices vif2.
[2010-06-25 03:10:41 4409] DEBUG (DevController:139) Waiting for devices vif.
[2010-06-25 03:10:41 4409] DEBUG (DevController:144) Waiting for 0.
[2010-06-25 03:10:41 4409] INFO (XendDomainInfo:2150) Domain has shutdown: name=VM-4836078C.1515.21 id=8 reason=reboot.
[2010-06-25 03:10:41 4409] DEBUG (XendDomainInfo:3115) XendDomainInfo.destroy: domid=8
[2010-06-25 03:10:41 4409] INFO (XendDomainInfo:2150) Domain has shutdown: name=VM-4836078C.1515.21 id=8 reason=reboot.
[2010-06-25 03:10:41 4409] DEBUG (XendDomainInfo:1953) XendDomainInfo.handleShutdownWatch
[2010-06-25 03:10:41 4409] DEBUG (DevController:628) hotplugStatusCallback /local/domain/0/backend/vif/26/0/hotplug-status.
[2010-06-25 03:13:36 4401] INFO (SrvDaemon:332) Xend Daemon started
[2010-06-25 03:13:36 4401] INFO (SrvDaemon:336) Xend changeset: unavailable.
... ...



/var/log/messages:
... ...
Jun 25 03:10:41 r21b02004 tapdisk2[16340]: /guest/VM-420A07DA/disk10369/image.vhd: 4
Jun 25 03:10:41 r21b02004 kernel: blktap_ring_open: opening device blktap3
Jun 25 03:10:41 r21b02004 kernel: blktap_ring_open: opened device 3
Jun 25 03:10:41 r21b02004 kernel: blktap_ring_mmap: blktap: mapping pid is 16340
Jun 25 03:10:41 r21b02004 kernel: blktap_validate_params: vhd:/guest/VM-420A07DA/disk10369/image.vhd: capacity: 419430400, sector-size: 512
Jun 25 03:10:41 r21b02004 kernel: blktap_validate_params: vhd:/guest/VM-420A07DA/disk10369/image.vhd: capacity: 419430400, sector-size: 512
Jun 25 03:10:41 r21b02004 kernel: blktap_device_create: minor 3 sectors 419430400 sector-size 512
Jun 25 03:10:41 r21b02004 kernel: blktap_device_create: creation of 252:3: 0
Jun 25 03:10:41 r21b02004 sshd[16414]: Did not receive identification string from 10.247.10.51
Jun 25 03:10:41 r21b02004 kernel: device 001107 entered promiscuous mode
Jun 25 03:10:41 r21b02004 kernel: eth0: port 3(001107) entering forwarding state
Jun 25 11:16:10 r21b02004 syslogd 1.4.1: restart.
... ...


Can anyone give me some tips? Thanks!

tsk

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