Re: [Xen-users] DomU suspension/hibernation

[Joshua Tuttle <jtuttle@xxxxxxxxx>]

________________________________________
From: Ian Murray
Sent: Tuesday, June 18, 2013 3:46 PM
To: Joshua Tuttle
Cc: xen-users@xxxxxxxxxxxxx
Subject: Re: [Xen-users] DomU suspension/hibernation

On 18/06/13 20:36, Joshua Tuttle wrote:
>
> -----Original Message-----
> From: Ian Murray [mailto:murrayie@xxxxxxxxxxx]
> Sent: Tuesday, June 18, 2013 3:19 PM
> To: Joshua Tuttle
> Cc: xen-users@xxxxxxxxxxxxx
> Subject: Re: [Xen-users] DomU suspension/hibernation
>
> On 18/06/13 19:44, Joshua Tuttle wrote:
>> -----Original Message-----
>> From: xen-users-bounces@xxxxxxxxxxxxx
>> [mailto:xen-users-bounces@xxxxxxxxxxxxx] On Behalf Of Ian Murray
>> Sent: Tuesday, June 18, 2013 1:56 PM
>> To: xen-users@xxxxxxxxxxxxx
>> Subject: Re: [Xen-users] DomU suspension/hibernation
>>
>> On 18/06/13 16:42, Joshua Tuttle wrote:
>>> -----Original Message-----
>>> From: Ian Campbell [mailto:Ian.Campbell@xxxxxxxxxx]
>>> Sent: Tuesday, June 18, 2013 11:33 AM
>>> To: Joshua Tuttle
>>> Cc: xen-users@xxxxxxxxxxxxx
>>> Subject: Re: [Xen-users] DomU suspension/hibernation
>>>
>>> On Tue, 2013-06-18 at 15:16 +0000, Joshua Tuttle wrote:
>>>> Hey,
>>>>
>>>>
>>>>
>>>> I thought there was supposed to be an ability for domU’s to be put
>>>> into a hibernated state (E.g. current running tasks and memory) when
>>>> dom0 is shutdown or rebooted. When
>>>>
>>>> I look in my /etc/default/xendomains file, I have the variable’s
>>>> “XENDOMAINS_SAVE=/var/lib/xen/save” and “XENDOMAINS_RESTORE=true”.
>>>> However, when I reboot, I always have
>>>>
>>>> to restart my domains manually and their state was not saved.
>>>> My current configuration is as follows: Xen 4.2.1, dom0: Debian 7.0,
>>>> domU:Debian 7.0, dom0 kernel 3.2.0-4
>>> Are you using the Debian packages or Xen compiled from source?
>>>
>>> Which toolstack are you using?
>>>
>>> If you installed from source, did you enable the xendomains script
>>> when you did so? (by invoking update-rc.d or something equivalent)
>>>
>>> Does manually running xendomains ("service xendomains stop" then "service 
>>> xendomains start") produce any output?
>>>
>>> Ian.
>>>
>>>
>>> I am using Xen compiled from source. 4.2.1 and the XL toolstack.
>>> I ran update rc.d on xecommons, xend, xendomains, xen-watchdog.
>>> Xend can probably be disabled, I'm not sure if having it running would be 
>>> causing a problem.
>>> Manually stopping xendomains produces a line that confirms xendomains is 
>>> stopped.
>>> Starting xendomains produces no output, but I check the service with "xl 
>>> list"
>>>
>>>
>> Have a read of http://osdir.com/ml/general/2013-05/msg46973.html and see if 
>> this is the same issue (sorry for not linking directly to Xen, Google seems 
>> to link to the wrong message when I follow its links).
>>
>> If it is the same issue, then a patch has been submitted and accepted which 
>> I believe is destined for 4.3. Also, there was an issue around the regex 
>> stuff which got cleared up by a previous patch that I traced back to yaji 
>> (maybe!). I don't know when the other fix came in, so you may need to go to 
>> 4.22 to apply the linked patch.
>>
>>
>>
>> Thanks for replying.
>>
>> I applied a patch " hotplug/Linux: xendomains compatibility with xl" , but 
>> still have had no luck. The only thing it fixed, is if I place a symlink to 
>> my config file in /etc/xen/auto, it will automatically start the domU 
>> instance. However, its still not putting a previous instance into a 
>> hibernated state.
>>
> I think that is the same patch I linked... which is odd because it isn't 
> supposed to fix an auto issue. I don't recall in issue for that myself.
> Did you patch against 4.2.2 or 4.2.1? If it is the yaji/regex issue then I 
> think that would have caused issue against stopping rather than restarting, 
> as it has issue with xl list -l, AFAIR.
>
> I presume the save file gets created, but just incase, please try:-
>
>
> (Assuming you have a domU running)
> root@xen6:/var/lib/xen/save# service xendomains stop Shutting down Xen 
> domains: vpn2(save)....
>    *   [done]
> root@xen6:/var/lib/xen/save# ls /var/lib/xen/save
> vpn2
> root@xen6:/var/lib/xen/save# service xendomains start Restoring Xen domains: 
> vpn2
>    *   [done]
> root@xen6://var/lib/xen/save# ls /var/lib/xen/save 
> root@xen6://var/lib/xen/save#
>
> for me, it is gone on the second ls.
>
> If it is still there, what happens if you manually reload it with:-
>
> xl restore /var/lib/xen/save/vpn2 (in my case)
>
>
>
>
> I applied it against 4.2.1. When I run "service xendomains stop" I receive 
> the following output:
>
> An error occurred while saving domain:
> Option `1' not supported.
> 'xl save' requires at least 2 arguments.
>
> !
> (shut)
> An error occurred while shutting down domain:
>
> !
> SHUTDOWN_ALL
> An error occurred while shutting down all domains:
>
> !
> [ ok ] [done].
>
>
>
>
>
> ________________________________
> This message and all attachments are PRIVATE, and contain information that is 
> PROPRIETARY to Intelligent Automation, Inc. You are not authorized to 
> transmit or otherwise disclose this message or any attachments to any third 
> party whatsoever without the express written consent of Intelligent 
> Automation, Inc. If you received this message in error or you are not willing 
> to view this message or any attachments on a confidential basis, please 
> immediately delete this email and any attachments and notify Intelligent 
> Automation, Inc.
Is this different behaviour now because you said that part was working
earlier?

What is the output of xl list -l ? I think this is the command
xendomains uses to generate the list to shutdown.

Unfortunately, you are not in the territory I thought you were.





This is my output:

(domain
        (domid -1)
        (create_info)
        (hvm 1)
        (hap <default>)
        (oos <default>)
        (ssidref 0)
        (name joshtest)
        (uuid <unknown>)
        (cpupool Pool-0)
        (xsdata (null))
        (platformdata (null))
        (build_info)
        (max_vcpus 1)
        (tsc_mode default)
        (max_memkb 1048576)
        (target_memkb 1048576)
        (nomigrate <default>)
        (image
                (hvm
                        (firmware (null))
                        (video_memkb -1)
                        (shadow_memkb 9216)
                        (pae <default>)
                        (apic <default>)
                        (acpi True)
                        (nx <default>)
                        (viridian <default>)
                        (hpet <default>)
                        (vpt_align <default>)
                        (timer_mode (null))
                        (nestedhvm <default>)
                        (stdvga False)
                        (vnc True)
                        (vnclisten 0.0.0.0)
                        (vncdisplay 0)
                        (vncunused <default>)
                        (keymap (null))
                        (sdl False)
                        (opengl <default>)
                        (nographic <default>)
                        (spice <default>)
                        (spiceport 0)
                        (spicetls_port 0)
                        (spicehost (null))
                        (spicedisable_ticketing <default>)
                        (spiceagent_mouse <default>)
                        (device_model default)
                        (gfx_passthru <default>)
                        (serial pty)
                        (boot (null))
                        (usb <default>)
                        (usbdevice mouse)
                )
        )
        (device
                (tap
                        (backend_domid 0)
                        (frontend_domid -1)
                        (physpath /home/josh/domu1.img)
                        (phystype 0)
                        (virtpath hda)
                        (unpluggable 0)
                        (readwrite 1)
                        (is_cdrom 0)
                )
        )
)



________________________________
This message and all attachments are PRIVATE, and contain information that is 
PROPRIETARY to Intelligent Automation, Inc. You are not authorized to transmit 
or otherwise disclose this message or any attachments to any third party 
whatsoever without the express written consent of Intelligent Automation, Inc. 
If you received this message in error or you are not willing to view this 
message or any attachments on a confidential basis, please immediately delete 
this email and any attachments and notify Intelligent Automation, Inc.


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users