Hello, I''m using a Debian Etch server (AMD 64 bits) and I''m trying to use Xen 3.0.1 from Debian respositories to install another Debian (64 bits). Using route network configuration (not bridge). The Debian DomU doesn''t find any Ethernet card (I execute lspci and I don''t see anything related with Ethernet) The /etc/xen/xend-config.sxp file contains: -------------- (logfile /var/log/xen/xend.log) (network-script network-route) (vif-script vif-route) (dom0-min-mem 196) (dom0-cpus 0) (vnc-listen ''192.168.0.1'') -------------- (and other comented lines :-) ) And the /etc/xen/machinename.hvm (last version) contains: -------------- kernel="/usr/lib64/xen-3.0.3-1/boot/hvmloader" builder=''hvm'' device_model=''/usr/lib64/xen-3.0.3-1/bin/qemu-dm'' memory=256 name=''chronojump'' vif = [ ''ip=192.168.0.150''] disk=[''file:/home/xen/domains/chronojump/root,sda1,w'',''file:/home/xen/domains/de bian-etch.iso,hdc:cdrom,r''] boot=''d'' vnc=1 vncviewer=1 sdl=0 vncpasswd='''' pae=1 #acpi=0 #apic=0 stdvga=0 ne2000=1 -------------- I have tried without ne2000=1/0, also I have tried adding ip and gatway parameters, and adding names to vif parameter, but I never got any card in domU. I send attached the last part of /var/log/xend.log. Any idea please? Something else to read? (I have been searching information for quite long time and I made many tests...) Thank you so much! -- Carles Pina i Estany GPG id: 0x8CBDAE64 http://pinux.info Manresa - Barcelona _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi again, On Mar/08/2008, Carles Pina i Estany wrote:> The Debian DomU doesn''t find any Ethernet card (I execute lspci and I > don''t see anything related with Ethernet)(requirements: HVM, network route (no nat, no bridge)) If somebody could send me the relevant sections from xend-config.sxp and /etc/xen/machinename, and the lspci inside the domU I will be happy and I think that I will be able to finish the puzzle :-) Thanks! -- Carles Pina i Estany GPG id: 0x8CBDAE64 http://pinux.info Manresa - Barcelona _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello, On Mar/08/2008, Carles Pina i Estany wrote:> > Hi again, > > On Mar/08/2008, Carles Pina i Estany wrote: > > > The Debian DomU doesn''t find any Ethernet card (I execute lspci and I > > don''t see anything related with Ethernet)I see that the qemu-dm is running (indeed) but doesn''t have any reference to the nic option: /usr/lib64/xen-3.0.3-1/bin/qemu-dm -d 17 -m 256 -boot d -vcpus 1 -domain-name thename -vncunused -k en-us -vnclisten 192.168.0.1 As I was expecting I started to play a bit with xm/create.py but I think that somebody will know the reason faster :-) In a previous message you have my xend.log, I can resend. Thank you, -- Carles Pina i Estany GPG id: 0x8CBDAE64 http://pinux.info Manresa - Barcelona _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
You need to specify ''type=ioemu'' in your vif line. If running
multiple
domu''s you should also specify a unique mac address for each one. Also
in
my version of XEN (3.0.3) the domu would not start if I didn''t have a
bridge
created ahead of time even though I am using route and not bridge. I fixed
this by adding ''brctl addbr xenbr0'' to network-route.
Good Luck!
Max Baro
Technical Support Supervisor
FACTS Services, Inc.
(305) 284 - 7440
meb@factsservices.com
-----Original Message-----
Message: 6
Date: Sat, 8 Mar 2008 16:53:54 +0100
From: Carles Pina i Estany <carles@pina.cat>
Subject: [Xen-users] domU HVM network problem
To: xen-users@lists.xensource.com
Message-ID: <20080308155354.GA8029@pina.cat>
Content-Type: text/plain; charset="us-ascii"
Hello,
I''m using a Debian Etch server (AMD 64 bits) and I''m trying to
use Xen
3.0.1 from Debian respositories to install another Debian (64 bits).
Using route network configuration (not bridge).
The Debian DomU doesn''t find any Ethernet card (I execute lspci and I
don''t see anything related with Ethernet)
The /etc/xen/xend-config.sxp file contains:
--------------
(logfile /var/log/xen/xend.log)
(network-script network-route)
(vif-script vif-route)
(dom0-min-mem 196)
(dom0-cpus 0)
(vnc-listen ''192.168.0.1'')
--------------
(and other comented lines :-) )
And the /etc/xen/machinename.hvm (last version) contains:
--------------
kernel="/usr/lib64/xen-3.0.3-1/boot/hvmloader"
builder=''hvm''
device_model=''/usr/lib64/xen-3.0.3-1/bin/qemu-dm''
memory=256
name=''chronojump''
vif = [ ''ip=192.168.0.150'']
disk=[''file:/home/xen/domains/chronojump/root,sda1,w'',''file:/home/xen/domain
s/de
bian-etch.iso,hdc:cdrom,r'']
boot=''d''
vnc=1
vncviewer=1
sdl=0
vncpasswd=''''
pae=1
#acpi=0
#apic=0
stdvga=0
ne2000=1
--------------
I have tried without ne2000=1/0, also I have tried adding ip and gatway
parameters, and adding names to vif parameter, but I never got any card
in domU.
I send attached the last part of /var/log/xend.log.
Any idea please? Something else to read? (I have been searching information
for quite long time and I made many tests...)
Thank you so much!
--
Carles Pina i Estany GPG id: 0x8CBDAE64
http://pinux.info Manresa - Barcelona
-------------- next part --------------
[2008-03-08 16:34:20 xend.XendDomainInfo 5195] DEBUG (__init__:1072)
XendDomainInfo.create([''vm'', [''name'',
''chronojump''], [''memory'', 256],
[''vcpus'', 1],
[''image'', [''hvm'',
[''kernel'',
''/usr/lib64/xen-3.0.3-1/boot/hvmloader''],
[''args'', ''VNC_VIEWER=127.0.0.1:5501 ''],
[''pae'', 1], [''vcpus'', 1],
[''boot'',
''d''],
[''vnc'', 1], [''vncunused'', 1],
[''xauthority'', ''/root/.Xauthority''],
[''device_model'',
''/usr/lib64/xen-3.0.3-1/bin/qemu-dm'']]],
[''device'', [''vbd'',
[''uname
'', ''file:/home/xen/domains/chronojump/root''],
[''dev'', ''sda1''], [''mode'',
''w'']]], [''device'', [''vbd'',
[''uname'',
''file:/home/xen/domains/debian-etch.iso''],
[''dev'', ''hdc:cdrom''],
[''mode'', ''r'']]],
[''device'', [''vif'', [''ip'',
''192.168.0.150'']]]])
[2008-03-08 16:34:20 xend.XendDomainInfo 5195] DEBUG (__init__:1072)
parseConfig: config is [''vm'', [''name'',
''chronojump''], [''memory'', 256],
[''vcpus'', 1]
, [''image'', [''hvm'',
[''kernel'',
''/usr/lib64/xen-3.0.3-1/boot/hvmloader''],
[''args'', ''VNC_VIEWER=127.0.0.1:5501 ''],
[''pae'', 1], [''vcpus'', 1],
[''boot'',
''d'']
, [''vnc'', 1], [''vncunused'', 1],
[''xauthority'', ''/root/.Xauthority''],
[''device_model'',
''/usr/lib64/xen-3.0.3-1/bin/qemu-dm'']]],
[''device'', [''vbd'',
[''unam
e'', ''file:/home/xen/domains/chronojump/root''],
[''dev'', ''sda1''], [''mode'',
''w'']]], [''device'', [''vbd'',
[''uname'',
''file:/home/xen/domains/debian-etch.iso''],
[''dev'', ''hdc:cdrom''],
[''mode'', ''r'']]],
[''device'', [''vif'', [''ip'',
''192.168.0.150'']]]]
[2008-03-08 16:34:20 xend.XendDomainInfo 5195] DEBUG (__init__:1072)
parseConfig: result is {''shadow_memory'': None,
''uuid'': None, ''on_crash'':
None, ''on_
reboot'': None, ''localtime'': None,
''image'': [''hvm'',
[''kernel'',
''/usr/lib64/xen-3.0.3-1/boot/hvmloader''],
[''args'',
''VNC_VIEWER=127.0.0.1:5501 ''], [''pae'',
1], [''vcpus'', 1], [''boot'',
''d''], [''vnc'', 1],
[''vncunused'', 1],
[''xauthority'', ''/root/.Xauthority''],
[''device_model'',
''/usr/lib64/xen-3.0.3-1/bin/qemu-dm
'']], ''on_poweroff'': None,
''bootloader_args'': None, ''cpus'': None,
''name'':
''chronojump'', ''backend'': [],
''vcpus'': 1, ''cpu_weight'': None,
''features'':
None,
''vcpu_avail'': None, ''memory'': 256,
''device'': [(''vbd'', [''vbd'',
[''uname'',
''file:/home/xen/domains/chronojump/root''],
[''dev'', ''sda1''], [''mode'',
''w'']]),
(''v
bd'', [''vbd'', [''uname'',
''file:/home/xen/domains/debian-etch.iso''],
[''dev'',
''hdc:cdrom''], [''mode'',
''r'']]), (''vif'', [''vif'',
[''ip'', ''192.168.0.150'']])],
''bo
otloader'': None, ''cpu'': None,
''maxmem'': None}
[2008-03-08 16:34:20 xend.XendDomainInfo 5195] DEBUG (__init__:1072)
XendDomainInfo.construct: None
[2008-03-08 16:34:20 xend.XendDomainInfo 5195] DEBUG (__init__:1072)
XendDomainInfo.initDomain: 3 1.0
[2008-03-08 16:34:20 xend 5195] DEBUG (__init__:1072) args: boot, val: d
[2008-03-08 16:34:20 xend 5195] DEBUG (__init__:1072) args: fda, val: None
[2008-03-08 16:34:20 xend 5195] DEBUG (__init__:1072) args: fdb, val: None
[2008-03-08 16:34:20 xend 5195] DEBUG (__init__:1072) args: soundhw, val:
None
[2008-03-08 16:34:20 xend 5195] DEBUG (__init__:1072) args: localtime, val:
None
[2008-03-08 16:34:20 xend 5195] DEBUG (__init__:1072) args: serial, val:
None
[2008-03-08 16:34:20 xend 5195] DEBUG (__init__:1072) args: std-vga, val:
None
[2008-03-08 16:34:20 xend 5195] DEBUG (__init__:1072) args: isa, val: None
[2008-03-08 16:34:20 xend 5195] DEBUG (__init__:1072) args: vcpus, val: 1
[2008-03-08 16:34:20 xend 5195] DEBUG (__init__:1072) args: acpi, val: None
[2008-03-08 16:34:20 xend 5195] DEBUG (__init__:1072) args: usb, val: None
[2008-03-08 16:34:20 xend 5195] DEBUG (__init__:1072) args: usbdevice, val:
None
[2008-03-08 16:34:20 xend 5195] DEBUG (__init__:1072) Balloon: 278144 KiB
free; need 278120; done.
[2008-03-08 16:34:20 xend 5195] INFO (__init__:1072) buildDomain os=hvm
dom=3 vcpus=1
[2008-03-08 16:34:20 xend 5195] DEBUG (__init__:1072) dom = 3
[2008-03-08 16:34:20 xend 5195] DEBUG (__init__:1072) image
/usr/lib64/xen-3.0.3-1/boot/hvmloader
[2008-03-08 16:34:20 xend 5195] DEBUG (__init__:1072) store_evtchn = 1
[2008-03-08 16:34:20 xend 5195] DEBUG (__init__:1072) memsize = 256
[2008-03-08 16:34:20 xend 5195] DEBUG (__init__:1072) vcpus = 1
[2008-03-08 16:34:20 xend 5195] DEBUG (__init__:1072) pae = 1
[2008-03-08 16:34:20 xend 5195] DEBUG (__init__:1072) acpi = 0
[2008-03-08 16:34:20 xend 5195] DEBUG (__init__:1072) apic = 0
[2008-03-08 16:34:20 xend 5195] DEBUG (__init__:1072) hvm shutdown watch
registered
[2008-03-08 16:34:20 xend 5195] DEBUG (__init__:1072) DevController: writing
{''backend-id'': ''0'',
''virtual-device'': ''2049'',
''device-type'': ''disk'', ''state
'': ''1'', ''backend'':
''/local/domain/0/backend/vbd/3/2049''} to
/local/domain/3/device/vbd/2049.
[2008-03-08 16:34:20 xend 5195] DEBUG (__init__:1072) DevController: writing
{''domain'': ''chronojump'',
''frontend'':
''/local/domain/3/device/vbd/2049'', ''de
v'': ''sda1'', ''state'':
''1'', ''params'':
''/home/xen/domains/chronojump/root'',
''mode'': ''w'', ''online'':
''1'', ''frontend-id'': ''3'',
''type'': ''file''} to
/local/domai
n/0/backend/vbd/3/2049.
[2008-03-08 16:34:20 xend 5195] DEBUG (__init__:1072) exception looking up
device number for hdc: [Errno 2] No such file or directory:
''/dev/hdc''
[2008-03-08 16:34:20 xend 5195] DEBUG (__init__:1072) DevController: writing
{''backend-id'': ''0'',
''virtual-device'': ''5632'',
''device-type'': ''cdrom'', ''stat
e'': ''1'', ''backend'':
''/local/domain/0/backend/vbd/3/5632''} to
/local/domain/3/device/vbd/5632.
[2008-03-08 16:34:20 xend 5195] DEBUG (__init__:1072) DevController: writing
{''domain'': ''chronojump'',
''frontend'':
''/local/domain/3/device/vbd/5632'', ''de
v'': ''hdc'', ''state'':
''1'', ''params'':
''/home/xen/domains/debian-etch.iso'',
''mode'': ''r'', ''online'':
''1'', ''frontend-id'': ''3'',
''type'': ''file''} to
/local/domain
/0/backend/vbd/3/5632.
[2008-03-08 16:34:20 xend 5195] DEBUG (__init__:1072) DevController: writing
{''backend-id'': ''0'', ''mac'':
''00:16:3e:5d:63:f8'', ''handle'':
''0'', ''state'': ''1''
, ''backend'':
''/local/domain/0/backend/vif/3/0''} to
/local/domain/3/device/vif/0.
[2008-03-08 16:34:20 xend 5195] DEBUG (__init__:1072) DevController: writing
{''domain'': ''chronojump'',
''handle'': ''0'', ''script'':
''/etc/xen/scripts/vif-rou
te'', ''ip'': ''192.168.0.150'',
''state'': ''1'', ''frontend'':
''/local/domain/3/device/vif/0'', ''mac'':
''00:16:3e:5d:63:f8'', ''online'':
''1'',
''frontend-id'': ''3''} to
/local/domain/0/backend/vif/3/0.
[2008-03-08 16:34:20 xend 5195] INFO (__init__:1072) spawning device models:
/usr/lib64/xen-3.0.3-1/bin/qemu-dm
[''/usr/lib64/xen-3.0.3-1/bin/qemu-dm'', ''
-d'', ''3'', ''-m'',
''256'', ''-boot'', ''d'',
''-vcpus'', ''1'',
''-domain-name'',
''chronojump'', ''-vncunused'',
''-k'', ''en-us'',
''-vnclisten'', ''192.168.0.1'']
[2008-03-08 16:34:20 xend 5195] INFO (__init__:1072) device model pid: 6184
[2008-03-08 16:34:20 xend.XendDomainInfo 5195] DEBUG (__init__:1072) Storing
VM details: {''shadow_memory'': ''3'',
''uuid'': ''e5f8cbae-e126-967f-55d5-9d5f7c7
be5dc'', ''on_reboot'': ''restart'',
''start_time'': ''1204990460.52'',
''on_poweroff'': ''destroy'',
''name'': ''chronojump'',
''xend/restart_count'': ''0'',
''vcpus'': ''1'',
''vcpu_avail'': ''1'',
''memory'': ''256'',
''on_crash'': ''restart'',
''image'': "(hvm
(kernel /usr/lib64/xen-3.0.3-1/boot/hvmloader) (args
''VNC_VIEWER=127.0.0.1:550
1 '') (pae 1) (vcpus 1) (boot d) (vnc 1) (vncunused 1) (xauthority
/root/.Xauthority) (device_model /usr/lib64/xen-3.0.3-1/bin/qemu-dm))",
''maxmem'': ''256
''}
[2008-03-08 16:34:20 xend.XendDomainInfo 5195] DEBUG (__init__:1072) Storing
domain details: {''console/port'': ''2'',
''name'': ''chronojump'',
''console/limit''
: ''1048576'', ''vm'':
''/vm/e5f8cbae-e126-967f-55d5-9d5f7c7be5dc'',
''domid'': ''3'',
''cpu/0/availability'': ''online'',
''memory/target'': ''262144'',
''store/ring-ref''
: ''281761'', ''store/port'':
''1''}
[2008-03-08 16:34:20 xend 5195] DEBUG (__init__:1072) hvm_shutdown fired,
shutdown reason=None
[2008-03-08 16:34:20 xend.XendDomainInfo 5195] DEBUG (__init__:1072)
XendDomainInfo.handleShutdownWatch
[2008-03-08 16:34:20 xend 5195] DEBUG (__init__:1072) Waiting for devices
vif.
[2008-03-08 16:34:20 xend 5195] DEBUG (__init__:1072) Waiting for 0.
[2008-03-08 16:34:20 xend 5195] DEBUG (__init__:1072) hotplugStatusCallback
/local/domain/0/backend/vif/3/0/hotplug-status.
[2008-03-08 16:34:20 xend 5195] DEBUG (__init__:1072) hotplugStatusCallback
/local/domain/0/backend/vif/3/0/hotplug-status.
[2008-03-08 16:34:20 xend 5195] DEBUG (__init__:1072) hotplugStatusCallback
1.
[2008-03-08 16:34:20 xend 5195] DEBUG (__init__:1072) Waiting for devices
usb.
[2008-03-08 16:34:20 xend 5195] DEBUG (__init__:1072) Waiting for devices
vbd.
[2008-03-08 16:34:20 xend 5195] DEBUG (__init__:1072) Waiting for 2049.
[2008-03-08 16:34:20 xend 5195] DEBUG (__init__:1072) hotplugStatusCallback
/local/domain/0/backend/vbd/3/2049/hotplug-status.
[2008-03-08 16:34:22 xend 5195] DEBUG (__init__:1072) hotplugStatusCallback
/local/domain/0/backend/vbd/3/2049/hotplug-status.
[2008-03-08 16:34:22 xend 5195] DEBUG (__init__:1072) hotplugStatusCallback
1.
[2008-03-08 16:34:22 xend 5195] DEBUG (__init__:1072) Waiting for 5632.
[2008-03-08 16:34:22 xend 5195] DEBUG (__init__:1072) hotplugStatusCallback
/local/domain/0/backend/vbd/3/5632/hotplug-status.
[2008-03-08 16:34:22 xend 5195] DEBUG (__init__:1072) hotplugStatusCallback
1.
[2008-03-08 16:34:22 xend 5195] DEBUG (__init__:1072) Waiting for devices
irq.
[2008-03-08 16:34:22 xend 5195] DEBUG (__init__:1072) Waiting for devices
pci.
[2008-03-08 16:34:22 xend 5195] DEBUG (__init__:1072) Waiting for devices
ioports.
[2008-03-08 16:34:22 xend 5195] DEBUG (__init__:1072) Waiting for devices
tap.
[2008-03-08 16:34:22 xend 5195] DEBUG (__init__:1072) Waiting for devices
vtpm.
[2008-03-08 16:34:22 xend 5195] INFO (__init__:1072) Domain chronojump (3)
unpaused.
[2008-03-08 16:36:50 xend 5195] ERROR (__init__:1072) method
"xend_vnets" is
not supported
hotplug-status.
[2008-03-08 16:34:22 xend 5195] DEBUG (__init__:1072) hotplugStatusCallback
/local/domain/0/backend/vbd/3/2049/hotplug-status.
[2008-03-08 16:34:22 xend 5195] DEBUG (__init__:1072) hotplugStatusCallback
1.
[2008-03-08 16:34:22 xend 5195] DEBUG (__init__:1072) Waiting for 5632.
[2008-03-08 16:34:22 xend 5195] DEBUG (__init__:1072) hotplugStatusCallback
/local/domain/0/backend/vbd/3/5632/hotplug-status.
[2008-03-08 16:34:22 xend 5195] DEBUG (__init__:1072) hotplugStatusCallback
1.
[2008-03-08 16:34:22 xend 5195] DEBUG (__init__:1072) Waiting for devices
irq.
[2008-03-08 16:34:22 xend 5195] DEBUG (__init__:1072) Waiting for devices
pci.
[2008-03-08 16:34:22 xend 5195] DEBUG (__init__:1072) Waiting for devices
ioports.
[2008-03-08 16:34:22 xend 5195] DEBUG (__init__:1072) Waiting for devices
tap.
[2008-03-08 16:34:22 xend 5195] DEBUG (__init__:1072) Waiting for devices
vtpm.
[2008-03-08 16:34:22 xend 5195] INFO (__init__:1072) Domain chronojump (3)
unpaused.
------------------------------
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
End of Xen-users Digest, Vol 37, Issue 48
*****************************************
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Hello, On Mar/08/2008, Max E. Baro wrote:> You need to specify ''type=ioemu'' in your vif line. If running multiple > domu''s you should also specify a unique mac address for each one. Also in > my version of XEN (3.0.3) the domu would not start if I didn''t have a bridge > created ahead of time even though I am using route and not bridge. I fixed > this by adding ''brctl addbr xenbr0'' to network-route.thank you! finally I have a NIC card! :-) I spent lot of time yesterday for this issue. We use the same Xen version, I also needed to add brctl. Thank again! -- Carles Pina i Estany GPG id: 0x8CBDAE64 http://pinux.info Manresa - Barcelona _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Sorry, I guess I forgot to elaborate on the rest of the setup to make it
work.
I modified vif-route because the default behavior is to set the eth0 ip
address to the vif interface and I could never get that to work properly.
Instead I assign the IP in the configuration file as you did, but I assign a
network number address, not a host address.
vif-route:
dir=$(dirname "$0")
. "$dir/vif-common.sh"
main_ip=$(dom0_ip)
case "$command" in
online)
ifconfig ${vif} ${ip} netmask 255.255.255.255 up
<<<<< changed to ip from main_ip
echo 1 >/proc/sys/net/ipv4/conf/${vif}/proxy_arp
ipcmd=''add''
cmdprefix=''''
;;
offline)
do_without_error ifdown ${vif}
ipcmd=''del''
cmdprefix=''do_without_error''
;;
esac
if [ "${ip}" ] ; then
# If we''ve been given a list of IP addresses, then add routes from
dom0
to
# the guest using those addresses.
for addr in ${ip} ; do
${cmdprefix} ip route ${ipcmd} ${addr} dev ${vif} src ${main_ip}
<<<<<<<<<<<<<<< same here
done
fi
handle_iptable
log debug "Successful vif-route $command for $vif."
if [ "$command" == "online" ]
then
success
fi
Then in config I assign IP as "192.168.1.0". This is important
because you
will cause a conflict with the eth0 adapter inside the domU. In my domU I
configure ifcfg-eth0 with IPADDRESS=192.168.1.2. AFTER the domU is started
I assign IP address 192.168.1.1 to the tap/tun device created in dom0 for
that domain.
Here is where the problem with routing comes in. The tap/tun device created
is not specific to the domU id in anyway, it depends in what order the
domU''s are created. If you have two HVM domains and each only one nic
assigned, then the first one to be created will use device tap0 and the
second one created will use tap1. I have not found a way to specify which
tap device to create so I cannot assign the IP address for the tap device
automatically on startup.
Max Baro
Technical Support Supervisor
FACTS Services, Inc.
(305) 284 - 7440
meb@factsservices.com
-----Original Message-----
From: Carles Pina i Estany [mailto:carles@pina.cat]
Sent: Sunday, March 09, 2008 5:44 AM
To: Max E. Baro
Cc: ''xen-users@lists.xensource.com''
Subject: Re: [Xen-users] domU HVM network problem
Hello,
On Mar/08/2008, Max E. Baro wrote:> You need to specify ''type=ioemu'' in your vif line. If
running multiple
> domu''s you should also specify a unique mac address for each one.
Also in
> my version of XEN (3.0.3) the domu would not start if I didn''t
have a
bridge> created ahead of time even though I am using route and not bridge. I
fixed> this by adding ''brctl addbr xenbr0'' to network-route.
thank you! finally I have a NIC card! :-) I spent lot of time yesterday
for this issue. We use the same Xen version, I also needed to add brctl.
Thank again!
--
Carles Pina i Estany GPG id: 0x8CBDAE64
http://pinux.info Manresa - Barcelona
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Hello, On Mar/09/2008, Max E. Baro wrote:> Sorry, I guess I forgot to elaborate on the rest of the setup to make it > work.don''t worrie...> I modified vif-route because the default behavior is to set the eth0 > ip address to the vif interface and I could never get that to work > properly. Instead I assign the IP in the configuration file as you > did, but I assign a network number address, not a host address.in /etc/xend/machine.cfg, do you assign a network address? Could you show me what do you mean? I''m not sure if I get the point :-( [here you explained some changes in vif-route, I did it and now the vifXX.0 has the domU IP and not dom0, good!]> Then in config I assign IP as "192.168.1.0". This is important because youin the domU config? in the vif line? If I set up [''ip=192.168.0.0,type=ioemu''], after xm create NAME I get: ---- Error: Device 0 (vif) could not be connected. Backend device not found. ---- (Are you using the same network for domU and dom0? -192.168.1.0/24- or are you using two different networks? -like 192.168.1.0/24 and 192.168.0.0/24?)> will cause a conflict with the eth0 adapter inside the domU. In my domU I > configure ifcfg-eth0 with IPADDRESS=192.168.1.2. AFTER the domU is started > I assign IP address 192.168.1.1 to the tap/tun device created in dom0 for > that domain.ok I understand (but I cannot ping it from domU to dom0 :-( )> Here is where the problem with routing comes in. The tap/tun device created > is not specific to the domU id in anyway, it depends in what order the > domU''s are created. If you have two HVM domains and each only one nic > assigned, then the first one to be created will use device tap0 and the > second one created will use tap1. I have not found a way to specify which > tap device to create so I cannot assign the IP address for the tap device > automatically on startup.well, I will be able to handle it in some way... after I have one machine working :-) Thank you a lot again, I think that I''m the last steps (I hope!) -- Carles Pina i Estany GPG id: 0x8CBDAE64 http://pinux.info Manresa - Barcelona _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
By network address I mean in the machine.cfg on the vif= line instead of
assigning an IP address I use the network address which in TCP/IP end in a
zero. This is because the VIF is not actually the tunnel to the domU nic.
My vif line looks like this:
vif = [ ''type=ioemu, vifname=vif0.0, ip=192.168.0.0,
mac=FA:CE:00:00:00:01''
]
You have to make sure the tuntap module is loaded by typing lsmod:
[root@srv140 xen]# lsmod
Module Size Used by
xt_tcpudp 36417 1
xt_physdev 36049 2
iptable_filter 36161 1
ip_tables 55329 1 iptable_filter
x_tables 50249 3 xt_tcpudp,xt_physdev,ip_tables
tun 44993 1
<<<<<<<<<<<<<<<<<<<<<<<<<
When I tested with Xen 3.0.1 the system craeted tun0 for the first domain.
Now in Xen 3.0.3 it creates tap0. You have to type ifconfig -a to see the
tun/tap devices and they are only created while the domU is running. They
get deleted when you shutdown the domU. To keep things standard TCP/IP I
assign the first address of the subnet to the tun/tap device and make that
address the default gateway inside the domU:
in dom0:
tap0 Link encap:Ethernet HWaddr CE:B9:F8:5E:22:D1
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
in domU:
[root@Xdom1 ~]# ip r
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.2
default via 192.168.0.1 dev eth0
My dom0 and each of my domU''s are all on different subnets so I can use
dom0
as a router.
I hope this helps.
Max Baro
Technical Support Supervisor
FACTS Services, Inc.
(305) 284 - 7440
meb@factsservices.com
-----Original Message-----
From: Carles Pina i Estany [mailto:carles@pina.cat]
Sent: Sunday, March 09, 2008 5:54 PM
To: Max E. Baro
Cc: ''xen-users@lists.xensource.com''
Subject: Re: [Xen-users] domU HVM network problem
Hello,
On Mar/09/2008, Max E. Baro wrote:> Sorry, I guess I forgot to elaborate on the rest of the setup to make it
> work.
don''t worrie...
> I modified vif-route because the default behavior is to set the eth0
> ip address to the vif interface and I could never get that to work
> properly. Instead I assign the IP in the configuration file as you
> did, but I assign a network number address, not a host address.
in /etc/xend/machine.cfg, do you assign a network address? Could you
show me what do you mean? I''m not sure if I get the point :-(
[here you explained some changes in vif-route, I did it and now the
vifXX.0 has the domU IP and not dom0, good!]
> Then in config I assign IP as "192.168.1.0". This is important
because
you
in the domU config? in the vif line? If I set up
[''ip=192.168.0.0,type=ioemu''], after xm create NAME I get:
----
Error: Device 0 (vif) could not be connected. Backend device not found.
----
(Are you using the same network for domU and dom0? -192.168.1.0/24- or
are you using two different networks? -like 192.168.1.0/24 and
192.168.0.0/24?)
> will cause a conflict with the eth0 adapter inside the domU. In my domU I
> configure ifcfg-eth0 with IPADDRESS=192.168.1.2. AFTER the domU is
started> I assign IP address 192.168.1.1 to the tap/tun device created in dom0 for
> that domain.
ok I understand (but I cannot ping it from domU to dom0 :-( )
> Here is where the problem with routing comes in. The tap/tun device
created> is not specific to the domU id in anyway, it depends in what order the
> domU''s are created. If you have two HVM domains and each only one
nic
> assigned, then the first one to be created will use device tap0 and the
> second one created will use tap1. I have not found a way to specify which
> tap device to create so I cannot assign the IP address for the tap device
> automatically on startup.
well, I will be able to handle it in some way... after I have one
machine working :-)
Thank you a lot again, I think that I''m the last steps (I hope!)
--
Carles Pina i Estany GPG id: 0x8CBDAE64
http://pinux.info Manresa - Barcelona
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Hello, On Mar/09/2008, Max E. Baro wrote:> By network address I mean in the machine.cfg on the vif= line instead of > assigning an IP address I use the network address which in TCP/IP end in a > zero. This is because the VIF is not actually the tunnel to the domU nic. > My vif line looks like this: > > vif = [ ''type=ioemu, vifname=vif0.0, ip=192.168.0.0, mac=FA:CE:00:00:00:01''correct, yesterday night I tried (in ip) the same LAN than eth0 in dom0 and Xen was failing to create the machine, now is fine.> You have to make sure the tuntap module is loaded by typing lsmod:yes, it''s there> in dom0: > tap0 Link encap:Ethernet HWaddr CE:B9:F8:5E:22:D1 > inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0same here> in domU: > [root@Xdom1 ~]# ip r > 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.2 > default via 192.168.0.1 dev eth0I cannot ping from domU to the 192.168.0.1 :-(> My dom0 and each of my domU''s are all on different subnets so I can > use dom0 as a router. > > I hope this helps.192.168.10.150 is my domU IP 192.168.10.1 is my dom0 IP for tap0 192.168.0.1 is my dom0 IP for eth0 If I ping from domU to dom0 I can see "something": ----------- servidor:/etc/xen/scripts# tcpdump -i tap0 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on tap0, link-type EN10MB (Ethernet), capture size 96 bytes 09:28:29.965232 arp who-has 192.168.10.1 tell 192.168.10.150 09:28:30.965280 arp who-has 192.168.10.1 tell 192.168.10.150 09:28:31.965310 arp who-has 192.168.10.1 tell 192.168.10.150 09:28:33.965421 arp who-has 192.168.10.1 tell 192.168.10.150 ----------- But not answering. My dom0 network configuration is: ------- tap0 Link encap:Ethernet HWaddr 7E:2D:04:8D:94:CF inet addr:192.168.10.1 Bcast:192.168.10.255 Mask:255.255.255.0 inet6 addr: fe80::7c2d:4ff:fe8d:94cf/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:404 errors:0 dropped:0 overruns:0 frame:0 TX packets:18 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:24848 (24.2 KiB) TX bytes:972 (972.0 b) vif38.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet addr:192.168.10.0 Bcast:192.168.10.255 Mask:255.255.255.255 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) eth0 Link encap:Ethernet HWaddr 00:1A:A0:D9:D5:CE inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::21a:a0ff:fed9:d5ce/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3515449 errors:0 dropped:0 overruns:0 frame:0 TX packets:3748272 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1491664039 (1.3 GiB) TX bytes:3251114826 (3.0 GiB) Interrupt:16 ------- (I executed echo 1 > /proc/sys/net/ipv4/conf/tun0/proxy_arp, just in case) What we have different? Thank you for all your help! -- Carles Pina i Estany GPG id: 0x8CBDAE64 http://pinux.info Manresa - Barcelona _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello, On Mar/10/2008, Carles Pina i Estany wrote:> > Hello, > > On Mar/09/2008, Max E. Baro wrote:> ----------- > servidor:/etc/xen/scripts# tcpdump -i tap0 > tcpdump: verbose output suppressed, use -v or -vv for full protocol > decode > listening on tap0, link-type EN10MB (Ethernet), capture size 96 bytes > 09:28:29.965232 arp who-has 192.168.10.1 tell 192.168.10.150 > 09:28:30.965280 arp who-has 192.168.10.1 tell 192.168.10.150 > 09:28:31.965310 arp who-has 192.168.10.1 tell 192.168.10.150 > 09:28:33.965421 arp who-has 192.168.10.1 tell 192.168.10.150 > -----------I suspect about that bridge that I did yesterday. Could you show me your brctl show output? The question is... the bridge xenbr0 has, as interface, tap0 only? Or has some other interface like eth0? I would like to test but now it''s a remote machine :-) Thanks a lot again, -- Carles Pina i Estany GPG id: 0x8CBDAE64 http://pinux.info Manresa - Barcelona _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I create a bridge in network-route but I don''t use it. I commented out the ''brctl addif'' command in /etc/qemu-ifup. I also did not enable proxy_arp in this configuration. Verify the routing in your dom0 with ''ip r'' and make sure they are correct. The routes are added by vif-route per interface. Also, you will need to make sure the default gateway in your domU is pointing to 192.168.10.1. Can you ping that address from the domU? In dom0 you should have a route to the domU interface: 192.168.0.0 dev vif0.0 scope link src 192.168.4.53 Max Baro Technical Support Supervisor FACTS Services, Inc. (305) 284 - 7440 meb@factsservices.com -----Original Message----- From: Carles Pina i Estany [mailto:carles@pina.cat] Sent: Monday, March 10, 2008 4:38 AM To: Max E. Baro Cc: ''xen-users@lists.xensource.com'' Subject: Re: [Xen-users] domU HVM network problem Hello, On Mar/09/2008, Max E. Baro wrote:> By network address I mean in the machine.cfg on the vif= line instead of > assigning an IP address I use the network address which in TCP/IP end in a > zero. This is because the VIF is not actually the tunnel to the domU nic. > My vif line looks like this: > > vif = [ ''type=ioemu, vifname=vif0.0, ip=192.168.0.0,mac=FA:CE:00:00:00:01'' correct, yesterday night I tried (in ip) the same LAN than eth0 in dom0 and Xen was failing to create the machine, now is fine.> You have to make sure the tuntap module is loaded by typing lsmod:yes, it''s there> in dom0: > tap0 Link encap:Ethernet HWaddr CE:B9:F8:5E:22:D1 > inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0same here> in domU: > [root@Xdom1 ~]# ip r > 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.2 > default via 192.168.0.1 dev eth0I cannot ping from domU to the 192.168.0.1 :-(> My dom0 and each of my domU''s are all on different subnets so I can > use dom0 as a router. > > I hope this helps.192.168.10.150 is my domU IP 192.168.10.1 is my dom0 IP for tap0 192.168.0.1 is my dom0 IP for eth0 If I ping from domU to dom0 I can see "something": ----------- servidor:/etc/xen/scripts# tcpdump -i tap0 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on tap0, link-type EN10MB (Ethernet), capture size 96 bytes 09:28:29.965232 arp who-has 192.168.10.1 tell 192.168.10.150 09:28:30.965280 arp who-has 192.168.10.1 tell 192.168.10.150 09:28:31.965310 arp who-has 192.168.10.1 tell 192.168.10.150 09:28:33.965421 arp who-has 192.168.10.1 tell 192.168.10.150 ----------- But not answering. My dom0 network configuration is: ------- tap0 Link encap:Ethernet HWaddr 7E:2D:04:8D:94:CF inet addr:192.168.10.1 Bcast:192.168.10.255 Mask:255.255.255.0 inet6 addr: fe80::7c2d:4ff:fe8d:94cf/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:404 errors:0 dropped:0 overruns:0 frame:0 TX packets:18 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:24848 (24.2 KiB) TX bytes:972 (972.0 b) vif38.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet addr:192.168.10.0 Bcast:192.168.10.255 Mask:255.255.255.255 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) eth0 Link encap:Ethernet HWaddr 00:1A:A0:D9:D5:CE inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::21a:a0ff:fed9:d5ce/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3515449 errors:0 dropped:0 overruns:0 frame:0 TX packets:3748272 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1491664039 (1.3 GiB) TX bytes:3251114826 (3.0 GiB) Interrupt:16 ------- (I executed echo 1 > /proc/sys/net/ipv4/conf/tun0/proxy_arp, just in case) What we have different? I suspect about that bridge that I did yesterday. Could you show me your brctl show output? The question is... the bridge xenbr0 has, as interface, tap0 only? Or has some other interface like eth0? I would like to test but now it''s a remote machine :-) Thank you for all your help! -- Carles Pina i Estany GPG id: 0x8CBDAE64 http://pinux.info Manresa - Barcelona _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello, On Mar/10/2008, Max E. Baro wrote:> Verify the routing in your dom0 with ''ip r'' and make sure they are correct. > The routes are added by vif-route per interface. Also, you will need to > make sure the default gateway in your domU is pointing to 192.168.10.1. Can > you ping that address from the domU?not yet :-(> In dom0 you should have a route to the domU interface: > > 192.168.0.0 dev vif0.0 scope link src 192.168.4.53could you copy-paste the ip r output for vif0.0 (Ok, I have it), tap0, ifconfig tap0, ifconfig vif0.0 and tell me your internal IP address of eth0? When this will be working in my configuration I will write it in some public place :-) I still have some problems with ARP, asking and not answering... maybe I will get it in some minutes, hours or days without your help :-) Thanks Max, -- Carles Pina i Estany GPG id: 0x8CBDAE64 http://pinux.info Manresa - Barcelona _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users