Re: [Xen-users] Assign IP's

["Eric Peterson" <srcfoo@xxxxxxxxx>]

Try 'modprobe loop' in domain 0 before trying to start your guest domains.

On 8/7/06, Stefano Cislaghi <s.cislaghi@xxxxxxxxx> wrote:
> Also me I'm experiencing in a similar problem. I want that my virtual
> machine get a static IP from outside. This is my cfg file:
>
> xen:~# vi /etc/xen/vx1.cfg
>
> kernel = '/boot/vmlinuz-2.6.16-2-xen-686'
> ramdisk = '/boot/initrd.img-2.6.16-2-xen-686'
> memory = 256
> name   = 'vx1'
> root   = '/dev/sda1 ro'
> disk   = [ 'file:/vx/domains/vx1/disk.img,sda1,w',
> 'file:/vx/domains/vx1/swap.img,sda2,w' ]
>
> # network
> vif=[ '' ]
> dhcp="off"
> ip="151.39.235.217"
> netmask="255.255.255.192"
> gateway="151.39.235.193"
> hostname="vx1.sysman.iol.it"
>
> extra="3"
>
>
> xen:~# ifconfig
> eth0      Link encap:Ethernet  HWaddr 00:0E:0C:30:AA:BE
>           inet addr:151.39.235.216  Bcast:151.39.235.255  Mask:255.255.255.192
>           inet6 addr: fe80::20e:cff:fe30:aabe/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:2576 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:231 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:179952 (175.7 KiB)  TX bytes:24496 (23.9 KiB)
>
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           inet6 addr: ::1/128 Scope:Host
>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>           RX packets:8 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:560 (560.0 b)  TX bytes:560 (560.0 b)
>
> peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>           UP BROADCAST RUNNING NOARP MULTICAST  MTU:1500  Metric:1
>           RX packets:2579 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:245 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:100
>           RX bytes:191883 (187.3 KiB)  TX bytes:26494 (25.8 KiB)
>           Base address:0x2040 Memory:fe6a0000-fe6c0000
>
> vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:231 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:2581 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:24496 (23.9 KiB)  TX bytes:180338 (176.1 KiB)
>
> xenbr0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>           inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:2292 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:122371 (119.5 KiB)  TX bytes:468 (468.0 b)
>
>
>
> But domU does not start:
>
> xen:~# xm create vx1.cfg -c
> Using config file "/etc/xen/vx1.cfg".
> Error: Device 2049 (vbd) could not be connected. Backend device not found.
>
> In /var/log/xen-hotplug.log I've found:
>
> interface vif1.0 does not exist!
> xenstore-read: couldn't read path backend/vbd/1/2049/node
> xenstore-read: couldn't read path backend/vbd/1/2050/node
> xenstore-read: couldn't read path backend/vbd/2/2049/node
> xenstore-read: couldn't read path backend/vbd/2/2050/node
> xenstore-read: couldn't read path backend/vbd/3/2049/node
> xenstore-read: couldn't read path backend/vbd/3/2050/node
> xenstore-read: couldn't read path backend/vbd/4/2049/node
> xenstore-read: couldn't read path backend/vbd/4/2050/node
>
> And in /var/log/xend.log I got:
>
> [2006-08-07 16:54:32 xend.XendDomainInfo] DEBUG (XendDomainInfo:877)
> XendDomainInfo.handleShutdownWatch
> [2006-08-07 16:54:32 xend] DEBUG (DevController:132) Waiting for devices vif.
> [2006-08-07 16:54:32 xend] DEBUG (DevController:138) Waiting for 0.
> [2006-08-07 16:54:32 xend] DEBUG (DevController:403)
> hotplugStatusCallback /local/domain/0/backend/vif/4/0/hotplug-status.
> [2006-08-07 16:54:32 xend] DEBUG (DevController:403)
> hotplugStatusCallback /local/domain/0/backend/vif/4/0/hotplug-status.
> [2006-08-07 16:54:32 xend] DEBUG (DevController:417) hotplugStatusCallback 1.
> [2006-08-07 16:54:32 xend] DEBUG (DevController:132) Waiting for devices usb.
> [2006-08-07 16:54:32 xend] DEBUG (DevController:132) Waiting for devices vbd.
> [2006-08-07 16:54:32 xend] DEBUG (DevController:138) Waiting for 2049.
> [2006-08-07 16:54:32 xend] DEBUG (DevController:403)
> hotplugStatusCallback
> /local/domain/0/backend/vbd/4/2049/hotplug-status.
> [2006-08-07 16:54:32 xend] DEBUG (DevController:417) hotplugStatusCallback 2.
> [2006-08-07 16:54:32 xend.XendDomainInfo] DEBUG (XendDomainInfo:1327)
> XendDomainInfo.destroy: domid=4
> [2006-08-07 16:54:32 xend.XendDomainInfo] DEBUG (XendDomainInfo:1335)
> XendDomainInfo.destroyDomain(4)
>
>
>
> Maybe can something be wrong in /etc/xen/xend-config.sxp ? Now is
> uncommented only:
> (network-script network-bridge)
> (network-script network-dummy)
> (vif-script vif-bridge)
>
>
>
> Thanks
> Stefano
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users