Inconsistent location of kvm-ifup, missing kvm-ifdown

Bug #376387 reported by Richard Davies
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
qemu-kvm (Ubuntu)
Fix Released
High
Dustin Kirkland 

Bug Description

Binary package hint: kvm

I'm running Ubuntu 9.04 Jaunty with kvm 1:84+dfsg-0ubuntu11

In this package, "kvm -net tap" defaults to "script=/etc/kvm-ifup" and "downscript=/etc/kvm-ifdown". However the package actually includes /etc/kvm/kvm-ipup (different location) and no kvm-ifdown at all.

This forces users to write write their own kvm-ifdown, and respecify the location for kvm-ifup.

It would be better if:

- The "kvm -net tap" default for kvm-ifup was the same as where the package actually puts it (either move the script or compile kvm with a different default).

- The package shipped with a kvm-ifdown script (again ideally in the location which the binary expects by default). A reasonable example (which mirrors the current kvm-ifup) would be:

#!/bin/sh

# NOTE: For this script to operate properly, it is expected that
# you have a br0

BRIDGE=br0

/usr/sbin/brctl delif $BRIDGE $1
/sbin/ifconfig $1 0.0.0.0 down

Related branches

Revision history for this message
Dustin Kirkland  (kirkland) wrote :

Thanks for the information, Richard.

I should be able to fix this for Karmic. Marking triaged.

:-Dustin

Changed in kvm (Ubuntu):
assignee: nobody → Dustin Kirkland (kirkland)
importance: Undecided → High
milestone: none → ubuntu-9.10
status: New → Triaged
Revision history for this message
Dominic Evans (oldmanuk) wrote :

Hi, I actually spotted this today in karmic and so did a quick debdiff to make it point at the correct ifup script.

Attached.

Revision history for this message
Dominic Evans (oldmanuk) wrote :

Also updated the debdiff to add the kvm-ifdown script as suggested

Changed in kvm (Ubuntu):
status: Triaged → In Progress
affects: kvm (Ubuntu) → qemu-kvm (Ubuntu)
Changed in qemu-kvm (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.