Luescher,
Thanks for the follow-up, indeed we don't currently enable the virtio_blk
driver (# CONFIG_VIRTIO_BLK is not set - in the kernel) as that effects the
runnix bootloader as well.
Since AstLinux does not require high performance disk access, this seemed
reasonable. Do you understand why you are having such high CPU usage for
/dev/sda access ?
Testing other KVM/Xen environments this seemed to work just fine.
Your testing is noted.
Lonnie
On Dec 8, 2016, at 10:19 AM, Luescher Claude <starg...@tango.lu> wrote:
> Hello,
>
> Well here is what I concluded so far after spending couple of hours Today on
> the migration.
>
> After failing to reproduce a bootable image by creating partitions (fat16,
> ext2) and copying the boot files there plus mbr 446 bytes, I have converted
> the Vmware image to Qcow 2 format:
>
> qemu-img convert -O qcow2 PBX.vmdk PBX.qcow2
>
>
> The conversion was successful and in this case the boot loader will load
> runnix which gets to a point where it fails with:
>
> Runnix: AstLinux medium not found.
>
> This was the clone of my astlinux-1.1.0 - Asterisk 11.2.1. So for next
> shot I pulled out all the boot files from the latest "VM" image and replaced
> the boot. It's the same thing.
>
>
> root@sysresccd /root/1 % fdisk -l
>
> Disk /dev/vda: 10 GiB, 10737418240 bytes, 20971520 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
> Disklabel type: dos
> Disk identifier: 0xa396d229
>
> Device Boot Start End Blocks Id System
> /dev/vda1 * 63 524159 262048+ 6 FAT16
> /dev/vda2 524160 20971519 10223680 83 Linux
>
> #
>
>
> root@sysresccd /root/1 % file -s /dev/vda1
> /dev/vda1: DOS/MBR boot sector, code offset 0x58+2, OEM-ID "mkdosfs",
> sectors/cluster 8, reserved sectors 8, root entries 512, Media descriptor
> 0xf8, sectors/FAT 256, sectors/track 32, heads 64, sectors 524096 (volumes >
> 32 MB) , reserved 0x1, serial number 0x3fc1b4f2, label: "RUNNIX ", FAT
> (16 bit)
> #
>
>
> root@sysresccd /root/1 % file -s /dev/vda2
> /dev/vda2: Linux rev 1.0 ext2 filesystem data (mounted or unclean),
> UUID=d997ed65-b32f-4fd3-9dcc-b02dbd3cfbc8, volume name "ASTURW" (large files)
> #
>
>
> root@sysresccd /root/1 % dd if=/dev/vda bs=512 count=1 | hexdump -C
> 1+0 records in
> 1+0 records out
> 512 bytes (512 B) copied, 0.00350655 s, 146 kB/s
> 00000000 fa 31 c0 8e d8 8e d0 bc 00 7c 89 e6 06 57 8e c0 |.1.......|...W..|
> 00000010 fb fc bf 00 06 b9 00 01 f3 a5 ea 1f 06 00 00 52 |...............R|
> 00000020 52 b4 41 bb aa 55 31 c9 30 f6 f9 cd 13 72 13 81 |R.A..U1.0....r..|
> 00000030 fb 55 aa 75 0d d1 e9 73 09 66 c7 06 8d 06 b4 42 |.U.u...s.f.....B|
> 00000040 eb 15 5a b4 08 cd 13 83 e1 3f 51 0f b6 c6 40 f7 |..Z......?Q...@.|
> 00000050 e1 52 50 66 31 c0 66 99 e8 66 00 e8 21 01 4d 69 |.RPf1.f..f..!.Mi|
> 00000060 73 73 69 6e 67 20 6f 70 65 72 61 74 69 6e 67 20 |ssing operating |
> 00000070 73 79 73 74 65 6d 2e 0d 0a 66 60 66 31 d2 bb 00 |system...f`f1...|
> 00000080 7c 66 52 66 50 06 53 6a 01 6a 10 89 e6 66 f7 36 ||fRfP.Sj.j...f.6|
> 00000090 f4 7b c0 e4 06 88 e1 88 c5 92 f6 36 f8 7b 88 c6 |.{.........6.{..|
> 000000a0 08 e1 41 b8 01 02 8a 16 fa 7b cd 13 8d 64 10 66 |..A......{...d.f|
> 000000b0 61 c3 e8 c4 ff be be 7d bf be 07 b9 20 00 f3 a5 |a......}.... ...|
> 000000c0 c3 66 60 89 e5 bb be 07 b9 04 00 31 c0 53 51 f6 |.f`........1.SQ.|
> 000000d0 07 80 74 03 40 89 de 83 c3 10 e2 f3 48 74 5b 79
> |..t...@.......ht[y|
> 000000e0 39 59 5b 8a 47 04 3c 0f 74 06 24 7f 3c 05 75 22 |9Y[.G.<.t.$.<.u"|
> 000000f0 66 8b 47 08 66 8b 56 14 66 01 d0 66 21 d2 75 03 |f.G.f.V.f..f!.u.|
> 00000100 66 89 c2 e8 ac ff 72 03 e8 b6 ff 66 8b 46 1c e8 |f.....r....f.F..|
> 00000110 a0 ff 83 c3 10 e2 cc 66 61 c3 e8 62 00 4d 75 6c |.......fa..b.Mul|
> 00000120 74 69 70 6c 65 20 61 63 74 69 76 65 20 70 61 72 |tiple active par|
> 00000130 74 69 74 69 6f 6e 73 2e 0d 0a 66 8b 44 08 66 03 |titions...f.D.f.|
> 00000140 46 1c 66 89 44 08 e8 30 ff 72 13 81 3e fe 7d 55 |F.f.D..0.r..>.}U|
> 00000150 aa 0f 85 06 ff bc fa 7b 5a 5f 07 fa ff e4 e8 1e |.......{Z_......|
> 00000160 00 4f 70 65 72 61 74 69 6e 67 20 73 79 73 74 65 |.Operating syste|
> 00000170 6d 20 6c 6f 61 64 20 65 72 72 6f 72 2e 0d 0a 5e |m load error...^|
> 00000180 ac b4 0e 8a 3e 62 04 b3 07 cd 10 3c 0a 75 f1 cd |....>b.....<.u..|
> 00000190 18 f4 eb fd 00 00 00 00 00 00 00 00 00 00 00 00 |................|
> 000001a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
> 000001b0 00 00 00 00 00 00 00 00 29 d2 96 a3 00 00 80 01 |........).......|
> 000001c0 01 00 06 3f 3f 81 3f 00 00 00 41 ff 07 00 00 00 |...??.?...A.....|
> 000001d0 01 82 83 11 11 51 80 ff 07 00 80 00 38 01 00 00 |.....Q......8...|
> 000001e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
> 000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.|
> 00000200
> #
>
>
> root@sysresccd /root/1 % ls -al
> total 5612
> drwxr-xr-x 4 root root 16384 Dec 8 15:26 .
> drwx------ 10 root root 140 Dec 8 15:21 ..
> -rwxr-xr-x 1 root root 4096 Dec 8 15:26 1.txt
> -rwxr-xr-x 1 root root 308 Dec 8 15:25 boot.msg
> -r-xr-xr-x 1 root root 15218 Dec 8 15:25 ldlinux.sys
> -rwxr-xr-x 1 root root 172400 Dec 8 15:25 memtest
> drwxr-xr-x 3 root root 4096 Dec 8 15:25 old
> drwxr-xr-x 2 root root 4096 Dec 8 15:25 os
> -rwxr-xr-x 1 root root 2636048 Dec 8 15:25 runnix
> -rwxr-xr-x 1 root root 2872954 Dec 8 15:25 runnix.img
> -rwxr-xr-x 1 root root 655 Dec 8 15:25 syslinux.cfg
> -rwxr-xr-x 1 root root 16 Dec 8 15:25 ver
>
>
> Unfortunately setting the disk subsystem in kvm to SCSI will pull the CPUs on
> 200% unlike virtio but yeah in that case the disk will show up as sda instead
> of vda but guess what the installer will fail with the exact same error, no
> suitable disk found.
>
> <disk type='file' device='disk'>
> <driver name='qemu' type='qcow2'/>
> <source file='/mnt/kvm/pbx2.qcow'/>
> <target dev='sda' bus='scsi'/>
> <address type='drive' controller='0' bus='0' target='0' unit='0'/>
> </disk>
>
> After further experimenting I found a workaround, using IDE hdd.
>
> <disk type='file' device='disk'>
> <driver name='qemu' type='qcow2'/>
> <source file='/mnt/kvm/pbx2.qcow'/>
> <target dev='hda' bus='ide'/>
> <address type='drive' controller='0' bus='0' target='0' unit='0'/>
> </disk>
>
> In this case the disk will show up as SDA and even my old system could boot
> but performance for FS access is far worse than kvm, if I do any IO op on the
> disk KVM pulls the cpu on 100%.
>
> So make this a top priority for the KVM version to use the virtio driver.
>
>
>
> On 2016-11-30 16:23, Lonnie Abelbeck wrote:
>> Luescher,
>> Yes, all the supplied ISO's are installers, hence they are labeled:
>> "Download Install ISO"
>> We have tested and offer documentation for various VM environments:
>> https://doc.astlinux.org/userdoc:documentation#guest_virtual_machines
>> We make no promise that the "KVM/Xen x86-64bit (Video Console):"
>> Installer ISO works for every VM situation.
>> If you want to offer help and guidance for your situation, that would be
>> great.
>> Lonnie
>> On Nov 30, 2016, at 8:17 AM, Luescher Claude <starg...@tango.lu> wrote:
>>> Hi,
>>> I slowly migrating my remaining Linux based virtual machines from Vmware
>>> -> KVM.
>>> Astlinux was not an easy one for sure. I still using the:
>>> AstLinux Release: astlinux-1.1.0 - Asterisk 11.2.1
>>> Which based on kernel 2.6.35.14-astlinux and I have found no virtio
>>> kernel module for it so it would not recognize my KVM virtual disk
>>> anyway.
>>> I decided to start with a fresh install with your specifically made
>>> KVM/Xen image (astlinux-1.2.8-genx86_64-vm.iso) but that does not
>>> recognize the disk either.
>>> The virtual disk is definitely there and working because I can boot in
>>> the system from systemrescue CD which sees the vda disks.
>>> Anyone who basically tried to install this crap in KVM would experience
>>> the exact same issue, so that means that there are no KVM users here at
>>> all.
>>> Why are you advertising that image as working KVM when it's clearly not
>>> working. You should put it under Alfa-version section.
>>> Are you planning to make a working image in the near future for KVM?
>>> Also please don't call it "image" call it installer because this is what
>>> it suppose to be. You could produce a .qcow2/.raw image for KVM and call
>>> that an image so people can just dl it from your site drop it into a vm
>>> config and start the virtual machine up.
>>> ------------------------------------------------------------------------------
>>> _______________________________________________
>>> Astlinux-users mailing list
>>> Astlinux-users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>>> Donations to support AstLinux are graciously accepted via PayPal to
>>> pay...@krisk.org.
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Astlinux-users mailing list
>> Astlinux-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>> Donations to support AstLinux are graciously accepted via PayPal to
>> pay...@krisk.org.
>
>
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/xeonphi
_______________________________________________
Astlinux-users mailing list
Astlinux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to
pay...@krisk.org.
