[one-users] Opennebula 4.6.2. Problem with VM creation

Tue Jun 17 07:04:09 PDT 2014

It seems that you have the host configured with kvm drivers, not xen
drivers. Xen drivers (both 3 and 4 versions) do not use libvirt.

virsh list by default shows qemu/kvm machines, that's why your are not
seeing you xen VMs.

On Tue, Jun 17, 2014 at 12:30 PM, Vlad <vladsol at ukr.net> wrote:
> Yes, this is my fault.
> At this moment all is ok, have running xen VM on the XEN host :-)
> Some one question) Migration. From xen hosts is supported?
>
> Host compute2.domain.com is a xen host:
> Tue Jun 17 13:19:18 2014 [VMM][D]: Message received: LOG I 21 Command
> execution fail: /var/tmp/one/vmm/kvm/save 'one-21'
> '/var/lib/one//datastores/102/21/checkpoint' 'compute2.domain.com' 21
> compute2.domain.com
> Tue Jun 17 13:19:18 2014 [VMM][D]: Message received: LOG I 21 save: Moving
> old checkpoint file /var/lib/one//datastores/102/21/checkpoint
> Tue Jun 17 13:19:18 2014 [VMM][D]: Message received: LOG E 21 save: Command
> "virsh --connect qemu:///system save one-21
> /var/lib/one//datastores/102/21/checkpoint" failed: error: failed to get
> domain 'one-21'
> Tue Jun 17 13:19:18 2014 [VMM][D]: Message received: LOG I 21 error: Domain
> not found: no domain with matching name 'one-21'
> Tue Jun 17 13:19:18 2014 [VMM][D]: Message received: LOG E 21 Could not save
> one-21 to /var/lib/one//datastores/102/21/checkpoint
> Tue Jun 17 13:19:18 2014 [VMM][D]: Message received: LOG I 21 ExitCode: 1
> Tue Jun 17 13:19:18 2014 [VMM][D]: Message received: LOG I 21 Failed to
> execute virtualization driver operation: save.
> Tue Jun 17 13:19:18 2014 [VMM][D]: Message received: SAVE FAILURE 21 Could
> not save one-21 to /var/lib/one//datastores/102/21/checkpoint
>
> virsh list said that no vm's, but i have one running vm on this host, and i
> see it in xl :
> # xl vm-list
> UUID                                  ID    name
> 7ba32f37-36ee-45cd-abe0-b69dfa468465  7    one-21
>
> 17.06.2014 12:19, Carlos Martín Sánchez пишет:
>
> Hi,
>
> This is all explained in the documentation:
>
> http://docs.opennebula.org/4.6/administration/virtualization/xeng.html
>
>> xen4 drivers are meant to be used with Xen >=4.2 with xl/xenlight
>> interface. You will need to stop xend daemon for this. For Xen 3.x and Xen
>> 4.x with xm (with xend daemon) you will need to use xen3 drivers.
>
>
>>
>> When using "xen3" drivers for Xen 4.x you should change the configuration
>> file /var/lib/oneremotes/vmm/xen3/xenrc and uncomment the XM_CREDITS line.
>
>
> Regards.
> --
> Carlos Martín, MSc
> Project Engineer
> OpenNebula - Flexible Enterprise Cloud Made Simple
> www.OpenNebula.org | cmartin at opennebula.org | @OpenNebula
>
>
> On Mon, Jun 16, 2014 at 1:22 PM, Vlad <vladsol at ukr.net> wrote:
>>
>> With xen3 driver:
>>
>> Mon Jun 16 14:12:34 2014 [TM][D]: Message received: TRANSFER SUCCESS 20 -
>> Mon Jun 16 14:12:34 2014 [VMM][D]: Message received: LOG I 20 ExitCode: 0
>> Mon Jun 16 14:12:34 2014 [VMM][D]: Message received: LOG I 20 Successfully
>> execute network driver operation: pre.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG D 20 deploy:
>> Credits set to 256
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 Error:
>> Subcommand sched-cred not found!
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG E 20 deploy:
>> Unable to set VM credits
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 ExitCode: 0
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 Successfully
>> execute virtualization driver operation: deploy.
>> Mon Jun 1Message received: LOG I 20 uptime               Print uptime for
>> all/some domains.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 usb-add
>> Add the usb device to FV VM.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 usb-del
>> Delete the usb device to FV VM.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 domstate
>> get the state of a domain
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 vcpu-set
>> Set the number of active VCPUs for allowed for
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 the domain.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 <Domain> can
>> either be the Domain Name or Id.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 For more
>> help on 'xm' see the xm(1) man page.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 For more
>> help on 'xm create' see the xmdomain.cfg(5)  man page.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 For a
>> complete list of subcommands run 'xm help'.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 one-20'
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 bash: line
>> 23: Domain: No such file or directory
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 ExitCode: 1
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 Command
>> execution fail: /var/tmp/one/vmm/xen3/cancel 'Usage: xm <subcommand> [args]
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 Control,
>> list, and manipulate Xen guest instances.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 Common 'xm'
>> commands:
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 console
>> Attach to <Domain>'s console.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 vncviewer
>> Attach to <Domain>'s VNC server.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 create
>> Create a domain based on <ConfigFile>.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 new
>> Adds a domain to Xend domain management
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 delete
>> Remove a domain from Xend domain management.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 destroy
>> Terminate a domain immediately.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 dump-core
>> Dump core for a specific domain.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 help
>> Display this message.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 list
>> List information about all/some domains.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 mem-set
>> Set the current memory usage for a domain.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 migrate
>> Migrate a domain to another machine.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 pause
>> Pause execution of a domain.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 reboot
>> Reboot a domain.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 reset
>> Reset a domain.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 restore
>> Restore a domain from a saved state.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 resume
>> Resume a Xend managed domain
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 save
>> Save a domain state to restore later.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 shell
>> Launch an interactive shell.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 shutdown
>> Shutdown a domain.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 start
>> Start a Xend managed domain
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 suspend
>> Suspend a Xend managed domain
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 top
>> Monitor a host and the domains in real time.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 unpause
>> Unpause a paused domain.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 uptime
>> Print uptime for all/some domains.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 usb-add
>> Add the usb device to FV VM.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 usb-del
>> Delete the usb device to FV VM.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 domstate
>> get the state of a domain
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 vcpu-set
>> Set the number of active VCPUs for allowed for
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 the domain.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 <Domain> can
>> either be the Domain Name or Id.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 For more
>> help on 'xm' see the xm(1) man page.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 For more
>> help on 'xm create' see the xmdomain.cfg(5)  man page.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 For a
>> complete list of subcommands run 'xm help'.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 one-20'
>> 'compute2.domain.com' 20 compute2.domain.com
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 bash: line
>> 25: Domain: No such file or directory
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 ExitCode: 1
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 Failed to
>> execute virtualization driver operation: cancel.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 Failed to
>> execute network driver operation: post.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: DEPLOY FAILURE 20 -6
>> 14:12:35 2014 [VMM][D]: Message received: LOG I 20 Command execution fail:
>> /var/tmp/one/vnm/dummy/post
>> PFZNPjxJRD4yMDwvSUQ+PERFUExPWV9JRC8+PEhJU1RPUllfUkVDT1JEUz48SElTVE9SWT48SE9TVE5BTUU+Y29tcHV0ZTIudHJpYW5ndWx1bS51YTwvSE9TVE5BTUU+PC9ISVNUT1JZPjwvSElTVE9SWV9SRUNPUkRTPjwvVk0+
>> 'Usage: xm <subcommand> [args]
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 Control,
>> list, and manipulate Xen guest instances.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 Common 'xm'
>> commands:
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 console
>> Attach to <Domain>'s console.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 vncviewer
>> Attach to <Domain>'s VNC server.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 create
>> Create a domain based on <ConfigFile>.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 new
>> Adds a domain to Xend domain management
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 delete
>> Remove a domain from Xend domain management.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 destroy
>> Terminate a domain immediately.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 dump-core
>> Dump core for a specific domain.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 help
>> Display this message.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 list
>> List information about all/some domains.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 mem-set
>> Set the current memory usage for a domain.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 migrate
>> Migrate a domain to another machine.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 pause
>> Pause execution of a domain.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 reboot
>> Reboot a domain.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 reset
>> Reset a domain.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 restore
>> Restore a domain from a saved state.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 resume
>> Resume a Xend managed domain
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 save
>> Save a domain state to restore later.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 shell
>> Launch an interactive shell.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 shutdown
>> Shutdown a domain.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 start
>> Start a Xend managed domain
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 suspend
>> Suspend a Xend managed domain
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 top
>> Monitor a host and the domains in real time.
>> Mon Jun 16 14:12:35 2014 [VMM][D]: Message received: LOG I 20 unpause
>> Unpause a paused domain.
>> Mon Jun 16 14:12:35 2014 [VMM][D]:
>>
>>
>>
>>
>> 16.06.2014 13:30, Vlad wrote:
>>>
>>> I didn't know, how, but i solved this problem... But only with KVM.
>>> With xen i found a new problem:
>>>
>>> Mon Jun 16 13:13:30 2014 [TM][D]: Message received: TRANSFER SUCCESS 19 -
>>> Mon Jun 16 13:13:30 2014 [VMM][D]: Message received: LOG I 19 ExitCode: 0
>>> Mon Jun 16 13:13:30 2014 [VMM][D]: Message received: LOG I 19
>>> Successfully execute network driver operation: pre.
>>> Mon Jun 16 13:13:30 2014 [VMM][D]: Message received: LOG I 19 Command
>>> execution fail: cat << EOT | /var/tmp/one/vmm/xen4/deploy
>>> '/var/lib/one//datastores/102/19/deployment.0' 'compute2.domain.com' 19
>>> compute2.domain.com
>>> Mon Jun 16 13:13:30 2014 [VMM][D]: Message received: LOG I 19 xend is
>>> running, which may cause unpredictable results when using
>>> Mon Jun 16 13:13:30 2014 [VMM][D]: Message received: LOG I 19 this xl
>>> command.  Please shut down xend before continuing.
>>> Mon Jun 16 13:13:30 2014 [VMM][D]: Message received: LOG I 19
>>> Mon Jun 16 13:13:30 2014 [VMM][D]: Message received: LOG I 19 (This check
>>> can be overridden with the -f option.)
>>> Mon Jun 16 13:13:30 2014 [VMM][D]: Message received: LOG E 19 Unable
>>> Mon Jun 16 13:13:30 2014 [VMM][D]: Message received: LOG I 19 ExitCode: 1
>>> Mon Jun 16 13:13:30 2014 [VMM][D]: Message received: LOG I 19 Failed to
>>> execute virtualization driver operation: deploy.
>>> Mon Jun 16 13:13:30 2014 [VMM][D]: Message received: DEPLOY FAILURE 19
>>> Unable
>>>
>>>
>>> - but if i stopped the xend, i am loosing virtual host from hosts list
>>> :-)
>>> Xen version is 4.2.4, so i'm using xen4 driver.
>>> Should i use xen3 driver with this xen version?
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opennebula.org
>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>

-- 
Javier Fontán Muiños
Developer
OpenNebula - Flexible Enterprise Cloud Made Simple
www.OpenNebula.org | @OpenNebula | github.com/jfontan