]> git.ipfire.org Git - thirdparty/libvirt.git/commit
Don't expose 'vnet%d' to the user
authorMark McLoughlin <markmc@redhat.com>
Tue, 18 Aug 2009 12:32:42 +0000 (13:32 +0100)
committerMark McLoughlin <markmc@redhat.com>
Tue, 18 Aug 2009 12:36:37 +0000 (13:36 +0100)
commit2b1f67d418e595057931bbf18f2b6f3311020ece
treea830775fcac61ac33750461d360431582bb59e9c
parente8ad33931296c67de0538e78d12e21706a826d37
Don't expose 'vnet%d' to the user

https://bugzilla.redhat.com/517371

Matt Booth points out that if you use a non-existent bridge name when
start a guest you get a weird error message:

  Failed to add tap interface 'vnet%d' to bridge 'virbr0'

and dev='vnet%d' appears in the dumpxml output.

Fix that by not including 'vnet%d' in the error message and freeing the
'vnet%d' string if adding the tap device to the bridge fails.

* src/qemu_conf.c, src/uml_conf.c: fix qemudNetworkIfaceConnect()
  and umlConnectTapDevice() to not expose 'vnet%d' to the user
src/qemu_conf.c
src/uml_conf.c