From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sander Eikelenboom Subject: Re: No shutdown of domU: xenbus_dev_shutdown: device/console/0: Initialising != Connected, skipping Date: Wed, 17 Nov 2010 12:58:30 +0100 Message-ID: <12657116.20101117125830@eikelenboom.it> References: <1882718364.20101112183010@eikelenboom.it> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <1882718364.20101112183010@eikelenboom.it> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Sander Eikelenboom Cc: Ian , Jeremy Fitzhardinge , "Xen-devel@lists.xensource.com" , Ian Jackson , Keir Fraser List-Id: xen-devel@lists.xenproject.org Hmm .. i haven't received any response, is there anyone who could point me = to the functions involved in communicating the state of the console from "i= nitializing" to "connected" ? That way i could at some additional printk's to find out why the state of d= omU consoles stays "1" instead of "4" in xenstore. -- Sander Friday, November 12, 2010, 6:30:10 PM, you wrote: > I'm encountering the following problem: > When trying to shutdown a PV domU with more than 1 vpcu, the shutdown fai= ls. > The domain keeps running with 100% cpu, and it's still possible to get th= e console of this domU with xm console. > When only 1 vcpu is assigned the domain does shutdown. > Last lines of the PV domU console: > Debian GNU/Linux 5.0 tv hvc0 > INIT: Switching to runlevel: 0 > INIT: Sending processes the TERM signal > Stopping web server: apache2 ... waiting . > Stopping MythTV server: mythbackend No /usr/bin/mythbackend found running= ; none killed. > . > Stopping MTA: exim4_listener. > Stopping rsync daemon: rsync. > Stopping MySQL database server: mysqld. > Saving the system clock. > Cannot access the Hardware Clock via any known method. > Use the --debug option to see the details of our search for an access met= hod. > Stopping enhanced syslogd: rsyslogd. > Asking all remaining processes to terminate...done. > All processes ended within 2 seconds....done. > Deconfiguring network interfaces...done. > Cleaning up ifupdown.... > Deactivating swap...done. > Unmounting local filesystems...done. > Will now halt. > [ 4336.046876] md: stopping all md devices. > [ 4337.047171] xenbus_dev_shutdown: trying shutdown of device/console/0:= Initialising > [ 4337.047194] xenbus_dev_shutdown: device/console/0: Initialising !=3D C= onnected, skipping > [ 4337.047200] xenbus_dev_shutdown: result of shutdown of device/console/= 0: Initialising > [ 4337.047205] xenbus_dev_shutdown: trying shutdown of device/vif/0: Con= nected > [ 4337.110869] xenbus_dev_shutdown: result of shutdown of device/vif/0: C= losed > [ 4337.110883] xenbus_dev_shutdown: trying shutdown of device/vbd/51714:= Connected > [ 4337.161975] xenbus_dev_shutdown: result of shutdown of device/vbd/5171= 4: Closed > [ 4337.161989] xenbus_dev_shutdown: trying shutdown of device/vbd/51713:= Connected > [ 4337.217136] xenbus_dev_shutdown: result of shutdown of device/vbd/5171= 3: Closed > [ 4337.217167] System halted. > But when using xenstore-ls .. i see that for every domain (but 1 and mult= iple vcpu's): > - All devices have state=3D4 > - Except all backend =3D "/local/domain/0/backend/console/*/0" entrie= s, those have state=3D1 > - Although xenstore is saying the state is initializing .. xm console= works perfectly for all domains. > - Perhaps this also explains the high event/0 load in dom0, related t= o tty and xenconsoled ? > DomU kernels vary from debian 2.6.26-xen kernels, to 2.6.37-rc1 mainline. > Xen-unstable-tip and xen-next-2.6.32 dom0 > -- > Sander --=20 Best regards, Sander mailto:linux@eikelenboom.it