<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Again, when you see this type of error, it’s because your kernel expects to find NFS as a module. A module is like a shared library (i.e., *.so) for the OS. Modules are good for general use, but are a pain to work with during Litmus development. We suggest that you avoid them.<div><br></div><div>Module files are denoted with a “.ko” suffix and are located in /lib/modules/<kernel name>/*. That is, modules are stored on the filesystem. In this case, your kernel is looking for the NFS module for your specific kernel in the qcow2.img file. Of course, there are no modules in your image file because you compiled the kernel within your host environment, not the guest environment. To get NFS working, you need to compile NFS support DIRECTLY INTO the kernel—analogous to a static library (i.e., *.a).</div><div><div><div><br></div><div>To do so:</div><div>1) Bring up your compilation configuration with “make menuconfig”</div><div>2) Select “File systems”</div><div>3) Navigate towards the bottom of the list and select “Network File Systems”. Hit space-bar to ensure that there is a “[*]” next to the option.</div><div>4) With “Network File Systems” selected, hit enter/return to select more options.</div><div>5) Enable the NFS features that you need (probably just “NFS client subsystem”, but you can select the others to, just to be safe). Keep hitting space-bar until the item is selected with “<*>”. The “*” means that it will be compiled into the kernel. “<M>” means that the feature will be compiled as a module. Don’t compile as a module!!!! <*> good. <M> bad.</div><div><br></div><div>These instructions should guide you in the right direction, but I don’t have time or ability to replicate your particular system configuration to test them. You may have to spend some more time on your own, perhaps searching google for answers, to finally get things to work. There is no shortage of Linux kernel tutorials online. You can always try googling a particular error code or message. I’m sorry that we don’t have a complete turn-key configuration for Litmus. Unfortunately, Linux doesn’t really either (at least for x86), so it’s all but impossible for us to provide one.</div><div><br></div><div>-Glenn</div><div><br></div><div><br><div><div>On Jan 20, 2014, at 11:45 AM, Sanjib Das <<a href="mailto:cnt.sanjib@googlemail.com">cnt.sanjib@googlemail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div><div><div>Hi,<br></div>here is the last few lines before the login prompt come up using this command <br>"qemu-system-x86_64 -enable-kvm -cpu host -smp 2 -hda /home/sdas/images/ubuntu.<div dir="ltr">
backing.qcow2.img -m 1024 -name "ubuntu-qemu-cjk" -nographic -kernel "/home/sdas/litmus/litmus-rt/arch/x86_64/boot/bzImage" -append "console=ttyS0,115200 root=/dev/hda1" -gdb tcp::12345 -net nic -net user,hostfwd=::2222-:22</div>
"<br><br>OUTPUT::<br><br>modprobe: chdir(3.10.5-litmus2012.2+): No such file or directory<br>Begin: Loading essential drivers ... done.<br>Begin: Running /scripts/init-premount ... done.<br>Begin: Mounting root file system ... Begin: Running /scripts/local-top ... modprobe: chdir(3.10.5-litmus2012.2+): No such file or directory<br>
done.<br>Begin: Running /scripts/local-premount ... done.<br>modprobe: chdir(3.10.5-litmus2012.2+): No such file or directory<br>[ 13.709380] EXT4-fs (hda1): mounted filesystem with ordered data mode. Opts: (null)<br>Begin: Running /scripts/local-bottom ... done.<br>
done.<br>Begin: Running /scripts/init-bottom ... done.<br><br>Last login: Mon Jan 20 10:59:16 EST 2014 on ttyS0<br>Welcome to Ubuntu 11.10 (GNU/Linux 3.10.5-litmus2012.2+ x86_64)<br><br> * Documentation: <a href="https://help.ubuntu.com/">https://help.ubuntu.com/</a><br>
Your Ubuntu release is not supported anymore.<br>For upgrade information, please visit:<br><a href="http://www.ubuntu.com/releaseendoflife">http://www.ubuntu.com/releaseendoflife</a><br><br>New release '12.04.3 LTS' available.<br>
Run 'do-release-upgrade' to upgrade to it.<br><br></div>Thanks in advance <br></div>Sanjib<br><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jan 20, 2014 at 5:36 PM, Sanjib Das <span dir="ltr"><<a href="mailto:cnt.sanjib@googlemail.com" target="_blank">cnt.sanjib@googlemail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>Dear Andea and Glenn,<br><br></div>Thank you very much.<br></div>Now I am able to make an nfs and also share data. but only with the following command <br>
'qemu-system-x86_64 -enable-kvm -cpu host -smp 2 -hda /home/sdas/images/ubuntu.backing.qcow2.img -m 1024 -name "ubuntu-qemu-cjk" -nographic -net nic -net user,hostfwd=::2222-:22'<br>
<br></div>But it use this command "qemu-system-x86_64 -enable-kvm -cpu host -smp 2 -hda /home/sdas/images/ubuntu.backing.qcow2.img -m 1024 -name "ubuntu-qemu-cjk" -nographic -kernel "/home/sdas/litmus/litmus-rt/arch/x86_64/boot/bzImage" -append "console=ttyS0,115200 root=/dev/hda1" -gdb tcp::12345 -net nic -net user,hostfwd=::2222-:22"<br>
<div class="gmail_extra"><br></div><div class="gmail_extra">'modprobe nfs' returns error 'Can't read module /lib/modules........................'<br><br></div><div class="gmail_extra">I guessed I have to use -initrd option in qemu-system-x86_63 command, make bzImage is not creating any initrd or initramfs file.<br>
<br></div><div class="gmail_extra">Any suggestion with cordially accepted. <br><br></div><div class="gmail_extra">Thanks in advance<span class="HOEnZb"><font color="#888888"><br><br></font></span></div><span class="HOEnZb"><font color="#888888"><div class="gmail_extra">
Sanjib<br></div></font></span><div><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">
On Mon, Jan 20, 2014 at 2:48 PM, Andrea Bastoni <span dir="ltr"><<a href="mailto:bastoni@sprg.uniroma2.it" target="_blank">bastoni@sprg.uniroma2.it</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div><p dir="ltr"><br>
On Jan 20, 2014 2:40 PM, "Glenn Elliott" <<a href="mailto:gelliott@cs.unc.edu" target="_blank">gelliott@cs.unc.edu</a>> wrote:<br>
><br>
> Comments inline.<br>
><br>
> On Jan 20, 2014, at 2:17 AM, Sanjib Das <<a href="mailto:cnt.sanjib@googlemail.com" target="_blank">cnt.sanjib@googlemail.com</a>> wrote:<br>
><br>
>> Hi Glenn,<br>
>><br>
>> ssh -p 2222 realtime@localhost Command requires a password, where I gave 'realtime' and is not working.<br>
>> sdas@debian:~$ ssh -p 2222 realtime@localhost<br>
>> realtime@localhost's password:<br>
><br>
><br>
> Well, at least it’s working. It looks like we’ve lost any documentation of the passwords.</p>
</div><p dir="ltr">Hi all,</p><p dir="ltr">Perhaps silly question, but did someone already try root root?</p><p dir="ltr">I believe I initially set up our qemu like that, but they've been reworked quite a bit since that.</p><p dir="ltr">Thanks,<br>
Andrea</p><div><p dir="ltr">> However, you say that you can log in when -vga is working. So do this:<br>
> 1) Boot with -vga. This will dump you into a root-privelged console.<br>
> 2) Do “passwd”<br>
> 3) Pick any password you want for the root user. (You can also reset the password of the “realtime” user if you wish.)<br>
> 4) Shutdown<br>
><br>
>> FYI:"<br>
>><br>
>> kvm -smp 2 -m 512 -boot c -vga std -net nic -net user,hostfwd=tcp::10022-:22 -kernel path_to_kernel/arch/x86/boot/bzImage -append root=/dev/hda1 -hda kvm_image.img<br>
>><br>
>> "<br>
>> also ask for user-name and password, whats exactly i don't know. But if I use -nographic instead of -vga std it doesn't ask for pass.<br>
><br>
><br>
> 5) Now relaunch with “-nographic”. Doing “ssh -p 2222 root@localhost” should now work using the password you set in step #3 above.<br>
><br>
>> And also<br>
>><br>
>> sdas@debian:~$ sudo chmod u+s /usr/local/libexec/qemu-bridge-helper<br>
>> chmod: cannot access `/usr/local/libexec/qemu-bridge-helper': No such file or directory<br>
>> sdas@debian:~$<br>
>><br>
>> It seems to be a bug.<br>
><br>
><br>
> Not a bug. You just don’t have qemu-bridge-helper installed at /usr/local/libexec/. On my 12.x version of Ubuntu, it’s at /usr/lib/qemu-bridge-helper (“> find /usr -name “*qemu*” is a brute force way of searching for a file). I’m not sure about Debian. I found an old bug report that indicates Debian (at least in 2012) may not have it installed (<a href="http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691138" target="_blank">http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691138</a>).<br>
><br>
>> And nfsd output<br>
>> sdas@debian:~$ sudo tail -f /var/log/messages | grep -i 'nfs'<br>
>> Jan 20 07:41:24 debian kernel: <a href="tel:%5B%202768.813543" value="+12768813543" target="_blank">[ 2768.813543</a>] nfsd: last server has exited, flushing export cache<br>
>> Jan 20 07:41:26 debian kernel: [ 2770.506707] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory<br>
>> Jan 20 07:41:26 debian kernel: [ 2770.506741] NFSD: starting 90-second grace period<br>
>><br>
>><br>
>> Thanks in advance<br>
>> Sanjib<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> On Mon, Jan 20, 2014 at 1:19 AM, Glenn Elliott <<a href="mailto:gelliott@cs.unc.edu" target="_blank">gelliott@cs.unc.edu</a>> wrote:<br>
>>><br>
>>><br>
>>> On Jan 19, 2014, at 7:07 PM, Sanjib Das <<a href="mailto:cnt.sanjib@googlemail.com" target="_blank">cnt.sanjib@googlemail.com</a>> wrote:<br>
>>><br>
>>>> Dear Concern,<br>
>>>><br>
>>>> Can any one give me some suggestion about file sharing. Cause I am following the link <a href="https://wiki.litmus-rt.org/litmus/LiblitmusViaNFS" target="_blank">https://wiki.litmus-rt.org/litmus/LiblitmusViaNFS</a> but still not succeeded.<br>
>>>><br>
>>>> I am trying to do this with the following command 'qemu-system-x86_64 -enable-kvm -cpu host -smp 2 -hda /home/sdas/images/ubuntu.backing.qcow2.img -m 1024 -name "ubuntu-qemu-cjk" -nographic -kernel "/home/sdas/litmus/litmus-rt/arch/x86_64/boot/bzImage" -append "console=ttyS0,115200 root=/dev/hda1" -gdb tcp::12345 -net nic -net user,hostfwd=::2222-:22' <br>
>>>><br>
>>>> And as a result eth0 in side the guest is configured automatically <br>
>>>><br>
>>>> From guest to host 'ping 10.0.2.2' is working<br>
>>>> "root@ubuntu-qemu:~# ping 10.0.2.2<br>
>>>> PING 10.0.2.2 (10.0.2.2) 56(84) bytes of data.<br>
>>>> 64 bytes from <a href="http://10.0.2.2/" target="_blank">10.0.2.2</a>: icmp_req=1 ttl=255 time=2.28 ms<br>
>>>> 64 bytes from <a href="http://10.0.2.2/" target="_blank">10.0.2.2</a>: icmp_req=2 ttl=255 time=0.515 ms<br>
>>>> ^C<br>
>>>> --- 10.0.2.2 ping statistics ---<br>
>>>> 2 packets transmitted, 2 received, 0% packet loss, time 1001ms<br>
>>>> rtt min/avg/max/mdev = 0.515/1.398/2.281/0.883 ms<br>
>>>> root@ubuntu-qemu:~# <br>
>>>> "<br>
>>>> But Host to guest 'ping 10.0.2.15' not working<br>
>>>><br>
>>>> "sdas@debian:~$ ping 10.0.2.15<br>
>>>> PING 10.0.2.15 (10.0.2.15) 56(84) bytes of data.<br>
>>>> ^C<br>
>>>> --- 10.0.2.15 ping statistics ---<br>
>>>> 2 packets transmitted, 0 received, 100% packet loss, time 1006ms<br>
>>>><br>
>>>> sdas@debian:~$ <br>
>>>> "<br>
>>>><br>
>>>> ip route guest :<br>
>>>> root@ubuntu-qemu:~# ip route<br>
>>>> default via 10.0.2.2 dev eth0 metric 100 <br>
>>>> <a href="http://10.0.2.0/24" target="_blank">10.0.2.0/24</a> dev eth0 proto kernel scope link src 10.0.2.15 <br>
>>>> root@ubuntu-qemu:~# <br>
>>>><br>
>>>><br>
>>>> ip route host:<br>
>>>><br>
>>>> sdas@debian:~$ ip route<br>
>>>> default via 192.168.0.1 dev eth0 <br>
>>>> <a href="http://169.254.0.0/16" target="_blank">169.254.0.0/16</a> dev eth0 scope link metric 1000 <br>
>>>> <a href="http://192.168.0.0/24" target="_blank">192.168.0.0/24</a> dev eth0 proto kernel scope link src 192.168.0.101 <br>
>>>> sdas@debian:~$ <br>
>>>><br>
>>>> my host is debian 7 wheezy.<br>
>>>><br>
>>>> Any quick suggestion/ alternate tutorial / link/ will very helpful.<br>
>>><br>
>>><br>
>>><br>
>>> I don’t believe that direct network access from the host to the guest is necessary to get NFS to work. With respect to host->guest networking, you can ssh into the guest OS by doing “ssh -p 2222 realtime@localhost”. If you want to set up a virtual network, I believe these instructions will be useful: <a href="http://wiki.qemu.org/Features/HelperNetworking" target="_blank">http://wiki.qemu.org/Features/HelperNetworking</a><br>
>>><br>
>>> Anyway, assuming that your NFS server on the host is working and your guest can ping the host, I believe your guest OS should be able to mount the host’s network drive. You’ve already shown that the guest can ping the host. Are you sure NFS is working on the host? What do the NFS logs say?<br>
>>><br>
>>> -Glenn<br>
>>><br>
>>><br>
>>> _______________________________________________<br>
>>> litmus-dev mailing list<br>
>>> <a href="mailto:litmus-dev@lists.litmus-rt.org" target="_blank">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>
>>><br>
>><br>
>> _______________________________________________<br>
>> litmus-dev mailing list<br>
>> <a href="mailto:litmus-dev@lists.litmus-rt.org" target="_blank">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>
><br>
><br>
><br>
> _______________________________________________<br>
> litmus-dev mailing list<br>
> <a href="mailto:litmus-dev@lists.litmus-rt.org" target="_blank">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>
><br>
</p>
</div><br>_______________________________________________<br>
litmus-dev mailing list<br>
<a href="mailto:litmus-dev@lists.litmus-rt.org" target="_blank">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>
<br></blockquote></div><br></div></div></div></div>
</blockquote></div><br></div>
_______________________________________________<br>litmus-dev mailing list<br><a href="mailto:litmus-dev@lists.litmus-rt.org">litmus-dev@lists.litmus-rt.org</a><br>https://lists.litmus-rt.org/listinfo/litmus-dev<br></blockquote></div><br></div></div></div></body></html>