search for: suspend_evtchn

...ens seldomly but do happen. After checking the source code, I found there are some places that potentially cause lock file unlinked, including: 1) in lock_suspend_event() function, when write_exact fails, it doesn''t remove the lock file and later there is no chance to remove it. 2) in xc_suspend_evtchn_init() function, in "cleanup" block, I can''t see any reason for checking if(suspend_evtchn != -1), if suspend_evtchn=-1, it doesn''t remove the lock file and later there is no chance to remove it. These places have been modified in the following patch, and, in addition,...

..., "/local/domain/%d/device/suspend/event-channel", domid); @@ -88,20 +88,19 @@ si.xce = xc_evtchn_open(); if (si.xce < 0) { - errx(1, "failed to open event channel handle"); + warnx("failed to open event channel handle"); goto cleanup; } si.suspend_evtchn = xc_evtchn_bind_interdomain(si.xce, domid, port); if (si.suspend_evtchn < 0) { - errx(1, "failed to bind suspend event channel: %d", - si.suspend_evtchn); + warnx("failed to bind suspend event channel: %d", si.suspend_evtchn); goto cleanup; } rc = xc_...

This patch series adds support for preservation of the VM generation ID buffer address in xenstore across save/restore and migrate, and also code to increment the value in all cases except for migration. Patch 1 modifies the guest ro and rw node creation to an open coding style and cleans up some extraneous node creation. Patch 2 modifies creation of the hvmloader key in xenstore and adds

This patch series adds support for preservation of the VM generation ID buffer address in xenstore across save/restore and migrate, and also code to increment the value in all cases except for migration. The first patch modifies creation of the hvmloader key in xenstore and adds creation of a new read/write hvmloader/generation-id-addr key. The second patch changes hvmloader to use the new key (as

This patch series adds support for preservation of the VM generation ID buffer address in xenstore across save/restore and migrate, and also code to increment the value in all cases except for migration. The vast majority of the code is in second patch. The first patch merely changes the xenstore key name used by hvmloader to store the buffer address.

These two patches were originally part of the XSM series that I have posted, and remain prerequisites for that series. However, they are independent of the XSM changes and are a useful simplification regardless of the use of XSM. The Acked-bys on these patches were provided before rebasing them over the copyback changes in 26268:1b72138bddda, which had minor conflicts that I resolved. [PATCH

The following is a revised patch series to add support for a VM generation ID virtual device for HVM guests. The basic requirements of this device are as follows: - It must be exposed somewhere in ACPI namespace with a _CID of "VM_Gen_Counter". - It must also include a _DDN of "VM_Gen_Counter". - It must contain a _HID object but no particular value is required. - It must

Changes from v3: - mini-os configuration files moved into stubdom/ - mini-os extra console support now a config option - Fewer #ifdefs - grant table setup uses hypercall bounce - Xenstore stub domain syslog support re-enabled Changes from v2: - configuration support added to mini-os build system - add mini-os support for conditionally compiling frontends, xenbus -