Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 225428 - Paravirtualized xen guest hangs when guest is shutdown - Guest domain does not terminate
Paravirtualized xen guest hangs when guest is shutdown - Guest domain does no...
Status: CLOSED DUPLICATE of bug 221626
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: xen (Show other bugs)
ia64 Linux
medium Severity medium
: ---
: ---
Assigned To: Xen Maintainance List
Depends On:
  Show dependency treegraph
Reported: 2007-01-30 11:13 EST by Joseph Szczypek
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-01-30 14:32:51 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Joseph Szczypek 2007-01-30 11:13:55 EST
Description of problem:
When shutting down a paravirtualized xen guest, the guest hangs (the domain does
not terminate.  I've experienced this problem at the point where auditd is
shutting down.   I've disabled auditd using chkconfig and then experience the
problem at the point where 'Halting system' is displayed.  The domain doesn't

Version-Release number of selected component (if applicable):
2.6.18-1.3002.el5xen (rcs7)

How reproducible:
Occurs every time I shut the guest down.

Steps to Reproduce:
1. "shutdown -h now" in the guest, or
2. "xm shutdown 'guest_id'" in dom0
Actual results:
Guest domain does not terminate.

Expected results:
Guest domain should terminate.

Additional info:
Paravirtualized guest has 2GB of memory, 2 vcpus, and is installed to a physical
(SCSI) disk.  Guest and Dom0 are installed with the same version of the OS.
Comment 1 Markus Armbruster 2007-01-30 14:32:51 EST

*** This bug has been marked as a duplicate of 221626 ***

Note You need to log in before you can comment on or make changes to this bug.