Kali USB – Multiple Persistent Stores
i try to build this usb configuration, as described in the following link :
HTML Code:
https://www.offensive-security.com/kali-linux/usb-multiple-persistent-stores/
i follow the steps described, using the 64bit iso from here :
HTML Code:
http://images.kali.org/kali-linux-2.0-amd64.torrent
I think everything is ok, and after i finished, considered my usb device as /dev/sdh,
i have the following :
Code:
##
## parted -l <device>
Model: Kingston DataTraveler 2.0 (scsi)
Disk /dev/sdh: 7757MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.8kB 3238MB 3238MB primary boot, hidden
2 3238MB 3321MB 82.5MB primary fat16
3 3321MB 5000MB 1679MB primary
4 5000MB 7757MB 2758MB primary ext3
##
## fdisk -l <device>
Disk /dev/sdh: 7757 MB, 7757398016 bytes
239 heads, 62 sectors/track, 1022 cylinders, total 15151168 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: 0x0a9a1b1a
Device Boot Start End Blocks Id System
/dev/sdh1 * 64 6324223 3162080 17 Hidden HPFS/NTFS
/dev/sdh2 6324224 6485375 80576 1 FAT12
/dev/sdh3 6486016 9764863 1639424 83 Linux
/dev/sdh4 9764864 15151103 2693120 83 Linux
##
## blkid |grep <device>
/dev/sdh1: LABEL="Kali Live" TYPE="iso9660"
/dev/sdh2: SEC_TYPE="msdos" UUID="C655-7B4F" TYPE="vfat"
/dev/sdh3: UUID="aee9de21-fa81-43f5-9ff6-2e634bedf30a" TYPE="crypto_LUKS"
/dev/sdh4: LABEL="uspace" UUID="718d91fa-3e1e-4633-8490-bdba2e56c037" TYPE="ext3"
My PC is a x86/32bit machine, so to test this usb config, i make this script :
Code:
#!/bin/sh
# this usb UUID
thisUsbDev=`blkid|grep "Kali\ Live"|cut -c1-8`
# RAM in megabytes
defaultMemory=512
# uncomment, to make changes to temporary files, not to any drive
#OPS='-snapshot'
qemu-system-x86_64 ${OPS} -cpu qemu64 -net nic -net user -m ${defaultMemory} -cdrom ${thisUsbDev} -boot d
, and it runs very very nice !
My problem is,
that when i give my usb to someone with a real x64 arch, it fails to boot ...
Is something i do wrong, or my PC's arch, dont create, what its supposed to ?
