similar to: Problem with MTU > 1500, ifconfig segmentation fault

Hi, The recent (changeset 7700) switch to use the architecture specific skbuff allocation routine breaks with very large MTU sizes. The below patch raises the MAX_SKBUFF_ORDER to 3. Could this be applied to make it the default? Thanks, Phil Signed-Off-by: Philip Auld <pauld@egenera.com> diff -r 136b2d20dc81 linux-2.6-xen-sparse/arch/xen/kernel/skbuff.c ---

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=395 The guest domain crashed during the routine daily tests that I ran. Machine: IBM ThinkCentre, 1GB of RAM with FC3 based setup. Xen build, PAE enabled using changeset: 7701:abbe3df33774 [root@thinkcentre-dom0 xen-unstable.hg]# cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 15 model : 3

Hello, I have Ubuntu installed as a domU on the debian dom0, and connect via VNC in dom0. This is great for doing installs, and seeing the console output. However the VNC session doesn''t seem to keep the active connection during a domU reboot. Has anyone got this working? If so, how? -- John _______________________________________________ Xen-users mailing list

Hi Folks, I need some large chunk of physical memory, so I allocate it early using alloc_bootmem_low_pages and use it later (akin to bigphysarea patch). The trouble I am having is the following. Suppose the virtual address for the memory area is 0xc14d6000. After xen_create_contiguous_region call, I do a virt_to_bus and the bus address comes out to be 0x18000000. So far so good. However,

At OLS we had a couple of "Xen Mini Summit" sessions. Although there weren''t any formal minutes, here''s a rough summary of what we discussed/concluded. Status as of 24 July 2005 ========================= Summary: We have a couple of annoying bugs, but things are coming together nicely. x86_32p (PAE 16GB) and x86_64 ports are close to being feature complete with

Hi all, this patch series enables xen-swiotlb on arm and arm64. It has been heavily reworked compared to the previous versions in order to achieve better performances and to address review comments. We are not using dma_mark_clean to ensure coherency anymore. We call the platform implementation of map_page and unmap_page. We assume that dom0 has been mapped 1:1 (physical address == machine

Hi, Is there a reason that the allocate_empty_lowmem_region() function in hypervisor.c is only available in Domain 0. It is only included if CONFIG_XEN_PHYSDEV_ACCESS is defined, however, when I remove this it seems to work fine in DomUs. Thanks, Ross _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Running with Xen option dom0_mem=6G and kernel option mem=8G, I would have expected that I would see the system with a 2G balloon right after boot. However, the balloon is empty. Briefly looking at this, it would seem to me that, with all pages being reserved when the system starts and only the populated ones getting the reserved status cleared in __free_pages_bootmem(), the condition to put pages

During boot of dom0, I get the following. Box is remote, so I''m now waiting for proxy power button pusher ;-) tg3 init fails doing dma_alloc_coherent (I assume this is from tg3_init_one -> tg3_test_dma -> pci_alloc_consistent -> dma_alloc_coherent). Looks like an issue with the amount of memory in dom0. Is this known? thanks, -chris root (hd0,0) Filesystem type is ext2fs,

Hi all, this little series removes the last swiotlb API exposed to modules. Diffstat: arch/x86/include/asm/xen/swiotlb-xen.h | 6 ------ arch/x86/kernel/pci-dma.c | 28 ++++------------------------ drivers/gpu/drm/nouveau/nouveau_ttm.c | 10 +++------- drivers/pci/xen-pcifront.c | 6 ------ kernel/dma/swiotlb.c | 1 - 5 files changed, 7

Hello, I''ve hit known problem with dynamic memory management - memory fragmentation... This dynamic memory management basically does xl mem-set to balance memory. After some time of running system, xen memory is so fragmented that it is impossible to start new VM with PCI device. Sometimes it crashes during boot (no 64MB contiguous memory for SWIOTLB), or later - eg. iwlagn cannot

Hi, I have a FreeBSD 4.8 box connected to the net which until recently hasn't had any problems. Today DNS lookups mysteriously stopped working (the box has tinydns & dnscache installed to handle dns requests). I noticed some strange things while checking the problem with tcpdump. Tcpdump appears not to show any traffic whatsoever on either my external interface or internal lan interface,

I''m new to openvpn and maybe I should be asking on openvpn''s list... But I read the tutorial: http://www.shorewall.net/OPENVPN.html#id2452626 and saw the following: " On System A: ifconfig 192.168.99.1 192.168.99.2 " I don''t understand the reason for using these "virual" IPs. For instance, I configured openvpn on my peers so that the IPs on the

>Submitter-Id: current-users >Originator: Jason Hellenthal >Organization: >Confidential: no >Synopsis: ifconfig(8) fails to set MTU on multiple interfaces. >Severity: non-critical >Priority: high >Category: kern >Class: sw-bug >Release: FreeBSD 8.3-STABLE i386 >Environment: System: FreeBSD disbatch.DataIX.local 8.3-STABLE FreeBSD 8.3-STABLE #23 r238498: Sun Jul

Hi, Just thought I'd mention that I spent a while battling with tinc today. I had quite a weird behaviour - in routing mode, tinc would come up fine on both hosts, but pinging hosta from hostb wouldn't work until hosta pinged hostb. I've used an earlier version of tinc before in a different environment with no problems, and vaguely remembered a more complicated tinc-up script, so I

I just made one of my 4.x remote servers inaccessible and just tested it on my 5.x laptop, and it does the same thing ... not sure if this is considered a 'desirable' effect, or a but ... but ... 'ifconfig <device> -alias' will wipe out all IPs on the device: mobile# ifconfig -a lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 inet 127.0.0.1 netmask

Hello, when going mobile and scanning lots of APs, the old and no longer reachable APs don't get flushed from the list. That means, the list can only grow. Thus, I currently have a list of 17 APs, yet none of them is even remotely reachable. I already tried up/down'ing the interface and reloading the firmware, yet no change. Wouldn't such a feature be useful? Ulrich Spoerlein --

wiki name: HavardSorli Page for update : https://wiki.centos.org/FAQ/CentOS7 some notes / comments to: FAQ "7. What have you done with ifconfig/netstat?" "no longer install the net-utils package" I am not 100% sure, but I think "net-utils" is the wrong package name. I have checked Centos 4.9 and 7.2, ifconfig is part of the net-tools package # rpm -ql net-tools

I cannot run ifconfig even with su. Is this available as only an added package or something? Thanks for any help. -Brad

I don't have ifconfig on my new installation of CentOS 5.6, but it is on my server in the cloud. What package contains it? Thanks, John -- John J. Boyer; President, Chief Software Developer Abilitiessoft, Inc. http://www.abilitiessoft.com Madison, Wisconsin USA Developing software for people with disabilities