Can't Start Ubuntu 8.10 Xen DomU with 2.6.27-7.12 Kernel

Bug #286178 reported by agent 8131
26
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I tried upgrading a development domu system from hardy to intrepid. While the system boots with the old 2.6.24 kernels from hardy I was not able to get a 2.6.27 kernel working. I tried linux-image-2.6.27-7-server and linux-image-2.6.27-7-virtual. Neither created entries for grub and when I created the menu.lst entries manually I got a message from pygrub that the kernel was invalid. The host system is running Ubuntu Hardy / Xen 3.2. I understand that there will be no Dom0 support in Intrepid but I was under the impression that DomU support would be available (indeed mention of the Xen modules shows up in the latest changelog). It would be helpful to begin documenting the steps necessary to upgrade an existing DomU Ubuntu system to 8.10 as well as how to create an Ubuntu 8.10 DomU that can be booted via pygrub, pvgrub, or hvmloader.

Revision history for this message
Mihai (ropiku) wrote :

I also tried this on a CentOS 5.2 host and the 2.6.27 kernel does not work, while the old one works.
Thank you.

Revision history for this message
Andy Smith (grifferz) wrote :

I have heard a rumour that booting this kernel under Xen PV will not
work unless the dom0 is running at least xen 3.3.x as it needs
something called "the vmlinuz bootloader patches".

I do find it hard to believe as not even Ubuntu Hardy has xen-3.3,
but if this is the case could anyone confirm?

Revision history for this message
usul (usul-timedout) wrote :

I support Andy's request - could anyone confirm that Xen >= 3.3 is required in order to get Ubuntu 8.10 running as domU?

Revision history for this message
Boris Derzhavets (bderzhavets) wrote :

Yes , Xen Hypervisor 3.3.0 is required on Ubuntu Hardy Dom0 ( via backport)
http://lxer.com/module/newswire/view/112045/index.html

Revision history for this message
Boris Derzhavets (bderzhavets) wrote :

Ubuntu 8.10 Server domU is also running fine at Xen 3.3.1 openSUSE 11.1 Dom0, Xen 3.3.1 port CentOS 5.2. View for instance :-
http://lxer.com/module/newswire/view/111103/index.html
http://lxer.com/module/newswire/view/111292/index.html

Revision history for this message
Etienne Goyer (etienne-goyer-outlands) wrote :

I reported a bug against ubuntu-website, as the Intrepid press release did not qualify the Xen version Ubuntu 8.10 would run as a paravirtualized guest on.

    https://bugs.launchpad.net/ubuntu-website/+bug/310931

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi agent,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 286178

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

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