similar to: iSCSI root on Dom0

Microsoft has their "boot" version of their iSCSI software initiator. Apparently this still requires that the network card be iSCSI Boot "enabled." Intel seems to be the only obvious company out there supporting it on their Server adapters - I was wondering if there are any thoughts/plans on implementing iSCSI Boot functionality in the HVM Boot ROM? Or maybe there''s

Hi all, Someone played with kickstart bonding with centos 6.4 ? CentOS 6.4, as upstream now support ifcae bonding in kickstart network section. I've an issue with configuring a second bonding iface in kicstart on CentOS 6.4. The first bonding (bond0) works as espected but the second is not configured during installation. I've a 6 nic server (two for "puclic" network, two for

Hi Bootmeisters, I am using gpxelinux.0 + sanboot.c32 to boot a diskless machine into Linux. I would like to use device-mapper-multipath to provide fault tolerant access to its root disk. Although I am able to do this by hardcoding the additional paths in the initrd, it would be better if the bootloader could pass the information in the iBFT (iSCSI Boot Firmware Table). However, at the

Hello All, I seem to have run into a bug with the new --bridgeslaves=<INTERFACE> option. It would seem that if I tell the bridge device to use a virtual interface (like bond0) rather than a physical interface (em1/em2) that kickstart completely barfs on it. I have provided my network section below which works fine as long as i don't enable all the bridge content. When the

Hi, I'm kickstarting a vm in ESXi 5.1. ks.cfg is on floppy, install media is ISO file. This works great as long as I don't add an additional repo, in our case it is vmware tools on one of our webservers. If I add the repo line, anaconda asks then for the used network card and indeed, switching to console the interfaces are still unconfigured. Chosing eth0 in gui continues the

Hi Folks, I'm interested in "headless" installation. If I use GRUB, then I provide arguments to the kernel of things like "headless vnc vncpassword=whoopie ip=dhcp" GRUB passes this on to ISOLinux, which manages the CD and subsequently the installation. Shouldn't I be able to do exactly the same thing with EXTLinux? I ask, because, as you might suspect, I

Hello, I want to implement a diskless xen hypervisor. The way I suppose it will work is xen booted over pxe and getting iscsi san storage to store vm images. Is solution like that usable ? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 23/02/15 08:16 PM, Steven Tardy wrote: > >> On Feb 23, 2015, at 6:34 PM, Ashley M. Kirchner >> <ashley at pcraft.com> wrote: >> >> I have a Dell server that has two built-in ethernet devices. When >> I kickstart the machine, they are correctly identified as eth0 >> and eth1 (correctly meaning they

> > We are not ready for "prime-time" though. > Using the "lpxelinux.0" file from 6.03-pre19 ... > > My RHEL5 installs, when using the "http://" for kernel, initrd and append lines, seem to be hitting some sort of parameter length limit. > The culprit seems to be the long "append" line. > > The same append line, when NOT using

Hi, after IPv6 day, I was wondering if our server were really secure... And, I know we should switch on IPv6 everywhere but... it will take some time. Usually, we disable(d) IPv6; so we are not running ip6tables. Can I start ip6tables in all cases (even if only IPv4) just to be on the safe side? On CentOS 6 servers, I use the --noipv6 in the kickstart files and I removed NetworkManager; but

Hello, I?m using virt-install to build a guest system with CentOS. The system boots up, times out with dracut-initqueue timeout and drops me into an emergency shell. If I exit the shell the install continues and I get a working machine. Any ideas? virt-install \ -n TEST \ -r 8192 \ --os-type=linux \ --disk=/vm-images/test.img,device=disk,bus=virtio,size=100,format=raw \

Using a kickstart file that stops with a curses dialog "You have multiple network devices on this system. Which one do you want to install through?" The machine being configured with PXEboot has two ethernet interfaces. What's missing from the network entries below? I'd like this install to proceed without asking which ethernet interface. PXE begins the install with DHCP, so

I tested the memdisk-acpi branch with following results: - Bochs The BIOS provides a RSDT. Available tables are RSDT, FACP, DSDT, FACS, APIC, SSDT. memdisk-acpi is able to hook the SSDT. - VMware The BIOS provides a RSDT and XSDT. Available tables are RSDT, FACP, DSDT(*), FACS(*), BOOT(*), APIC(*) and XSDT, FACP, DSDT(*), FACS(*), BOOT(*), APIC(*). Tables marked with an asterisk (*) are

Hello, This version addresses comments by Gerd and Michael: - instead of returning -EPIPE if host is not connected in the write case, just block the write if it's a blocking file and return -EAGAIN if it's non-blocking. - Removes early_console_printk after the first console is found - Adds early_put_chars fix by Fran??ois Diakhat??. It still needs a sign-off by him. Standard

Hello, This version addresses comments by Gerd and Michael: - instead of returning -EPIPE if host is not connected in the write case, just block the write if it's a blocking file and return -EAGAIN if it's non-blocking. - Removes early_console_printk after the first console is found - Adds early_put_chars fix by Fran??ois Diakhat??. It still needs a sign-off by him. Standard

From 8be8951015673d6279d7d49b0138645194317dc2 Mon Sep 17 00:00:00 2001 From: Shao Miller <shao.miller at yrdsb.edu.on.ca> Date: Wed, 9 Dec 2009 19:11:38 +0000 Subject: [PATCH] doc: document mBFT and "safe hook" --- doc/memdisk.txt | 40 ++++++++++++++++++++++++++++++++++++++++ 1 files changed, 40 insertions(+), 0 deletions(-) diff --git a/doc/memdisk.txt b/doc/memdisk.txt

Hello all, This new patchset switches over to using the control queue for port discovery so that we can stay in sync with the host for port enumeration and also don't use bitmaps to limit us to config space sizes. This changes the ABI, so it would be better to merge this for 2.6.34 so that we don't have to worry about released kernels with the older ABI. Amit Shah (7): MAINTAINERS:

Hello all, This new patchset switches over to using the control queue for port discovery so that we can stay in sync with the host for port enumeration and also don't use bitmaps to limit us to config space sizes. This changes the ABI, so it would be better to merge this for 2.6.34 so that we don't have to worry about released kernels with the older ABI. Amit Shah (7): MAINTAINERS:

Hi virt, im stumped... any help would be appreciated. I normally create my VMs like this: base="http://mirror.pnl.gov/fedora/linux/releases/20/Fedora/x86_64/os/" sudo virt-install --hvm --name $vm_name$i --ram 4000 \ --disk path=/VirtualMachines/$vm_name$i,size=30 \ --location $base -x "ks=http://xxx.os21.ks$kx" HOWEVER... I'm finding that my VMs dont boot after i

I have a remote CentOS 4 machine on a network where I can't put a DHCP or PXE server, and I want to do a complete reinstall. So what I want to do is, from the currently-running system, to invoke an installation kernel and initrd in just the same way that GRUB would, giving it a boot command line that specifies a remote kickstart file, installation tree, and other required info. It looks like