[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-bugs] [Bug 1456] New: Fc6/win-XP guest can not reboot right after booting up



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

           Summary: Fc6/win-XP guest can not reboot right after booting up
           Product: Xen
           Version: unstable
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Hypervisor
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: haicheng.li@xxxxxxxxx


Environment:
------------
Service Arch (ia32/ia32e/IA64): ia32/ia32e
Guest Arch (ia32/ia32e/IA64): ia32/ia32e
Guest OS Type (Linux/Windows):fc6/win-xp
Change Set: 19578
Hardware: Stoakley
Other:

Bug detailed description:
If we reboot the guest right after it boots up, reboot will fail.

Xend Log:
[2009-04-29 11:24:04 6738] INFO (XendDomain:1180) Domain vgtp13_1240975442 (3)
unpaused.
[2009-04-29 11:25:01 6738] INFO (XendDomainInfo:1894) Domain has shutdown:
name=vgtp13_1240975442 id=3 reason=reboot.
[2009-04-29 11:25:01 6738] ERROR (XendDomainInfo:2011) VM vgtp13_1240975442
restarting too fast (Elapsed time: 57.223925 seconds). Refusing to restart to
avoid loops.

Sometimes, we can see other error msg from xend.log:

[2009-04-29 11:26:50 6738] ERROR (XendDomainInfo:2050) Failed to restart domain
4.
Traceback (most recent call last):
  File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line
2036, in _restart
    new_dom.waitForDevices()
  File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line
1067, in waitForDevices
    self.getDeviceController(devclass).waitForDevices()
  File "/usr/lib64/python2.4/site-packages/xen/xend/server/DevController.py",
line 140, in waitForDevices
    return map(self.waitForDevice, self.deviceIDs())
  File "/usr/lib64/python2.4/site-packages/xen/xend/server/DevController.py",
line 164, in waitForDevice
    raise VmError("Device %s (%s) could not be connected. "
VmError: Device 768 (tap) could not be connected. Setting up the backend
failed. See the log files in /var/log/xen/ for details


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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.