Hello Wouter, Thank you for your input.
I replayed the test as follows: -> qemu-nbd -p 2000 -persist /root/qemu/q1.img & -> nbd-client localhost 2000 /dev/nbd0 -> echo reboot >/sys/power/disk -> echo disk >/sys/power/state The "reboot" is a handy way to test, as it goes through the complete hibernate cycle and returns to the prompt. In this case the client DID try to reconnect as you suggest, however the 'qemu-nbd' server side had exited, so no go. Regards, Mark T. On 9/21/13 2:59 AM, "Wouter Verhelst" <[email protected]> wrote: >On 20-09-13 20:00, Mark Trumpold wrote: >> Stefan, >> >> So, I tried the following: >> >> -> qemu-nbd -p 2000 /root/qemu/q1.img & >> -> nbd-client localhost 2000 /dev/nbd0 & > >That won't work. nbd-client will only try the reconnect thing if you use >the "-persist" option. > >Also, nbd-client will do a fork(), so the & isn't necessary. > >-- >This end should point toward the ground if you want to go to space. > >If it starts pointing toward space you are having a bad problem and you >will not go to space today. > > -- http://xkcd.com/1133/ > ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk _______________________________________________ Nbd-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nbd-general
