search for: coproc

On Thu, 2013-08-15 at 12:14 +0200, Pavel Machek wrote: > Hi! > Hi! > > > > Since it is a PCIe card, it does not have the ability to host hardware > > > > devices for networking, storage and console. We provide these devices > > > > on X100 coprocessors thus enabling a self-bootable equivalent environment > > > > for applications. A key benefit of our solution is that it leverages > > > > the standard virtio framework for network, disk and console devices, > > > > though in our case the virtio framework is...

On Thu, 2013-08-15 at 12:14 +0200, Pavel Machek wrote: > Hi! > Hi! > > > > Since it is a PCIe card, it does not have the ability to host hardware > > > > devices for networking, storage and console. We provide these devices > > > > on X100 coprocessors thus enabling a self-bootable equivalent environment > > > > for applications. A key benefit of our solution is that it leverages > > > > the standard virtio framework for network, disk and console devices, > > > > though in our case the virtio framework is...

On Tue, 2013-08-13 at 14:43 +0200, Pavel Machek wrote: > Hi! > > > Since it is a PCIe card, it does not have the ability to host hardware > > devices for networking, storage and console. We provide these devices > > on X100 coprocessors thus enabling a self-bootable equivalent environment > > for applications. A key benefit of our solution is that it leverages > > the standard virtio framework for network, disk and console devices, > > though in our case the virtio framework is used across a PCIe bus. >...

On Tue, 2013-08-13 at 14:43 +0200, Pavel Machek wrote: > Hi! > > > Since it is a PCIe card, it does not have the ability to host hardware > > devices for networking, storage and console. We provide these devices > > on X100 coprocessors thus enabling a self-bootable equivalent environment > > for applications. A key benefit of our solution is that it leverages > > the standard virtio framework for network, disk and console devices, > > though in our case the virtio framework is used across a PCIe bus. >...

Hi, We have a VM with several USB devices attached. Everything works well, but sometimes, after a reboot of the host, some usb device get a different bus/device number and that prevent the reboot of the VM : ------- error: Failed to start domain xxx error: internal error: Did not find USB device 04b9:0300 bus:1 device:5 ------- I guess this is because we have multiple usb devices with the same

...tach devices when they are plugged into a # specific port on the host machine. # # See: https://github.com/olavmrk/usb-libvirt-hotplug # # Abort script execution on errors set -e PROG="$(basename "$0")" if [ ! -t 1 ]; then # stdout is not a tty. Send all output to syslog. coproc logger --tag "${PROG}" exec >&${COPROC[1]} 2>&1 fi DOMAIN="$1" if [ -z "${DOMAIN}" ]; then echo "Missing libvirt domain parameter for ${PROG}." >&2 exit 1 fi # # Do some sanity checking of the udev environment variables. # if [...

.../etc/default/xendomains ] && . /etc/default/xendomains shopt -s nullglob check_config_name() { xen create --quiet --dryrun --defconfig "$1" | sed -n 's/^.*(name \(.*\))$/\1/p' } check_running() { xen domid "$1" > /dev/null 2>&1 return $? } timeout_coproc() { local TIMEOUT=$1 shift coproc "$@" 2>&1 1>/dev/null local COPROC_OUT exec {COPROC_OUT}<&"${COPROC[0]}" local PID="$COPROC_PID" for no in $(seq 0 $TIMEOUT); do if [ -z "$COPROC_PID" ]; then break; fi sleep 1 log_a...

Hi! > > > Since it is a PCIe card, it does not have the ability to host hardware > > > devices for networking, storage and console. We provide these devices > > > on X100 coprocessors thus enabling a self-bootable equivalent environment > > > for applications. A key benefit of our solution is that it leverages > > > the standard virtio framework for network, disk and console devices, > > > though in our case the virtio framework is used across a...

.../etc/default/xendomains ] && . /etc/default/xendomains shopt -s nullglob check_config_name() { xen create --quiet --dryrun --defconfig "$1" | sed -n 's/^.*(name \(.*\))$/\1/p' } check_running() { xen domid "$1" > /dev/null 2>&1 return $? } timeout_coproc() { TIMEOUT="$1" for no in $(seq 0 $TIMEOUT); do if [ -z "$COPROC_PID" ]; then return 0; fi sleep 1 log_action_cont_msg done kill -INT "$COPROC_PID" >/dev/null 2>&1 wait $COPROC_PID return 1 } timeout_domain() { name="$1"...

This round implements all of the review comments from V2 and all patches are now acked. Unless there are any objections I intend to apply later this morning. Ian.

...AArch64 system register and a AArch32 cp register. To try and reduce ifdeferry in common code I''ve introduced some macros which take the AArch64 name but which translate to the appropriate AArch32 cpreg access in the 32-bit hypervisor. A little bit of ifdeferry remains. Other uses of the coprocessors (e.g. cache/TLB flushing etc) are replaced with explicit instructions (again there''s mostly a 1-1 mapping). We had already wrapped most of these in a suitable inline function so it was easy enough to abstract away. Lastly, rather than switch internally from explicitly sized types to...

Hello everyone, this is the fourth version of the patch series that introduces ARMv7 with virtualization extensions support in Xen. The series allows Xen and Dom0 to boot on a Cortex-A15 based Versatile Express simulator. See the following announce email for more informations about what we are trying to achieve, as well as the original git history: See

Hello everyone, this is the very first version of the patch series that introduces ARMv7 with virtualization extensions support in Xen. The series allows Xen and Dom0 to boot on a Cortex-A15 based Versatile Express simulator. See the following announce email for more informations about what we are trying to achieve, as well as the original git history: See