[Pkg-libvirt-maintainers] Bug#531802: Bug#531802: libvirt0: bridges containing VLAN interfaces are not recognized
Andreas Unterkircher
unki at netshadow.at
Thu Jun 4 10:43:48 UTC 2009
> Running virt-manager with --no-fork --debug should provide more
> information on what's going on with that VLAN.
That brings up the following:
unki at vmtest:~$ sudo virt-manager --no-fork --debug
2009-06-04 12:22:37,621 (virt-manager:144): Application startup
2009-06-04 12:22:37,702 (keyring:31): No support for gnome-keyring
2009-06-04 12:22:37,800 (engine:81): About to connect to uris
['qemu:///system']
2009-06-04 12:22:37,804 (connection:144): Bonding masters are: []
2009-06-04 12:22:37,807 (connection:170): Got physical net device
/org/freedesktop/Hal/devices/net_00_1b_78_31_3d_1a
2009-06-04 12:22:37,808 (connection:230): Adding net device eth1
00:1b:78:31:3d:1a /sys/class/net/eth1 (bridge: br1)
2009-06-04 12:22:37,809 (connection:202): Checking for VLANs on
/sys/class/net/eth1
2009-06-04 12:22:37,811 (connection:170): Got physical net device
/org/freedesktop/Hal/devices/net_00_1b_78_31_3d_70
2009-06-04 12:22:37,812 (connection:230): Adding net device eth0
00:1b:78:31:3d:70 /sys/class/net/eth0 (bridge: br0)
2009-06-04 12:22:37,813 (connection:202): Checking for VLANs on
/sys/class/net/eth0
2009-06-04 12:22:37,853 (engine:320): window counter incremented to 1
2009-06-04 12:22:37,858 (connection:431): Scheduling background open
thread for qemu:///system
2009-06-04 12:22:37,859 (connection:561): Background thread is running
2009-06-04 12:22:37,861 (connection:599): Background open thread
complete, scheduling notify
2009-06-04 12:22:37,892 (connection:608): Notifying open result
2009-06-04 12:22:37,903 (manager:495): About to append vm: Win_Autoinst2
2009-06-04 12:22:37,904 (manager:495): About to append vm: wks-fl-ubuntutest
2009-06-04 12:22:37,905 (manager:495): About to append vm: test
2009-06-04 12:22:37,905 (manager:495): About to append vm: srv-fl-ftp01
2009-06-04 12:22:37,906 (manager:483): VM srv-fl-ftp01 started
strace shows:
...
write(3, "[Thu, 04 Jun 2009 12:26:50 virt-manager 8973] DEBUG
(connection:202) Checking for VLANs on /sys/class/net/eth1\n"..., 111)
= 111
stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2211, ...}) = 0
stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2211, ...}) = 0
write(2, "2009-06-04 12:26:50,619 (connection:202): Checking for VLANs
on /sys/class/net/eth1\n"..., 842009-06-04 12:26:50,619
(connection:202): Chec
king for VLANs on /sys/class/net/eth1
) = 84
open("/sys/class/net", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = 15
fstat(15, {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0
getdents(15, /* 11 entries */, 4096) = 288
getdents(15, /* 0 entries */, 4096) = 0
close(15) = 0
...
That is all what it does here. Then it already jumps to the next interface.
What virt-manager does here according the for-loop in line 203 is
looking for sysfspath + ".*" which results in:
/sys/class/net/eth0.*
/sys/class/net/eth1.*
But that directory just contains:
vmtest:/sys/class/net# ls -l
total 0
drwxr-xr-x 6 root root 0 Jun 4 09:43 br0
drwxr-xr-x 6 root root 0 Jun 4 09:43 br1
drwxr-xr-x 6 root root 0 Jun 4 10:57 br2
drwxr-xr-x 5 root root 0 Jun 4 09:43 eth0
drwxr-xr-x 5 root root 0 Jun 4 09:43 eth1
drwxr-xr-x 4 root root 0 Jun 4 09:42 lo
drwxr-xr-x 5 root root 0 Jun 4 10:57 vlan152
drwxr-xr-x 5 root root 0 Jun 4 10:38 vnet0
drwxr-xr-x 5 root root 0 Jun 4 10:38 vnet1
I'm not sure what it is supposed to do. Maybe they look out for a
specific naming of the VLAN interfaces which is not the case on Debian.
Cheers,
Andreas
More information about the Pkg-libvirt-maintainers
mailing list