[LITMUS^RT] Can not register DEMO Scheduler Plugin in LITMUS^RT
Sanjib Das
cnt.sanjib at googlemail.com
Thu Jan 9 17:36:34 CET 2014
Dear Concern,
Thank you for the reply. Now its booting but its not connecting with
network with the following command.
qemu-system-x86_64 -gdb tcp::1234 -s -S -enable-kvm -cpu host -smp 2 -m 512
-kernel /home/sdas/litmus/litmus-rt/arch/x86_64/boot/bzImage -hda
/home/sdas/ubuntu_iso/ubuntu.backing.qcow2.img -append
"console=ttyS0,115200 root=/dev/sda1 " -nographic -net nic -net
user,hostfwd=::2222-:22
There was an error while booting the qemu image:
* Starting AppArmor
profiles Cache read/write
disabled: /sys/kernel/security/apparmor/features interface file missing.
(Kernel needs AppArmor 2.4 compatibility patch.)
Cache read/write disabled: /sys/kernel/security/apparmor/features interface
file missing. (Kernel needs AppArmor 2.4 compatibility patch.)
Warning from /etc/apparmor.d/usr.sbin.tcpdump
(/etc/apparmor.d/usr.sbin.tcpdump line 64): profile /usr/sbin/tcpdump
network rules not enforced
Warning from /etc/apparmor.d/sbin.dhclient (/etc/apparmor.d/sbin.dhclient
line 73): profile /sbin/dhclient network rules not enforced
and also here is the output of fdisk -l command
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 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: 0x000a0e83
Device Boot Start End Blocks Id System
/dev/sda1 * 2048 206847 102400 7 HPFS/NTFS/exFAT
/dev/sda2 206848 204818431 102305792 7 HPFS/NTFS/exFAT
/dev/sda3 204818432 409618431 102400000 7 HPFS/NTFS/exFAT
/dev/sda4 409620478 976771071 283575297 f W95 Ext'd (LBA)
/dev/sda5 409620480 614420479 102400000 7 HPFS/NTFS/exFAT
/dev/sda6 614422528 618326015 1951744 83 Linux
/dev/sda7 618328064 626139135 3905536 82 Linux swap / Solaris
/dev/sda8 626141184 976771071 175314944 83 Linux
Thanks in advance
Sanjib
On Thu, Jan 9, 2014 at 11:05 AM, Björn Brandenburg <bbb at mpi-sws.org> wrote:
>
> On 09 Jan 2014, at 04:03, Sanjib Das <cnt.sanjib at googlemail.com> wrote:
>
> > But still I am getting 'kernel panic not syncing vfs unable to mount
> root fs on unknown-block (0,0)'.
>
>
> This typically means one of two things:
>
> - You are missing the driver for the block device that contains your root
> partition.
>
> - You are missing the driver for the file system that your root partition
> is formatted in.
>
> This happens either if you forget to include the driver in your config, or
> if you compile it as a module and forget to boot with the correct initrd
> (or an outdated one).
>
> Regards,
> Björn
>
>
> _______________________________________________
> litmus-dev mailing list
> litmus-dev at lists.litmus-rt.org
> https://lists.litmus-rt.org/listinfo/litmus-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.litmus-rt.org/pipermail/litmus-dev/attachments/20140109/19ebd391/attachment.html>
More information about the litmus-dev
mailing list