From: Ted Kaczmarek <tedkaz@gmail.com>
To: xen-devel@lists.xensource.com
Subject: changeset 6902 issues
Date: Sun, 18 Sep 2005 07:44:44 -0400 [thread overview]
Message-ID: <1127043884.23958.6.camel@pluto.linsolutions.com> (raw)
With changset 6902 on FC4, Tyan 2462 SMP, 2 gig,a few minutes after
bringing up domU's all of them toast.
Unable to read memory/target is what I see at the domU's console.
I do see "/proc/xen/baloon"
Also caught this on a restart of all the domU's after the memory/target
error occured.
xen_blk: Initialising virtual block device driver
vbd: probe of vbd-2050 failed with error -110
kernel BUG at drivers/xen/xenbus/xenbus_xs.c:493
(register_xenbus_watch)!
Poked around the archives and no direct matches on this one.
As well as
DEBUG (blkif:24) exception looking up device number for sda2: [Errno 2]
No such file or directory: '/dev/sda2
I see this always, whether the domU is able to mount /root or not.
Also on startup of xend occasionally I see
ERROR (process:37) [network-bridge] s/inet/ip addr add/
ERROR (process:37) [network-bridge] s@\([0-9]\+\.[0-9]\+\.[0-9]\
+\.[0-9]\+/[0-9]\+\)@\1@
ERROR (process:37) [network-bridge] s/eth0/dev xen-br0/
ERROR (process:37) [network-bridge] '
ERROR (process:37) [network-bridge] + sh -e
ERROR (process:37) [network-bridge] Cannot find device "xen-br0:1"
If I stop and start again tight after seeing this error
ERROR (process:37) [network-bridge] s/eth0/xen-br0/
ERROR (process:37) [network-bridge] s/^/ip route add /
ERROR (process:37) [network-bridge] P
ERROR (process:37) [network-bridge] d
ERROR (process:37) [network-bridge] }'
ERROR (process:37) [network-bridge] + sh -e
ERROR (process:37) [network-bridge] RTNETLINK answers: File exists
After a reboot all domU's will work again for a few minutes, than the
memory/target error occurs again.
Regards,
Ted
reply other threads:[~2005-09-18 11:44 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=1127043884.23958.6.camel@pluto.linsolutions.com \
--to=tedkaz@gmail.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.