From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?ISO-8859-1?Q?Rainer_Brinkm=F6ller?= Subject: Error Messages at NetBSD domain halt and shutdown Date: Sat, 28 May 2005 00:37:12 +0200 Message-ID: <4297A118.9060402@web.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org I am running xen (first 2.0.5 now 2.0.6) with NetBSD 3.0_BETA as domain and guest OS. If i execute the command "halt -p" in the unprivileged domain and wait till the last message (... done), nothing happens until i press the enter button. Then i get this output: on the screen ************************ REMOTE CONSOLE EXITED ************************ (54, 'Connection reset by peer') Error: Error connecting to xend, is xend running? $ I press the enter key again and next i get this: Traceback (most recent call last): File "/usr/pkg/sbin/xm", line 9, in ? main.main(sys.argv) File "/usr/pkg/lib/python2.3/site-packages/xen/xm/main.py", line 808, in main $ xm.main(args) File "/usr/pkg/lib/python2.3/site-packages/xen/xm/main.py", line 106, in main self.main_call(args) File "/usr/pkg/lib/python2.3/site-packages/xen/xm/main.py", line 124, in main_ call p.main(args[1:]) File "/usr/pkg/lib/python2.3/site-packages/xen/xm/main.py", line 259, in main create.main(args) File "/usr/pkg/lib/python2.3/site-packages/xen/xm/create.py", line 476, in mai n console_client.connect('localhost', console) File "/usr/pkg/lib/python2.3/site-packages/xen/util/console_client.py", line 8 6, in connect __send_to_sock(sock) File "/usr/pkg/lib/python2.3/site-packages/xen/util/console_client.py", line 4 4, in __send_to_sock data = os.read(0,1024) OSError: [Errno 5] Input/output error Now i get the command prompt i want. I am sure xend is still running because i get a appropriate output by executing 'xm list'. By executing 'xm shutdown -H dom1' from domain0 the same messages appear. Will this be fixed in future release? Is there any workaround which prevent this?