[one-users] Problem boot VM template with opennebula
Javier Fontan
jfontan at opennebula.org
Mon Apr 14 07:30:55 PDT 2014
To automate it I can only think of a script that does that for you.
The output format of templates when updating is fairly standard as it
is converted from xml back to the template format.
A way to do that without calling directly the API is creating a script
that changes PORT = "-1" to nothing or PORT = "" and adds CPU when it
is not found. Change EDITOR to that script and iterate over all the
templates calling onetemplate update.
On Mon, Apr 14, 2014 at 3:46 PM, Steven Timm <timm at fnal.gov> wrote:
>
> Is there any way as part of the upgrading from older versions to newer
> versions to automatically modify the templates?
>
> We have 200-some user templates which specify PORT=-1 which is no longer
> allowed in ONE4.4. We have already checked and found that the onedb
> upgrade command does not remove deprecated syntax from the template pool
> database table, nor does it add fields that are now required (CPU) that
> didn't use to be. Short of doing "onetemplate update" 200 times, what is
> our option?
>
> Steve Timm
>
>
>
> On Mon, 14 Apr 2014, Javier Fontan wrote:
>
>> No. I am talking about the VM template.
>>
>> On Mon, Apr 14, 2014 at 12:47 PM, Cuquerella Sanchez, Javier
>> <javier.cuquerella at atos.net> wrote:
>>>
>>> Hi,
>>>
>>> this is enabled in sunstone-server. conf, no? and when you are indicating
>>> that the port has to be empty you mean the value of: vnc_proxy_port?
>>>
>>> Regards
>>>
>>> ---------------------------------------------------
>>> Javier Cuquerella Sánchez
>>>
>>> Javier.cuquerella at atos.net
>>> Atos Research & Innovation
>>> Systems Administrator
>>> Albarracin 25
>>> 28037-Madrid (SPAIN)
>>> Tfno: +34.91.214.8080
>>> www.atosresearch.eu
>>> es.atos.net
>>>
>>>
>>>
>>> -----Original Message-----
>>> From: Javier Fontan [mailto:jfontan at opennebula.org]
>>> Sent: Monday, April 14, 2014 12:17 PM
>>> To: Cuquerella Sanchez, Javier; users at lists.opennebula.org
>>> Subject: Re: Problem boot VM template with opennebula
>>>
>>> Just don't specify the port. If you are manually modifying templates this
>>> is the configuration for VNC that automatically generates the
>>> port:
>>>
>>> --8<------
>>> GRAPHICS = [
>>> TYPE = "vnc",
>>> LISTEN = "0.0.0.0"]
>>> ------>8--
>>>
>>> In Sunstone VNC must be activated and the port value empty. Make sure
>>> that the listen IP is "0.0.0.0".
>>>
>>> On Mon, Apr 14, 2014 at 11:54 AM, Cuquerella Sanchez, Javier
>>> <javier.cuquerella at atos.net> wrote:
>>>>
>>>> Hi,
>>>>
>>>> But... I should do in my template to enable VNC OpenNebula autonomously?
>>>>
>>>>
>>>> Regards
>>>>
>>>>
>>>>
>>>> ---------------------------------------------------
>>>> Javier Cuquerella Sánchez
>>>>
>>>> Javier.cuquerella at atos.net
>>>> Atos Research & Innovation
>>>> Systems Administrator
>>>> Albarracin 25
>>>> 28037-Madrid (SPAIN)
>>>> Tfno: +34.91.214.8080
>>>> www.atosresearch.eu
>>>> es.atos.net
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: Javier Fontan [mailto:jfontan at opennebula.org]
>>>> Sent: Wednesday, April 09, 2014 3:17 PM
>>>> To: Cuquerella Sanchez, Javier
>>>> Cc: users at lists.opennebula.org
>>>> Subject: Re: Problem boot VM template with opennebula
>>>>
>>>> I think it is better to let OpenNebula choose the port as you can use
>>>> the same template to start several VMs and the VNC ports wont clash.
>>>>
>>>> On Wed, Apr 2, 2014 at 9:57 AM, Cuquerella Sanchez, Javier
>>>> <javier.cuquerella at atos.net> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> actually I specify the port manually. and there is no other service
>>>>> using port 5902. I should do in my template to enable VNC OpenNebula
>>>>> autonomously?
>>>>>
>>>>> Regards.
>>>>> Javier.
>>>>>
>>>>> ---------------------------------------------------
>>>>> Javier Cuquerella Sánchez
>>>>>
>>>>> Javier.cuquerella at atos.net
>>>>> Atos Research & Innovation
>>>>> Systems Administrator
>>>>> Albarracin 25
>>>>> 28037-Madrid (SPAIN)
>>>>> Tfno: +34.91.214.8080
>>>>> www.atosresearch.eu
>>>>> es.atos.net
>>>>>
>>>>>
>>>>> -----Original Message-----
>>>>> From: Javier Fontan [mailto:jfontan at opennebula.org]
>>>>> Sent: Tuesday, April 01, 2014 3:38 PM
>>>>> To: Cuquerella Sanchez, Javier
>>>>> Cc: users at lists.opennebula.org
>>>>> Subject: Re: Problem boot VM template with opennebula
>>>>>
>>>>> Are you specifying the port manually. It may be that there's another VM
>>>>> already using that port. Do not set it, let OpenNebula chose one for you.
>>>>>
>>>>> If this does not work try also unsetting the keymap. I can not think of
>>>>> any other problem with that.
>>>>>
>>>>> On Tue, Apr 1, 2014 at 11:43 AM, Cuquerella Sanchez, Javier
>>>>> <javier.cuquerella at atos.net> wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I have instantiated the machine, removing and setting parameters and
>>>>>> end the problem is on the line of the VNC:
>>>>>>
>>>>>> GRAPHICS=[ KEYMAP=es, LISTEN=0.0.0.0, PORT=5902,
>>>>>> TYPE=vnc ]
>>>>>>
>>>>>> If I remove the template the machine boots into Xen and opennebula
>>>>>> and I access the virtual machine using the command
>>>>>>
>>>>>> xm console IDMachine
>>>>>>
>>>>>> The template instantiate is:
>>>>>>
>>>>>> [root at VTSS003 CUQUE]# cat VMencourageprueba4.tmpl
>>>>>> NAME = Encourageprueba4
>>>>>> MEMORY = 4096
>>>>>> CPU = 1
>>>>>> OS=[ KERNEL = "/boot/vmlinuz-2.6.32-279.el6.x86_64", INITRD =
>>>>>> "/boot/initramfs-2.6.32-279.el6.x86_64.img", root = "xvda1" ] DISK
>>>>>> =[ DRIVER="file:", IMAGE_ID="29", TARGET="xvda1" ] DISK =[ TYPE =
>>>>>> "swap", SIZE = 1024, TARGET = "sdb" ] NIC = [ NETWORK_ID = 3 ]
>>>>>> RAW=[ DATA="device_model='/usr/lib64/xen/bin/qemu-dm'", TYPE=xen ]
>>>>>>
>>>>>> And the deployment created:
>>>>>>
>>>>>> [root at VTSS003 124]# cat deployment.0 name = 'one-124'
>>>>>> #O CPU_CREDITS = 256
>>>>>> memory = '4096'
>>>>>> kernel = '/boot/vmlinuz-2.6.32-279.el6.x86_64'
>>>>>> ramdisk = '/boot/initramfs-2.6.32-279.el6.x86_64.img'
>>>>>> root = '/dev/xvda1'
>>>>>> disk = [
>>>>>> 'file:/var/lib/one//datastores/0/124/disk.0,xvda1,w',
>>>>>> 'tap:aio:/var/lib/one//datastores/0/124/disk.1,sdb,w',
>>>>>> ]
>>>>>> vif = [
>>>>>> ' mac=02:00:5f:d3:e8:04,ip=95.211.232.4,bridge=br0',
>>>>>> ]
>>>>>> device_model='/usr/lib64/xen/bin/qemu-dm'
>>>>>>
>>>>>>
>>>>>> can you see any error on line to VNC: GRAPHICS=[ KEYMAP=es,
>>>>>> LISTEN=0.0.0.0, PORT=5902, TYPE=vnc ]
>>>>>>
>>>>>> regards.
>>>>>> Javier.
>>>>>>
>>>>>> ---------------------------------------------------
>>>>>> Javier Cuquerella Sánchez
>>>>>>
>>>>>> Javier.cuquerella at atos.net
>>>>>> Atos Research & Innovation
>>>>>> Systems Administrator
>>>>>> Albarracin 25
>>>>>> 28037-Madrid (SPAIN)
>>>>>> Tfno: +34.91.214.8080
>>>>>> www.atosresearch.eu
>>>>>> es.atos.net
>>>>>>
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Javier Fontan [mailto:jfontan at opennebula.org]
>>>>>> Sent: Wednesday, March 26, 2014 4:19 PM
>>>>>> To: Cuquerella Sanchez, Javier
>>>>>> Cc: users at lists.opennebula.org
>>>>>> Subject: Re: Problem boot VM template with opennebula
>>>>>>
>>>>>> Let's try taking out a couple of parameters. KERNEL_CMD, swap disk,
>>>>>> device_model and VNC. I'm using the template you provided in a previous
>>>>>> email:
>>>>>>
>>>>>> NAME = Encourage7
>>>>>> MEMORY = 4096
>>>>>> CPU = 1
>>>>>> OS=[ KERNEL = "/boot/vmlinuz-2.6.32-279.el6.x86_64", INITRD =
>>>>>> "/boot/initramfs-2.6.32-279.el6.x86_64.img", root = "xvda1" ] DISK =[
>>>>>> DRIVER="file:", IMAGE_ID="27", TARGET="xvda1" ] NIC = [ NETWORK_ID =
>>>>>> 3 ]
>>>>>>
>>>>>> In case this works you can start adding some other parameters. I'll
>>>>>> start with the swap disk.
>>>>>>
>>>>>> On Wed, Mar 26, 2014 at 3:55 PM, Cuquerella Sanchez, Javier
>>>>>> <javier.cuquerella at atos.net> wrote:
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> The deployment file generated by OpenNebula is:
>>>>>>>
>>>>>>> [root at VTSS003 114]# cat deployment.0 name = 'one-114'
>>>>>>> #O CPU_CREDITS = 256
>>>>>>> memory = '4096'
>>>>>>> kernel = '/boot/vmlinuz-2.6.32-279.el6.x86_64'
>>>>>>> ramdisk = '/boot/initramfs-2.6.32-279.el6.x86_64.img'
>>>>>>> root = '/dev/xvda1'
>>>>>>> extra = 'ro xencons=tty console=tty1'
>>>>>>> disk = [
>>>>>>> 'file:/var/lib/one//datastores/0/114/disk.0,xvda1,w',
>>>>>>> 'tap:aio:/var/lib/one//datastores/0/114/disk.1,sdb,w',
>>>>>>> ]
>>>>>>> vif = [
>>>>>>> ' mac=02:00:5f:d3:e8:04,ip=95.211.232.4,bridge=br0',
>>>>>>> ]
>>>>>>> vfb = ['type=vnc,vnclisten=0.0.0.0,vncdisplay=2,keymap=es']
>>>>>>> device_model='/usr/lib64/xen/bin/qemu-dm'
>>>>>>>
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> Regards
>>>>>>>
>>>>>>> ---------------------------------------------------
>>>>>>> Javier Cuquerella Sánchez
>>>>>>>
>>>>>>> Javier.cuquerella at atos.net
>>>>>>> Atos Research & Innovation
>>>>>>> Systems Administrator
>>>>>>> Albarracin 25
>>>>>>> 28037-Madrid (SPAIN)
>>>>>>> Tfno: +34.91.214.8080
>>>>>>> www.atosresearch.eu
>>>>>>> es.atos.net
>>>>>>>
>>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Javier Fontan [mailto:jfontan at opennebula.org]
>>>>>>> Sent: Monday, March 24, 2014 6:43 PM
>>>>>>> To: Cuquerella Sanchez, Javier
>>>>>>> Cc: users at lists.opennebula.org
>>>>>>> Subject: Re: Problem boot VM template with opennebula
>>>>>>>
>>>>>>> Can you send us the deployment file generated by OpenNebula? Just to
>>>>>>> check if there is something too different to your deployment file. It
>>>>>>> should be located in you frontend at
>>>>>>> /var/lib/one/vms/<vmid>/deployment.0
>>>>>>>
>>>>>>> On Mon, Mar 24, 2014 at 10:29 AM, Cuquerella Sanchez, Javier
>>>>>>> <javier.cuquerella at atos.net> wrote:
>>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> have been able to look at something ?
>>>>>>>>
>>>>>>>> I do not understand because if I start the same image with xen ONLY
>>>>>>>> works:
>>>>>>>>
>>>>>>>> xm create encourage.cfg
>>>>>>>>
>>>>>>>> name = " encourage"
>>>>>>>>
>>>>>>>> memory = 4096
>>>>>>>> maxmem = 4096
>>>>>>>> vcpus = 1
>>>>>>>>
>>>>>>>> # bootloader = "/ usr / bin / pygrub "
>>>>>>>> # bootloader = "/ usr/lib64/xen/bin/pygrub "
>>>>>>>> on_poweroff = "destroy"
>>>>>>>> on_reboot = " restart"
>>>>>>>> on_crash = " restart"
>>>>>>>>
>>>>>>>> disk =
>>>>>>>> ['file:/home/jcuque/encourage/encourage2.img,xvda1,w','file:/home/jcuque/encourage/encourage2.swap,xvda2,w']
>>>>>>>> vif = [' bridge = br0 ']
>>>>>>>> kernel = " / boot/vmlinuz-2.6.32-279.el6.x86_64 "
>>>>>>>> ramdisk = "/ boot/initramfs-2.6.32-279.el6.x86_64.img "
>>>>>>>> root = " / dev/xvda1 ro"
>>>>>>>>
>>>>>>>> [root @ VTSS003 ~ ] # xm list | grep Encourage Encourage 135 4096
>>>>>>>> 1-b
>>>>>>>> ---- 20.8
>>>>>>>>
>>>>>>>> the machine is started well but also can login via console:
>>>>>>>>
>>>>>>>> [root @ VTSS003 ~ ] # xm console 135
>>>>>>>>
>>>>>>>> CentOS release 6.4 ( Final)
>>>>>>>> Kernel 2.6.32 - 279.el6.x86_64 on an x86_64
>>>>>>>>
>>>>>>>> encourage.es.atos.net login :
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ---------------------------------------------------
>>>>>>>> Javier Cuquerella Sánchez
>>>>>>>>
>>>>>>>> Javier.cuquerella at atos.net
>>>>>>>> Atos Research & Innovation
>>>>>>>> Systems Administrator
>>>>>>>> Albarracin 25
>>>>>>>> 28037-Madrid (SPAIN)
>>>>>>>> Tfno: +34.91.214.8080
>>>>>>>> www.atosresearch.eu
>>>>>>>> es.atos.net
>>>>>>>>
>>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: Cuquerella Sanchez, Javier
>>>>>>>> Sent: Friday, March 21, 2014 9:30 AM
>>>>>>>> To: 'Javier Fontan'
>>>>>>>> Cc: 'users at lists.opennebula.org'
>>>>>>>> Subject: RE: Problem boot VM template with opennebula
>>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I don't output anything. by putting the command stays there
>>>>>>>>
>>>>>>>> [root at VTSS003 ~]# xm list
>>>>>>>> Name ID Mem VCPUs
>>>>>>>> State Time(s)
>>>>>>>> Domain-0 0 1024 1
>>>>>>>> r----- 19487.0
>>>>>>>> ciudad20201 67 2048 1
>>>>>>>> -b---- 2512.8
>>>>>>>> ciudad20202 68 2048 1
>>>>>>>> -b---- 559.8
>>>>>>>> ciudad20203 69 2048 1
>>>>>>>> -b---- 8516.7
>>>>>>>> one-106 133 4096 1
>>>>>>>> -b---- 489.9
>>>>>>>> [root at VTSS003 ~]# xm console 133
>>>>>>>>
>>>>>>>> maybe it's useful to bring to the template: KERNEL_CMD = "ro
>>>>>>>> xencons=tty console=tty1"] , no?
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Thanks.
>>>>>>>>
>>>>>>>> Regards
>>>>>>>>
>>>>>>>>
>>>>>>>> ---------------------------------------------------
>>>>>>>> Javier Cuquerella Sánchez
>>>>>>>>
>>>>>>>> Javier.cuquerella at atos.net
>>>>>>>> Atos Research & Innovation
>>>>>>>> Systems Administrator
>>>>>>>> Albarracin 25
>>>>>>>> 28037-Madrid (SPAIN)
>>>>>>>> Tfno: +34.91.214.8080
>>>>>>>> www.atosresearch.eu
>>>>>>>> es.atos.net
>>>>>>>>
>>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: Javier Fontan [mailto:jfontan at opennebula.org]
>>>>>>>> Sent: Thursday, March 20, 2014 6:56 PM
>>>>>>>> To: Cuquerella Sanchez, Javier
>>>>>>>> Cc: users at lists.opennebula.org
>>>>>>>> Subject: Re: Problem boot VM template with opennebula
>>>>>>>>
>>>>>>>> Are you getting an error with xm console or it just doesn't output
>>>>>>>> anything?
>>>>>>>>
>>>>>>>> On Thu, Mar 20, 2014 at 5:50 PM, Cuquerella Sanchez, Javier
>>>>>>>> <javier.cuquerella at atos.net> wrote:
>>>>>>>>>
>>>>>>>>> HI,
>>>>>>>>>
>>>>>>>>> The virtual machine runs on both xen and opennebula:
>>>>>>>>>
>>>>>>>>> [root at VTSS003 106]# xm list | grep one
>>>>>>>>> one-106 133 4096 1
>>>>>>>>> -b---- 11.3
>>>>>>>>>
>>>>>>>>> [oneadmin at VTSS003 CUQUE]$ onevm list
>>>>>>>>> ID USER GROUP NAME STAT UCPU UMEM HOST
>>>>>>>>> TIME
>>>>>>>>> 106 oneadmin oneadmin one-106 runn 0 4G
>>>>>>>>> ARICLOUD1 0d 01h10
>>>>>>>>>
>>>>>>>>> Template virtual machine:
>>>>>>>>>
>>>>>>>>> [oneadmin at VTSS003 CUQUE]$ cat VMencourage7.tmpl
>>>>>>>>> NAME = Encourage7
>>>>>>>>> MEMORY = 4096
>>>>>>>>> CPU = 1
>>>>>>>>> OS=[ KERNEL = "/boot/vmlinuz-2.6.32-279.el6.x86_64", INITRD =
>>>>>>>>> "/boot/initramfs-2.6.32-279.el6.x86_64.img", KERNEL_CMD = "ro" ,
>>>>>>>>> root = "xvda1" ] DISK =[ DRIVER="file:", IMAGE_ID="27",
>>>>>>>>> TARGET="xvda1" ] DISK =[ TYPE = "swap", SIZE = 1024, TARGET =
>>>>>>>>> "sdb"
>>>>>>>>> ] NIC = [ NETWORK_ID = 3 ] GRAPHICS=[ KEYMAP=es, LISTEN=0.0.0.0,
>>>>>>>>> PORT=5902, TYPE=vnc ] RAW=[
>>>>>>>>> DATA="device_model='/usr/lib64/xen/bin/qemu-dm'",
>>>>>>>>> TYPE=xen ]
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Xen log is correct:
>>>>>>>>>
>>>>>>>>> [root at VTSS003 CUQUE]# tail -f /var/log/xen/xend.log
>>>>>>>>> [2014-03-20 16:15:56 4335] DEBUG (DevController:139) Waiting for
>>>>>>>>> devices vbd.
>>>>>>>>> [2014-03-20 16:15:56 4335] DEBUG (DevController:144) Waiting for
>>>>>>>>> 51713.
>>>>>>>>> [2014-03-20 16:15:56 4335] DEBUG (DevController:628)
>>>>>>>>> hotplugStatusCallback /local/domain/0/backend/vbd/133/51713/hotplug-status.
>>>>>>>>> [2014-03-20 16:15:56 4335] DEBUG (DevController:642)
>>>>>>>>> hotplugStatusCallback 1.
>>>>>>>>> [2014-03-20 16:15:56 4335] DEBUG (DevController:139) Waiting for
>>>>>>>>> devices irq.
>>>>>>>>> [2014-03-20 16:15:56 4335] DEBUG (DevController:139) Waiting for
>>>>>>>>> devices vfb.
>>>>>>>>> [2014-03-20 16:15:56 4335] DEBUG (DevController:139) Waiting for
>>>>>>>>> devices pci.
>>>>>>>>> [2014-03-20 16:15:56 4335] DEBUG (DevController:139) Waiting for
>>>>>>>>> devices vusb.
>>>>>>>>> [2014-03-20 16:15:56 4335] DEBUG (DevController:139) Waiting for
>>>>>>>>> devices vtpm.
>>>>>>>>> [2014-03-20 16:15:56 4335] INFO (XendDomain:1225) Domain one-106
>>>>>>>>> (133) unpaused.
>>>>>>>>>
>>>>>>>>> but I can not connect to the machine or by using VNC or xen using
>>>>>>>>> the
>>>>>>>>> command: xm console IDmachine
>>>>>>>>>
>>>>>>>>> Opennebula log :
>>>>>>>>>
>>>>>>>>> [root at VTSS003 CUQUE]# tail -f /var/log/one/106.log Thu Mar 20
>>>>>>>>> 16:15:52
>>>>>>>>> 2014 [LCM][I]: New VM state is BOOT Thu Mar 20 16:15:52 2014
>>>>>>>>> [VMM][I]:
>>>>>>>>> Generating deployment file: /var/lib/one/106/deployment.0 Thu Mar
>>>>>>>>> 20
>>>>>>>>> 16:15:53 2014 [VMM][I]: ExitCode: 0 Thu Mar 20 16:15:53 2014
>>>>>>>>> [VMM][I]:
>>>>>>>>> Successfully execute network driver operation: pre.
>>>>>>>>> Thu Mar 20 16:15:56 2014 [VMM][D]: deploy: Credits set to 256 Thu
>>>>>>>>> Mar
>>>>>>>>> 20 16:15:56 2014 [VMM][I]: ExitCode: 0 Thu Mar 20 16:15:56 2014
>>>>>>>>> [VMM][I]: Successfully execute virtualization driver operation:
>>>>>>>>> deploy.
>>>>>>>>> Thu Mar 20 16:15:56 2014 [VMM][I]: ExitCode: 0 Thu Mar 20 16:15:56
>>>>>>>>> 2014 [VMM][I]: Successfully execute network driver operation: post.
>>>>>>>>> Thu Mar 20 16:15:56 2014 [LCM][I]: New VM state is RUNNING Thu Mar
>>>>>>>>> 20
>>>>>>>>> 16:26:01 2014 [VMM][I]: Found interface tap-52-2064 but domain 52
>>>>>>>>> does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-53-2064 but
>>>>>>>>> domain 53 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-54-2064 but
>>>>>>>>> domain 54 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-55-2064 but
>>>>>>>>> domain 55 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-56-2064 but
>>>>>>>>> domain 56 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-57-2064 but
>>>>>>>>> domain 57 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-58-2064 but
>>>>>>>>> domain 58 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-59-2064 but
>>>>>>>>> domain 59 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-60-2064 but
>>>>>>>>> domain 60 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-61-2064 but
>>>>>>>>> domain 61 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-62-2064 but
>>>>>>>>> domain 62 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-63-2064 but
>>>>>>>>> domain 63 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-64-2064 but
>>>>>>>>> domain 64 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-65-2064 but
>>>>>>>>> domain 65 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-66-2064 but
>>>>>>>>> domain 66 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-70-2064 but
>>>>>>>>> domain 70 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-71-2064 but
>>>>>>>>> domain 71 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-72-2064 but
>>>>>>>>> domain 72 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-73-2064 but
>>>>>>>>> domain 73 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-74-2064 but
>>>>>>>>> domain 74 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-75-2064 but
>>>>>>>>> domain 75 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-76-2064 but
>>>>>>>>> domain 76 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-77-2064 but
>>>>>>>>> domain 77 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-78-2064 but
>>>>>>>>> domain 78 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-79-2064 but
>>>>>>>>> domain 79 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-100-2064 but
>>>>>>>>> domain 100 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-80-2064 but
>>>>>>>>> domain 80 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-101-2064 but
>>>>>>>>> domain 101 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-81-2064 but
>>>>>>>>> domain 81 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-102-2064 but
>>>>>>>>> domain 102 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-82-2064 but
>>>>>>>>> domain 82 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-103-2064 but
>>>>>>>>> domain 103 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-83-2064 but
>>>>>>>>> domain 83 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-104-2064 but
>>>>>>>>> domain 104 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-105-2064 but
>>>>>>>>> domain 105 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-106-2064 but
>>>>>>>>> domain 106 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-18-2064 but
>>>>>>>>> domain 18 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-107-2064 but
>>>>>>>>> domain 107 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-87-2064 but
>>>>>>>>> domain 87 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-19-2064 but
>>>>>>>>> domain 19 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-108-2064 but
>>>>>>>>> domain 108 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-88-2064 but
>>>>>>>>> domain 88 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-109-2064 but
>>>>>>>>> domain 109 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-89-2064 but
>>>>>>>>> domain 89 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-20-2064 but
>>>>>>>>> domain 20 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-21-2064 but
>>>>>>>>> domain 21 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-110-2064 but
>>>>>>>>> domain 110 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-90-2064 but
>>>>>>>>> domain 90 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-22-2064 but
>>>>>>>>> domain 22 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-111-2064 but
>>>>>>>>> domain 111 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-91-2064 but
>>>>>>>>> domain 91 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-23-2064 but
>>>>>>>>> domain 23 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-112-2064 but
>>>>>>>>> domain 112 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-92-2064 but
>>>>>>>>> domain 92 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-24-2064 but
>>>>>>>>> domain 24 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-113-2064 but
>>>>>>>>> domain 113 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-93-2064 but
>>>>>>>>> domain 93 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-25-2064 but
>>>>>>>>> domain 25 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-114-2064 but
>>>>>>>>> domain 114 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-94-2064 but
>>>>>>>>> domain 94 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-26-2064 but
>>>>>>>>> domain 26 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-115-2064 but
>>>>>>>>> domain 115 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-95-2064 but
>>>>>>>>> domain 95 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-27-2064 but
>>>>>>>>> domain 27 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-116-2064 but
>>>>>>>>> domain 116 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-96-2064 but
>>>>>>>>> domain 96 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-28-2064 but
>>>>>>>>> domain 28 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-117-2064 but
>>>>>>>>> domain 117 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-97-2064 but
>>>>>>>>> domain 97 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-29-2064 but
>>>>>>>>> domain 29 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-118-2064 but
>>>>>>>>> domain 118 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-98-2064 but
>>>>>>>>> domain 98 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-119-2064 but
>>>>>>>>> domain 119 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-99-2064 but
>>>>>>>>> domain 99 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-30-2064 but
>>>>>>>>> domain 30 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-31-2064 but
>>>>>>>>> domain 31 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-120-2064 but
>>>>>>>>> domain 120 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-32-2064 but
>>>>>>>>> domain 32 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-121-2064 but
>>>>>>>>> domain 121 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-33-2064 but
>>>>>>>>> domain 33 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-122-2064 but
>>>>>>>>> domain 122 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-34-2064 but
>>>>>>>>> domain 34 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-123-2064 but
>>>>>>>>> domain 123 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-35-2064 but
>>>>>>>>> domain 35 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-124-2064 but
>>>>>>>>> domain 124 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-36-2064 but
>>>>>>>>> domain 36 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-125-2064 but
>>>>>>>>> domain 125 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-37-2064 but
>>>>>>>>> domain 37 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-126-2064 but
>>>>>>>>> domain 126 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-38-2064 but
>>>>>>>>> domain 38 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-39-2064 but
>>>>>>>>> domain 39 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-40-2064 but
>>>>>>>>> domain 40 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-41-2064 but
>>>>>>>>> domain 41 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-42-2064 but
>>>>>>>>> domain 42 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-131-2064 but
>>>>>>>>> domain 131 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-43-2064 but
>>>>>>>>> domain 43 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-132-2064 but
>>>>>>>>> domain 132 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-44-2064 but
>>>>>>>>> domain 44 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-45-2064 but
>>>>>>>>> domain 45 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-46-2064 but
>>>>>>>>> domain 46 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-47-2064 but
>>>>>>>>> domain 47 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-48-2064 but
>>>>>>>>> domain 48 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-49-2064 but
>>>>>>>>> domain 49 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-50-2064 but
>>>>>>>>> domain 50 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-51-2064 but
>>>>>>>>> domain 51 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-52-2064 but
>>>>>>>>> domain 52 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-53-2064 but
>>>>>>>>> domain 53 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-54-2064 but
>>>>>>>>> domain 54 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-55-2064 but
>>>>>>>>> domain 55 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-56-2064 but
>>>>>>>>> domain 56 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-57-2064 but
>>>>>>>>> domain 57 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-58-2064 but
>>>>>>>>> domain 58 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-59-2064 but
>>>>>>>>> domain 59 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-60-2064 but
>>>>>>>>> domain 60 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-61-2064 but
>>>>>>>>> domain 61 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-62-2064 but
>>>>>>>>> domain 62 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-63-2064 but
>>>>>>>>> domain 63 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-64-2064 but
>>>>>>>>> domain 64 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-65-2064 but
>>>>>>>>> domain 65 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-66-2064 but
>>>>>>>>> domain 66 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-70-2064 but
>>>>>>>>> domain 70 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-71-2064 but
>>>>>>>>> domain 71 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-72-2064 but
>>>>>>>>> domain 72 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-73-2064 but
>>>>>>>>> domain 73 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-74-2064 but
>>>>>>>>> domain 74 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-75-2064 but
>>>>>>>>> domain 75 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-76-2064 but
>>>>>>>>> domain 76 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-77-2064 but
>>>>>>>>> domain 77 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-78-2064 but
>>>>>>>>> domain 78 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-79-2064 but
>>>>>>>>> domain 79 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-100-2064 but
>>>>>>>>> domain 100 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-80-2064 but
>>>>>>>>> domain 80 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-101-2064 but
>>>>>>>>> domain 101 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-81-2064 but
>>>>>>>>> domain 81 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-102-2064 but
>>>>>>>>> domain 102 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-82-2064 but
>>>>>>>>> domain 82 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-103-2064 but
>>>>>>>>> domain 103 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-83-2064 but
>>>>>>>>> domain 83 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-104-2064 but
>>>>>>>>> domain 104 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-105-2064 but
>>>>>>>>> domain 105 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-106-2064 but
>>>>>>>>> domain 106 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-18-2064 but
>>>>>>>>> domain 18 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-107-2064 but
>>>>>>>>> domain 107 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-87-2064 but
>>>>>>>>> domain 87 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-19-2064 but
>>>>>>>>> domain 19 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-108-2064 but
>>>>>>>>> domain 108 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-88-2064 but
>>>>>>>>> domain 88 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-109-2064 but
>>>>>>>>> domain 109 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-89-2064 but
>>>>>>>>> domain 89 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-20-2064 but
>>>>>>>>> domain 20 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-21-2064 but
>>>>>>>>> domain 21 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-110-2064 but
>>>>>>>>> domain 110 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-90-2064 but
>>>>>>>>> domain 90 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-22-2064 but
>>>>>>>>> domain 22 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-111-2064 but
>>>>>>>>> domain 111 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-91-2064 but
>>>>>>>>> domain 91 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-23-2064 but
>>>>>>>>> domain 23 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-112-2064 but
>>>>>>>>> domain 112 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-92-2064 but
>>>>>>>>> domain 92 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-24-2064 but
>>>>>>>>> domain 24 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-113-2064 but
>>>>>>>>> domain 113 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-93-2064 but
>>>>>>>>> domain 93 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-25-2064 but
>>>>>>>>> domain 25 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-114-2064 but
>>>>>>>>> domain 114 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-94-2064 but
>>>>>>>>> domain 94 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-26-2064 but
>>>>>>>>> domain 26 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-115-2064 but
>>>>>>>>> domain 115 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-95-2064 but
>>>>>>>>> domain 95 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-27-2064 but
>>>>>>>>> domain 27 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-116-2064 but
>>>>>>>>> domain 116 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-96-2064 but
>>>>>>>>> domain 96 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-28-2064 but
>>>>>>>>> domain 28 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-117-2064 but
>>>>>>>>> domain 117 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-97-2064 but
>>>>>>>>> domain 97 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-29-2064 but
>>>>>>>>> domain 29 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-118-2064 but
>>>>>>>>> domain 118 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-98-2064 but
>>>>>>>>> domain 98 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-119-2064 but
>>>>>>>>> domain 119 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-99-2064 but
>>>>>>>>> domain 99 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-30-2064 but
>>>>>>>>> domain 30 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-31-2064 but
>>>>>>>>> domain 31 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-120-2064 but
>>>>>>>>> domain 120 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-32-2064 but
>>>>>>>>> domain 32 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-121-2064 but
>>>>>>>>> domain 121 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-33-2064 but
>>>>>>>>> domain 33 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-122-2064 but
>>>>>>>>> domain 122 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-34-2064 but
>>>>>>>>> domain 34 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-123-2064 but
>>>>>>>>> domain 123 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-35-2064 but
>>>>>>>>> domain 35 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-124-2064 but
>>>>>>>>> domain 124 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-36-2064 but
>>>>>>>>> domain 36 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-125-2064 but
>>>>>>>>> domain 125 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-37-2064 but
>>>>>>>>> domain 37 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-126-2064 but
>>>>>>>>> domain 126 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-38-2064 but
>>>>>>>>> domain 38 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-39-2064 but
>>>>>>>>> domain 39 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-40-2064 but
>>>>>>>>> domain 40 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-41-2064 but
>>>>>>>>> domain 41 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-42-2064 but
>>>>>>>>> domain 42 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-131-2064 but
>>>>>>>>> domain 131 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-43-2064 but
>>>>>>>>> domain 43 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-132-2064 but
>>>>>>>>> domain 132 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-44-2064 but
>>>>>>>>> domain 44 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-45-2064 but
>>>>>>>>> domain 45 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-46-2064 but
>>>>>>>>> domain 46 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-47-2064 but
>>>>>>>>> domain 47 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-48-2064 but
>>>>>>>>> domain 48 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-49-2064 but
>>>>>>>>> domain 49 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-50-2064 but
>>>>>>>>> domain 50 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: Found interface tap-51-2064 but
>>>>>>>>> domain 51 does not exist.
>>>>>>>>> Thu Mar 20 16:26:01 2014 [VMM][I]: ExitCode: 0 Thu Mar 20 16:26:01
>>>>>>>>> 2014 [VMM][W]: Adding custom monitoring attribute: NAME one-106 Thu
>>>>>>>>> Mar 20 16:26:01 2014 [VMM][D]: Monitor Information:
>>>>>>>>> CPU : 0
>>>>>>>>> Memory: 4194304
>>>>>>>>> Net_TX: 3072
>>>>>>>>> Net_RX: 0
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Thanks.
>>>>>>>>>
>>>>>>>>> Regards
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ---------------------------------------------------
>>>>>>>>> Javier Cuquerella Sánchez
>>>>>>>>>
>>>>>>>>> Javier.cuquerella at atos.net
>>>>>>>>> Atos Research & Innovation
>>>>>>>>> Systems Administrator
>>>>>>>>> Albarracin 25
>>>>>>>>> 28037-Madrid (SPAIN)
>>>>>>>>> Tfno: +34.91.214.8080
>>>>>>>>> www.atosresearch.eu
>>>>>>>>> es.atos.net
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> -----Original Message-----
>>>>>>>>> From: Javier Fontan [mailto:jfontan at opennebula.org]
>>>>>>>>> Sent: Thursday, March 20, 2014 11:45 AM
>>>>>>>>> To: Cuquerella Sanchez, Javier
>>>>>>>>> Cc: users at lists.opennebula.org
>>>>>>>>> Subject: Re: Problem boot VM template with opennebula
>>>>>>>>>
>>>>>>>>> The problem is the root parameter:
>>>>>>>>>
>>>>>>>>> --8<------
>>>>>>>>> dracut Warning: No root device "block:/dev//dev/xvda1" found
>>>>>>>>> ------>8--
>>>>>>>>>
>>>>>>>>> In OpenNebula template you should drop de "/dev/" prefix and "ro"
>>>>>>>>> parameter:
>>>>>>>>>
>>>>>>>>> --8<------
>>>>>>>>> OS=[ KERNEL = "/boot/vmlinuz-2.6.32-279.el6.x86_64", INITRD =
>>>>>>>>> "/boot/initramfs-2.6.32-279.el6.x86_64.img", root = "xvda1" ]
>>>>>>>>> ------>8--
>>>>>>>>>
>>>>>>>>> In case you want to add the "ro" parameter or any other one you
>>>>>>>>> should use KERNEL_CMD parameter [1].
>>>>>>>>>
>>>>>>>>> Cheers
>>>>>>>>>
>>>>>>>>> [1]
>>>>>>>>> http://docs.opennebula.org/4.4/user/references/template.html#os-and
>>>>>>>>> -
>>>>>>>>> b
>>>>>>>>> o
>>>>>>>>> ot-options-section
>>>>>>>>>
>>>>>>>>> On Wed, Mar 19, 2014 at 5:40 PM, Cuquerella Sanchez, Javier
>>>>>>>>> <javier.cuquerella at atos.net> wrote:
>>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> I have a problem when starting a virtual machine. me the error
>>>>>>>>>> that appears is:
>>>>>>>>>>
>>>>>>>>>> Freeing unused kernel memory: 1260k freed Write protecting the
>>>>>>>>>> kernel read-only data: 10240k Freeing unused kernel memory: 972k
>>>>>>>>>> freed Freeing unused kernel memory: 1732k freed
>>>>>>>>>> dracut: dracut-004-283.el6
>>>>>>>>>> device-mapper: uevent: version 1.0.3
>>>>>>>>>> device-mapper: ioctl: 4.22.6-ioctl (2011-10-19) initialised:
>>>>>>>>>> dm-devel at redhat.com
>>>>>>>>>> udev: starting version 147
>>>>>>>>>> dracut: Starting plymouth daemon
>>>>>>>>>> xlblk_init: register_blkdev major: 202
>>>>>>>>>> blkfront: xvda1: barriers disabled
>>>>>>>>>> XENBUS: Waiting for devices to initialise:
>>>>>>>>>> 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...
>>>>>>>>>> dracut Warning: No root device "block:/dev//dev/xvda1" found
>>>>>>>>>> dracut
>>>>>>>>>> Warning: Boot has failed. To debug this issue add "rdshell" to the
>>>>>>>>>> kernel command line.
>>>>>>>>>> dracut Warning: Signal caught!
>>>>>>>>>> dracut Warning: Boot has failed. To debug this issue add "rdshell"
>>>>>>>>>> to the kernel command line.
>>>>>>>>>> Kernel panic - not syncing: Attempted to kill init!
>>>>>>>>>> Pid: 1, comm: init Not tainted 2.6.32-279.el6.x86_64 #1 Call
>>>>>>>>>> Trace:
>>>>>>>>>> [<ffffffff814fd11a>] ? panic+0xa0/0x168 [<ffffffff81070bd2>] ?
>>>>>>>>>> do_exit+0x862/0x870 [<ffffffff8117ca75>] ? fput+0x25/0x30
>>>>>>>>>> [<ffffffff81070c38>] ? do_group_exit+0x58/0xd0
>>>>>>>>>> [<ffffffff81070cc7>] ?
>>>>>>>>>> sys_exit_group+0x17/0x20 [<ffffffff8100b0f2>] ?
>>>>>>>>>> system_call_fastpath+0x16/0x1b
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> The template is:
>>>>>>>>>>
>>>>>>>>>> NAME = Encourage5
>>>>>>>>>> MEMORY = 4096
>>>>>>>>>> CPU = 1
>>>>>>>>>> OS=[ KERNEL = "/boot/vmlinuz-2.6.32-279.el6.x86_64", INITRD =
>>>>>>>>>> "/boot/initramfs-2.6.32-279.el6.x86_64.img", root = "/dev/xvda1
>>>>>>>>>> ro"
>>>>>>>>>> ] DISK =[ DRIVER="file:", IMAGE_ID="27", TARGET="xvda1" ] DISK =[
>>>>>>>>>> TYPE = "swap", SIZE = 1024, TARGET = "sdb" ] NIC = [ NETWORK_ID =
>>>>>>>>>> 3 ] GRAPHICS=[ KEYMAP=es, LISTEN=0.0.0.0, PORT=5901, TYPE=vnc ]
>>>>>>>>>> RAW=[ DATA="device_model='/usr/lib64/xen/bin/qemu-dm'", TYPE=xen ]
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> used as a virtual disk image. img, created with dd. If I lift the
>>>>>>>>>> image with xen: xm create encourage.cfg machine working properly. the
>>>>>>>>>> configuration file for xen is:
>>>>>>>>>>
>>>>>>>>>> cat ../encourage/encourage.cfg
>>>>>>>>>> name = "encourage"
>>>>>>>>>>
>>>>>>>>>> memory = 4096
>>>>>>>>>> maxmem = 4096
>>>>>>>>>> vcpus = 1
>>>>>>>>>>
>>>>>>>>>> #bootloader = "/usr/bin/pygrub"
>>>>>>>>>> #bootloader = "/usr/lib64/xen/bin/pygrub"
>>>>>>>>>> on_poweroff = "destroy"
>>>>>>>>>> on_reboot = "restart"
>>>>>>>>>> on_crash = "restart"
>>>>>>>>>>
>>>>>>>>>> disk =
>>>>>>>>>> ['file:/home/jcuque/encourage/encourage2.img,xvda1,w','file:/home/
>>>>>>>>>> j c u q ue/encourage/encourage2.swap,xvda2,w']
>>>>>>>>>> vif = ['bridge=br0']
>>>>>>>>>> kernel = "/boot/vmlinuz-2.6.32-279.el6.x86_64"
>>>>>>>>>> ramdisk = "/boot/initramfs-2.6.32-279.el6.x86_64.img"
>>>>>>>>>> root = "/dev/xvda1 ro"
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Can you help me? Tell me if you need more date
>>>>>>>>>>
>>>>>>>>>> Thanks
>>>>>>>>>> regards
>>>>>>>>>>
>>>>>>>>>> ---------------------------------------------------
>>>>>>>>>> Javier Cuquerella Sánchez
>>>>>>>>>>
>>>>>>>>>> Javier.cuquerella at atos.net
>>>>>>>>>> Atos Research & Innovation
>>>>>>>>>> Systems Administrator
>>>>>>>>>> Albarracin 25
>>>>>>>>>> 28037-Madrid (SPAIN)
>>>>>>>>>> Tfno: +34.91.214.8080
>>>>>>>>>> www.atosresearch.eu
>>>>>>>>>> es.atos.net
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Javier Fontán Muiños
>>>>>>>>> Developer
>>>>>>>>> OpenNebula - The Open Source Toolkit for Data Center Virtualization
>>>>>>>>> www.OpenNebula.org | @OpenNebula | github.com/jfontan
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Javier Fontán Muiños
>>>>>>>> Developer
>>>>>>>> OpenNebula - The Open Source Toolkit for Data Center Virtualization
>>>>>>>> www.OpenNebula.org | @OpenNebula | github.com/jfontan
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Javier Fontán Muiños
>>>>>>> Developer
>>>>>>> OpenNebula - The Open Source Toolkit for Data Center Virtualization
>>>>>>> www.OpenNebula.org | @OpenNebula | github.com/jfontan
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Javier Fontán Muiños
>>>>>> Developer
>>>>>> OpenNebula - The Open Source Toolkit for Data Center Virtualization
>>>>>> www.OpenNebula.org | @OpenNebula | github.com/jfontan
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Javier Fontán Muiños
>>>>> Developer
>>>>> OpenNebula - The Open Source Toolkit for Data Center Virtualization
>>>>> www.OpenNebula.org | @OpenNebula | github.com/jfontan
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Javier Fontán Muiños
>>>> Developer
>>>> OpenNebula - The Open Source Toolkit for Data Center Virtualization
>>>> www.OpenNebula.org | @OpenNebula | github.com/jfontan
>>>
>>>
>>>
>>>
>>> --
>>> Javier Fontán Muiños
>>> Developer
>>> OpenNebula - The Open Source Toolkit for Data Center Virtualization
>>> www.OpenNebula.org | @OpenNebula | github.com/jfontan
>>
>>
>>
>>
>> --
>> Javier Fontán Muiños
>> Developer
>> OpenNebula - The Open Source Toolkit for Data Center Virtualization
>> www.OpenNebula.org | @OpenNebula | github.com/jfontan
>> _______________________________________________
>> Users mailing list
>> Users at lists.opennebula.org
>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>
>
> ------------------------------------------------------------------
> Steven C. Timm, Ph.D (630) 840-8525
> timm at fnal.gov http://home.fnal.gov/~timm/
> Fermilab Scientific Computing Division, Scientific Computing Services Quad.
> Grid and Cloud Services Dept., Associate Dept. Head for Cloud Computing
--
Javier Fontán Muiños
Developer
OpenNebula - The Open Source Toolkit for Data Center Virtualization
www.OpenNebula.org | @OpenNebula | github.com/jfontan
More information about the Users
mailing list