Enviroment setting 1. Fedora12 + XEN 4.0 + 2.6.32.11-1.2.97.xendom0.fc12.x86_64 2. Fedora12 + XEN 4.0 + kernel-2.6.32.12-1.2.103.xendom0.fc12.x86_64 We test these settings on Supermicro ,Quanta,DELL R210、R410、R710. Only DELL R210,R410,R710 can reboot normaly. Other machines will hang after we reboot from os. We tried different settings of BIOS(EX: ACPI) and boot option (http://blogs.koolwal.net/2009/08/04/howto-fix-linux-hangfreeze-during-reboots-and-restarts/ ),and we still can''t reboot normaly. We also tried OPEN SUSE 11.2 + XEN 3.4.1 + kernel 2..6.31(all from YaST2) on supermicro,and it can''t reboot normaly, too. TREND MICRO EMAIL NOTICE The information contained in this email and any attachments is confidential and may be subject to copyright or other intellectual property protection. If you are not the intended recipient, you are not authorized to use or disclose this information, and we request that you notify us by reply mail or telephone and delete the original message from your mail system. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Did you ret reboot=kbd on Xen''s command line (not dom0''s)? K. On 21/05/2010 03:36, "wenche_chang@trend.com.tw" <wenche_chang@trend.com.tw> wrote:> Enviroment setting > > 1. Fedora12 + XEN 4.0 + 2.6.32.11-1.2.97.xendom0.fc12.x86_64 > 2. Fedora12 + XEN 4.0 + kernel-2.6.32.12-1.2.103.xendom0.fc12.x86_64 > > We test these settings on Supermicro ,Quanta,DELL R210、R410、R710. > Only DELL R210,R410,R710 can reboot normaly. > Other machines will hang after we reboot from os. > > We tried different settings of BIOS(EX: ACPI) and boot option > (http://blogs.koolwal.net/2009/08/04/howto-fix-linux-hangfreeze-during-reboots > -and-restarts/ ),and we still can''t reboot normaly. > > We also tried OPEN SUSE 11.2 + XEN 3.4.1 + kernel 2..6.31(all from YaST2) on > supermicro,and it can''t reboot normaly, too. > TREND MICRO EMAIL NOTICE > The information contained in this email and any attachments is confidential > and may be subject to copyright or other intellectual property protection. If > you are not the intended recipient, you are not authorized to use or disclose > this information, and we request that you notify us by reply mail or telephone > and delete the original message from your mail system. >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
<wenche_chang@trend.com.tw>
2010-May-25 01:37 UTC
RE: [Xen-devel] Reboot from OS will hang
Do you mean use "xm reboot=kbd" ? By the way,we found the problem may be caused by xend. in init 1 ,reboot is ok in init 2 ,reboot is ok in init 3 ,reboot hang we manually start services which in init3 but not in init 2. Reboot hangs if we start xend ini init 2. ________________________________ From: Keir Fraser [mailto:keir.fraser@eu.citrix.com] Sent: 2010/5/21 [星期五] 下午 02:54 To: Wen Che Chang (RD-TW); xen-devel@lists.xensource.com Subject: Re: [Xen-devel] Reboot from OS will hang Did you ret reboot=kbd on Xen''s command line (not dom0''s)? K. On 21/05/2010 03:36, "wenche_chang@trend.com.tw" <wenche_chang@trend.com.tw> wrote:> Enviroment setting > > 1. Fedora12 + XEN 4.0 + 2.6.32.11-1.2.97.xendom0.fc12.x86_64 > 2. Fedora12 + XEN 4.0 + kernel-2.6.32.12-1.2.103.xendom0.fc12.x86_64 > > We test these settings on Supermicro ,Quanta,DELL R210、R410、R710. > Only DELL R210,R410,R710 can reboot normaly. > Other machines will hang after we reboot from os. > > We tried different settings of BIOS(EX: ACPI) and boot option > (http://blogs.koolwal.net/2009/08/04/howto-fix-linux-hangfreeze-during-reboots > -and-restarts/ ),and we still can''t reboot normaly. > > We also tried OPEN SUSE 11.2 + XEN 3.4.1 + kernel 2..6.31(all from YaST2) on > supermicro,and it can''t reboot normaly, too. > TREND MICRO EMAIL NOTICE > The information contained in this email and any attachments is confidential > and may be subject to copyright or other intellectual property protection. If > you are not the intended recipient, you are not authorized to use or disclose > this information, and we request that you notify us by reply mail or telephone > and delete the original message from your mail system. >TREND MICRO EMAIL NOTICE The information contained in this email and any attachments is confidential and may be subject to copyright or other intellectual property protection. If you are not the intended recipient, you are not authorized to use or disclose this information, and we request that you notify us by reply mail or telephone and delete the original message from your mail system. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Hi, I''ve encountered the same problem. After reboot machine went to sleep (or power off) mode, so I can''t even reset it through IPMI, only powercycle (by IPMI too) works. I saw this problem only on new machine (Core i7 based, Xeon E5520, Supermicro X8DTL motherboard), but on Pentium D and Supermicro PDSMi reboot works. Also server hangs after reboot only with pvops Dom0 kernels (I tried stable-2.6.32.x and stable-2.6.33.x with hypervisors 3.4.3-rc and 4.0.0), but reboots normally with 2.6.30.4 "Xenified" kernel (under 3.4.3-rc and 4.0.0 too). All kernels and hypervisors were built for x86-64 architecture. Changing BIOS settings related to ACPI and reboot didn''t help. I tried all reboot= options in hypervisor command line: acpi, kbd, triple, but it didn''t help when pvops kernels were used. With best reagrds, Sergey Kononenko. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Hi, I''ve encountered the same problem. After reboot machine went to sleep (or power off) mode, so I can''t even reset it through IPMI, only powercycle (by IPMI too) works. I saw this problem only on new machine (Core i7 based, Xeon E5520, Supermicro X8DTL motherboard), but on Pentium D and Supermicro PDSMi reboot works. Also server hangs after reboot only with pvops Dom0 kernels (I tried stable-2.6.32.x and stable-2.6.33.x with hypervisors 3.4.3-rc and 4.0.0), but reboots normally with 2.6.30.4 "Xenified" kernel (under 3.4.3-rc and 4.0.0 too). All kernels and hypervisors were built for x86-64 architecture. Changing BIOS settings related to ACPI and reboot didn''t help. I tried all reboot= options in hypervisor command line: acpi, kbd, triple, but it didn''t help when pvops kernels were used. With best reagrds, Sergey Kononenko. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Pasi Kärkkäinen
2010-May-28 10:48 UTC
Re: [Xen-devel] Reboot from OS will hang with pvops dom0 kernel
On Fri, May 28, 2010 at 01:26:12PM +0300, Sergey Kononenko wrote:> Hi, > > I''ve encountered the same problem. After reboot machine went to sleep > (or power off) mode, so I can''t even reset it through IPMI, only > powercycle (by IPMI too) works. > I saw this problem only on new machine (Core i7 based, Xeon E5520, > Supermicro X8DTL motherboard), but on Pentium D and Supermicro > PDSMi reboot works. > Also server hangs after reboot only with pvops Dom0 kernels (I > tried stable-2.6.32.x and stable-2.6.33.x with hypervisors 3.4.3-rc and > 4.0.0), but reboots normally with 2.6.30.4 "Xenified" kernel (under > 3.4.3-rc and 4.0.0 too). All kernels and hypervisors were built for > x86-64 architecture. > Changing BIOS settings related to ACPI and reboot didn''t help. > I tried all reboot= options in hypervisor command line: acpi, kbd, > triple, but it didn''t help when pvops kernels were used. >Are there any debug/error messages printed when/before it hangs? -- Pasi _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Sergey Kononenko
2010-May-28 11:16 UTC
Re: [Xen-devel] Reboot from OS will hang with pvops dom0 kernel
> Are there any debug/error messages printed when/before it hangs?I didn''t notice any, but machine went to power off state too fast, so may be I didn''t have time to notice all messages before screen on KVM became black. I''ll try to use SoL IPMI on this machine to capture all kernel messages. With best regards, Sergey Kononenko. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel