similar to: domU on v3.2 is not booting

Hey, I've a problem with an ext3 filesystem and don't know how to fix it or find the failure :( The Hardware: Tyan mainboard, AMD Athlon CPU, ARECA ARC-1120 RaidController Raid5 with 400GB Seagate HD's, 756 MB Ram, other harddisks for system, network and avm isdn controller. Couse of the filesystem problems I run memtest and found one bad memory module which I replaced yet. The

Hi all, I downloaded the xen 3.3.0 and now testing the pci pass-through with the NIC. Using late binding, the pci slot 0000:08:01.0 is assigned to pciback. But pci related xm commands are not working. For eg: linux-242:/home/xen-3.3.0 # xm pci-list-assignable-devices Unexpected error: <type ''exceptions.OSError''> Please report to

I recently came across an enormous cluster of x86 clone machines running fedora core 1 (2.4.24) which have typically all intel or amd have VIA IDE chipsets. They frequently experience corrupted journals rendering the ext3 partition in read-only mode. More important than recovering the filesystem, I am interested in finding the root of the problem. The common hardware that all of these

Hi all, I have been using Xen for a couple of weeks now. So far, I could run domU with direct access to the NIC using late binding method. This way NIC is giving a throughput close to that of native linux system. Now I would like to know whether Xen supports the direct assignment of PCIe virtual function to domU. If yes, how could I do this? Thanks and Regards, Masroor

Hi all, In a bridged setup, how we can set a large mtu(4k) for the interface on domU? Eventhough ''ifconfig eth4 mtu 4000'' command worked in my case, whether it reflect on the actual device? Moreover I can''t set mtu for the bridge as 4k. Setting any value above 1500 mtu shows the following error, xen-152:~ # ifconfig xenbr1 mtu 4000 SIOCSIFMTU: Invalid argument So

We have several large ext3 file system partitions. One of them sets itself to read-only after getting journel problems. I understand that's a good thing, but obviously I need to correct the problem so that it will stop locking itself. Here are some details; OS is Redhat EL4 x86_64 running on a SunFire v40z, kernel is 2.6.9-42.0.2.ELsmp. The disk storage in question is external, via

The system stopped responding to ssh but still responded to ping. The logs showed this error: (its long) Feb 4 00:08:08 server1 kernel: gdmgreeter: page allocation failure. order:0, mode:0x50 Feb 4 00:08:08 server1 kernel: [<c014f863>] __alloc_pages+0x28b/0x29d Feb 4 00:08:08 server1 kernel: [<c014b70f>] find_or_create_page+0x39/0x72 Feb 4 00:08:08 server1 kernel:

I did a complete clean install of CentOS 5 from CD yesterday. I took the default selinux configuration. After that I ran yum update and found 600 plus updates and installs. I let it go to do the updates and during that process I saw a large number of issues in the selinux troubleshooter. I also see these kinds of things in /var/log/messages: **Unmatched Entries** (Only first 10 out of 49031

A mysql database file was copied over to a new box running Fedora Core 1. The kernel was updated to the latest Fedora release. However mysqld complains about corrupted tables. The kernel was then updated to 2.6.5 mysqld still complains about corrupted tables. Hardware: Dual PIII 800. 3ware RAID dmesg: ... ... ... EXT3-fs error (device sdb1): ext3_free_blocks: Freeing blocks not in

Hi all, my domU guests stop booting in my new 3.2 (kernel 2.6.18.8) xen installation when run perfectly in my other 3.0.2 (2.6.16) xen server. whe i start the domU with "xm create" i get these messages: Using config file "./debian.4-0.xen3.cfg". Started domain debian.4-0 IP route cache hash table entries: 4096 (order: 2, 16384 bytes) TCP established hash table

I wanted to install Xen on 32bit processor with 8GB RAM. I am running Debian on it. The general Kernel can only address ~4GB of RAM. So, Is it necessary to install BigMEM kernel so that all the memory get addressed? And then install xen kernel. Or ?? Suggestions welcome. Thanks, gorkhe _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

Hello, Please consider including upstream commit 08e34eb14fe4cfd934b5c169a7682a969457c4ea in the next v3.2.y release. It was included upstream as of v3.3-rc1. It has been tested and confirmed to resolve http://bugs.launchpad.net/bugs/1154608 . commit 08e34eb14fe4cfd934b5c169a7682a969457c4ea Author: Laszlo Ersek <lersek at redhat.com> Date: Sun Dec 11 01:48:59 2011 +0000

Hello, Please consider including upstream commit 08e34eb14fe4cfd934b5c169a7682a969457c4ea in the next v3.2.y release. It was included upstream as of v3.3-rc1. It has been tested and confirmed to resolve http://bugs.launchpad.net/bugs/1154608 . commit 08e34eb14fe4cfd934b5c169a7682a969457c4ea Author: Laszlo Ersek <lersek at redhat.com> Date: Sun Dec 11 01:48:59 2011 +0000

I am migrating the llvm/clang derived compiler for our processor from the v3.1 to v3.2 codebase. This has mostly gone well except that instruction latency scheduling is no longer happening. The people who implemented this previously sub-classed 'ScheduleDAGInstrs' and implemented the virtual methods 'computeLatency' and 'computeOperandLatency'. However, these methods

On Apr 26, 2013, at 3:53 AM, Martin J. O'Riordan <Martin.ORiordan at movidius.com> wrote: > I am migrating the llvm/clang derived compiler for our processor from the > v3.1 to v3.2 codebase. This has mostly gone well except that instruction > latency scheduling is no longer happening. > > The people who implemented this previously sub-classed 'ScheduleDAGInstrs'

I recently tried to update my Aastra 57i to version 3.2 and ran into a problem. It won't properly register and says "contact mismatch". I added "sip contact matching: 2" to aastra.cfg, but that didn't help. When I look at the SIP trace, but I see is the Aastra sending a REGISTER and Asterisk replying with the 401. The phone then sends the REGISTER again, this time

I had a busy mailserver fail on me the other day. Below is what was printed in dmesg. We first suspected a hardware failure (raid controller or something else), so we moved the drives to another (identical hardware) machine and ran fsck. Fsck complained ("short read while reading inode") and asked if I wanted to ignore and rewrite (which I did). After booting up again, the problem came

Hi, I'm using ext3 filesystems in embedded devices (storage is on 512Mb or 1Gb CF cards). A typical development cycle would see the filesystem created on the desktop PC running linux 2.4 (eg. RedHat 9). The CF card would be installed in the hardware and linux 2.4 (eg. Montavista Pro 3.1, on PPC) would boot from the CF. Recently I tried a linux 2.6 desktop (CentOS) for the same task and

My old machine started getting a bit flaky, so I have kicked it off my desk, but still wanted to get some nouveau bugs fixed on it. (In fact it's easier now that I can reboot it more easily.) So I put a spare old hard drive on it and rebuilt it, but I'm having a heck of a time getting it working. Whenever it tries to load the nouveau module, it blows up. What's funny is that it

Below is a kernel dump that I just got. This is a fresh new install of centos 5.1 on NVIDIA gigabyte MB-GA-M61P-S3. nothing extra has been added. I have not tried the irqpoll but I am surprised to get this. Also the machine keeps running just hod this show on the console... Any ideas??? Jerry Jan 8 05:20:00 localhost kernel: irq 169: nobody cared (try booting with the "irqpoll"