From: list user <xktnniuymlla@mailinator.com>
To: xen-devel@lists.xensource.com
Subject: xendomains fails if domU has pci= line
Date: Fri, 12 May 2006 09:48:04 -0700 [thread overview]
Message-ID: <4464BC44.4090500@mailinator.com> (raw)
Hi all,
Using xen-3.0.2-2 w/ linux 2.6.16-xen from src on fedora core 4.
xendomains seems to have gone buggy but I'll only address this one issue.
domU1 has this line in its config file (for a 1G nic):
pci = [ '00:0d.0' ]
domU2 has this (for a 10/100 nic):
pci = [ '00:0f.1' ]
Each also has 1G xennet cards attached to xen bridges.
It works. I've a multi-legged router and a set of servers on the dmz.
As long as I manually start and stop them using xm everything is OK.
Now if I bring them up the first time, i.e. there is no
"/var/lib/xen/save/*", using "service xendomains start" both domains
start and run. At that point "service xendomains stop" yields NO ERROR
messages. A following "service xendomains start" tries to start domU1
twice, both times failing. domU2 starts but is left seg-faulted.
Domain-0 survives all this.
This is typical of the errors displayed:
"/usr/lib/xen/bin/xm_restore 11 18 1 18432 1 2 failed!"
Looking at xend.log: this is domU id #5
[2006-05-12 09:30:45 xend] DEBUG (XendCheckpoint:80) [xc_save]:
/usr/lib/xen/bin/xc_save 11 18 5 0 0 0
[2006-05-12 09:30:45 xend] DEBUG (XendCheckpoint:200) suspend
[2006-05-12 09:30:45 xend] DEBUG (XendCheckpoint:83) In saveInputHandler
suspend
[2006-05-12 09:30:45 xend] DEBUG (XendCheckpoint:85) Suspending 5 ...
[2006-05-12 09:30:45 xend.XendDomainInfo] DEBUG (XendDomainInfo:877)
XendDomainInfo.handleShutdownWatch
[2006-05-12 09:30:45 xend.XendDomainInfo] DEBUG (XendDomainInfo:877)
XendDomainInfo.handleShutdownWatch
[2006-05-12 09:30:45 xend.XendDomainInfo] INFO (XendDomainInfo:836)
Domain has shutdown: name=migrating-vm2 id=5 reason=suspend.
[2006-05-12 09:30:46 xend] INFO (XendCheckpoint:88) Domain 5 suspended.
[2006-05-12 09:30:46 xend] DEBUG (XendCheckpoint:91) Written done
[2006-05-12 09:30:46 xend] ERROR (XendCheckpoint:227) Had 0 unexplained
entries in p2m table
[2006-05-12 09:30:47 xend.XendDomainInfo] INFO (XendDomainInfo:836)
Domain has shutdown: name=migrating-vm2 id=5 reason=suspend.
[2006-05-12 09:30:47 xend] ERROR (XendCheckpoint:227) Saving memory
pages: iter 1 0%^H^H^H^H 6%^H^H^H^H 12%^H^H^H^H 18%^H^H^H^H
24%^H^H^H^H 30%^H^H^H^H 36%^H^H^H^H 42%^H^H^H^H 49%^H^H^H^H 56%^H^H^H^H
62%^H^H^H^H 68%^H^H^H^H 75%^H^H^H^H 81%^H^H^H^H 87%^H^H^H^H 94%^M 1:
sent 16348, skipped 0, delta 1930ms, dom0 100%, target 0%, sent 277Mb/s,
dirtied 5020Mb/s 134513459 pages
[2006-05-12 09:30:47 xend] ERROR (XendCheckpoint:227) Total pages sent=
16348 (0.89x)
[2006-05-12 09:30:47 xend] ERROR (XendCheckpoint:227) (of which 0 were
fixups)
[2006-05-12 09:30:47 xend] ERROR (XendCheckpoint:227) All memory is saved
[2006-05-12 09:30:47 xend] ERROR (XendCheckpoint:227) Save exit rc=0
[2006-05-12 09:30:47 xend.XendDomainInfo] DEBUG (XendDomainInfo:1335)
XendDomainInfo.destroyDomain(5)
I've poked at this for a couple days and don't understand this well
enough to debug it myself. I'm not even sure where to begin.
If anybody wants to help I'll do whatever experiments on my side I can
and report whatever is requested.
Waiting eagerly for help... ;)
Thanks,
Mike Wright
reply other threads:[~2006-05-12 16:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4464BC44.4090500@mailinator.com \
--to=xktnniuymlla@mailinator.com \
--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.