For what its worth the line within the interfaces section:

<link state='up'/>

Causes the container creation to fail on the first try, and then work on
the second. I've attached the output and log below:

==== Command output ====
[root@stark-ssd02 ~]# virsh define dom.xml
error: Failed to define domain from dom.xml
error: internal error: PRL_ERR_VM_NOT_CREATED PRL_ERR_VM_NOT_CREATED
========


==== Log Output ====
Aug 10 15:04:00 stark-ssd02 prl_disp_service: 08-10 15:04:00.552 F
/disp:3342:3387/ Processing command 'DspCmdGetDefaultVmConfig' 2156
(PJOC_UNKNOWN)
Aug 10 15:04:00 stark-ssd02 prl_disp_service: 08-10 15:04:00.558 F
/disp:3342:3387/ Processing command 'DspCmdGetDefaultVmConfig' 2156 for CT
uuid=''
Aug 10 15:04:00 stark-ssd02 prl_disp_service: 08-10 15:04:00.589 F
/disp:3342:3387/ Processing command 'DspCmdAddVirtualNetwork' 2111
(PJOC_SRV_ADD_VIRTUAL_NETWORK)
Aug 10 15:04:00 stark-ssd02 prl_disp_service: 08-10 15:04:00.590 F
/disp:3342:6815/ Task '24Task_ManagePrlNetService' with uuid =
{560a2b5e-247f-4d0b-8cbf-ed16aeaefe7b} was started. Flags = 0x800
Aug 10 15:04:00 stark-ssd02 libvirtd: 1677: error
 : virNetworkAssignDefLocked:555 : operation failed: network 'ovsbr0'
already exists with uuid 53089767-a631-48d8-a33b-571d8f67ecbf
Aug 10 15:04:00 stark-ssd02 prl_disp_service: 08-10 15:04:00.592 F
/disp:3342:6815/ libvirt error operation failed: network 'ovsbr0' already
exists with uuid 53089767-a631-48d8-a33b-571d8f67ecbf
Aug 10 15:04:00 stark-ssd02 prl_disp_service: 08-10 15:04:00.645 F
/disp:3342:6815/ error: -2147483355 was catched. reason Success
Aug 10 15:04:00 stark-ssd02 prl_disp_service: 08-10 15:04:00.646 F
/disp:3342:6815/ Task '24Task_ManagePrlNetService' with uuid =
{560a2b5e-247f-4d0b-8cbf-ed16aeaefe7b} was finished with result
PRL_ERR_VM_NOT_CREATED (0x80000125) )
Aug 10 15:04:00 stark-ssd02 libvirtd: 1672: error : prlsdkAddNet:3038 :
internal error: PRL_ERR_VM_NOT_CREATED PRL_ERR_VM_NOT_CREATED
Aug 10 15:04:00 stark-ssd02 prl_disp_service: 08-10 15:04:00.649 F
/disp:3342:3387/ Processing command 'DspCmdDeleteVirtualNetwork' 2113
(PJOC_SRV_DELETE_VIRTUAL_NETWORK)
Aug 10 15:04:00 stark-ssd02 prl_disp_service: 08-10 15:04:00.650 F
/disp:3342:6816/ Task '24Task_ManagePrlNetService' with uuid =
{58665f42-2560-47ba-a779-f7ad69fff736} was started. Flags = 0
Aug 10 15:04:00 stark-ssd02 prl_disp_service: 08-10 15:04:00.734 F
/disp:3342:6816/ Task '24Task_ManagePrlNetService' with uuid =
{58665f42-2560-47ba-a779-f7ad69fff736} was finished with result
PRL_ERR_SUCCESS (0) )
========

On Wed, Aug 10, 2016 at 7:20 AM, Maxim Nestratov <mnestra...@virtuozzo.com>
wrote:

> 10-Aug-16 13:27, Sergey Bronnikov пишет:
>
> Hi, Frank
>>
>> On 09:43 Tue 09 Aug , Frank Laszlo wrote:
>>
>>> Hello,
>>>
>>> My company is rolling out a new setup, which was originally going to use
>>> openvz 6. With the release of vz7, we'd like to take a moment to see if
>>> it
>>> meets our requirements.
>>>
>>> I have a handful of questions that I have no been able to find answers
>>> to,
>>> as the documentation is rather spare.
>>>
>>> 1) Am I able to create containers using libvirt? (specifically from XML
>>> passed to virsh) What does this XML look like?
>>>
>> Max, please comment.
>>
>
> Yes you are. Below is an example:
>
> <domain type='vz'>
>   <name>your-ct-name</name>
>   <uuid>5869cd3e-13fc-4e69-b99a-d37c020987b6</uuid>
>   <memory unit='KiB'>524288</memory>
>   <currentMemory unit='KiB'>524288</currentMemory>
>   <vcpu placement='static'>1</vcpu>
>   <os>
>     <type arch='x86_64'>exe</type>
>     <init>/sbin/init</init>
>   </os>
>   <clock offset='utc'/>
>   <on_poweroff>destroy</on_poweroff>
>   <on_reboot>restart</on_reboot>
>   <on_crash>destroy</on_crash>
>   <devices>
>     <filesystem type='file' accessmode='passthrough'>
>       <driver type='ploop' format='ploop'/>
>       <source file='/path/to/your/ploop/disk/directory'/>
>       <target dir='/'/>
>     </filesystem>
>     <interface type='bridge'>
>       <mac address='fa:16:3e:c6:5c:90'/>
>       <source bridge='some-bridge'/>
>       <target dev='veth1234'/>
>       <link state='up'/>
>     </interface>
>     <input type='mouse' bus='parallels'/>
>     <input type='keyboard' bus='parallels'/>
>     <graphics type='vnc' port='-1' autoport='yes' listen='10.27.68.3'>
>       <listen type='address' address='10.27.68.3'/>
>     </graphics>
>     <video>
>       <model type='parallels' heads='1'/>
>     </video>
>   </devices>
> </domain>
>
>
> 2) Are OS Templates any different than openvz 6.0?
>>>
>> Yes, OpenVZ 7 uses EZ templates.
>> See https://docs.openvz.org/openvz_users_guide.webhelp/_managing
>> _templates.html
>>
>> 3) Has vz7 been tested with openvswitch and veth?
>>>
>>
> it was tested via intermediate linux bridge
>
> 4) Does networking in vz7 work like KVM does now that we're using KVM for
>>> the hypervisor?
>>>
>>
> you can use veth interfaces in CTs, which can be plugged into an arbitrary
> bridge on the host
>
> 5) I noticed vz7 supports qcow2, In my testing containers created with
>>> prlctl were still using ploop. Is there a trick to enable this?
>>>
>>
> ploop format is for containers, qcow2 - for virtual machines. There is no
> trick to make containers use qcow2 at the moment.
>
>
> Dima, please comment.
>>
>> 6) Can VZ7 hosts be kickstarted? I thought I read somewhere that kickstart
>>> was a "premium" feature only available in the paid version.
>>>
>> Installation using Kickstart is available in OpenVZ 7 too -
>> https://docs.openvz.org/openvz_installation_using_pxe_guide.
>> webhelp/_creating_a_kickstart_file.html
>>
>> I'm sure I'll have a bunch more questions, but this is where I'm starting
>>> at. Thank you.
>>>
>>> --
>>> Frank Laszlo
>>> Nexcess - Beyond Hosting
>>> 21700 Melrose Ave.
>>> Southfield, MI. 48075
>>> Phone: +1.866.639.2377
>>> Fax:   +1.248.281.0473
>>> _______________________________________________
>>> Users mailing list
>>> Users@openvz.org
>>> https://lists.openvz.org/mailman/listinfo/users
>>>
>>
>>
>


-- 
Frank Laszlo
Nexcess - Beyond Hosting
21700 Melrose Ave.
Southfield, MI. 48075
Cell: +1.248.602.6123
Phone: +1.866.639.2377
Fax:   +1.248.281.0473
_______________________________________________
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users

Reply via email to