[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [Bug 671831] [NEW] Sparc guest assert error
From: |
Stefan Hajnoczi |
Subject: |
Re: [Qemu-devel] [Bug 671831] [NEW] Sparc guest assert error |
Date: |
Wed, 10 Nov 2010 09:42:22 +0000 |
On Tue, Nov 9, 2010 at 5:07 PM, Nigel Horne <address@hidden> wrote:
> Stefan,
>> $ /sbin/fdisk -lu ~njh/qemu/sparc/debian.img
>> ...hopefully this displays the slices/partitions...
>> Device Boot Start End Blocks
>> Id System
>> test.raw1 * 2048 1026047 512000 83 Linux
>>
>> $ mount -o loop,offset=$((2048 * 512)) /mnt
>> (The offset is calculated by taking the start block number from fdisk
>> and multiplying it by 512 bytes)
>>
>> $ ls /mnt/boot
>> ...there should be a vmlinuz and initrd, you could check the silo.conf
>> or other boot configuration if you don't know the exact kernel/initrd
>> filenames.
>>
>> $ cp /mnt/boot/{vmlinuz,initrd} /tmp
>> $ umount /mnt
>>
>
> Sadly that doesn't work:
>
> address@hidden:~/qemu/sparc$ /sbin/fdisk -lu debian.img
>
> Disk debian.img: 0 MB, 0 bytes
> 255 heads, 63 sectors/track, 0 cylinders, total 0 sectors
> Units = sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x00000000
>
> Disk debian.img doesn't contain a valid partition table
fdisk doesn't like the SPARC partition table. I used to have tools to
deal with this but have forgotten which ones they were.
> But, it has occurred to me, - I boot using your code and get
> /boot/vmlinuz and /boot/initrd.img that way. Would that be OK?
Sure :).
Stefan