All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jérôme Petazzoni" <jp@enix.org>
To: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: More Xen troubles (with xend this time)
Date: Tue, 30 Nov 2004 18:14:09 +0100	[thread overview]
Message-ID: <41ACAA61.2090105@enix.org> (raw)
In-Reply-To: <E1CZBOE-0002vo-00@mta1.cl.cam.ac.uk>


>>But if the restore operation crashes xend, I will never be able to get a 
>>crash dump - unless there's another way to get the information ?
>>    
>>
>
>Put '-c' on the restore command line to connect to the console.
>  
>
I tried that, but it just dumps the domain config in SXP format, and 
then stops (see below).

>>If I don't use save/restore/migrate, can I expect Xen to be
>>stable ? 
>>    
>>
>It's stable for most people even using save/restore/migrate. It
>must be something about your particular setup or configuration
>which is provoking the bug. We've actually put a fair amount of
>effort into trying to reproduce the resume crash, but haven't
>managed it. 
>  
>
I must have a "NOLUCK" flag :-) we tried Xen on two different P4 boxes, 
on two different Celeron boxes, and we had different problems each time. 
Would some bootflags be of any use ? Do some chipsets have a bad 
reputation, or something like that ?

Here's what happens when I attempt a restore :

isnpro:~# xm restore xipetotec.xen -c
(domain
    (id 24)
    (name xipetotec)
    (memory 0)
    (maxmem 65536)
    (state ----c)
    (cpu 0)
    (cpu_time 0.045590639)
    (up_time 3.83165788651)
    (start_time 1101834496.66)
    (console
        (status closed)
        (id 58)
        (domain 24)
        (local_port 0)
        (remote_port 0)
        (console_port 9624)
    )
    (devices)
    (config
        (vm
            (name xipetotec)
            (memory 64)
            (restart onreboot)
            (image
                (linux (kernel /boot/vmlinuz-2.6.9-xenU) (root 
'/dev/hda1 ro'))
            )
            (device (vbd (uname phy:isnpro/xipetotec-root) (dev hda1) 
(mode w)))
            (device (vif (mac aa:00:00:00:00:09) (bridge xen-br0)))
        )
    )
)
isnpro:~# xm list
Name              Id  Mem(MB)  CPU  State  Time(s)  Console
Domain-0           0       59    0  r----   5987.9       
Domain-16         16       63    0  -b---    329.2       
Domain-17         17      127    0  -b---    700.0       
Domain-21         21        0    0  ----c      0.0       
Domain-22         22        0    0  ----c      0.0       
xipetotec         24        0    0  ----c      0.0    9624
isnpro:~#



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

  reply	other threads:[~2004-11-30 17:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-30 13:45 More Xen troubles (with xend this time) Jérôme Petazzoni
2004-11-30 14:09 ` Ian Pratt
2004-11-30 16:45   ` Jérôme Petazzoni
2004-11-30 16:57     ` Christian Limpach
2004-11-30 17:10       ` Jérôme Petazzoni
2004-12-01 10:19         ` Mike Wray
2004-11-30 17:02     ` Ian Pratt
2004-11-30 17:14       ` Jérôme Petazzoni [this message]
2004-11-30 14:09 ` Keir Fraser

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=41ACAA61.2090105@enix.org \
    --to=jp@enix.org \
    --cc=Ian.Pratt@cl.cam.ac.uk \
    --cc=xen-devel@lists.sourceforge.net \
    /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.