[Xen-bugs] [Bug 605] New: Kernel Panic and reboot on dom0 after xm shutdown of VM

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=605

           Summary: Kernel Panic and reboot on dom0 after xm shutdown of VM
           Product: Xen
           Version: 3.0.1
          Platform: x86-64
        OS/Version: Linux-2.6
            Status: NEW
          Severity: major
          Priority: P3
         Component: Hypervisor
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: blaise@xxxxxxxxx


Still investigating but it would appear that we suffered a kernel panic that
forced our machine to reboot after we issued an xm shutdown for one of our VMs. 

We have the xend-debug.log and the xend.log for the event.

machine specs:
amd athlon64 x2 
Tyan motherboard
2 gigs of ram
vms are LVM based
Fedora Core 5 (release)
Xen 3.0.1

there were 3 other VMs running at the time. 

I'm not sure what priority or severity to assign to this, but please let me
know if there's anything else i can provide to aid diagnostics.


Last error in the xend-debug.log is:

Exception in thread Thread-30:
Traceback (most recent call last):
  File "/usr/lib64/python2.4/threading.py", line 442, in __bootstrap
    self.run()
  File "/usr/lib64/python2.4/threading.py", line 605, in run
    self.function(*self.args, **self.kwargs)
  File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line
868, in refreshShutdown
    threading.Timer(timeout, self.refreshShutdown).start()
  File "/usr/lib64/python2.4/threading.py", line 416, in start
    _start_new_thread(self.__bootstrap, ())
error: can't start new thread


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