similar to: Xen 3.0.3 troubles with a plain old ide disk.

Hi all, Im network booting initrd-2.6.9-22.EL.img from pxelinux. <snip from init script> echo Creating root device mkrootdev /dev/root umount /sys echo Mounting root filesystem mount -o defaults --ro -t ext3 /dev/root /sysroot mount -t tmpfs --bind /dev /sysroot/dev echo Switching to new root switchroot /sysroot echo UMOUNTING initrd-dev umount /initrd/dev </snip> I receive error

Hey, I''ve been trying to get the gplpv drivers working with Windows 2008 R2 64-bit on both a stock CentOS 5.8 install and CentOS 5.8 w/ Xen 4.1.2 from the gitco repos. I''m getting a BSOD shortly after boot up and it can be seen at http://techmonkeys.org/xen/ -- along with the qemu log. Has anyone had success with these drivers and Windows 2008 R2 64-bit? If so, what am I

Recently, I was able to create a workable Centos 4.4 "Live USB" on my 1G Lexar Firefly pendrive using the steps in http://linux.web.psi.ch/livecd/usbdisk.html. At the moment, it is doing its job, so I probably won't focus too much more on it. One thing that is annoying, although doesn't cause a problem is that on powerdown and reboot, the cd rom drive ejects - of course, there

Hi all, I have a Opteron-machine with the MPT SCSI-controller (Symbios 53c1030). At least in i386-mode, mkinitrd does not seem to build a usable initrd for 2.6.13.x (.3 tested) with this kernel. With 2.6.12.6 it works fine. I have not tested this in x86_64 -mode yet. The symptom is that mptbase and mptscsih load, but mptscsih does not discover any controllers nor drives, and things like

I''m struggling to get Xen to boot on a FC4 Opteron box. I''ve included the tail of the boot log below [1]. I suspect that the problems relates to the software RAID 1 root and boot partitions, and how it relates to the initrd image. The RAID volumes fail to mount. I compiled the Xen snapshot from the 23rd September, and the only change I''ve made is to enable the

Hi , I am ruuning Senmail with MailScanner on CentOS 4.4. It has updated to kernel 2.6.9-42.0.8.EL from its past kernel 2.6.9-42.0.3.EL. Now the Server can not boot up and gives the below error. mkrootdev: label / not found Mounting root filesystem mount: error 2 mouting ext3 switchroot: mount failed: 22 Kernel panic - not syncing: Attempted to kill init! But I can boot up from its

The attached patch breaks out the /dev/root device node creation from do_mounts, placing it in it's own utility (called mkrootdev). This is worthwhile, as certain setups will need the device node there to run fstype and load a proper module (or other things). No, it does not currently configure raid devices.... I didn't know if that made sense in there or not.... Let me know what you

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi I''m currently using xen-3.0.2-testing on several servers. But when xen 3.0.3 was announced I wanted to try it, of course it should have several iprovements and bugfixes, etc. I did the same steps I was previously done in order to compile xen-3.0.2, and in fact xen compiled and installed very cleanly. I created my initrd image and then I

Hello everyone. I am looking for a way to move a CentOS 4 installed production hard disk to another system (which has another hardware). The first has an nvidia sata controller (sata_nv), but the second has a via sata (sata_via). For all the rest of the hardware it can upgrade well I know, but if the sata driver is different, then the system doesn't boot because the proper driver is not

I encountered same error when use Xen3.0.2(source file) on CentOS4.2, after I downgraded to Xen2.0.7(source file), this error disappeared. now, I am using Xen2.0.7 instead of 3.0.2, it works well. --taylor -----邮件原件----- 发件人: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] 代表 xen-users-request@lists.xensource.com 发送时间: 2006年6月15日 5:24 收件人:

I hope the CentOS people don't mind me cross-posting for their input. I've just done a clean, text-mode minimal WBEL4 install on an IBM Netfinity 4500, essentially the same hardware as an xSeries 340. The install went fine but now the box will boot, run through the initrd init sequence, perform its switchroot then hang here... SELinux: Initializing. SELinux: Starting in permissive mode

Basically the issue comes down to my Volume Groups not being found by this initrd, causing good ole kernel panic. initrd-2.6.12.6-xen3_12.1_rhel4.1.img [root@xen01 lvm]# uname -a Linux xen01.inside.***.com 2.6.9-22.0.2.ELsmp #1 SMP Thu Jan 5 17:13:01 EST 2006 i686 i686 i386 GNU/Linux [root@xen01 lvm]# cat /etc/redhat-release Red Hat Enterprise Linux ES release 4 (Nahant Update 2) Everything

I used the xensource install script for RHEL4 and after trying to boot on the new kernel the system just continually rebooted. I appended a noreboot to the xen line and now i''m seeing the following... Freeing unused kernel memory: 184k freed dm_mod: no version for "struct_module" found: kernel tainted. device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel@redhat.com

I updated a C5 system to 2.6.18-406.el5 (from 404) and the kvm_intel module doesn't load anymore: # dmesg |grep kvm kvm_intel: disagrees about version of symbol struct_module anyone seeing similarities? -- LF

Quad core duo 2.4Ghz (Q6600) Kernel 2.6.18-53.1.14.el5PAE #1 SMP 4Gb RAM VirtualBox-1.5.6_28266_rhel5-1.i586.rpm The package installed OK. I did KERN_DIR=/usr/src/kernels/2.6.18-53.1.14.el5-i686 /etc/init.d/vboxdrv setup and the module compiles AOK. BUT... at modprobe time: vboxdrv: disagrees about version of symbol struct_module Am I doing something stupid? -- rgds Stephen

Hello, Some time ago, I noticed that whilst I had upgraded to Xen 3.1 (kernel 2.6.18-xen), I''d forgot to upgrade the paravirt DomU .cfg kernels from 2.6.16-xen to reflect this. So, I upgraded the DomU kernels & ran into issues with mounting devices, and the ext3 module not being available. After a bit of faffing about, I managed to sort this out and load the ext3 module.

Hi! I am trying to export a PCI device (an AVM Fritzcard PCI ISDN card...) to a domU but when starting my domU I am getting this error: "pciback pci-4-0: 22 Couldn''t locate PCI device (0000:00:06.0)! perhaps already in-use?" My system is running both debian etch in dom0 and domU... Below you can find (hopefully) all important information... Sincerely, Gaubatz Patrick

Hello, I have a computer with this sound card (from lspci): 0000:01:04.0 Multimedia audio controller: Creative Labs SB Audigy LS Alsa is installed (maybe not properly...) # cat /proc/asound/cards 0 [CA0106 ]: CA0106 - CA0106 Live! 7.1 24bit [SB0410] at 0xc800 irq 10 But I have the impression alsa is ok : :~# aplay -l **** List of PLAYBACK Hardware Devices **** card

Hello all, I just got the latest cvs snapshot and I'm trying to compile asterisk.. When I run nefeli:/usr/src/asterisk/zaptel# make clean; make linux26 Compile stops with errors... /usr/src/asterisk/zaptel/zaptel.c:6509: warning: passing argument 2 of 'class_device_create' makes pointer from integer without a cast /usr/src/asterisk/zaptel/zaptel.c:6509: warning: passing argument 3