Also see this answer of Avadh, if it helps:


On Sat, Aug 27, 2011 at 11:09 AM, avadh patel <[email protected]> wrote:
I noticed that you tried to run 'create_checkpoint' script on '.img' (raw
image) file. Checkpoints are only supported in '.qcow2' images.
You can convert from .img to .qcow using 'qemu-img' which will be in 'qemu/'
folder.

Once the checkpoints are created, you can confirm its available by running
following command:
   $ qemu-img info your_qcow2_file

It will list the available checkpoints/snapshots in the qcow2 image.
These scripts use old parameters to create a checkpoint which is slow. You
need to use 'cache=unsafe' option to create/load checkpoints faster.
I have uploaded new scripts on github that reflects this change.

- Avadh





On Thu, Sep 1, 2011 at 9:11 AM, mihai pricopi <[email protected]>wrote:

> Hi,
>
>  I am new with marssx86 simulator and I want to run the
> create_checkpoints.py script. I keep getting this error and I don't
> understand what is wrong:
>
> python scripts/create_checkpoints.py
> Execution command:  /home/mihai/work/marss/qemu/qemu-system-x86_64 -m 1024
> -serial pty -vnc :20 -cpu singleCore -drive
> file=/home/mihai/work/marss/disk_images/parsecROI.img
> Number of Chekcpoints to create: 1
> Starting QEMU for checkpoint: blackscholes
> initing the ooomachine
> char device redirected to /dev/pts/3
> Traceback (most recent call last):
>   File "scripts/create_checkpoints.py", line 445, in <module>
>     pty_to_stdout(pty_term, ':')
>   File "scripts/create_checkpoints.py", line 410, in pty_to_stdout
>     chr = os.read(fd, 1)
> OSError: [Errno 5] Input/output error
>
>  Can you help please ?
>
> Thanks
>
> _______________________________________________
> http://www.marss86.org
> Marss86-Devel mailing list
> [email protected]
> https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel
>
>
_______________________________________________
http://www.marss86.org
Marss86-Devel mailing list
[email protected]
https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel

Reply via email to