WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] linux hvm network problem

To: xen-users <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] linux hvm network problem
From: "Marco Strullato" <marco.strullato@xxxxxxxxx>
Date: Thu, 6 Dec 2007 17:21:57 +0100
Delivery-date: Thu, 06 Dec 2007 08:22:47 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; bh=Nmxn4KwdNTTC8/xE0xNiF7Su67suNdZ0wVdWx5iKfXs=; b=UqqeUFE1wd/PbfrZObcJm0MNYkwYlPe7lWW8loLnQQF8wBFEE3uKcKquYNervKD6M+lHVFFZvVjpvIBQ4Cwj0H+VkIsYcHWLMOxAHViiRO0mUa6KO2aWVU2xevJZoxHeuRqpStooDcYHJ5dG+Lxx4ZcFbiKYGaay38qHuMQChts=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=bx5DdK/o5q/Q4sNor7/IVoSWwgzrQV6dUGYY7qsDXUc0S7gui8opsfYzTx8kavDzlk923/3oW09LmyaSyaJvSMyUfVWotpgUZ9BpdjMjgVXmTIV+PlNsTzBnkynZmdGcDN85HXDB8SaDCBWwQ9/6toWwkiBeJ1pVOy1+Ar6ha1c=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi all,
I'm having network problems with hvm.
My conf is centos5 with xen 3.0.3. I'm booting a RedHat 9 with this conf file

kernel = "/usr/lib/xen/boot/hvmloader"
builder='hvm'
memory = 1536
shadow_memory = 8
name = "SERVER"
vcpus=2
pae=0
acpi=0
apic=0
disk = [ 'phy:/dev/HYP02VM/LUMINA,ioemu:hda,w',  ]
device_model = '/usr/lib/xen/bin/qemu-dm'
sdl=1
vnc=1
vnclisten="0.0.0.0"
vncdisplay=1
vncunused=1
vncconsole=1
vncpasswd='abc123'
nographic=0
stdvga=0
serial='pty'
vif = [ 'type=ioemu, bridge=xenbr0, model=ne2k_pci']

After the 1st boot, the guest recognize the new configuration and reconfigure the network correctly with kudzu: the guest can reach the dhcp server and get a valid ip address. After the first connection to the dhcp server the guest became "isolated". I mean I can not connet to the default gateway. I tried to assign manually the ip address but nothing changes.

I took a tcpdump on the dom0 listenting to the bridge and to the hvm domU. I have the same result:  only arp requests


10.0.1.29 is the ip address of the hvm guest... the other is the mine ip.


15:53:30.472523 arp who-has 10.0.0.34 tell 10.0.1.29
15:53:31.492565 arp who-has 10.0.0.34 tell 10.0.1.29
15:53:32.492586 arp who-has 10.0.0.34 tell 10.0.1.29
15:53:33.492619 arp who-has 10.0.0.34 tell 10.0.1.29
15:53:34.492697 arp who-has 10.0.0.34 tell 10.0.1.29
15:53:35.492687 arp who-has 10.0.0.34 tell 10.0.1.29
15:53:36.492717 arp who-has 10.0.0.34 tell 10.0.1.29
15:53:37.492786 arp who-has 10.0.0.34 tell 10.0.1.29
15:53:38.492787 arp who-has 10.0.0.34 tell 10.0.1.29


Do you have some suggestions? Dom0's network is running  well, I have other linux paravirtualized vm running...


Regards,

Marco


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>