All of lore.kernel.org
 help / color / mirror / Atom feed
From: Valtteri Kiviniemi <valtteri.kiviniemi@dataproof.fi>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Re: [PATCH] xen: register timer interrupt with	IRQF_TIMER
Date: Tue, 24 Nov 2009 16:23:21 +0200	[thread overview]
Message-ID: <4B0BEC59.10101@dataproof.fi> (raw)
In-Reply-To: <4B0BEA33.7080603@dataproof.fi>

Hi,

I can confirm that save works, but restore does not work. It will 
restore the domU, but the domU wont respond to anything. In the console 
I can see

root@xen:/# xm console db
Using V2 grant tables.

And then its stuck, cant login.

xend.log from restore:

[2009-11-24 16:20:11 14312] DEBUG (balloon:181) Balloon: 16069048 KiB 
free; need 1048576; done.
[2009-11-24 16:20:11 14312] DEBUG (XendCheckpoint:305) [xc_restore]: 
/usr/lib/xen/bin/xc_restore 4 2 1 2 0 0 0 0
[2009-11-24 16:20:11 14312] INFO (XendCheckpoint:424) xc_domain_restore 
start: p2m_size = 40000
[2009-11-24 16:20:11 14312] INFO (XendCheckpoint:424) Reloading memory 
pages:   0%
[2009-11-24 16:20:48 14312] INFO (XendCheckpoint:424) ERROR Internal 
error: Error when reading batch size
[2009-11-24 16:20:48 14312] INFO (XendCheckpoint:424) ERROR Internal 
error: error when buffering batch, finishing
[2009-11-24 16:20:48 14312] INFO (XendCheckpoint:424)
[2009-11-24 16:20:48 14312] INFO (XendCheckpoint:4100%
[2009-11-24 16:20:48 14312] INFO (XendCheckpoint:424) Memory reloaded (0 
pages)
[2009-11-24 16:20:48 14312] INFO (XendCheckpoint:424) read VCPU 0
[2009-11-24 16:20:48 14312] INFO (XendCheckpoint:424) read VCPU 1
[2009-11-24 16:20:48 14312] INFO (XendCheckpoint:424) read VCPU 2
[2009-11-24 16:20:48 14312] INFO (XendCheckpoint:424) read VCPU 3
[2009-11-24 16:20:48 14312] INFO (XendCheckpoint:424) read VCPU 4
[2009-11-24 16:20:48 14312] INFO (XendCheckpoint:424) read VCPU 5
[2009-11-24 16:20:48 14312] INFO (XendCheckpoint:424) read VCPU 6
[2009-11-24 16:20:48 14312] INFO (XendCheckpoint:424) read VCPU 7
[2009-11-24 16:20:48 14312] INFO (XendCheckpoint:424) Completed 
checkpoint load
[2009-11-24 16:20:48 14312] INFO (XendCheckpoint:424) Domain ready to be 
built.
[2009-11-24 16:20:48 14312] INFO (XendCheckpoint:424) Restore exit with rc=0
[2009-11-24 16:20:48 14312] DEBUG (XendCheckpoint:395) store-mfn 4037254
[2009-11-24 16:20:48 14312] DEBUG (XendCheckpoint:395) console-mfn 4037253
[2009-11-24 16:20:48 14312] DEBUG (XendDomainInfo:2883) 
XendDomainInfo.completeRestore



- Valtteri Kiviniemi

Valtteri Kiviniemi kirjoitti:
> Hi,
> 
> Ok, sorry didn not notice that. my domU kernels are quite small, they 
> dont contain anything that is not necessary and since power management 
> options were not necessary on Xen 3.4 I did not enable them on unstable 
> either. Gonna now compile new domU kernels and test again.
> 
> Thanks.
> 
> - Valtteri Kiviniemi
> 
> Ian Campbell kirjoitti:
>> On Tue, 2009-11-24 at 12:51 +0000, Valtteri Kiviniemi wrote:
>>> Hi,
>>>
>>> This is not still working, when I try to save a domain:
>>>
>>> file:
>>>
>>> root@xen:/# du -h db.save
>>> 64K     db.save
>>>
>>> domU console.
>>>
>>> Ignoring shutdown request: suspend
>>
>> As I said before - enable CONFIG_PM_SLEEP, you won't get anywhere
>> without it.
>>
>> Ian.
>>
>>> xend.log:
>>>
>>> [2009-11-24 14:47:57 2131] DEBUG (XendCheckpoint:124) [xc_save]: 
>>> /usr/lib/xen/bin/xc_save 54 1 0 0 0
>>> [2009-11-24 14:47:57 2131] INFO (XendCheckpoint:424) xc_save: failed 
>>> to get the suspend evtchn port
>>>
>>> domU config:
>>>
>>> kernel = "/boot/bzImage-domU"
>>> builder = "linux"
>>> memory = "1024"
>>> name = "db"
>>> vcpus = "8"
>>> cpus = [ "0", "1", "2", "3", "4", "5", "6", "7" ]
>>> tsc_native="1"
>>> vif = [ "mac=00:50:56:13:27:d9, bridge=eth0" ]
>>> disk = [ "phy:/dev/virtuals/db,xvda1,w" ]
>>> root = "/dev/xvda1 ro"
>>> extra = "console=hvc0"
>>> on_poweroff = "destroy"
>>> on_reboot = "restart"
>>> on_crash = "restart"
>>>
>>> Latest xen-unstable (compiled 1 hour ago) latest 2.6.31.6 kernel with 
>>> this patch applied.
>>>
>>> - Valtteri Kiviniemi
>>>
>>> Ian Campbell kirjoitti:
>>>> On Tue, 2009-11-24 at 10:16 +0000, Ian Campbell wrote:
>>>>> Otherwise the timer is disabled by dpm_suspend_noirq() which in 
>>>>> turn prevents
>>>>> correct operation of stop_machine on multi-processor systems and 
>>>>> breaks
>>>>> suspend.
>>>> This appears to have been broken since after 2.6.29 sometime (I see
>>>> failures with 2.6.30). I suspect this commit, or one related to it, 
>>>> made
>>>> IRQF_TIMER a hard requirement:
>>>>
>>>>         commit 0a0c5168df270a50e3518e4f12bddb31f8f5f38f
>>>>         Author: Rafael J. Wysocki <rjw@sisk.pl>
>>>>         Date:   Mon Mar 16 22:33:49 2009 +0100
>>>>                     PM: Introduce functions for suspending and 
>>>> resuming device interrupts
>>>>                         Introduce helper functions allowing us to 
>>>> prevent device drivers from
>>>>             getting any interrupts (without disabling interrupts on 
>>>> the CPU)
>>>>             during suspend (or hibernation) and to make them start 
>>>> to receive
>>>>             interrupts again during the subsequent resume.  These 
>>>> functions make it
>>>>             possible to keep timer interrupts enabled while the 
>>>> "late" suspend and
>>>>             "early" resume callbacks provided by device drivers are 
>>>> being
>>>>             executed.  In turn, this allows device drivers' "late" 
>>>> suspend and
>>>>             "early" resume callbacks to sleep, execute ACPI 
>>>> callbacks etc.
>>>>                         The functions introduced here will be used 
>>>> to rework the handling of
>>>>             interrupts during suspend (hibernation) and resume.  
>>>> Namely,
>>>>             interrupts will only be disabled on the CPU right before 
>>>> suspending
>>>>             sysdevs, while device drivers will be prevented from 
>>>> receiving
>>>>             interrupts, with the help of the new helper function, 
>>>> before their
>>>>             "late" suspend callbacks run (and analogously during 
>>>> resume).
>>>>
>>>> Ian.
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Xen-devel mailing list
>>>> Xen-devel@lists.xensource.com
>>>> http://lists.xensource.com/xen-devel
>>
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
> 

      reply	other threads:[~2009-11-24 14:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-24 10:16 [PATCH] xen: register timer interrupt with IRQF_TIMER Ian Campbell
2009-11-24 10:41 ` Ian Campbell
2009-11-24 12:51   ` Valtteri Kiviniemi
2009-11-24 13:11     ` Ian Campbell
2009-11-24 14:14       ` Valtteri Kiviniemi
2009-11-24 14:23         ` Valtteri Kiviniemi [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B0BEC59.10101@dataproof.fi \
    --to=valtteri.kiviniemi@dataproof.fi \
    --cc=Ian.Campbell@citrix.com \
    --cc=jeremy@goop.org \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.