Bug 502365
Summary: | RAMDISK: incomplete write (-28 != 32768) 16777216 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Richard W.M. Jones <rjones> |
Component: | libguestfs | Assignee: | Richard W.M. Jones <rjones> |
Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | rawhide | CC: | rjones, virt-maint |
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: | 2009-05-24 14:42:46 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: |
Description
Richard W.M. Jones
2009-05-24 13:53:27 UTC
This error only happens when we try to run libguestfs on Debian (still using Fedora inside the appliance of course). We found by googling and experimentation that we can get rid of the 'RAMDISK: incomplete write' error by adding ramdisk=NNN option, eg: LIBGUESTFS_APPEND="ramdisk_size=128000" However this doesn't in itself resolve the problem with booting. (In reply to comment #1) > ramdisk=NNN option, eg: That should be 'ramdisk_size=NNN' of course. False alarms all round - the ramdisk_size parameter is NOT needed. The problem was that Debian's cpio command defaults to using the obsolete 'bin' cpio format, not 'newc' (which is what Fedora defaults to). Therefore Debian's cpio was making an initramfs image that the kernel simply couldn't understand. Fixes to this are: http://git.et.redhat.com/?p=febootstrap.git;a=commit;h=346a893d8035212e8d2acbe3a14521df504116e2 http://git.et.redhat.com/?p=febootstrap.git;a=commit;h=0eacd743cb1ff655a09f7b941320a0235d482df0 |