WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-bugs

[Xen-bugs] [Bug 626] Kernel oops when using domU's

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=626





------- Comment #9 from mangoo@xxxxxxxx  2006-09-11 09:26 -------
Here's a description on how to reproduce it.

I use VLANs, and I start them using "my-network-script":


#!/bin/sh -x

dir=$(dirname "$0")

"$dir/network-bridge" "$@" vifnum=0 netdev=eth0.100 bridge=xenbr100

"$dir/network-bridge" "$@" vifnum=1 netdev=eth0.101 bridge=xenbr101

"$dir/network-bridge" "$@" vifnum=2 netdev=eth0.102 bridge=xenbr102


So, basically, it starts "network-bridge" script, which creates VLANs attached
to appropriate bridges.
With the script above, Xen kernel will panic when creating the first domain
(you have to wait 5-30 seconds).


With the script below, Xen kernel doesn't panic:

#!/bin/sh -x

dir=$(dirname "$0")


"$dir/network-bridge" "$@" vifnum=0 netdev=eth0 bridge=xenbr0

"$dir/network-bridge" "$@" vifnum=1 netdev=eth0.100 bridge=xenbr100

"$dir/network-bridge" "$@" vifnum=2 netdev=eth0.101 bridge=xenbr101

"$dir/network-bridge" "$@" vifnum=3 netdev=eth0.102 bridge=xenbr102


The only difference is that I attached eth0 to xenbr0.


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs

<Prev in Thread] Current Thread [Next in Thread>