<div dir="ltr"><div><div><div><div><div>Dear Concern, <br><br></div>Thank you for the reply. Now its booting but its not connecting with network with the following command.<br><br>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<br>
<br></div>There was an error while booting the qemu image:<br><br>* Starting AppArmor profiles Cache read/write disabled: /sys/kernel/security/apparmor/features interface file missing. (Kernel needs AppArmor 2.4 compatibility patch.)<br>
Cache read/write disabled: /sys/kernel/security/apparmor/features interface file missing. (Kernel needs AppArmor 2.4 compatibility patch.)<br>Warning from /etc/apparmor.d/usr.sbin.tcpdump (/etc/apparmor.d/usr.sbin.tcpdump line 64): profile /usr/sbin/tcpdump network rules not enforced<br>
Warning from /etc/apparmor.d/sbin.dhclient (/etc/apparmor.d/sbin.dhclient line 73): profile /sbin/dhclient network rules not enforced<br><br><br></div>and also here is the output of fdisk -l command <br><br>Disk /dev/sda: 500.1 GB, 500107862016 bytes<br>
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors<br>Units = sectors of 1 * 512 = 512 bytes<br>Sector size (logical/physical): 512 bytes / 512 bytes<br>I/O size (minimum/optimal): 512 bytes / 512 bytes<br>
Disk identifier: 0x000a0e83<br><br> Device Boot Start End Blocks Id System<br>/dev/sda1 * 2048 206847 102400 7 HPFS/NTFS/exFAT<br>/dev/sda2 206848 204818431 102305792 7 HPFS/NTFS/exFAT<br>
/dev/sda3 204818432 409618431 102400000 7 HPFS/NTFS/exFAT<br>/dev/sda4 409620478 976771071 283575297 f W95 Ext'd (LBA)<br>/dev/sda5 409620480 614420479 102400000 7 HPFS/NTFS/exFAT<br>
/dev/sda6 614422528 618326015 1951744 83 Linux<br>/dev/sda7 618328064 626139135 3905536 82 Linux swap / Solaris<br>/dev/sda8 626141184 976771071 175314944 83 Linux<br><br><br><br>
</div>Thanks in advance <br><br></div>Sanjib<br><div><div><div><br><br><div><div><div><div><br></div></div></div></div></div></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jan 9, 2014 at 11:05 AM, Björn Brandenburg <span dir="ltr"><<a href="mailto:bbb@mpi-sws.org" target="_blank">bbb@mpi-sws.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"><br>
On 09 Jan 2014, at 04:03, Sanjib Das <<a href="mailto:cnt.sanjib@googlemail.com">cnt.sanjib@googlemail.com</a>> wrote:<br>
<br>
> But still I am getting 'kernel panic not syncing vfs unable to mount root fs on unknown-block (0,0)'.<br>
<br>
<br>
</div>This typically means one of two things:<br>
<br>
- You are missing the driver for the block device that contains your root partition.<br>
<br>
- You are missing the driver for the file system that your root partition is formatted in.<br>
<br>
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).<br>
<br>
Regards,<br>
Björn<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
_______________________________________________<br>
litmus-dev mailing list<br>
<a href="mailto:litmus-dev@lists.litmus-rt.org">litmus-dev@lists.litmus-rt.org</a><br>
<a href="https://lists.litmus-rt.org/listinfo/litmus-dev" target="_blank">https://lists.litmus-rt.org/listinfo/litmus-dev</a><br>
</div></div></blockquote></div><br></div>