From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eugene Fedotov Subject: Unable to create VM with nic device on Arndale Date: Wed, 18 Dec 2013 15:07:23 +0400 Message-ID: <52B181EB.6080303@samsung.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=------------040400020505040108060307 Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org This is a multi-part message in MIME format. --------------040400020505040108060307 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hello! Could someone check VIF creation on ARM ? My domU's config is following: extra = "console=hvc0 debug ipv6.disable=1"; kernel = "/boot/zImageU" memory = 128 name = "domU-1" vcpus = 1 vif = [ 'script=/etc/xen/scripts/vif-route, ip=10.0.0.1' ]; "xl create domU.conf" causes following output: Parsing config from domU.conf libxl: error: libxl_create.c:1180:domcreate_attach_vtpms: unable to add nic devices libxl: error: libxl_device.c:780:libxl__initiate_device_remove: unable to get my domid libxl: error: libxl.c:1452:devices_destroy_cb: libxl__devices_destroy failed for 1 Libxl code assumes that domcreate_attach_vtpms handler called, that calls domcreate_attach_pci. Why vif is logically depend on PCI and vtpm on ARM platform? (it is confusing). Best regards, Eugene --------------040400020505040108060307 Content-Type: text/x-vcard; charset=utf-8; name="e_fedotov.vcf" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="e_fedotov.vcf" YmVnaW46dmNhcmQNCmZuOkV2Z2VueSBGZWRvdG92ICANCm46RmVkb3RvdjtFdmdlbnkNCm9y ZzpTYW1zdW5nO0NTRw0KYWRyO2RvbTo7O0R2aW50c2V2IDEyLzEgQnVpbGRpbmcgQztNb3Nj b3cNCmVtYWlsO2ludGVybmV0OmUuZmVkb3RvdkBzYW1zdW5nLmNvbQ0KdGl0bGU6RW5naW5l ZXINCnZlcnNpb246Mi4xDQplbmQ6dmNhcmQNCg0K --------------040400020505040108060307 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --------------040400020505040108060307--