/build/static/layout/Breadcrumb_cap_w.png

Chaining Windows and Linux deployment

Before implementing this you need to have a working fedora repository and a kickstart.cfg file to automate the Linux deployment.

Then this what we do :

First partitioning the hard drive, we make 4 partitions, two for windows, one for linux system and one for swap :

REM lecteur cd = R:\
select vol 0
assign letter=r
REM Nettoyage du disque dur
select disk 0
clean
REM creation des partitions
create partition primary SIZE=8000
create partition primary SIZE=20000
create partition primary SIZE=32000
create partition primary
REM formatage
select partition 1
format FS=FAT32 LABEL=SWAP QUICK
Assign Letter=S
select partition 2
format FS=FAT32 LABEL=LINUX QUICK
offline volume
select partition 3
format FS=NTFS LABEL=Donnees QUICK
assign letter=D
select partition 4
format FS=NTFS LABEL=Windows quick
assign letter=C
active
Then we copy the necesssary files in the s: partition

We get vboot from https://sourceforge.net/p/vdfuse/wiki/_discuss/thread/7c0b2059/7731/attachment/vboot.zip (vdfuse on sourceforge) which give us a working grub for windows.

the zip file is decompress at s:\vboot and we copy s:\vboot\vbootldr.mbr at s:\vbootldr.mbr

then we modify the grub.conf file, this section :

menuentry "Install Linux" {
    set gfxpayload=keep
    linux (hd0,1)/vmlinuz ro inst.stage2=http://your.repo.server/fedora/releases/22/Server/x86_64/os/ ip=dhcp ks=http://your.repo.server/ks22.cfg net.ifnames=0 biosdevname=0
    initrd (hd0,1)/initrd.img
}
After that take the vmlinuz and initrd.img files from the correspondig fedora serveur http://mirrors.ircam.fr/pub/fedora/linux/releases/22/Server/x86_64/os/images/pxeboot/

Next step is to modify the windows boot :

SET UID={b5c3a250-0a09-11e5-8432-080027fe3cd6}
cd /d c:\windows\system32
BCDEDIT /CREATE %UID% /D "Deploiement Linux" /APPLICATION BOOTSECTOR
BCDEDIT /SET %UID% DEVICE PARTITION=S:
BCDEDIT /SET %UID% path \vboot\vbootldr.mbr
BCDEDIT /DISPLAYORDER %UID% /ADDLAST
BCDEDIT /bootsequence %UID%
BCDEDIT /TIMEOUT 0

All these steps recap in our post-install script :

Rem script Linux Deployment
 
rem copying files for grub
 
ROBOCOPY "%~dp0vboot" "s:\vboot" /MIR
COPY "%~dp0vboot\vbootldr" "s:\" /Y
COPY "%~dp0initrd.img" "s:\" /Y
COPY "%~dp0vmlinuz" "s:\" /Y
 
rem BCD modification
 
SET UID={b5c3a250-0a09-11e5-8432-080027fe3cd6}
cd /d c:\windows\system32
BCDEDIT /CREATE %UID% /D "Deploiement Linux" /APPLICATION BOOTSECTOR
BCDEDIT /SET %UID% DEVICE PARTITION=S:
BCDEDIT /SET %UID% path \vboot\vbootldr.mbr
BCDEDIT /DISPLAYORDER %UID% /ADDLAST
BCDEDIT /bootsequence %UID%
BCDEDIT /TIMEOUT 0

On the next boot, you should start your linux deployment.

Hope this will help.

The vboot is a free software, maybe Dell could integrate it in k2000 future release with the support for a fedora repo and help the developer !

Comments

  • This is very cool. Out of curiosity are using this for hobbyist stuff or you are pushing this into production? - ajstein 6 years ago
    • This is our production script and is works like a charme ! - gwir 6 years ago
  • Very happy to have this method for dual boot Windows/ linux
    But don't andertand : "%~dp0vboot" "s:\vboot"
    how to put vboot to S: ???
    please help me

    thank - ENPCAssistance 5 years ago
    • The S: partition is the future swap for linux.
      In batch script %~dp0 mean script Drive letter and Path. I use robocopy to copy the vboot directory and it's content to s:\, /MIR option is for MIRror. - gwir 5 years ago
  • I try to make same configuration but it's not work :
    this line : ROBOCOPY "%~dp0kickstart" S:\ /E
    where I can download it ? and for what??
    Thank for a possible message. - ENPCAssistance 5 years ago
    • It's a line I forgot to delete, used to copy the kickstart file from the post install zip instead of taking it from a web server. I edit the post to correct it. - gwir 5 years ago
This post is locked

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ