linux-virtual kernel does not allow network configuration via kernel command line
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: linux-virtual
I am using Ubuntu Lucid 10.04 inside a Xen 4 domU with the linux-virtual kernel, which is recommended for that purpose. Xen allows for the configuration of the domU's network device(s) via its configuration files in dom0, IP, netmask, hostname etc. can be set there. these settings are then handed over to the kernel of the domU at creation time. On previous installs (with a self-compiled kernel) the domU's eth0 was then brought up automagically with the correct settings, without the need to touch e.g. /etc/network/
This is a very clean way of keeping the domU's settings together in one file and makes using generic domU images possible (ideally with an upgradeable stock linux-virtual kernel). However, this doesn't work as supposed, since CONFIG_IP_PNP is not set in the linux-virtual kernel configuration. Since the linux-virtual kernel is just there to be used in VMs, I reckon this option should be set anyways in this kernel.
affects: | linux-meta (Ubuntu) → linux (Ubuntu) |
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
This bug is missing log files that will aid in dianosing the problem. From a terminal window please run:
apport-collect 720644
and then change the status of the bug back to 'New'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.