Ubuntu 12.04 Precise Pangolin paravirtualized DomU can't be bootet with the Ubuntu Kernel and Mainline Kernel on Xen 4.1 and Ubuntu 12.04 as Dom0

Bug #1018619 reported by Wer Wie Was
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu
High
Unassigned

Bug Description

I'm created a Dom0 with Xen 4.1 as hypervisor on Ubuntu 12.04 and created a new root filesystem (also 12.04 in paravirtualization mode) with debootstrap.

Then I wrote the Xen DomU configuration file and tried to boot the DomU with the 3.2.0-25-generic kernel. The DomU gets created but stucks in the boot process at the following sequence:

 7.179839] EXT3-fs (xvda1): mounted filesystem with ordered data mode
Begin: Running /scripts/local-bottom ... done.
done.
Begin: Running /scripts/init-bottom ... done.
fsck from util-linux 2.20.1
/dev/xvda1: clean, 15756/1310720 files, 215621/5242880 blocks

Seems to be a bug. In the Dom0/Xen logs are no errors reported. Other guests like Debian Squeeze work with the same kernel as DomU kernel. So I think its a problem with the kernel it self or with the interaction of the system with the kernel.

Does someone has a solution for this problem?

The problem can be reproduced by creating a paravirtualized DomU on Ubuntu Precise Pangolin 12.04 with Xen 4.1 (all packages from normal distro repository) and boot the DomU with the actual standard Ubuntu 3.2.0-25-generic kernel.

Best Regards

---
AlsaDevices:
 total 0
 crw-rw---T 1 root audio 116, 1 Jun 26 06:28 seq
 crw-rw---T 1 root audio 116, 33 Jun 26 06:28 timer
AplayDevices: aplay: device_list:252: no soundcards found...
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
ArecordDevices: arecord: device_list:252: no soundcards found...
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=fc35367f-2591-4e9c-bff9-b75137fa61d0
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd
MachineType: Bochs Bochs
Package: linux (not installed)
PciMultimedia:

ProcEnviron:
 SHELL=/bin/bash
 TERM=screen
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
ProcFB:

ProcKernelCmdLine: placeholder root=UUID=dfdfd1ae-0e81-4b25-aaaa-da19b9e64cf0 ro quiet splash
ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory /home/lukas not ours.
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-25-generic N/A
 linux-backports-modules-3.2.0-25-generic N/A
 linux-firmware 1.79
RfKill:

Tags: precise
Uname: Linux 3.2.0-25-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 01/01/2007
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr:
dmi.product.name: Bochs
dmi.sys.vendor: Bochs

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1018619

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: precise
Revision history for this message
Wer Wie Was (kzqd-deactivatedaccount-deactivatedaccount) wrote : AcpiTables.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Wer Wie Was (kzqd-deactivatedaccount-deactivatedaccount) wrote : BootDmesg.txt

apport information

Revision history for this message
Wer Wie Was (kzqd-deactivatedaccount-deactivatedaccount) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Wer Wie Was (kzqd-deactivatedaccount-deactivatedaccount) wrote : IwConfig.txt

apport information

Revision history for this message
Wer Wie Was (kzqd-deactivatedaccount-deactivatedaccount) wrote : Lspci.txt

apport information

Revision history for this message
Wer Wie Was (kzqd-deactivatedaccount-deactivatedaccount) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Wer Wie Was (kzqd-deactivatedaccount-deactivatedaccount) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Wer Wie Was (kzqd-deactivatedaccount-deactivatedaccount) wrote : ProcModules.txt

apport information

Revision history for this message
Wer Wie Was (kzqd-deactivatedaccount-deactivatedaccount) wrote : UdevDb.txt

apport information

Revision history for this message
Wer Wie Was (kzqd-deactivatedaccount-deactivatedaccount) wrote : UdevLog.txt

apport information

Revision history for this message
Wer Wie Was (kzqd-deactivatedaccount-deactivatedaccount) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a kernel version where you were not having this particular problem? This will help determine if the problem you are seeing is the result of the introduction of a regression, and when this regression was introduced.

Changed in linux (Ubuntu):
importance: Undecided → High
tags: added: kernel-da-key
Revision history for this message
Wer Wie Was (kzqd-deactivatedaccount-deactivatedaccount) wrote :

Hello Joseph,

I tried the kernel revisions 23-25 of the generic and virtual kernel distributed with Ubuntu 12.04. Also I have tried to boot with the Mainline Kernel 3.1.10 from the Ubuntu Kernel Team PPA but it didn't work. Because of this fact I think it's a problem which is located at the interaction with the kernel.

There was no upgrade before it's a normal Ubuntu 12.04 Precise Pangolin installed with the alternate CD. The DomU also was fresh setuped with debootstrap and never worked as PV guest.

The same problem was discussed short time before the release of Ubuntu 12.04 at Askubuntu: http://askubuntu.com/questions/126631/why-do-i-get-disk-i-o-errors-booting-the-3-2-kernel-on-a-xen-vps-server

The as workaround declared fstab option barrier=0 does not solve the problem.

Best Regards

Revision history for this message
Wer Wie Was (kzqd-deactivatedaccount-deactivatedaccount) wrote :

Hello,

I tested the same setup now also on an Debian Squeeze Dom0 and tried to boot the DomU with the Linux 3.2.0 kernel from the Debian Backports repository. In this setup the filesystem gets corrupted and can't be read so the DomU can't boot.

Best Regards

no longer affects: debian
Revision history for this message
Wer Wie Was (kzqd-deactivatedaccount-deactivatedaccount) wrote :

Changed package because it's not clear which packet realy makes this problem. I think it's not the kernel directly it's more the filesystem implementation or something like that.

affects: linux (Ubuntu) → ubuntu
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers