Hi Cansu, In the released CloudSuite images, there is no such the os disk. So, we did not point the os path.
Best regards, Jeongseob 2014-06-30 5:59 GMT+09:00 Cansu Kaynak <[email protected]>: > Dear Jeongseob and Wang, > > Thanks for pointing this out. I will fix it in the guide. > > The first path in the Simics file typically points to the OS image, like: > > checkpoint_path: ( “/path/to/os_disk”, >>> >>> “/path/to/binary_disk”, >>> >> “/path/to/media_streaming_data”, >>> “/path/to/cloudsuite/images/streaming/4cpu”) >>> >> So, there is no need to replicate the binary disk path twice. > > > -- > Cansu > > On 23 Jun 2014, at 12:07, J Ahn <[email protected]> wrote: > > There are two mistakes in the guideline ( > http://parsa.epfl.ch/simflex/doc/deploy_cloudsuite.pdf). > Firstly, as Wang mentioned earlier, the checkpoint_path is incorrect. It > produces the error output as follows. > > ------------------------------------------------------------------------------------------------------ > [error] setting attribute files in besim_sd0_image: > Error opening file /slice.1: No such file or directory > Error while loading a configuration: Failed to initialize all objects > This has left the configuration system in an inconsistent state. > Restarting Simics is recommended. > Failed to initialize all objects > Failed reading configuration > simics> > > ------------------------------------------------------------------------------------------------------ > To fix the problem, we should fix the path like below. > > checkpoint_path: ("/home/flexus/datasets/binary_disk", > "/home/flexus/datasets/binary_disk", > "/home/flexus/datasets/nutch-disks", > "/home/flexus/workloads/nutch/1cpu") > > Secondly, there is no 'save-configuration' command in Simics 3.0.31. We > need to replace 'save-configuration' with 'write-configuration' to create > initial checkpoint as phase_000. > > > > 2014-06-20 18:08 GMT+09:00 J Ahn <[email protected]>: > >> Hi Wang >> >> You mean that I need to replace the OS path with the binary_disk path? >> I do not understand why the binary_disk path should be duplicated. >> >> >> >> 2014-06-20 17:03 GMT+09:00 Wangjintang <[email protected]>: >> >> For you reference >>> >>> checkpoint_path: ( >>> >>> "/home/mainsd/datasets/binary_disk", >>> >>> "/home/mainsd/datasets/binary_disk", >>> >>> "/home/mainsd/datasets/data_analysis_data", >>> >>> "/home/mainsd/workloads/classification/1cpu") >>> >>> >>> >>> >>> >>> Best Regards, >>> >>> Wang jintang / Jed >>> >>> >>> >>> <image001.jpg> >>> >>> >>> >>> Huawei Technologies Co., Ltd. >>> >>> Email: [email protected] >>> >>> Building Z8, Huawei R&D center, Jiangshu Rd 360, Binjiang >>> District,Hangzhou 310051, P.R.China >>> >>> http://www.huawei.com >>> >>> >>> >>> *From:* J Ahn [mailto:[email protected]] >>> *Sent:* Friday, June 20, 2014 3:42 PM >>> *To:* [email protected] >>> *Subject:* Running cloudsuite on Flexus >>> >>> >>> >>> Hi all, >>> >>> As the guidelines using the released Simics images, the path for OS >>> image disappeared as follows. >>> >>> checkpoint_path: ( “”, >>> “/path/to/binary_disk”, >>> “/path/to/media_streaming_data”, >>> “/path/to/cloudsuite/images/streaming/4cpu”) >>> >>> >>> >>> Is there any potential problem to simulate the system? and I am just >>> wondering why the OS image is not included in the released images. >>> >>> - Jeongseob >>> >>> >>> >> >> > >
