Kernel 2.6.32-27 49 won't restart/shutdown under XenServer

Bug #695012 reported by Brian Lagoni
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

System: Ubuntu 10.04.1 LTS
Package: linux-image-2.6.32-27-virtual

The servers are running as guests under XenServer 5.6 (with update 1,2 and 4).
After installation of the new kernel, my ubuntu guests won't reboot or restart as they did with the older kernels.
Using the previous kernel(linux-image-2.6.32-24-virtual) it works at it should.

The console only states on reboot:
"* Will now restart
Restarting system."

and on shutdown
"System halted."

After this nothing happens.

To reboot/shutdown I have to make a forced reboot/shutdown from the XenCenter(the XenServer management tool).

If there are any information missing to this bug report, please let me known and I will try to supply them.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-27-server (not installed)
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-27.49-server 2.6.32.26+drm33.12
Uname: Linux 2.6.32-27-server x86_64
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
CurrentDmesg:
 [427761.846905] eth0: no IPv6 routers present
 [427762.336904] eth3: no IPv6 routers present
 [427770.263292] eth1: no IPv6 routers present
 [427770.563083] eth4: no IPv6 routers present
 [427772.744477] eth2: no IPv6 routers present
Date: Tue Dec 28 13:59:52 2010
InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 (20100427)
Lspci:

Lsusb: Error: command ['lsusb'] failed with exit code 1:
ProcCmdLine: root=UUID=3bd0c366-862b-4b20-96c1-fb22d04a745e ro
ProcEnviron:
 LANG=en_DK.UTF-8
 SHELL=/bin/bash
ProcModules:
 xenfs 6105 1 - Live 0xffffffffa000c000
 lp 9336 0 - Live 0xffffffffa001c000
 parport 37160 1 lp, Live 0xffffffffa0010000
 xen_netfront 17890 0 - Live 0xffffffffa0005000
 xen_blkfront 10665 4 - Live 0xffffffffa0000000
SourcePackage: linux

Revision history for this message
Brian Lagoni (lagonix) wrote :
Revision history for this message
Hans Bickhofe (hb-niwo) wrote :

I also tried to change GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub
to GRUB_CMDLINE_LINUX_DEFAULT="quiet acpi=force", but there's no change.

Revision history for this message
Horst Platz (hp-localhorst) wrote :

i figured out after a while one of the VCPU increase nearly to 100% on the
performance screen from xencenter see performance.jpg

if i change the VCPU from the VM to only one, the reboot behavior changed to
a normal manner.

description: updated
Revision history for this message
Brian Lagoni (lagonix) wrote :

Just a update from me..

I can confirm that changing the VCPU to one, resolves the issue.

I have build a new kernel where I have removed/reverted this patch :
http://kerneltrap.org/mailarchive/linux-kernel/2010/11/19/4648631

Now the reboot/shutdown issues is gone.
Next step for me, must be to find the bug from this patch.

Revision history for this message
Horst Platz (hp-localhorst) wrote :

maybe it help.

in a test environment i made a realease-upgrade to ubuntu 10.10 with kernel 2.6.35-24-server.
you run in a grub2 error but with editing manually

vim /boot/grub/grub.cfg

:%s/(hd0,msdos1)/(hd0,0)/g

the VM boot/reboot the kernel 2.6.35-24-server in a regular way.

Revision history for this message
Horst Platz (hp-localhorst) wrote :

today there is a update from ubuntu 10.04.1 LTS kernel up to 2.6.32-28-server.

package -> linux-image-2.6.32-28-server 2.6.32-28.55

that kernel solve the problem for me.

Revision history for this message
Brian Lagoni (lagonix) wrote :

I can say that the 2.6.32-28-server kernel also have resolved the problem of me.

Changed in linux (Ubuntu):
status: New → Incomplete
status: Incomplete → Opinion
status: Opinion → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.