<div class="gmail_quote">On 25 Mar 2015 21:09, "Priyanka Naik" <<a href="mailto:prnk.nk1@gmail.com">prnk.nk1@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">That is fine that I should provide u with log files but my guest does not scroll bcoz of which I m nt able to see the errors and not even able to take that file out of guest.</p>
<p dir="ltr">So he suggested me the way of mounting my vdisk.img but the steps as I told you gave me errors. So I m unable to proceed.</p>
<div class="gmail_quote">On 25 Mar 2015 21:01, "Christopher Covington" <<a href="mailto:cov@codeaurora.org" target="_blank">cov@codeaurora.org</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Priyanka,<br>
<br>
On 03/24/2015 01:31 AM, Priyanka Naik wrote:<br>
> I m running a sample process on my host machine and dumping it on the host. If<br>
> i try to restore the process on the host OS, the process gets restored back<br>
> successfully. But now I m tarring my dumped files directory into a .tgz file<br>
> and sending it to guest using virtIO serial as the medium of transfer. The<br>
> transfer of dumped files take place successfully as I m checking the hash<br>
> values of both the files using md5sum. I m untarring it on guest and trying to<br>
> restore it back on the guest system but due to some reasons we are unable to<br>
> restore it back on the guest system.<br>
<br>
Perhaps file transfer over serial is more useful to you, but in my environment<br>
I've found the 9P passthrough filesystem to be the easiest way to transfer files.<br>
<br>
<a href="http://www.linux-kvm.org/page/9p_virtio" target="_blank">http://www.linux-kvm.org/page/9p_virtio</a><br>
<a href="http://wiki.qemu.org/Documentation/9psetup" target="_blank">http://wiki.qemu.org/Documentation/9psetup</a><br>
<br>
(If you want a 9P *rootfs*, which is what I use, you'll need the following in<br>
your kernel command line:<br>
<br>
rootfstype=9p rootflags=trans=virtio,version=9p2000.L<br>
<br>
You'll also need to use the mount tag "/dev/root" and/or add<br>
"root=<mount_tag>" to the kernel command line.)<br>
<br>
> Firstly to start the guest we are using following command :<br>
><br>
> qemu-system-x86_64 -m 1024 -s -hda vdisk.img -kernel<br>
> /usr/src/linux-3.17.6/arch/x86_64/boot/bzImage -initrd<br>
> /home/priyanka/tmp2/newinitrd.img -append "root=/dev/sda10" -name myguest<br>
> -device virtio-serial -chardev socket,path=/tmp/foo,server,nowait,id=foo<br>
> -device virtserialport,chardev=foo,name=org.fedoraproject.port.0<br>
><br>
> Now once we boot the system and type the tty command on the guest we get<br>
> /dev/console and if we type tty on host it gives output as /dev/pts/no i.e.<br>
> some number associated with that terminal. We checked with the code of tty.c<br>
> which has facilities for both PTS and CONSOLE. But we are not getting the<br>
> exact reason for criu not working on guest, since we are creating exact copy<br>
> of the kernel on host system, the guest should have all the facilities<br>
> required for criu since criu is working on host.<br>
><br>
> And as Cyrill said that we need /dev/ptmx on guest, so it is present. Even<br>
> /dev/pts/ptmx is present.<br>
><br>
> What can be the problems on guest side which will make our project work? What<br>
> is exactly going wrong?<br>
<br>
You may be able to work around the issue by redirecting STDIN, STDOUT, and<br>
STDERR from and to files. That's what I've been doing on ARM where ttyAMA (ARM<br>
PL011 serial) hasn't historically been supported (although maybe that's been<br>
fixed now). Example:<br>
<br>
app /share/suite/app/input < /dev/null &> app.log &<br>
<br>
The full log that Pavel was talking about (contents of logfile from `criu -v4<br>
> logfile` or criu -v4 -o logfile`) would have details about what exactly is<br>
going wrong.<br>
<br>
Hope that helps,<br>
Chris<br>
<br>
--<br>
Qualcomm Innovation Center, Inc.<br>
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,<br>
a Linux Foundation Collaborative Project<br>
</blockquote></div>
</blockquote></div>