dhclient fails in domU
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xen-3.0 (Ubuntu) |
Expired
|
Undecided
|
Unassigned | ||
xen-3.2 (Ubuntu) |
Expired
|
Low
|
Unassigned |
Bug Description
Xen was installed from the feisty repositories, the domU system was installed with debootstrap using the "debian lenny" template and later with the "ubuntu feisty" template. The installation is detailed later on this page. This recipe used to work fine but now show shortcomings. The eth0 interface is configured in the domU to dynamically retrieve its IP address.
The domU boots but can't get an IP address:
root@azalee:~# dhclient eth0
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://
socket: Address family not supported by protocol - make sure
CONFIG_PACKET (Packet socket) and CONFIG_FILTER
(Socket Filtering) are enabled in your kernel
configuration!
DomU installation step:
1. create a partition {{{
lvcreate -n azalee -L 2G hd && mkfs.ext3 /dev/mapper/
mkdir /mnt/azalee && mount /dev/mapper/
1. install a minimum debian system: {{{
debootstrap feisty /mnt/azalee}}}
1. configure the minimum debian system : {{{
chroot /mnt/azalee
cat > /etc/hostname <<.
azalee
.
cat > /etc/fstab <<.
/dev/hda1 / ext3 defaults 0 1
.
cat > /etc/network/
auto lo eth0
iface lo inet loopback
iface eth0 inet dhcp
.
exit
umount /mnt/azalee
}}}
1. create a "xen domain" ie a vm {{{
cat > /etc/xen/azalee <<.
name = "azalee"
kernel = "/boot/
ramdisk = "/boot/
root = "/dev/hda1"
disk = [ 'phy:/dev/
vif = [ 'mac=00:
memory = 200
.}}}
description: | updated |
Changed in xen-3.2: | |
importance: | Undecided → Low |
Check if the af_packet.ko module is available in the domU
excerpt from net/packet/Kconfig:
The Packet protocol is used by applications which communicate
directly with network devices without an intermediate network
protocol implemented in the kernel, e.g. tcpdump