search for: bootopts

I use xen 4.0(dom0 is suse11.sp1,2.6.32 x86_64) on Dell R710 with PERC H700 RAID adapter. --Intel(R) Xeon(R) CPU E5620 @ 2.40GHz --8 CPU cores. --Memory 64G --RAID5 4.5T When I dedicated (pin) a CPU core only for dom0 use. (I specify "dom0_max_vcpus=1 dom0_vcpus_pin" options for Xen) I got dom0 kernel panic error(pin-1-5.30.bmp) When I pin 2 core to dom0, the dom0 system can boot up,

greetings does the list at this url cover *all* options or are there some hidden or newer ones by chance? http://www.centos.org/docs/4/html/rhel-ig-x8664-multi-en-4/ap-bootopts.html i am playing with CentOS 4 on some Compaq dual PIII hardware. The first unit is an 1850R with dual 500Mhz. If you need more info please let me know. it is a basic unit with raid controller and a Gig of DRAM etc. may i ask what others are putting in their "additional boot options" s...

Hi all, I am testing new kernel on a mips machine (64 bits for kernel, 32 bits userland) and I found a problem when mounting the root file system. It is an ext3 file system that is correctly mounted as read only. While booting the system remount the file system as read/write and keep starting all daemons. Moving from 2.6.26 to 2.6.30 kernel, I get this error while remounting the file system

While I was tying down a supernet to the discard interface, the box crashed on me. Its a STABLE box from June 4th. I was in zebra at the time and thought I would route a /24 to ds0 instead of to the IP on ds0 (which I had done for a number of other aggregate routes). The only other "strange" thing about the box is that ds0 is loaded via kld. I will see if I can reproduce it on a

...me=0 on the kernel boot for the installed system. PXE boot options: label c6inst-sda kernel /linux-boot/cent6-x64/vmlinuz append initrd=/linux-boot/cent6-x64/initrd.img ksdevice=bootif ip=dhcp ks=http://xx.xx.xx.xx/install/linux/ks/basic-cent6-sda.cfg ipappend 2 In kickstart: BOOTOPTS="biosdevname=0" Also in kickstart I do not specify the config for ANY network interfaces. I let anaconda pull in only the config for the boot interface from PXE. I manually configure everything else. The only thing I do to non-boot interfaces is set the DHCP and ONBOOT to no....

I did see your post. So, even though the sha256sum was perfect on the iso file and on the DVD, it failed to install. I then used a usb flash drive and booted the flash drive to do the install. It also failed. The screen image I took with my camera can be viewed at https://www.sendspace.com/file/4828ej The questions I have are: why VNC ??? VNC is a horribly insecure protocol. Why would I want

On Tue, Jun 09, 2015 at 09:16:07AM -0700, JD wrote: > The screen image I took with my camera can be viewed at > https://www.sendspace.com/file/4828ej > > The questions I have are: > why VNC ??? VNC is a horribly insecure protocol. > Why would I want someone from outside viewing my installation? > Why is the X server looking for display :1 ?? > I only have one display

Hi, I'm trying to get isolinux work with serial console; however, I fail. My means of testing is qemu -serial stdio -cdrom the.iso; when I use bootoption 'console=ttyS0', the linux kernel has no problems writing to serial and the serial output does appear in the terminal I've run qemu from, so I believe qemu is working alright in this regard. I've also had it working with

Hi all.... I had posted hte following on teh centos forums, and thought there might be additional people in here who do not browse those forum, so after 4 days I am posting over here as well (sorry for the double - but figured after 4 days it was safe to do so). Hi there.... I am trying to make a custom centos server cd that will essentially do the following: throw the disk in, boot the machine,

...t;> label c6inst-sda >> kernel /linux-boot/cent6-x64/vmlinuz >> append initrd=/linux-boot/cent6-x64/initrd.img ksdevice=bootif >> ip=dhcp ks=http://xx.xx.xx.xx/install/linux/ks/basic-cent6-sda.cfg >> ipappend 2 >> >> In kickstart: >> >> BOOTOPTS="biosdevname=0" >> >> Also in kickstart I do not specify the config for ANY network >> interfaces. >> I let anaconda pull in only the config for the boot interface from >> PXE. I >> manually configure everything else. The only thing I do to non-bo...

...> > PXE boot options: > > label c6inst-sda > kernel /linux-boot/cent6-x64/vmlinuz > append initrd=/linux-boot/cent6-x64/initrd.img ksdevice=bootif > ip=dhcp ks=http://xx.xx.xx.xx/install/linux/ks/basic-cent6-sda.cfg > ipappend 2 > > In kickstart: > > BOOTOPTS="biosdevname=0" > > Also in kickstart I do not specify the config for ANY network interfaces. > I let anaconda pull in only the config for the boot interface from PXE. I > manually configure everything else. The only thing I do to non-boot > interfaces is set the DHCP and...

I have not been able to enter the edit screen to edit the boot options and add inst.txt On 06/09/2015 10:55 AM, Jonathan Billings wrote: > On Tue, Jun 09, 2015 at 09:16:07AM -0700, JD wrote: >> The screen image I took with my camera can be viewed at >> https://www.sendspace.com/file/4828ej >> >> The questions I have are: >> why VNC ??? VNC is a horribly insecure

Hello, I'm running 6.4-PRELEASE, last built on 2008-10-05 with /usr/src updated on the same day. I had a panic that looks to me very similiar to the one described here (hence the subject): http://lists.freebsd.org/pipermail/freebsd-stable/2008-September/045405.html What caught my curiosity is the message: Unread portion of the kernel message buffer: acd0: WARNING - TEST_UNIT_READY read

All: I cvsup'ed earlier this evening and am still able to reproduce this panic at will. Command line, panic backtrace, dmesg, ldd output, and mplayer version follow. If more information is needed, just let me know. % mplayer foo.mov [a quicktime file] [plays for awhile, and then panics] # gdb -k -s /usr/obj/usr/src/sys/LICHEN/kernel.debug -e /var/crash/kernel.2 -c /var/crash/vmcore.2

Hi, I have been trying to install Centos 4.4 on my laptop with no success. I have just purchased a new Acer 5100 laptop with AMD Turion 64x2 1Gig ram 120Gig HD. I have tried the 64bit and the 32 bit versions but have the same problem with both of them. I can do the complete install but when the computer reboot it will hang on the hardware detection on the network right after where it says

Hello folks, I have a panic at shutdown related to FUSE. #0 doadump (textdump=<value optimized out>) at pcpu.h:234 234 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt full #0 doadump (textdump=<value optimized out>) at pcpu.h:234 No locals. #1 0xffffffff8090d9a6 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:449 _ep = (struct

Hi, I've encountered a strange problem while using FreeBSD 6.0 for our local mirror (mirror.math.uni-bielefeld.de) and thus is providing access via ftp, http, rsync and cvsup (all local and remote). The system crashes periodically with a kernel panic (panic: sbdrop). The uptimes between two crashes are going from a few hours to a few weeks. The system is a i386, Intel Pentium 4 based with

...cent6-x64/vmlinuz >>>> append initrd=/linux-boot/cent6-x64/initrd.img ksdevice=bootif >>>> ip=dhcp ks=http://xx.xx.xx.xx/install/linux/ks/basic-cent6-sda.cfg >>>> ipappend 2 >>>> >>>> In kickstart: >>>> >>>> BOOTOPTS="biosdevname=0" >>>> >>>> Also in kickstart I do not specify the config for ANY network >>>> interfaces. >>>> I let anaconda pull in only the config for the boot interface from >>>> PXE. >>>> I >>>> ma...

Xen 3.4 xen-unstable.hg from yesterday with debian etch on 64bit arch Intel/Lenovo Q35 Mainboard with VT-d enabled Bootoptions iommu=1 vtd=1 pci.backhide for a PCI-E nvidia graphiccard xm dmesg Error messages includes: [VT-D] iommu.c: 1694:d32767 iommu: mapping reserved region failed [VT-D] iommu.c: 1542:d0 intel_iommu_add_device: context mapping failed If i try to start my HVM by xm create

<overly trimmed> On 02/25/2015 01:56 PM, Ashley M. Kirchner wrote: > Ok, so some of this now works, but I'm still having problems. With the > bootif option, the system now correctly configures and uses the same > interface to get its kickstart file. However, when the system is done and > boots up, the interfaces are still messed up. So this is what I have in the >