Bug 193758
| Summary: | Using xenguest-install.py to an LVM backing fails on reboot | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Gwendolen <gwendolen.lynch> | ||||||||||||
| Component: | xen | Assignee: | Jeremy Katz <katzj> | ||||||||||||
| Status: | CLOSED RAWHIDE | QA Contact: | Brian Brock <bbrock> | ||||||||||||
| Severity: | medium | Docs Contact: | |||||||||||||
| Priority: | medium | ||||||||||||||
| Version: | 5 | CC: | bstein, katzj | ||||||||||||
| Target Milestone: | --- | ||||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | All | ||||||||||||||
| OS: | Linux | ||||||||||||||
| Whiteboard: | |||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2006-09-25 20:58:56 UTC | Type: | --- | ||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||
| Documentation: | --- | CRM: | |||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||
| Embargoed: | |||||||||||||||
| Attachments: |
|
||||||||||||||
The install succeeded successfully? Are there any errors in dmesg of the xen0
or in /var/log/xend{-debug}.log?
Created attachment 130468 [details]
xend.log excerpt from install
Created attachment 130469 [details]
xend.log excerpt from initial boot
Created attachment 130470 [details]
fsck output
Created attachment 130471 [details]
dmesg boot log
Created attachment 130472 [details]
dmesg log post guest install
Other than what apprears in the post install dmesg there are no other interesting bits and the install finishes OK. If I 'mount -o ro /boot', 'mount -o rmount rw /' and do an 'init 3' I can bring the guest up to a useable state. This works now |
Description of problem: Version-Release number of selected component (if applicable): xen-3.0.1-4 & xen-3.0.2-0.FC5.3 How reproducible: Everytime Steps to Reproduce: 1. Create an logical volume to install to: # lvcreate -L 2G vgxen -n myxenvg 2. Install FC5: # xenguest-install.py --name=myxen \ --file=/dev/vgxen/myxenvg \ --ram=256 \ --location=http://install.mylan.com.au/5/i386/ 3. Start the instance # xm create -c myxen Actual results: Setting up Logical Volume Management: 2 logical volume(s) in volume group "vg00" now active [ OK ] Checking filesystems Checking all file systems. [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/vg00/lv00 /dev/vg00/lv00: clean, 19347/418080 files, 126997/417792 blocks [/sbin/fsck.ext3 (1) -- /boot] fsck.ext3 -a /dev/xvda1 Error reading block 32 (Attempt to read block from filesystem resulted in short read). /boot: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options) Trying to fsck the /boot filesystem gives the following errors: Error reading block 32 (Attempt to read block from filesystem resulted in short read). Ignore error<y>? Expected results: The myxen domU should boot as it does when using a file backing. Additional info: Running the course of the fsck does not make any difference. Trying to manually mount and write to xvda1 will cause ext3 journal errors and the partition to be remounted read only.