similar to: where is xen_blkback xen_netback.ko source code?

Dear R users, I see a graph (shown athttps://cid-c486ebef16722625.photos.live.com/self.aspx/%e6%88%91%e5%96%9c%e6%ac%a2%e7%9a%84%e8%8a%b1/untitled.bmp) in a published paper, which is very informative and clear. But I don't know what type the graph is. It looks like a sactter plot but has the points with the same y values are seperate.. I really aprreciate it if someone can tell

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

Hello, I''m facing a rather strange problem with the netback interface. My setup involves a netvm, which has some physical network interfaces assigned, and a client VM where a net front is running (exposed as eth0) and which is connected to that netvm (via vif42.0 interface, as seen in the netvm on the dumps below). Now, the netvm has two physical network interfaces assigned: 1) A

On Mon, Jan 22, 2018 at 10:38 PM, Nathan March <nathan at gt.net> wrote: > Just a heads up that I'm seeing major stability problems on these builds. > Didn't have console capture setup unfortunately, but have seen my test > hypervisor hard lock twice over the weekend. > > This is with xpti being used, rather than the shim. Thanks for the heads-up. It's been

After an S3 host resume, I''m seeing: [48002.772629] ACPI: Low-level resume complete [48002.772802] PM: Restoring platform NVS memory [48002.776143] xen_acpi_processor: Uploading Xen processor PM info [48002.776691] ------------[ cut here ]------------ [48002.776712] WARNING: CPU: 0 PID: 10235 at drivers/base/syscore.c:104 syscore_resume+0x9a/0xe0() [48002.776751] Interrupts enabled after

Is there any problem moving to 4.9.31? This contains upstream commits f2e767bb5d6ee0d9 for mpt3sas and 69861e0a52f87333 for dom0 memory mappings. I am also trying to build a debuginfo package but it's not correct. Specifically I'm able to get vmlinux but the .debug files for modules are stripped, which isn't right. Does anyone know how to fix this? I'm also not sure how

On Mon, 17 Jul 2017, Johnny Hughes wrote: > Are the testing kernels (kernel-4.9.37-29.el7 and kernel-4.9.37-29.el6, > with the one config file change) working for everyone: > > (turn off: CONFIG_IO_STRICT_DEVMEM) Hello. Maybe it's not the most appropriate thread or time, but I have been signalling it before: 4.9.* kernels do not work well for me any more (and for other people

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

Since moving from 4.4 to 4.6, I've been seeing an increasing number of stability issues on our hypervisors. I'm not clear if there's a singular root cause here, or if I'm dealing with multiple bugs. One of the more common ones I've seen, is a VM on shutdown will remain in the null state and a kernel bug is thrown: xen001 log # xl list Name

Hi Michael: Sorry to brother. But I''ve been suffered this issue quite a long time. My test environment is 2.6.32.36 + xen 4.0.1 + bnx2, 2.3. Also cpu idle is disabled in grub. Grub info: title Red Hat Enterprise Linux Server (2.6.32.36xen) kernel /xen-4.0.1.gz iommu=off x2apic=off console=com1,vga com1=115200,8n1 noreboot cpuidle=0 cpufreq=none

Dear all, I have sent this problem earlier but maybe its not detail, here I try to write more detail. I hope anybody can help me to point out the problem. First of all I used Ubuntu 12.04 x64 both for domain0 and domainU with modification to run under xen hypervisor and work with remus. I follow and configured the remus with this notes

Hi Wei, I ran into the following problem when trying to boot another guest after less than a day of uptime. (the system started 15 guests at 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

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

Hello we see the same with debian Wheezy. Apr 16 16:02:25 hypervisor3 kernel: [2441115.664216] vif vif-17-0: vif17.0: Frag is bigger than frame. Apr 16 16:02:25 hypervisor3 kernel: [2441115.664267] vif vif-17-0: vif17.0: fatal error; disabling device Apr 16 16:02:25 hypervisor3 kernel: [2441115.675667] BUG: unable to handle kernel NULL pointer dereference at 00000000000008b8 Apr 16 16:02:25

Starting udev: Wait timeout. Will continue in the background.[FAILED] so slowly. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Starting udev: Wait timeout. Will continue in the background.[FAILED] so slowly. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hello CentOS Xen Heroes, Yesterday, I have installed testing kernel 4.9.23-26.el6.x86_64 from virt-xen-testing repo. It crashed today morning. Hardware is a pretty ancient, testing machine (CO6 PV guests only), but had no problems yet. It was stable on 4.9*, including testing 4.9.15-22.el6.x86_64 Console output: [59826.069427] general protection fault: 0000 [#1] SMP [59826.069463] Modules

> Thanks for the heads-up. It's been running through XenServer's tests > as well as the XenProject's "osstest" -- I haven't heard of any > additional issues, but I'll ask. Looks like I can reproduce this pretty easily, this happened upon ssh'ing into the server while I had a VM migrating into it. The system goes completely unresponsive (can't even

Hi, On Tue, Jan 23, 2018 at 10:35:24AM -0800, Nathan March wrote: > > Thanks for the heads-up. It's been running through XenServer's tests > > as well as the XenProject's "osstest" -- I haven't heard of any > > additional issues, but I'll ask. > > Looks like I can reproduce this pretty easily, this happened upon ssh'ing > into the