Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upDispVM start error - error: internal error: Failed to save domain '30' with libxenlight #2482
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Dec 4, 2016
Member
Take a look at /var/log/libvirt/libxl/libxl-driver.log - there should be more detailed message.
|
Take a look at |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
adrelanos
Dec 4, 2016
Member
2016-12-04 18:10:59 CET libxl: error: libxl_device.c:1006:device_backend_callback: unable to remove device with path /local/domain/3/backend/vif/28/0
2016-12-04 18:10:59 CET libxl: error: libxl.c:1699:devices_destroy_cb: libxl__devices_destroy failed for 28
2016-12-04 18:16:54 CET libxl: error: libxl_device.c:1006:device_backend_callback: unable to remove device with path /local/domain/3/backend/vif/29/0
2016-12-04 18:16:54 CET libxl: error: libxl.c:1699:devices_destroy_cb: libxl__devices_destroy failed for 29
2016-12-04 18:17:19 CET xc: error: Failed to get vcpu0 context (12 = Cannot allocate memory): Internal error
2016-12-04 18:17:19 CET xc: error: Save failed (12 = Cannot allocate memory): Internal error
2016-12-04 18:17:19 CET libxl: error: libxl_stream_write.c:329:libxl__xc_domain_save_done: saving domain: domain responded to suspend request: Cannot allocate memory
2016-12-04 18:17:21 CET libxl: error: libxl_device.c:1006:device_backend_callback: unable to remove device with path /local/domain/3/backend/vif/30/0
2016-12-04 18:17:22 CET libxl: error: libxl.c:1699:devices_destroy_cb: libxl__devices_destroy failed for 30
2016-12-04 18:39:43 CET libxl: error: libxl_device.c:1006:device_backend_callback: unable to remove device with path /local/domain/3/backend/vif/5/0
2016-12-04 18:39:43 CET libxl: error: libxl.c:1699:devices_destroy_cb: libxl__devices_destroy failed for 5
|
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Looks like out of memory. I guess you have a lot of VMs running? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
adrelanos
Dec 4, 2016
Member
I did. I've just closed 6 VMs or so to make sure there is enough RAM. Same issue. tailed the log in meanwhile to show only what it is saying for another new try (ignoring old messages).
2016-12-04 21:13:46 CET xc: error: Failed to get vcpu0 context (12 = Cannot allocate memory): Internal error
2016-12-04 21:13:46 CET xc: error: Save failed (12 = Cannot allocate memory): Internal error
2016-12-04 21:13:46 CET libxl: error: libxl_stream_write.c:329:libxl__xc_domain_save_done: saving domain: domain responded to suspend request: Cannot allocate memory
2016-12-04 21:13:47 CET libxl: error: libxl_device.c:1006:device_backend_callback: unable to remove device with path /local/domain/3/backend/vif/35/0
2016-12-04 21:13:47 CET libxl: error: libxl.c:1699:devices_destroy_cb: libxl__devices_destroy failed for 35
|
I did. I've just closed 6 VMs or so to make sure there is enough RAM. Same issue.
|
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Dec 4, 2016
Member
How much free memory xl info reports? Anything about it in xl dmesg (I guess nothing there)?
|
How much free memory |
andrewdavidwong
added
the
C: core
label
Dec 5, 2016
andrewdavidwong
added this to the Release 3.2 updates milestone
Dec 5, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
adrelanos
Dec 5, 2016
Member
Now, after the system was idle for some time, DispVM can be started. I'll provide this debug output again once I run into this again.
xl info
free_memory 3578
There may be something interesting indeed. Excerpt:
(XEN) Bogus DMIBAR [redacted] on [redacted]
(XEN) Scrubbing Free RAM on 1 nodes using 4 CPUs
(XEN) .................................done.
(XEN) Initial low memory virq threshold set at [redacted] pages.
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) Freed [redacted] init memory.
(XEN) Bogus DMIBAR [redacted] on [redacted]
(Full xl dmesg sent privately to @marmarek.)
|
Now, after the system was idle for some time, DispVM can be started. I'll provide this debug output again once I run into this again.
There may be something interesting indeed. Excerpt:
(Full |
adrelanos commentedDec 4, 2016
Qubes OS version (e.g.,
R3.2):R3.2 with testing repository.
Affected TemplateVMs (e.g.,
fedora-23, if applicable):whonix-ws (but probably not a template issue)
Actual behavior:
Already managed to reproduce this twice. Beforehand it was save domain '23' and now save domain '30'. No power loss at any time. No ctrl + c at any time. No hdd disk errors at any time.
Steps to reproduce the behavior:
Playing around with DispVMs a lot to deepen understanding. However, nothing unjustifiable. Steps here:
https://forums.whonix.org/t/qubes-dispvm-technical-discussion/3232/8