Wanted: How-to qemu 64-bit

[curaga]

< 3.4 won't add partitionless HD's to fstab, and I believe this prevents tce autodetection on those. Try 3.4rc2 or create a partition on the virtual hd.

[bsquared]

I thought it may have something to do with the image.  I dont see an explicit 3.4rc2 for 64-bit.

[gerald_clark]

hda is not a valid partition.

[bsquared]

do you mean to say that hda is not a valid partition as far as tce auto-mounting is concerned? therefore there is no need to check out rc2.

[curaga]

Your hda is an unpartitioned drive. hda1 would be a partition.

[maro]

Hold on guys: Yes '/dev/hda' is an unpartitioned drive (which would not have worked with 'rebuildfstab' of TC 3.3), but since TC 3.4rc1 that limitation has been overcome.

I implicitly assumed that bsquared was aware of this, and have also therefore on purpose used TC 3.4rc2 in my quick test (see reply #11). (Just ignore the fact that I'm using TC instead of MC, since it does not make any difference for the issue at hand).

@bsquared: If you insist on using 64-bit (which for your current issue would not really be required) just download the seperate files of the kernel and the initrd and use qemu-system-x86_64 -kernel bzImage -initrd microcore64.gz ... instead of qemu-system-x86_64 -cdrom microcore-64.iso -boot d ...

EDIT: To specify boot parameters with the '-kernel ...' style of using QEMU please add -append "tce=hda microcore showapps" to the command

[maro]

@bsquared: Thanks for your details reply #12.

My observation is that the numbers don't add up: The partition 1 that you've tried to extract starts at block 1,048,576 / 512 = 2,048 (which should be used as the 'skip' parameter). It's size is 7,975,469,056 / 512 = 15,577,088 blocks (which should be used as the 'count' parameter). The size reported by 'parted' (i.e. 7,975,469,056 = 7606 MBytes), does not match with what 'fdisk' reports (i.e. 8,387,559,424 = 7999 MBytes).

I'd therefore suggest to check the file system (e.g. via fsck /dev/hda). You'll need an un-mounted file system for this, so you better boot with boot codes 'base norestore' to ensure that.

I guess you could make your life slightly easier if you'd use 'unit s' (for sectors, i.e. blocks) in 'parted'. That way the reported numbers can be used directly in a 'dd bs=512 ...' scenario.

[bsquared]

Thanks all for you help.  I went another direction to get 64-bit emulation with the image.