Hello, i try to force the driver in the image but i got this error in var/log/one/XXXX.log
Sun Mar 30 23:59:04 2014 [DiM][I]: New VM state is ACTIVE.
Sun Mar 30 23:59:04 2014 [LCM][I]: New VM state is PROLOG.
Sun Mar 30 23:59:04 2014 [VM][I]: Virtual Machine has no context
Sun Mar 30 23:59:13 2014 [LCM][I]: New VM state is CLEANUP.
Sun Mar 30 23:59:14 2014 [DiM][I]: New VM state is DONE
Sun Mar 30 23:59:14 2014 [TM][W]: Ignored: LOG I 1687 Driver command for 1687 cancelled
Sun Mar 30 23:59:04 2014 [LCM][I]: New VM state is PROLOG.
Sun Mar 30 23:59:04 2014 [VM][I]: Virtual Machine has no context
Sun Mar 30 23:59:13 2014 [LCM][I]: New VM state is CLEANUP.
Sun Mar 30 23:59:14 2014 [DiM][I]: New VM state is DONE
Sun Mar 30 23:59:14 2014 [TM][W]: Ignored: LOG I 1687 Driver command for 1687 cancelled
Sun Mar 30 23:59:42 2014 [TM][W]: Ignored: TRANSFER SUCCESS 1687 -
And vm didnt start .
do you know what is this ?
thanks.
De: jfon...@opennebula.org
Enviada: Sexta-feira, 28 de Março de 2014 16:11
Para: kenny.ke...@bol.com.br
Assunto: [one-users] blktap xen 4.2 and opennebula 4.2
On Fri, Mar 28, 2014 at 3:37 PM, <kenny.ke...@bol.com.br> wrote:
> Thanks for the reply, i forgot to say im using NFS.
> Its a problem ?
It should not be a problem.
> I will check the files in the remote host.
> It´s in the same folder ?
No, in the nodes they reside in /var/tmp/one.
> I will see if the image has a driver.
> I can chage the image driver or i need to create a new one ?
You can use "oneimage update" command or the Sunstone web interface
>
>
> ________________________________
>
> De: jfon...@opennebula.org
> Enviada: Sexta-feira, 28 de Março de 2014 12:36
>
> Para: kenny.ke...@bol.com.br
> Assunto: [one-users] blktap xen 4.2 and opennebula 4.2
>
> Is it possible that you have a driver defined in the image you are
> attaching? An explicit driver takes precedence over the default one
> configured.
>
> Still, I've made the test with a vanilla OpenNebula 4.2 installation
> and the tips I've sent you work nicely. To test this I've changed the
> prefix to a wrong one so we can see the command:
>
> * Changed /var/lib/one/remotes/vmm/xen4/xenrc and set this line:
>
> export DEFAULT_FILE_PREFIX="this:should:not:work"
>
> * Executed "onehost sync" as oneadmin user. This part is very
> important as the nodes have a copy of driver files (remotes) and we
> need to update those files in the nodes when we modify something in
> the frontend.
>
> * Waited for the next monitoring cycle of all nodes. In OpenNebula 4.2
> the copy of remotes is done in the monitorization phase
>
> * Attach disk:
>
> $ onevm disk-attach 0 --image data
>
> * Got the error:
>
> ERROR="Fri Mar 28 12:41:33 2014 : Error attaching new VM Disk: Could
> not attach
> this:should:not:work:/home/one/one/install-4.2/var//datastores/0/0/disk.1
> (sda) to one-0"
>
> On Thu, Mar 27, 2014 at 8:18 PM, <kenny.ke...@bol.com.br> wrote:
>> see atached files.
>>
>>
>> thanks.
>> ________________________________
>>
>> De: jfon...@gmail.com
>> Enviada: Quinta-feira, 27 de Março de 2014 19:18
>>
>> Para: kenny.ke...@bol.com.br
>> Assunto: [one-users] blktap xen 4.2 and opennebula 4.2
>>
>> Disregard the --force. I've misread the problem. The parameter --force
>> does not work in one 4.2. Just execute:
>>
>> onehost sync
>>
>> On Thu, Mar 27, 2014 at 7:07 PM, Javier Fontan <jfon...@gmail.com> wrote:
>>> Are you sure that the drivers uncomented are xen4 and not xen3?
>>>
>>> Also, can you send me the file xenrc you've changed? That "invalid
>>> option: --force" is so strange.
>>>
>>> On Thu, Mar 27, 2014 at 7:03 PM, <kenny.ke...@bol.com.br> wrote:
>>>> it didnt work.
>>>>
>>>>
>>>>
>>>> i received this message
>>>> invalid option: --force
>>>>
>>>> and it always use file insstead of tap2:aio
>>>> i dont know what to do.
>>>> ________________________________
>>>>
>>>> De: jfon...@gmail.com
>>>> Enviada: Quinta-feira, 27 de Março de 2014 18:08
>>>> Para: kenny.ke...@bol.com.br
>>>> Assunto: [one-users] blktap xen 4.2 and opennebula 4.2
>>>>
>>>>
>>>> You can change it in in "/var/lib/one/remotes/vmm/xen4/xenrc", the
>>>> parameter is DEFAULT_FILE_PREFIX.
>>>>
>>>> Remember to do a onehost sync --force so these files are copied to the
>>>> remote hosts.
>>>>
>>>> On Thu, Mar 27, 2014 at 3:54 AM, <kenny.ke...@bol.com.br> wrote:
>>>>> Hello, i need to use blktap instead of default disk drive.
>>>>>
>>>>> i changed /var/lib/one/remotes/vmm/xen4/attach_disk and
>>>>> /etc/one/vmm_exec/vmm_exec_xen4.conf , but when take a look at
>>>>> deployment.0
>>>>> , it always with "file:".
>>>>> What i need to do to change that ?
>>>>>
>>>>> I will change it beacuase with file i can run just 8 vm per node.
>>>>>
>>>>>
>>>>> thank
>>>>>
>>>>> _______________________________________________
>>>>> Users mailing list
>>>>> Users@lists.opennebula.org
>>>>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Javier Fontán Muiños
>>>> OpenNebula Developer
>>>> OpenNebula - The Open Source Toolkit for Data Center Virtualization
>>>> www.OpenNebula.org | @OpenNebula | github.com/jfontan
>>>
>>>
>>>
>>> --
>>> Javier Fontán Muiños
>>> OpenNebula Developer
>>> OpenNebula - The Open Source Toolkit for Data Center Virtualization
>>> www.OpenNebula.org | @OpenNebula | github.com/jfontan
>>
>>
>>
>> --
>> Javier Fontán Muiños
>> OpenNebula 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@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
