search for: ckt9

...ARGET_DIR I've tried setting `-o debug=0xfff` but I get no debug info at all. Is it expected behaviour that filesystem shares get into a broken state after restoring a snapshot? If it's of any relevance, here's some more context: * The host is running Debian Jessie with Linux 3.16.7-ckt9-3~deb8u1, Libvirt 1.2.9, QEMU 2.1. * The guest is Tails (https://tails.boum.org) which is Debian Wheezy with Linux 3.16.7-ckt9-3. I doubt it matters since I tested this ~two years ago, and got (IIRC) the exact same results. Cheers!

...c_t10dif crct10dif_generic ehci_pci uhci_hcd crct10dif_pclmul ata_piix ehci_hcd scsi_transport_fc libata megaraid_sas scsi_tgt usbcore scsi_mod usb_common crct10dif_common bnx2 May 26 09:18:59 servername kernel: [31526.937917] CPU: 0 PID: 1311 Comm: snmpd Not tainted 3.16.0-4-amd64 #1 Debian 3.16.7-ckt9-3~deb8u1 May 26 09:18:59 servername kernel: [31526.937922] Hardware name: Dell Inc. PowerEdge R610/0F0XJ6, BIOS 6.4.0 07/23/2013 May 26 09:18:59 servername kernel: [31526.937927] task: ffff88008a86a250 ti: ffff880002b4c000 task.ti: ffff880002b4c000 May 26 09:18:59 servername kernel: [31526.937931]...

...--fs=ext4 --bridge=br-lan --dhcp --dist=jessie ~# apt-cache policy xen-hypervisor-4.4-amd64 xen-hypervisor-4.4-amd64: Install? : 4.4.1-9 Candidat : 4.4.1-9 ~# apt-cache policy xen-tools xen-tools: Install? : 4.5-1 Candidat : 4.5-1 # uname -a Linux hv0 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt9-3~deb8u1 (2015-04-24) x86_64 GNU/Linux The domU boot : root at hv0:~# xl create /etc/xen/test0.cfg && xl console test0 Parsing config from /etc/xen/test0.cfg [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup s...

...smbc_getFunctionRead to read from a Microsoft DFS share. Before each 64k read there are a QUERY_PATH_INFO and a GET_DFS_REFERRAL which slow down the transmission. Is there a way to query these only once at the beginning of the transmission and cache it? system: 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt9-3~deb8u1 (2015-04-24) x86_64 GNU/Linux lib: libsmbclient:amd64 2:4.1.17+dfsg-2 amd64 shared library for communication with SMB/CIFS servers libsmbclient-dev:amd64 2:4.1.17+dfsg-2 amd64 development files for libsmbclient smbclient 2...

...d>] ? system_call_fast_compare_end+0x10/0x15 I tried with xen-hypervisor 4.5 with no luck. I tried with linux-image-4.xxxx from unstable with no luck. xl info command output : host : jango release : 3.16.0-4-amd64 version : #1 SMP Debian 3.16.7-ckt9-3~deb8u1 (2015-04-24) machine : x86_64 nr_cpus : 32 max_cpu_id : 47 nr_nodes : 2 cores_per_socket : 8 threads_per_core : 2 cpu_mhz : 2400 hw_caps : bfebfbff:2c100800:00000000:00003f00:17bee3ff:00000000...

...amd64 Xenstore communications library for Xen ii xen-hypervisor-4.4-amd64 4.4.1-9 amd64 Xen Hypervisor on AMD64 ii xen-hypervisor-4.5-amd64 4.5.0-1 amd64 Xen Hypervisor on AMD64 ii xen-linux-system-3.16.0-4-amd64 3.16.7-ckt9-3 amd64 Xen system with Linux 3.16 on 64-bit PCs (meta-package) ii xen-linux-system-4.0.0-1-amd64 4.0.2-1 amd64 Xen system with Linux 4.0 on 64-bit PCs (meta-package) ii xen-linux-system-amd64 4.0+64 amd64 Xen system with Linux for 64-bit PCs (me...

Package: xen-hypervisor-4.5-amd64_4.5.0-1_amd64.deb Version: 4.5.0-1 Hi, I use xen with sdl, not with vnc. When I boot on xen-hypervisor-4.4-amd64, everything is fine. With Debian or Windows 8.1 I have a good display, But when I choose at boot, the xen-hypervisor-4.5-amd64, things go wrong. If I launch a xen Debian, I get some blur effect on the display. And when I launch a xen Windows8.1,

...file or directory [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt9-2 (2015-04-13) [ 0.000000] Command line: panic=1 console=ttyS0 udevtimeout=6000 no_timer_check acpi=off printk.time=1 cgroup_disable=memory root=/dev/sdb selinux=0 guestfs_verbose=1 TERM=xterm [ 0.000000] e820: BIOS-provided physical RAM map: [ 0.000000] BIOS-e820: [mem 0x0000000000000000-...

Greetings, I am suffering of several weird errors which show randomly and make me suspect some concurrency issue. Libguestfs version is 1.28.1, linux kernel 3.16, libvirt 1.2.9 and qemu 2.1. What I'm trying to do is comparing the disk state at two different point of a guest execution. Disk snapshots are taken through libvirt in different moments (I am aware of caching issue), from such