search for: xenwatch

...uns (at the time of testing) a single linux-x86 domu (128MB, 1VCPU). When issuing a reboot, everything looks as expected: - domu is saved - xend is stopped - drbd stopped - lvms unmounted - md0..4 stopped and the message "rebooting now" appears, but nothing happens until "INFO: task xenwatch is blocked for 120 seconds" and "INFO: task reboot is blocked for 120 seconds" appear. A hard reset is necessary to resume. Poking around I found that waiting for things to settle after the domu has been saved helps. For this, I modified /etc/init.d/xendomains, sleeping for 2 sec...

This is actually a kernel bug not a Xen one but I don't know which kernel you were running so I won't reassign yet. In any case please can you make sure you are running the latest kernel. Also if you can try the Wheezy kernel that would be very useful. I know that upstream have fixed some deadlocks in the xenbus kernel driver since Squeeze, there's probably a good chance that this is

Hi experts I use xen-4.0.0 and dom0 is 2.6.33 and domU is 2.6.34 #lspci ............... 01:00.0 Ethernet controller: Intel Corporation Unknown device 10a7 (rev 02) 01:00.1 Ethernet controller: Intel Corporation Unknown device 10a7 (rev 02) 05:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06) 05:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit

...virtual servers xen-utils-4.0 4.0.1-1 XEN administrative tools xen-utils-common 4.0.0-1 XEN administrative tools - common files xenstore-utils 4.0.1-1 Xenstore utilities for Xen xenwatch 0.5.4-2 Virtualization utilities, mostly for Xen ~# xm info host : dom0 release : 2.6.32-5-xen-amd64 version : #1 SMP Wed Oct 20 02:22:18 UTC 2010 machine : x86_64 nr_cpus :...

...a problem with the boot sequence hanging indefinitely at "stopping system V runlevel compatibility". Here are the steps I took to get to this point: 1) installed a single boot, server version of ubuntu 11.10 (intended to be dom0) 2) apt-get install xen-hypervisor-4.1-amd64 xen-utils-4.1 xenwatch xen-tools xen-utils-common xenstore-utils 3) updated grub as follows: - changed the default boot order - added the following entries GRUB_DISABLE_OS_PROBER=true GRUB_SERIAL_COMMAND="serial --unit=0 --speed=9600 --word=8 --parity=no --stop=1" GRUB_TERMINAL="console serial" GRUB_C...

....26-2-xen-686 root=/dev/mapper/athena-root ro console=tty0 module /initrd.img-2.6.26-2-xen-686 but aparently xend it not up: # xm list Error: Unable to connect to xend: No such file or directory. Is xend running? even though: # ps -ef | grep xen root 31 2 0 17:41 ? 00:00:00 [xenwatch] root 32 2 0 17:41 ? 00:00:00 [xenbus] root 3320 1 0 17:41 ? 00:00:00 xenstored --pid-file /var/run/xenstore.pid root 3327 1 0 17:41 ? 00:00:00 xenconsoled root 3781 3727 0 17:48 pts/0 00:00:00 grep xen I searched google and I''...

...problem when I am going to detach one specific LVM partitions of Xen, so I have been trying xm destroy <domain>, lvchange -an <lvm_partition>, lvremove -f.... So I haven''t had sucess. I restarted the server with init 1 yet and nothing... I have seem two specific process started xenwatch and xenbus, but I am not sure if this processes have some action over LVM partitions + XEN. I need to know how can I remove this partition to build another xen VM, an if I need to stop the xend and xendomais services to do the detachment. Thanks so much!!!! VG Name VGxen LV UU...

...xs_reset_watches function to shutdown watches from old kernel after kexec boot. The old kernel does not unregister all watches in the shutdown path. They are still active, the double registration can not be detected by the new kernel. When the watches fire, unexpected events will arrive and the xenwatch thread will crash (jumps to NULL). An orderly reboot of a hvm guest will destroy the entire guest with all its resources (including the watches) before it is rebuilt from scratch, so the missing unregister is not an issue in that case. With this change the xenstored is instructed to wipe all acti...

Hey, I''m experiencing strange problem: non-deterministic PV domain hang, only on some machines (with fast SSD drive). I''ve tried xen-4.1.0 and xen-4.1.1 with many kernels different kernels: VM: - 2.6.38.3 xenlinux based on SUSE package - vanilla 3.0.3 - vanilla 3.1 rc2 dom0: - 2.6.38.3 xenlinux based on SUSE package - vanilla 3.1 rc2 Result always the same: sometimes VM

..._interruptible() into wait_event() into a couple of places it looks to deal with the fact that signals weren''t being blocked. This results in an idle domU showing a load-average of 2, which was messing up some work-management tools. The attached patch blocks all signals for the xenbus and xenwatch daemons, instead. Signed-off-by: John Byrne <john.l.byrne@hp.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...n-utils-4.0 4.0.1-5.4 XEN administrative tools ii xen-utils-common 4.0.0-1 XEN administrative tools - common files ii xenstore-utils 4.0.1-5.4 Xenstore utilities for Xen ii xenwatch 0.5.4-2 Virtualization utilities, mostly for Xen Any advices how to solve ? Can it be a hardware problem with RAM ? Regards Slawek

...00 00 00 00 55 48 89 e5 39 3d c6 fd 80 00 76 0b e8 df fa ff ff <0f> b7 40 1c c9 c3 89 f9 31 c0 48 c7 c2 27 e2 99 81 be db 00 00 RIP [<ffffffff8141a301>] evtchn_from_irq+0x11/0x40 RSP <ffff88004334fc98> CR2: 000000000000001c ---[ end trace 1b5f6b359343fcfe ]--- Which leads to xenwatch being stuck in D state, which then requires us to reboot the host. SysRq : Show Blocked State task PC stack pid father xenwatch D ffff880101f938c0 5056 49 2 0x00000000 ffff880101305cb8 0000000000000246 ffff8801012a0760 00000000000138c0 ffff880101305...

...he time. I''ve also searched Google and Debian as well as openSUSE resources but haven''t found any hint about my issue :-( First I''ve tried to install it as a paravirtualized guest but when the Debian installer tries to detect the disks I get this: [ 173.233735] Process xenwatch (pid: 12, threadinfo ffff88003fe04000, task ffff88003fddce20) [ 173.233746] Stack: [ 173.233752] 0000000000000001 ffff8800027ed858 ffff8800027ed800 ffff8800027ed800 [ 173.233768] <0> ffff8800027ed800 ffff8800026c11a0 ffff8800027ed858 ffff880002038000 [ 173.233788] <0> 0000000000000...

Hey Jens, Please in your spare time (if there is such a thing at a conference) pull this branch: git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/for-jens-3.10 for your v3.10 branch. Sorry for being so late with this. <blurb> It has the ''feature-max-indirect-segments'' implemented in both backend and frontend. The current problem with the backend and

...panics as follows. This patch fixes it. union skb_entry assumes sizeof(link->skb, pointer) == sizeof(list->link, unsigned). However this isn't true on ia64. So make link type unsigned long. And introduced two accesor. kernel unaligned access to 0xe0000000000000bd, ip=0xa0000001004c2ca0 xenwatch[14]: error during unaligned kernel access -1 [1] Modules linked in: Pid: 14, CPU 0, comm: xenwatch psr : 0000101008422010 ifs : 8000000000000307 ip : [<a0000001004c2ca0>] Not tainted (2.6.26-rc4xen-ia64-dirty) ip is at dev_kfree_skb_irq+0x20/0x1a0 unat: 0000000000000000 pfs...

...panics as follows. This patch fixes it. union skb_entry assumes sizeof(link->skb, pointer) == sizeof(list->link, unsigned). However this isn't true on ia64. So make link type unsigned long. And introduced two accesor. kernel unaligned access to 0xe0000000000000bd, ip=0xa0000001004c2ca0 xenwatch[14]: error during unaligned kernel access -1 [1] Modules linked in: Pid: 14, CPU 0, comm: xenwatch psr : 0000101008422010 ifs : 8000000000000307 ip : [<a0000001004c2ca0>] Not tainted (2.6.26-rc4xen-ia64-dirty) ip is at dev_kfree_skb_irq+0x20/0x1a0 unat: 0000000000000000 pfs...

...panics as follows. This patch fixes it. union skb_entry assumes sizeof(link->skb, pointer) == sizeof(list->link, unsigned). However this isn't true on ia64. So make link type unsigned long. And introduced two accesor. kernel unaligned access to 0xe0000000000000bd, ip=0xa0000001004c2ca0 xenwatch[14]: error during unaligned kernel access -1 [1] Modules linked in: Pid: 14, CPU 0, comm: xenwatch psr : 0000101008422010 ifs : 8000000000000307 ip : [<a0000001004c2ca0>] Not tainted (2.6.26-rc4xen-ia64-dirty) ip is at dev_kfree_skb_irq+0x20/0x1a0 unat: 0000000000000000 pfs...

We have a (supposedly) quite standard setup: 2 Dom0 with drbd-on-lvm and a bunch of DomU, on Quad Xeon Dell servers. We tried with both sid-based and etch-based (+ 3.1 xen hypervisor and drbd 8 from backports.org ) Dom0, and quite consistently have "kernel: invalid opcode: 0000 [1] SMP" errors which freezes Dom0 (during lasts tests a simple start-and-stop loop of 10 DomU can trigger

...t boot already which went fine). dom0 is allocated a fixed 1536M. Both host as pv guests run the same kernel, some hvm''s run a slightly older kernel (3.9 f.e.) The are quite some granttable messages in xl dmesg, i also included these and a "vmstat -m" -- Sander [54807.299791] xenwatch: page allocation failure: order:4, mode:0x10c0d0 [54807.317520] CPU: 5 PID: 54 Comm: xenwatch Not tainted 3.12.0-20131104 #1 [54807.334747] Hardware name: MSI MS-7640/890FXA-GD70 (MS-7640) , BIOS V1.8B1 09/13/2010 [54807.351990] 0000000000000000 ffff8800591a3828 ffffffff81a6a8ba 0000000000000006...

...I do "xm list" or "xm info" I get an error message that xend has not started up? root@EM:/etc# xm list Error: Unable to connect to xend: No such file or directory. Is xend running? root@EM:/etc# root@EM:/etc# ps -efw | grep xen root 88 2 0 Feb07 ? 00:00:00 [xenwatch] root 89 2 0 Feb07 ? 00:00:00 [xenbus] root 6254 1 0 Feb07 ? 00:00:00 /usr/bin/python /usr/sbin/xend start root 6255 6254 0 Feb07 ? 00:00:17 /usr/bin/python /usr/sbin/xend start root 7043 5919 0 08:55 pts/2 00:00:00 grep --color=auto xen r...