Gutsy server kernel takes too long to initialize on VMWare ESX 3.0.2 as guest

Bug #160541 reported by Rouben
4
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned
linux-source-2.6.22 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: linux-source-2.6.22

Ubuntu Gutsy server takes too long to boot up as a guest on VMWare ESX 3.0.2 server with all the latest patches on both host and guest machines. It takes over 81 seconds for the kernel to initialize, as shown by this sniplet of dmesg log:

--- SNIP ---
[ 0.000000] Kernel command line: root=UUID=00b0896d-91ca-48fc-acc6-bfdd1c7a8333 ro quiet splash
[ 0.000000] Initializing CPU#0
[ 0.000000] PID hash table entries: 4096 (order: 12, 32768 bytes)
[ 81.594771] time.c: Detected 1994.569 MHz processor.
[ 81.613771] Console: colour VGA+ 80x25
[ 81.613817] Checking aperture...
--- SNIP ---

The full logs as requested by the kernel team bug policies page will be attached to this bug.

Revision history for this message
Rouben (rouben) wrote :

The following log files are attached from the Ubuntu Gutsy guest OS running under VMWare ESX Server 3.0.2:
    * uname -a > uname-a.log
    * cat /proc/version_signature > version.log
    * dmesg > dmesg.log
    * sudo lspci -vvnn > lspci-vvnn.log
All these files are in the attached tarball.

Revision history for this message
Rouben (rouben) wrote :
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Rouben,

The Hardy Heron Alpha series is currently under development and contains an updated version of the kernel. Care to test the linux-image-2.6.24-11-server and verify if this is still an issue? We'll keep this report open against the actively developer kernel bug against 2.6.22 this does not qualify for a stable release update and will be closed. Thanks.

Changed in linux:
status: New → Incomplete
Changed in linux-source-2.6.22:
status: New → Won't Fix
Revision history for this message
Rouben (rouben) wrote :

Since this isn't going to be fixed in Gutsy, then this bug should be marked as Invalid. The new Hardy server images aren't stable under ESX, probably because they are XEN-aware? Anyway, the problem with regular vanilla hardy server ISOs appears to be much more severe than just slow kernel initialization. I don't have time at the moment to gather enough info for a proper bug report, and as such I will submit a new bug report sometime in the future. I am therefore marking this bug as invalid, since this specific issue does not apply to Hardy at all. Thanks!

Changed in linux:
status: Incomplete → 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.