[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Debian Lenny, Xen 3.4.1 and DomU restart on xend restart


  • To: <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: "Etienne FLYE STE MARIE" <Etienne.Flye@xxxxxxxxx>
  • Date: Fri, 15 Jan 2010 15:20:16 +0100
  • Delivery-date: Fri, 15 Jan 2010 06:22:24 -0800
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: AcqV7dvermJtRAjTSyOw87jtpiW4XQ==
  • Thread-topic: Debian Lenny, Xen 3.4.1 and DomU restart on xend restart

Hello everybody,

 

I’m a recent user of xen hypervisor and after using deb version of Xen, I try to use a compiled version.

Compilation/Install is ok but my problem is that after xend stop/start or reboot, my domain doesn’t want to restart automatically.

 

I use :

Debian 5.0.3

Debian kernel 2.6.26-2-xen-686

Xen hypervisor 3.4.2 compiled from sources

 

I use these files configuration

 

In /etc/modprobe.d/aliases :

alias bond0 bonding

options bonding mode=6 miimon=100 downdelay=200 updelay=200

 

In /etc/network/interfaces:

auto br0

iface br0 inet static

        pre-up ifconfig bond0 up

        pre-up ifenslave bond0 eth0 eth1

        pre-up brctl addbr br0

        pre-up brctl addif br0 bond0

        pre-up ifconfig bond0 0.0.0.0 promisc up

        address 10.15.20.67

        netmask 255.255.255.0

        network 10.15.20.0

        broadcast 10.15.20.255

        gateway 10.15.20.1

        post-down delif br0 bond0

        post-down brctl addbr br0

        post-down ifconfig bond0 down

 

In /etc/xen/xend-config.sxp

 

(network-script network-dummy)

(vif-script vif-bridge)

 

In myDomU.cfg:

 

kernel      = '/boot/vmlinuz-2.6.26-2-xen-686'

ramdisk     = '/boot/initrd.img-2.6.26-2-xen-686'

memory      = '3000'

vcpus       =  4

 

root        = '/dev/xvda2 ro'

disk        = [

                  'file:/home/xen/domains/myDomU/swap.img,xvda1,w',

                  'file:/home/xen/domains/myDomU/disk.img,xvda2,w',

              ]

 

name        = ‘myDomU '

 

vif         = [ 'bridge=br0' ]

 

on_reboot   = 'restart'

on_crash    = 'restart'

max_vcpu_id': 3, 'cpu_time': 30756440432L, 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 0, 'dying': 0,'online_vcpus': 4, 'domid': 0, 'paused': 0, 'crashed': 0, 'running': 1, 'maxmem_kb': 4294967292L, 'shutdown': 0, 'mem_kb': 5221376L, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'blocked': 0, 'name':'Domain-0'})

[2010-01-15 15:03:17 5279] INFO (XendDomainInfo:158) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0

[2010-01-15 15:03:17 5279] DEBUG (XendDomain:453) Adding Domain: 0

[2010-01-15 15:03:17 5279] DEBUG (XendDomainInfo:1709) XendDomainInfo.handleShutdownWatch

[2010-01-15 15:03:17 5279] DEBUG (XendDomain:387) number of vcpus to use is 0

[2010-01-15 15:03:17 5279] DEBUG (XendDomainInfo:140) XendDomainInfo.recreate({'max_vcpu_id': 3, 'cpu_time': 11980077197L, 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 0, 'dying': 0, 'online_vcpus': 4, 'domid': 3, 'paused': 0, 'crashed': 0, 'running': 0, 'maxmem_kb': 3072000L, 'shutdown': 1, 'mem_kb': 3072000L, 'handle': [204, 60, 144, 79, 234, 148, 231, 84, 78, 248, 157, 230, 10, 214, 228, 207], 'blocked': 0})

[2010-01-15 15:03:17 5279] INFO (XendDomainInfo:158) Recreating domain 3, UUID cc3c904f-ea94-e754-4ef8-9de60ad6e4cf. at /local/domain/3

[2010-01-15 15:03:17 5279] DEBUG (XendDomain:453) Adding Domain: 3

[2010-01-15 15:03:17 5279] INFO (XendDomainInfo:1903) Domain has shutdown: name= myDomU id=3 reason=poweroff.

[2010-01-15 15:03:17 5279] DEBUG (XendDomainInfo:2732) XendDomainInfo.destroy: domid=3

[2010-01-15 15:03:17 5279] DEBUG (XendDomainInfo:2207) Destroying device model

[2010-01-15 15:03:17 5279] DEBUG (XendDomainInfo:2214) Releasing devices

[2010-01-15 15:03:17 5279] DEBUG (XendDomainInfo:2227) Removing vif/0

[2010-01-15 15:03:17 5279] DEBUG (XendDomainInfo:1134) XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0

[2010-01-15 15:03:17 5279] DEBUG (XendDomainInfo:2227) Removing vbd/51713

[2010-01-15 15:03:17 5279] DEBUG (XendDomainInfo:1134) XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/51713

[2010-01-15 15:03:17 5279] DEBUG (XendDomainInfo:2227) Removing vbd/51714

[2010-01-15 15:03:17 5279] DEBUG (XendDomainInfo:1134) XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/51714

[2010-01-15 15:03:17 5279] DEBUG (XendDomainInfo:2227) Removing console/0

[2010-01-15 15:03:17 5279] DEBUG (XendDomainInfo:1134) XendDomainInfo.destroyDevice: deviceClass = console, device = console/0

[2010-01-15 15:03:17 5279] DEBUG (XendDomainInfo:2212) No device model

[2010-01-15 15:03:17 5279] DEBUG (XendDomainInfo:2214) Releasing devices

[2010-01-15 15:03:17 5279] WARNING (XendAPI:701) API call: VBD.set_device not found

[2010-01-15 15:03:17 5279] WARNING (XendAPI:701) API call: VBD.set_type not found

[2010-01-15 15:03:17 5279] WARNING (XendAPI:701) API call: session.get_all_records not found

[2010-01-15 15:03:17 5279] WARNING (XendAPI:701) API call: event.get_record not found

[2010-01-15 15:03:17 5279] WARNING (XendAPI:701) API call: event.get_all not found

[2010-01-15 15:03:17 5279] WARNING (XendAPI:701) API call: VIF.get_network not found

[2010-01-15 15:03:17 5279] WARNING (XendAPI:701) API call: VIF.set_device not found

[2010-01-15 15:03:17 5279] WARNING (XendAPI:701) API call: VIF.set_MAC not found

[2010-01-15 15:03:17 5279] WARNING (XendAPI:701) API call: VIF.set_MTU not found

[2010-01-15 15:03:17 5279] WARNING (XendAPI:701) API call: debug.get_all not found

[2010-01-15 15:03:17 5279] INFO (XMLRPCServer:156) Opening Unix domain socket XML-RPC server on /var/run/xend/xen-api.sock; authentication has been disabled for this server.

[2010-01-15 15:03:17 5279] INFO (XMLRPCServer:156) Opening Unix domain socket XML-RPC server on /var/run/xend/xmlrpc.sock.

 

 

Do I miss a configuration part?

 

Thanks a lot

Etienne

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.