New: Kernel panic after adding tap interface to bridge
Subsystems (3)
A message that is not in the archive (sent off-list or not yet received): [email protected]/
(switched to email. Please respond via emailed reply-to-all, not via the bugzilla web interface).
Quoted 1 line · On Fri, 17 Apr 2009 13:51:06 GMT [email protected] wrote:
There's some additional info at the bugzillal ink.
Quoted 67 lines
Summary: Kernel panic after adding tap interface to bridge Product: Networking Version: 2.5 Kernel Version: 2.6.27.21 Platform: All OS/Version: Linux Tree: Fedora Status: NEW Severity: normal Priority: P1 Component: Other AssignedTo: [email protected] ReportedBy: [email protected] Regression: NoCreated an attachment (id=21029)
--> (http://bugzilla.kernel.org/attachment.cgi?id=21029)
serial output after kernel panicBox has a 1 active truncated Ethernet link with dozens VLANs. During system startup virtual interfaces are created to separate each VLAN data from the others'. Several brigdes sit on the top of them, one for each VLAN. Everything works fine until I try to add kvm linux guest to whichever VLAN brigde. Then kernel freezes in a few seconds.
Steps to reproduce:
1) configure network interfaces accordingly to what has been described above (standard RedHat/Fedora config files in
/etc/sysconfig/network-scriptssuffice).
2) create TAP device using tunctl
3) change the state of the device to up
4) add it to one of the bridges
5) run guest machine with one interface paired with previously created TAP deviceSteps 2-4 can be handled automatically by qemu-kvm running script like this one:
#!/bin/sh
# prep_script.sh set -xswitch=br100
if [ -n "$1" ];then
/usr/sbin/tunctl-p -t $1
/sbin/iplink set $1 up
sleep 0.5s
/usr/sbin/brctladdif $switch $1
exit 0
else
echo "Error: no interface specified"
exit 1
fiThen guest can be fired up using the following command:
qemu-kvm -m 1024 -net nic,model=e1000 -net tap,script=/path/to/prep_script.sh /path/to/disk.img
Additional info:
Host: Fedora 10 (see kernel ring buffer output file and kernel config file)
Guest: CentOS 5.3