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

[Xen-bugs] [Bug 256] New: "xm reboot" could not make domU reboot

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 256] New: "xm reboot" could not make domU reboot
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Fri, 23 Sep 2005 05:00:16 +0000
Delivery-date: Fri, 23 Sep 2005 05:00:26 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=256

           Summary: "xm reboot" could not make domU reboot
           Product: Xen
           Version: unstable
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Tools
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: ping.y.yu@xxxxxxxxx


Bug detailed description:
--------------------------
"xm reboot" could not make domU reboot. Instead, domU will shut down.


Reproduce steps:
----------------
(1)servie OS boots
(2)xend start
(3)xm create
(4)xm reboot 



Current result:
----------------
domU shutdown

Expected result:
----------------
domU could reboot


Basic root-causing log:
----------------------
==xend.log====
[2005-09-23 12:51:56 xend] DEBUG (__init__:988) initDomain: cpu=-1 
mem_kb=262144 ssidref=-1 dom=1
[2005-09-23 12:51:56 xend] DEBUG (__init__:988) init_domain> Created domain=1 
name=ExampleDomain1 memory=256
[2005-09-23 12:51:56 xend] INFO (__init__:988) EVENT> xend.domain.create 
['ExampleDomain1', 1]
[2005-09-23 12:51:56 xend] INFO (__init__:988) buildDomain os=linux dom=1 
vcpus=1
[2005-09-23 12:51:56 xend] DEBUG (__init__:988) dom            = 1
[2005-09-23 12:51:56 xend] DEBUG (__init__:988) image          = /boot/vmlinuz-
2.6.12-xenU
[2005-09-23 12:51:56 xend] DEBUG (__init__:988) store_evtchn   = 1
[2005-09-23 12:51:56 xend] DEBUG (__init__:988) console_evtchn = 2
[2005-09-23 12:51:56 xend] DEBUG (__init__:988) cmdline        =  
root=/dev/hda1 ro 4
[2005-09-23 12:51:56 xend] DEBUG (__init__:988) cmdline        =  
root=/dev/hda1 ro 4
[2005-09-23 12:51:56 xend] DEBUG (__init__:988) ramdisk        =
[2005-09-23 12:51:56 xend] DEBUG (__init__:988) flags          = 0
[2005-09-23 12:51:56 xend] DEBUG (__init__:988) vcpus          = 1
[2005-09-23 12:51:57 xend] DEBUG (__init__:988) exception looking up device 
number for hda1: [Errno 2] No such file or 
directory: '/dev/hda1'
[2005-09-23 12:51:57 xend] INFO (__init__:988) EVENT> xend.domain.unpause 
['ExampleDomain1', 1]
[2005-09-23 12:52:35 xend] DEBUG (__init__:988) domain_restart_schedule> 1 
reboot 1
[2005-09-23 12:52:35 xend] INFO (__init__:988) Scheduling restart for domain: 
name=ExampleDomain1 id=1
[2005-09-23 12:52:35 xend] INFO (__init__:988) EVENT> xend.domain.restart 
['ExampleDomain1', 1, 'schedule']
[2005-09-23 12:52:35 xend] INFO (__init__:988) EVENT> xend.domain.shutdown 
['ExampleDomain1', 1, 'reboot']
[2005-09-23 12:52:49 xend] DEBUG (__init__:988) domain died 
name=ExampleDomain1 domid=1
[2005-09-23 12:53:08 xend] INFO (__init__:988) Domain shutdown timeout 
expired: name=ExampleDomain1 id=1
[2005-09-23 12:53:08 xend] DEBUG (__init__:988) domain_restart_schedule> 1 
reboot 1
[2005-09-23 12:53:08 xend] INFO (__init__:988) Domain shutdown timeout 
expired: name=ExampleDomain1 id=1
[2005-09-23 12:53:08 xend] DEBUG (__init__:988) domain_restart_schedule> 1 
reboot 1
[2005-09-23 12:53:08 xend] INFO (__init__:988) Scheduling restart for domain: 
name=ExampleDomain1 id=1
[2005-09-23 12:53:08 xend] INFO (__init__:988) EVENT> xend.domain.restart 
['ExampleDomain1', 1, 'schedule']
[2005-09-23 12:53:12 xend] ERROR (__init__:988) domain_getinfo(1) failed, 
ignoring

-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-bugs] [Bug 256] New: "xm reboot" could not make domU reboot, bugzilla-daemon <=