On Tue, Oct 4, 2011 at 4:44 PM, Gabriel Michael Black
<[email protected]> wrote:
> The instructions on the website (and the script in util) don't create an
> ext2 image, they create a whole disk image that includes the partition
> table. X86 doesn't use the boot sector to boot, and it doesn't load the
> kernel off the disk. The documentation I'm referring to is here:
>
> http://gem5.org/Disk_images
>
> If you're using documentation that says something different from what's at
> that link, let us know so we can correct it.
>

Hi

Thanks for the response. I was using the same site as you mentioned
above, but read past the line : "The recommended method to create a
disk image is to use ./util/gem5img.py ". After reading it, it told me
that it was a good idea to do everything from scratch so that you can
modify things in an unusual way if required.

I think the from-scratch instructions don't include the partition
table creation. They create just an ext image using the mke2fs
command. I guess I ll try creating it with gem5img.py now.

Thanks again,
Anirudh

> Gabe
>
> Quoting Anirudh Sivaraman <[email protected]>:
>
>> Hi
>>
>> I see that all the full system file images begin with an x86 boot
>> sector followed by partition tables. The instructions on the GEM5 site
>> tell you how to create an ext2 image, but not how to create an ext2
>> image along with the x86 boot sector and partition tables. Without the
>> partition tables, the kernel seems to hang on every new file image
>> that I create saying kernel panic. Does anyone know how to address
>> this issue ?
>>
>> Anirudh
>> _______________________________________________
>> gem5-users mailing list
>> [email protected]
>> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
>>
>
>
> _______________________________________________
> gem5-users mailing list
> [email protected]
> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
>
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Reply via email to