similar to: Re[2]: setting up private networking between dom0 and domU?

Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> diff -r cfb49fe940fd -r 81f75ed45ec2 tools/hotplug/Linux/init.d/xencommons --- a/tools/hotplug/Linux/init.d/xencommons Tue Aug 16 16:56:16 2011 -0700 +++ b/tools/hotplug/Linux/init.d/xencommons Tue Aug 16 17:05:18 2011 -0700 @@ -29,12 +29,18 @@ XENCONSOLED_PIDFILE=/var/run/xenconsoled.pid shopt -s extglob -if [

put_user() may fail. In this case propagate error code from privcmd_ioctl_mmap_batch(). Signed-off-by: Vasiliy Kulikov <segooon at gmail.com> --- Compile tested. drivers/xen/xenfs/privcmd.c | 8 ++------ 1 files changed, 2 insertions(+), 6 deletions(-) diff --git a/drivers/xen/xenfs/privcmd.c b/drivers/xen/xenfs/privcmd.c index f80be7f..2eb04c8 100644 ---

put_user() may fail. In this case propagate error code from privcmd_ioctl_mmap_batch(). Signed-off-by: Vasiliy Kulikov <segooon at gmail.com> --- Compile tested. drivers/xen/xenfs/privcmd.c | 8 ++------ 1 files changed, 2 insertions(+), 6 deletions(-) diff --git a/drivers/xen/xenfs/privcmd.c b/drivers/xen/xenfs/privcmd.c index f80be7f..2eb04c8 100644 ---

Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> diff -r 8d6edc3d26d2 -r cfb49fe940fd tools/hotplug/Linux/init.d/xencommons --- a/tools/hotplug/Linux/init.d/xencommons Sat Aug 13 10:14:58 2011 +0100 +++ b/tools/hotplug/Linux/init.d/xencommons Tue Aug 16 16:56:16 2011 -0700 @@ -29,11 +29,9 @@ XENCONSOLED_PIDFILE=/var/run/xenconsoled.pid shopt -s extglob -if test

Dear xen-devel, There''s a race condition in xenfs (xenstore driver) that causes userspace utility xenstore-watch to crash. Normally, the userspace process gets an "OK" from xenfs and then the watch fires immediately after. Occasionally, this happens the other way around: the watch fires before the driver sends "OK", which confuses the xenstore-watch client. It seems

XEN_DOM0 is a silent option that has been automatically selected when CONFIG_XEN is selected since 6b0661a5e6fbf. If this option was changed to a menu configurable option then it would only give users the ability to compile out about 100 kbytes of code. As that option makes little sense to choose, and the option isn''t menu selectable anyway, then we can clean up some code by simply

XEN_DOM0 is a silent option that has been automatically selected when CONFIG_XEN is selected since 6b0661a5e6fbf. If this option was changed to a menu configurable option then it would only give users the ability to compile out about 100 kbytes of code. As that option makes little sense to choose, and the option isn''t menu selectable anyway, then we can clean up some code by simply

XEN_DOM0 is a silent option that has been automatically selected when CONFIG_XEN is selected since 6b0661a5e6fbf. If this option was changed to a menu configurable option then it would only give users the ability to compile out about 100 kbytes of code. As that option makes little sense to choose, and the option isn''t menu selectable anyway, then we can clean up some code by simply

On Wed, Oct 30, 2019 at 12:55:37PM -0400, Boris Ostrovsky wrote: > On 10/28/19 4:10 PM, Jason Gunthorpe wrote: > > From: Jason Gunthorpe <jgg at mellanox.com> > > > > gntdev simply wants to monitor a specific VMA for any notifier events, > > this can be done straightforwardly using mmu_range_notifier_insert() over > > the VMA's VA range. > > >

Hi. I am using xen 4.2.2, the system runs okay. But when I suspend it, it does so, but crashes on trying to resume. Here is lsmod output: Module Size Used by xen_pciback 52011 0 xen_netback 27468 0 xen_blkback 26998 0 xen_gntalloc 13144 0 xen_gntdev 17403 1 xen_evtchn 13132 1 xenfs 12985 1 xen_privcmd 13177 5 xenfs parport_pc 28152 0 ppdev 17073 0 rfcomm 42641 12 bnep 18036 2 ext2 72837 1

Hi. I am using xen 4.2.2, the system runs okay. But when I suspend it, it does so, but crashes on trying to resume. Here is lsmod output: Module Size Used by xen_pciback 52011 0 xen_netback 27468 0 xen_blkback 26998 0 xen_gntalloc 13144 0 xen_gntdev 17403 1 xen_evtchn 13132 1 xenfs 12985 1 xen_privcmd 13177 5 xenfs parport_pc 28152 0 ppdev 17073 0 rfcomm 42641 12 bnep 18036 2 ext2 72837 1

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9 Severity: critical Justification: breaks the whole system Dear Maintainer, After upgrading the R610 server from Debian 7 to Debian 8, the dom0 becomes unresponsive via ssh after an hour or so, although the domUs still remain accessible. Initially we thought it may be a disk space issue on / or /boot so action was taken to increase those

Package: xen-hypervisor-4.3-amd64 Version: 4.3.0-3+b1 Severity: critical File: xen-hypervisor-4.3-amd Justification: breaks the whole system Dear Maintainer, Installation is a minimal system designed only to get dom0 working. The following are the uncommented GRUB commands GRUB_DEFAULT=0 GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`

Hello everyone, I just put together a brand new system, and I''m getting the following when I try to start a domU: > [ 1902.049066] xend[12924]: segfault at b9ff6cd8 ip 00007f36c474afe1 sp 00007f36b9ff6af8 error 4 in libxenguest.so.4.0.0[7f36c4730000+24000] This is on an AMD CPU with the AVX instructions, and I already have this in my grub.cfg: > multiboot /xen-4.1.2.gz

Hello, I have problems running Xen (from Debian 7, i386 userspace) on Asus P3-AE5 system (M2V-TVM board) with Athlon 64 3000+ CPU (AM2, 1.8GHz). In short, Xen is not accessible from amd64 Linux kernels but works fine with 686 kernels. Long version: xen-system-i386 (4.1.4-3+deb7u1) works fine with linux-image-3.2.0-4-686-pae xen-system-amd64 (4.1.4-3+deb7u1) works fine with

Good evening everyone, I am attempting to compile Xen 4.2.1 from source on Ubuntu 12.10 and cannot for the life of me figure out what I am doing wrong. This is the script I wrote that I am running on a brand new install from ubuntu-12.10-server-amd64.iso apt-get update apt-get -y upgrade apt-get -y dist-upgrade reboot (uname -r returns back 3.5.0-23-generic) apt-get install -y build-essential

Hi, Thanks for your answer. During the Debian jessie installation, I had a problem at grub step. The os-prober part was stuck : grub was at 66 % (os-prober tried to browse all the VM on LVM partitions) After more than 15 minutes, os-prober seems to be stuck, so I rebooted the server. I had to boot in rescue mode, then, reinstalled grub and modified it to add

Hello, Similar to others I have freezeups on the system, it is consistent with high IO load. If the system runs (even with multiple) XenU it does not happen. But I can consistently force the situation to occur. Running 4 dd processes dumping 20GB each on a LVM/mdadm soft RAID5 volume it consistenly crashes in a DomU. Running without XEN I do not see the problem at all - (e.g. after about 3TB of

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9 Severity: grave Justification: renders package unusable Hi, I was running Debian Wheezy (amd64) and xen-hypervisor 4.1 on a Dell PowerEdge R720. Xen was working fine. Xen was configured with LVM Now, I'm trying Debian Jessie (amd64) and I have a strange problem. After booting, Xen seems to be working : /etc/init.d/xen status ? xen.service

Is there any way for unprivileged guests to map each others memory without grant tables? Now that the pressure is off for me to support SMP internally, I''d like to switch back to using -testing. Thanks. -Kip _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel