This version is no longer supported. If this is still reproducible,
please reopen.
** Changed in: linux (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/720644
Title:
linux-virtual kernel does not allow network configuration via kernel
command line
Status in linux package in Ubuntu:
Won't Fix
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/interfaces on
the domU's disk beforehand.
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/720644/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
