similar to: gentoo domU halting

Hello all, Today after a reboot of my server, I encountered the following error: > # xm console hackbloc > xenconsole: Could not read tty from store: No such file or directory I have not changed anything and have never run into this problem before. I have no idea what to do here, I mounted the image and checked that /dev/tty* were still there and they are. xm show lists the server as

I appologize if this was already answered somwhere on http://www.voip-info.org/wiki-Asterisk, I'm sure it probably is. And if you wish to just point me to a link that would be appreciated. I am very new to asterisk and unix all around, so these questions may sound rather ignorant. First being, how do I setup asterisk to point to another asterisk server and make all the lines which should

Hi all,whats the root password for Asterisk@home db, to login from the consel? Thx Q -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20050526/8912c6f4/attachment.htm

Supermicro X7DWN+, XEON 5410, Centos 5.2, Xen 3.2.1 At what looks like random times network traffic over xen bridge stops working, the only way I found to fix it is a reboot. This sometimes takes 10 min, other times it may be up for 10 days. This happened with default xen that comes with RedHat EL 5.2 as well as a default install of Fedora 8. Any ideas? ><> Nathan Stratton

I have started to receive a lot of positive response for the Asterisk@Home project. For those of you unfamiliar with this project the goal of Asterisk@Home is to make a full featured version of Asterisk very easy to install. We have created a 1 step .iso that installs RHEL (RedHat Enterprise Linux) and Asterisk. It includes a web GUI that allows easy editing of the Asterisk Config files.

I often get the message: EXT2-fs warning (device hda6): ext2_fill_super: mounting ext3 filesystem as ext2 I have googled for a reason and a way to solve this - but not found something I could use. Maybe somebody here konws what to do? best regards keld

In the bang head and repeat mode here. The live usb partition is /dev/sda1 Reboot / power on It auto mounts the /dev/sda2 as ext4 on /mnt/disc/sda2 $ umount /mnt/disc/sda2 $ mkdir /root/foo $ mke2fs /dev/sda2 $ mount /dev/sda2 /root/foo Kernel panic Snip from the kernel panic: ?????? list_del+0xb/0x71 cache_alloc_refill+0xf1/0x186 ext2_fill_super+0x0/0xa37 .... system_call+0x7e/0x83 --

I must profane ignorance of complicated filesystem stuff, so feel free to call me out here. Booting a root ext3 drive produces the following message at boot: kinit: trying to mount /dev/root on /root with type ext2 EXT2-fs warning (device hda3): ext2_fill_super: warning: mounting ext3 filesystem as ext2 When remounted rw by init, everything looks fine: $ mount | grep hda3 /dev/hda3 on / type

Hi, I made an ext3 filesystem with 8kB block size: # mkfs.ext3 -T largefile -v -b 8192 /dev/md0 Warning: blocksize 8192 not usable on most systems. mke2fs 1.38 (30-Jun-2005) Filesystem label= OS type: Linux Block size=8192 (log=3) Fragment size=8192 (log=3) 148480 inodes, 18940704 blocks 947035 blocks (5.00%) reserved for the super user First data block=0 290 block groups 65528 blocks per group,

When booting a CentOS4 domU, I''m getting some errors in the /etc/sysinit file. I''ve read that some edits are required in this file, but cannot find any specific references. Has anyone seen this before? Is there a workaround? EXT2-fs warning (device sda1): ext2_fill_super: mounting ext3 filesystem as ext2 VFS: Mounted root (ext2 filesystem) readonly. Freeing unused kernel

Hi, I have a perfectly running Xen 3.0.4 installation with kernel 2.6.16-42 with PCI passthrough for my internet interface (ethernet). But with I boot my 2.6.19 xen kernel on dom0, I''m unable to have the NIC working in domU. I can see the NIC both in domU and dom0 with lspci. All other network interfaces are working correctly (ethernet in dom0 and bridges). Here is my entry in grub

I realize this is ancient history, but I am trying to compile Ver 8.1 (from the download page) using Fixed Point and am getting compile errors as follows: argument of type "celt_sig *" is incompatible with parameter of type "celt_int16 *" libcelt81_orig_DSP/libcelt celt.c line 321 1304524612394 19769 argument of type "celt_sig *" is incompatible

https://bugzilla.mindrot.org/show_bug.cgi?id=2016 openssh at ml.breakpoint.cc changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |openssh at ml.breakpoint.cc --- Comment #5 from openssh at ml.breakpoint.cc --- The link local address (fe80::) require the

Hello, I am trying to boot a FC6 domU on Xen 3.2 (compiled on a FC6 system). After compiling Xen 3.2 successfully on FC6 and making the ramdisk, I modified the conf.grub as shown below. With this, I was able to boot xen. ------------------------------ --------------------------------------------------------------------------------- # grub.conf generated by anaconda # # Note that you do not have

Remote box SNV93 (xVM kernel) 192.168.1.54 (NIC RTL8169) Attempts of ssh connection from CentOS 5.1 DomU 192.168.1.37 at SNV93 Dom0 (NIC RTL8110SC) # ssh user1@192.168.1.54 hangs .. TCPDUMP running on remote box (192.168.1.54) # tcdump -s 1600 -vv One entry generates for each ssh connection attempt. First:- 17:12:43.058821 IP (tos 0x0, ttl 64, id 19771, offset 0, flags [DF], proto TCP (6),

Hi, I found one weird thing: I heard RAMDISK is not required for domU, but it seems I have to add RAMDISK to my domU config file, otherwiese the domU will hang up when it is booting. Please see the message below, the domU booting hangs up after "Continuing..." Does anyone have any clue for this issue? BTW, xen-friendly glibc is already installed. Thanks, Liang ---Begin of domU

Versions: OS: Redhat ES Linux 3.0 Windows OS: Windows 2003 & Active Directory Samba: samba-3.0.5rc1-2_rh9.i386.rpm Kerberos: krb5-1.3.4-i686-pc-linux-gnu.tar Using Windbind: Yes Objective: Allow Samba/Linux server to authenticate off of active directory to access Samba shares. Problem: I can get to some shares, but not to the user home shares. When trying to access a user home share I

hi all I want to know wt does s_log_blocksize represent in ext2's superblock structure in memory.. Is is 1024 for 1kb block size in ext2 file system.. Also wt does s_blocksize and s_blocksize_bits members of VFS superblock represent.. BTW are there any ext2 file system specific mailing lists.. bye a Linux lover

hi, after rebooting my host, i can''t have anymore the networking: here''s my output of /etc/init.d/networking restart Reconfiguring network interfaces...SIOCSIFADDR: No such device eth0: ERROR while getting interface flags: No such device SIOCSIFNETMASK: No such device eth0: ERROR while getting interface flags: No such device Failed to bring up eth0. done. cat

On Wed, Sep 18, 2013 at 4:09 PM, Chris Valentino <chris.valentino at 1010data.com> wrote: > I upgraded from syslinux 4.x to syslinux 6.01 and am now having issues with > pxe chaining. I've tried moving up as far as 6.02-pre16, but I'm still experiencing the same problem. The original config called the next server as follows: What's the version of the first and second