Bug 459384

Summary:	crond not reboot-save within DomU xen client machines
Product:	Red Hat Enterprise Linux 5	Reporter:	Florian La Roche <florian.laroche>
Component:	xen	Assignee:	Xen Maintainance List <xen-maint>
Status:	CLOSED DUPLICATE	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	high	Docs Contact:
Priority:	medium
Version:	5.2	CC:	berrange, clalance
Target Milestone:	rc
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-08-18 12:14:57 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Florian La Roche 2008-08-18 09:46:34 UTC

Description of problem:

Define a xen-server with several guest systems. If you reboot the
main xen-server Xen0, then the guest systems keep on running without
noticing the reboot. You can see this by looking at "uptime" etc.

After the reboot, the crond running in client DomU systems are
still running, but fail to run scheduled cron-scripts.

Maybe missed cron calls will completely make it fail to run
further requests?

Workaround: After a reboot of Dom0, run "service crond restart" in all
DomU systems.

regards,

Florian La Roche


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Daniel Berrangé 2008-08-18 10:19:43 UTC

Urm, it is impossible to guests to continue running while you reboot the dom0.

Are you perhaps using the xendomains script to save running guests to disk, and then restoring them on next boot ?

Comment 2 Florian La Roche 2008-08-18 11:00:35 UTC

Right, xendomains is saving/restoring the DomU machines.

regards,

Florian La Roche

Comment 3 Chris Lalancette 2008-08-18 12:14:57 UTC

OK.  In that case, I would guess this is the same as BZ 426861, which exhibits similar symptoms.  I'm going to close this as a dup of that one for now; if it turns out that that does not fix this issue, please re-open.

Chris Lalancette

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