similar to: Bug#786936: xen-hypervisor-4.4-amd64: Upgrade dom0 from wheezy to jessie on Dell R610 results in dom0 unaccessible with xen_netback issue

where is the source code of xen_blkback.ko xen_netback.ko? thanks _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Decided to try out lpxelinux on a couple of Dell R610s. Both versions 5.10 and 6.03 hung on a server with fairly up-to-date BIOS (6.1.0), but work fine on another R610 with old BIOS (1.2.6). Watching the TFTP log and running tcpdump on the PXE server, I see it download pxelinux.0 (renamed from lpxelinux.0), but it never even tries to transfer anything after that succeeds. It eventually (seems

I am currently using a Dell PowerEdge server R610 with Xen 4.0 installed and the 2.6.31.13 pvops kernel. I am accessing the server console using the iDRAC KVM feature of the dell management console. Does anyone know how to configure the console option in the grub menu so that all the boot messages can be seen on the mgmt console? Currently I can view only the Xen bootup messages if I dont specify

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

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

Hi I have a Win2k(2072) client and Linux samba 2.0.5 server. The samba server works fine with WinNT4.0, Win95, Win98, Win98Se But with win2k, i get this error message when trying to browse the samba server (listing the shares) The filename, directory name or volume label syntax is incorrect!! I also tried a very basic smb.conf setup with the same problem ?? Thanks in advance Lars Jeppesen

Hello Maybe there's a bug in samba-3.0.4. The following configuration does NO longer work. It did work fine in samba-3.0.2a. I did not test samba-3.0.3 The share is no longer accessible !!! [BKHI-CC3] path = /home/BKHI-CC3 valid users = @BKHI-CC3-R, @BKHI-CC3-W write list = @BKHI-CC3-W force group = +BKHI-CC3-W create mask = 0664

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

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

Does anyone know if a PERC H200 is a real RAID controller? I'm about to build a box to CentOS 6.5 (it was Windows...) with RAID 6 on Monday, and this PE R610 has this.... I'm familiar with PERC 6 and 7s, but just dunno 'bout this one. mark

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

I get backtraces from the dom0 kernel when running a guest with networking (via netback) enabled such as the one below (there are some slight variations but the first two lines and most of the rest of the contents are the same). Michael Young BUG: sleeping function called from invalid context at mm/page_alloc.c:2190 in_atomic(): 1, irqs_disabled(): 0, pid: 0, name: swapper Pid: 0, comm:

Hoping someone else has seen this before. I have a few dozen Dell R610 systems with CentOS 5.2 that are using kernels from 5.3 and 5.4 (2.6.18-128.1.10.el5 & 2.6.18-164.6.1.el5), that at random lose layer 2 network connectivity either partially or totally. Running tcpdump on the interface reveals only ARP broadcasts, no responses. Switch reports no packets being received on the interface.

In IRC today, someone who was hitting that same IB performance ceiling that occasionally gets reported had this to say [11:50] <nissim> first, I ran fedora which is not supported by Mellanox OFED distro [11:50] <nissim> so I moved to CentOS 6.3 [11:51] <nissim> next I removed all distibution related infiniband rpms and build the latest OFED package [11:52] <nissim>

Running Centos 5.4 with KVM on a Dell R610 server and I'd like to control which of the four ethernet interfaces are used for specific tasks My ideal configuration would be eth0 - Host traffic only, no virtual guests. Used for guest mirroring and management. eth1 - NAT guest traffic only, no address for local machine and in some environments in the same zone as eth0 eth2/3 - Allocated to two

Hi folks: At work, I have an R510, and R610 and an R710 - all with the H700 PERC controller. Based on experiments, it seems like there is no way to bypass the PERC controller - it seems like one can only access the individual disks if they are set up in RAID0 each. This brings me to ask some questions: a. Is it fine (in terms of an intelligent controller coming in the way of ZFS) to have the

I've been running 3.18.25-18.el6.x86_64 + our build of xen 4.4.3-9 on one host for the last couple of weeks and have gotten several soft lockups within the last 24 hours. I am posting here first in case anyone else has experienced the same issue. Here is the first instance: sched: RT throttling activated NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] Modules linked in:

> From: Edward Ned Harvey [mailto:shill at nedharvey.com] > > I have a Dell R710 which has been flaky for some time.? It crashes about once > per week.? I have literally replaced every piece of hardware in it, and > reinstalled Sol 10u9 fresh and clean. It has been over 3 weeks now, with no crashes, and me doing everything I can to get it to crash again. So I''m going to

In case you didn't see it, the initial CentOS 6 trees have been released to QA: http://qaweb.dev.centos.org/node/81 -- Paul Heinlein <> heinlein at madboa.com <> http://www.madboa.com/

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