Sorry if this is a stupid question, but are you saying that all HVM
guests are now resumable and there no longer needs to be any check for
that as was done by Brendan Cully's earlier patch requests?
If that's the case, there's something going on for me. I've tried to
different HVM guests (a Debian installation and a Damn Small Linux
Live CD) and after checkpointing, the guests seem to get lodged in a
strange state. I can no longer access the guest's console via VNC and
the state is reported by xend as "------". Any ideas?
Thanks!
Mike
On Fri, Sep 12, 2008 at 6:54 AM, Keir Fraser <keir.fraser@xxxxxxxxxxxxx> wrote:
> Actually it seems to work okay for me with or without PV drivers.
> xc_domain_resume() was long ago (pre-3.1) fixed to support any HVM guest.
>
> -- Keir
>
> On 12/9/08 07:10, "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx> wrote:
>
>> xc_domain_resume_any() should be doing just DOMCTL_resumedomain if called on
>> an HVM guest, rather than exiting with an error. Should be easy to fix.
>>
>> -- Keir
>>
>> On 12/9/08 03:29, "Mike Sun" <msun@xxxxxxxxxx> wrote:
>>
>>> Hi,
>>>
>>> I'm working off of the 3.1 branch. I am having problems performing an
>>> "xm save -c" on an HVM domain. The checkpoint works fine, but the HVM
>>> domain is then left in a corrupt state. I know that Brendan Cully had
>>> submitted patches that would check to see if the domain was resumable
>>> first. Did these patches make it upstream? More basically, I don't
>>> actually understand what deems a domain resumable or not....?
>>>
>>> Thanks,
>>> Mike
>>>
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>>> http://lists.xensource.com/xen-devel 
>>
>
>
>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel