From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexis RIES Subject: COLO Xen patch v12 - Unable to start virtual machine Date: Thu, 24 Mar 2016 11:22:33 +0100 Message-ID: <56F3BFE9.7030804@kinaxia.fr> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="------------090303000004050408010108" Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xen.org Sender: "Xen-devel" To: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org This is a multi-part message in MIME format. --------------090303000004050408010108 Content-Type: multipart/alternative; boundary="------------030400040500080908090108" --------------030400040500080908090108 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit I have managed to compile Xen, the kernel, COLO, following the information in this thread. http://lists.xenproject.org/archives/html/xen-devel/2016-02/msg03507.html Github branche : changlox/colo_v12 https://github.com/Pating/xen/tree/changlox/colo_v12 Xen (COLO version) is now compiled and installed, the kernel patched and network cards are configured as in the documentation below: http://wiki.xen.org/wiki/COLO_-_Coarse_Grain_Lock_Stepping When I try to start a virtual machine, I receive this error message: [root@xen1 ~]# xl create /var/virtualStore/test/test.cfg Parsing config from /var/virtualStore/test/test.cfg libxl: warning: libxl_dm.c:1447:libxl__build_device_model_args_new: Could not find user xen-qemuuser-shared, starting QEMU as root libxl: error: libxl_device.c:963:device_backend_callback: unable to add device with path /local/domain/0/backend/vif/3/0 libxl: error: libxl_create.c:1443:domcreate_attach_vtpms: unable to add nic devices libxl: error: libxl_device.c:963:device_backend_callback: unable to remove device with path /local/domain/0/backend/vif/3/0 libxl: error: libxl.c:1638:devices_destroy_cb: libxl__devices_destroy failed for 3 libxl: error: libxl.c:1565:libxl__destroy_domid: non-existant domain 3 libxl: error: libxl.c:1523:domain_destroy_callback: unable to destroy guest with domid 3 libxl: error: libxl.c:1452:domain_destroy_cb: destruction of domain 3 failed When I commented the network line in the virtual machine configuration file, it works correctly. I tried with or without COLO in the virtual machine configuration file, without success. Attached, the virtual machine configuration file. Someone an idea for this problem? --------------030400040500080908090108 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit I have managed to compile Xen, the kernel, COLO, following the information in this thread.
http://lists.xenproject.org/archives/html/xen-devel/2016-02/msg03507.html

Github branche : changlox/colo_v12
https://github.com/Pating/xen/tree/changlox/colo_v12

Xen (COLO version) is now compiled and installed, the kernel patched and network cards are configured as in the documentation below:
http://wiki.xen.org/wiki/COLO_-_Coarse_Grain_Lock_Stepping


When I try to start a virtual machine, I receive this error message:

[root@xen1 ~]# xl create /var/virtualStore/test/test.cfg
Parsing config from /var/virtualStore/test/test.cfg
libxl: warning: libxl_dm.c:1447:libxl__build_device_model_args_new: Could not find user xen-qemuuser-shared, starting QEMU as root
libxl: error: libxl_device.c:963:device_backend_callback: unable to add device with path /local/domain/0/backend/vif/3/0
libxl: error: libxl_create.c:1443:domcreate_attach_vtpms: unable to add nic devices
libxl: error: libxl_device.c:963:device_backend_callback: unable to remove device with path /local/domain/0/backend/vif/3/0
libxl: error: libxl.c:1638:devices_destroy_cb: libxl__devices_destroy failed for 3
libxl: error: libxl.c:1565:libxl__destroy_domid: non-existant domain 3
libxl: error: libxl.c:1523:domain_destroy_callback: unable to destroy guest with domid 3
libxl: error: libxl.c:1452:domain_destroy_cb: destruction of domain 3 failed

When I commented the network line in the virtual machine configuration file, it works correctly.

I tried with or without COLO in the virtual machine configuration file, without success.

Attached, the virtual machine configuration file.

Someone an idea for this problem?
--------------030400040500080908090108-- --------------090303000004050408010108 Content-Type: text/plain; charset=UTF-8; name="testmachine.cfg" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="testmachine.cfg" YnVpbGRlcj0naHZtJwptZW1vcnkgPSAyMDQ4CnZjcHVzPTIKY3B1cz1bIjIiLCAiMyJdCm5h bWUgPSAiaHZtX25vcHZfY29sbyIKCiNkaXNrID0gWyAnZm9ybWF0PXJhdyxkZXZ0eXBlPWRp c2ssYWNjZXM9dyx2ZGV2PWhkYSxiYWNrZW5kdHlwZT1xZGlzayxjb2xvLGNvbG8tcGFyYW1z PTEwLjAuMi4yOjkwMDA6ZXhwb3J0bmFtZT1xZGlzazEsYWN0aXZlLWRpc2s9L21udC9yYW1m cy9hY3RpdmVfZGlzay5pbWcsaGlkZGVuLWRpc2s9L21udC9yYW1mcy9oaWRkZW5fZGlzay5p bWcsdGFyZ2V0PS92YXIvdmlydHVhbFN0b3JlL3Rlc3QvWGVuR3Vlc3QxLmltZycgXQpkaXNr ID0gWyAnZmlsZTovdmFyL3ZpcnR1YWxTdG9yZS90ZXN0L1hlbkd1ZXN0MS5pbWcsaGRhLHcn LCAnZmlsZTovdmFyL3ZpcnR1YWxTdG9yZS9pc28vd2luZG93czcuaXNvLGhkYzpjZHJvbSxy JyBdCgp2aWYgPSBbICdtYWM9MDA6MTY6NGY6MDA6MDA6MTEsIGJyaWRnZT1icjAsIG1vZGVs PXZpcnRpby1uZXQsIGZvcndhcmRkZXY9ZXRoMScgXQojdmlmID0gWyAnbWFjPTAwOjE2OjRm OjAwOjAwOjExLCBicmlkZ2U9YnIwJyBdCgojLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0KIyBi b290IG9uIGZsb3BweSAoYSksIGhhcmQgZGlzayAoYyksIE5ldHdvcmsgKG4pIG9yIENELVJP TSAoZCkKIyBkZWZhdWx0OiBoYXJkIGRpc2ssIGNkLXJvbSwgZmxvcHB5CmJvb3Q9ImMiCnNk bD0wCnZuYz0xCnZuY2xpc3Rlbj0nMC4wLjAuMCcKdm5jdW51c2VkID0gMQpzdGR2Z2EgPSAw CnNlcmlhbD0ncHR5JwphcGljPTEKYXBjaT0xCnBhZT0xCmV4dGlkPTAKa2V5bWFwPSJlbi11 cyIKbG9jYWx0aW1lPTEKaHBldD0xCnVzYmRldmljZT0ndGFibGV0Jwp4ZW5fcGxhdGZvcm1f cGNpPTAK --------------090303000004050408010108 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVs IG1haWxpbmcgbGlzdApYZW4tZGV2ZWxAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlzdHMueGVuLm9y Zy94ZW4tZGV2ZWwK --------------090303000004050408010108--