|
Bugzilla – Full Text Bug Listing |
| Summary: | dom0-cpus limit causes xenwatch_cb running 100% and xm command freeze and xend dead | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.2 | Reporter: | Udo Attila Fischer <udo1> |
| Component: | Xen | Assignee: | Jan Beulich <jbeulich> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Critical | ||
| Priority: | P2 - High | CC: | 0.bugs.only.0, carnold, jbeulich, jdouglas, jfehlig, novell.admin |
| Version: | Final | ||
| Target Milestone: | unspecified | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 11.2 | ||
| Whiteboard: | |||
| Found By: | Community User | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Udo Attila Fischer
2009-11-26 10:11:55 UTC
This appears to also be a problem in native code (introduced in 2.6.30): If a CPU gets hot plugged while check_interval is zero (modifiable to zero via /sys, defaulting to zero on Xen), mce_timer will never get set up, and a subsequent del_timer() can't lock the timer as its base is NULL. Hence I'll get a patch submitted upstream first. Workaround for the time being would be "mce=off" on the kernel command line. Another workaround is to define vcpu number at boot time (submitted by Vladislav Karpenko on the xen-users list). add boot option dom0_max_vcpus=1 to menu.lst to the xen kernel parameter list like that kernel /xen.gz dom0_mem=512M dom0_vcpus_pin dom0_max_vcpus=1 this will set the cpu at boot time ( coldplug :) ) and the hotplug issue does not happen. ----------------------------- But if I understand the problem, it should occourt as well in opensuse 11.2 DomUs when changing the ammount of VCPUs at runtime... *** Bug 561607 has been marked as a duplicate of this bug. *** This should now be fixed with the import of 2.6.31.9 (and for HEAD/Factory 2.6.32.2), going to be available with a future kernel maintenance update. *** Bug 570443 has been marked as a duplicate of this bug. *** |