On Mon, 2010-06-28 at 15:40 -0500, Juan Luis Baptiste wrote:
> I'm new to this list and to Xen. I'm setting up a CentOS 5.5
> paravirtualized domU using virt-manager over a bridged connection, but
> I'm having a strange problem. Basically, the problem is that this domU
> can't get his IP address from our dhcp server, not even while doing
> the network installation process or after installed. I can manually
> asign an IP address on my network range which works and I can perform
> the network installation and after installation finished I can see
> other hosts, connect to the internet, etc. But choosing dhcp when
> configuring the network at installation time won't work, I will get an
> error that couldn't get a response from the dhcp server. The same
> happens after installation if I configure the network interface to use
> dhcp instead of a static address.
> This is the config file generated by virt-manager:
> name = "centos55_base"
> uuid = "e07b5490-2a1e-a5a8-a29a-28fc1d8d76a8"
> maxmem = 1024
> memory = 768
> vcpus = 1
> bootloader = "/usr/bin/pygrub"
> on_poweroff = "destroy"
> on_reboot = "restart"
> on_crash = "restart"
> vfb = [ "type=vnc,vncunused=1,keymap=en-us" ]
> disk = [ "tap:aio:/var/lib/xen/images/centos55_base.img,xvda,w" ]
> vif = [ "mac=00:16:36:5c:a5:b8,bridge=xenbr0,script=vif-bridge" ]
> Using full virtualization works fine, no problems using dhcp on the
> same xen server where I'm creating the paravirtualized domU.
> Any ideas why this could be happening?
You can try sniff the communication with tcpdump from Dom0 to find out
Xen-users mailing list