search for: write_exact

...imeval *new, struct timeval *old) +{ + return ((new->tv_sec - old->tv_sec)*1000000 ) + + (new->tv_usec - old->tv_usec); +} + + +#define RATE_IS_MAX() (0) +#define ratewrite(_io_fd, _buf, _n) write((_io_fd), (_buf), (_n)) +#define initialize_mbit_rate() + +static inline ssize_t write_exact(int fd, void *buf, size_t count) +{ + if(write(fd, buf, count) != count) + return 0; + return 1; +} + +static int print_stats(int xc_handle, uint32_t domid, int pages_sent, + xc_shadow_op_stats_t *stats, int print) +{ + static struct timeval wall_last; + sta...

...there is an obsolete lock file in place, which causes the current and later migration cannot get lock. That happens 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...

...ore 4 4 2 3 1 1 1 failed and on the sending hypervisor: [2009-02-02 11:57:32 11768] ERROR (XendCheckpoint:157) Save failed on domain xen20 (13) - r esuming. Traceback (most recent call last): File "/usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py", line 135, in save write_exact(fd, buf, "could not write device model state") File "/usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py", line 44, in write_e xact raise XendError(errmsg) XendError: could not write device model state what do "could not write device model state" and...

This patch series copies the core of the tapdisk process from blktap2, with updates coming from blktap2.5. Signed-off-by: Thanos Makatos <thanos.makatos@citrix.com>

The following series of 10 patches is a merge of the xenfb and xenconsoled functionality into the qemu-dm code. The general approach taken is to have qemu-dm provide two machine types - one for xen paravirt, the other for fullyvirt. For compatability the later is the default. The goals overall are to kill LibVNCServer, remove alot of code duplication and/or parallel impls of the same concepts, and