From: Greg Brackley <lists-xen-devel@lucidsolutions.co.nz>
To: xen-devel@lists.xensource.com
Subject: Re: Network-bridge script with bonding and vlan
Date: Sat, 22 Oct 2005 23:17:21 +1300 [thread overview]
Message-ID: <01af01c5d6f1$ca56dd80$0100a8c0@balls> (raw)
In-Reply-To: 1129907295.2987.50.camel@pluto.linsolutions.com
----- Original Message -----
From: "Ted Kaczmarek" <tedkaz@optonline.net>
> I am still seeing very erratic network behavior in general, on first
> reboot of the dom0 things will generally behave well, but after the dom0
> has been up for a while, with domU's brought up and down along the way
> all kinds of random failures start to happen.
Once the domains are up I haven't seen any additional problems. I seem to
be finally getting the networking under control by using standard FC4 init
scripts. I'm not sure what I was getting wrong with the networking
previously.
The current issue I have is that my test domainU fails to start every time
after dom0 is started (log below). It starts on the second and subsequent
restarts. I tried pulling the LVM/Raid support out of the XenU kernel, but
it didn't help. The root being passed to the domU in the log is a LVM volume
('phy:/dev/VolGroup00/root01xenu,sda1,w').
Greg :-)
Linux version 2.6.12-xenU (xxxx@blue.lucidsolutions.co.nz) (gcc version
4.0.1 20050727 (Red Hat 4.0.1-5)) #3 SMP Sat Oct 22 22:38:14 NZDT 2005
kernel direct mapping tables upto 10000000 @ 42e000-4b0000
Built 1 zonelists
Kernel command line: root=/dev/sda1 ro 3
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 65536 bytes)
Xen reported: 1593.798 MHz processor.
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Memory: 253184k/262144k available (1660k kernel code, 8496k reserved, 551k
data, 128k init)
Mount-cache hash table entries: 256
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 1024K (64 bytes/line)
Brought up 1 CPUs
NET: Registered protocol family 16
xen_mem: Initialising balloon driver.
Grant table initialized
IA32 emulation $Id: sys_ia32.c,v 1.32 2002/03/24 13:02:28 ak Exp $
audit: initializing netlink socket (disabled)
audit(1129974155.344:0): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
Xen virtual console successfully installed as tty1
Event-channel device installed.
xen_blk: Initialising virtual block device driver
xen_net: Initialising virtual ethernet driver.
NET: Registered protocol family 2
IP: routing cache hash table of 1024 buckets, 16Kbytes
TCP established hash table entries: 16384 (order: 6, 262144 bytes)
TCP bind hash table entries: 16384 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
VFS: Cannot open root device "sda1" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)
next prev parent reply other threads:[~2005-10-22 10:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-20 11:34 Network-bridge script with bonding and vlan Greg Brackley
2005-10-20 11:48 ` Ewan Mellor
2005-10-21 1:16 ` Greg Brackley
2005-10-21 9:26 ` Ewan Mellor
2005-10-21 11:23 ` Greg Brackley
2005-10-21 15:08 ` Ted Kaczmarek
2005-10-22 10:16 ` Greg Brackley
2005-10-22 10:17 ` Greg Brackley [this message]
2005-10-22 10:34 ` Ewan Mellor
2005-10-22 10:49 ` Greg Brackley
2005-11-23 10:35 ` Network-bridge script with bonding and vlan - WORKAROUND Greg Brackley
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='01af01c5d6f1$ca56dd80$0100a8c0@balls' \
--to=lists-xen-devel@lucidsolutions.co.nz \
--cc=greg.brackley-dated-1130581042.5b5294@lucidsolutions.co.nz \
--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.