April 2, 201412 yr as you can see from the subject i think ive managed to kill my xen installation on unraid 6b4, not sure if i get a prize, gold star or a choccie bar perhaps? basically i can no longer start my arch linux vm (not ironic's vm), xl create -c <path to cfg file> i see pygrub boot screen and then the following:- libxl: error: libxl_device.c:894:device_backend_callback: unable to add device with path /local/domain/0/backend/vif/34/0 libxl: error: libxl_create.c:1115:domcreate_attach_vtpms: unable to add nic devices libxl: error: libxl_device.c:894:device_backend_callback: unable to remove device with path /local/domain/0/backend/vif/34/0 libxl: error: libxl.c:1456:devices_destroy_cb: libxl__devices_destroy failed for 34 any of you xen guru's seen anything like this?, unfortunately i cant reboot my server yet to see if this clears the issue (running parity check) but once done i may well give it a swift kick in the knackers to see if it clears the issue. vm has been booting fine for last day and a half with multiple restarts.
April 2, 201412 yr Love the subject line ;-). Interested to know what you did before you started having this issue. Can you share your logs with us? Would be very helpful in diagnosing...
April 2, 201412 yr Author Repeated shutdown and start seems to of killed it, I think I may of been a bit quick on trying to start before VM was shutdown fully and some how blown up the xen stack Will post syslog later if I get chance
April 3, 201412 yr Author ok after parity check had completed i stopped the array and went for a shutdown (via gui), the server didnt shutdown and had to do a hard shutdown, luckily with the array already stopped i dont get a parity check on boot :-). booted up and its all working again, so i def managed to screw xen up in some way, ive attached the zipped up syslog if anybody is interested (syslog copied BEFORE attempted shutdown). syslog.zip
Archived
This topic is now archived and is closed to further replies.