Open guoyanzhang0817 opened 5 years ago
This version is not maintained anymore because it does not support TLS 1.2 and not compatible with the latest Virtualbox. Can you try using https://github.com/ArchiveTeam/Ubuntu-Warrior instead? People have reported that will work in VMware successfully.
This version is not maintained anymore because it does not support TLS 1.2 and not compatible with the latest Virtualbox. Can you try using https://github.com/ArchiveTeam/Ubuntu-Warrior instead? People have reported that will work in VMware successfully. Can you help me see what's wrong with my partition statement? I'm on an empty virtual machine. d-i partman-auto/disk string /dev/sda d-i partman-auto/method string regular d-i partman-auto/choose-recipe string atomic d-i partman-partitioning/confirm_write_new_label boolean true d-i partman/choose_partition string finish d-i partman/confirm boolean true d-i partman/confirm_nooverwrite boolean true
Sorry, I am not familiar with Debian preseeding or VMware. Can you explain what you are trying to do exactly? Is there a reason why you want to use this version of the Warrior instead of the newer one?
Sorry, I am not familiar with Debian preseeding or VMware. Can you explain what you are trying to do exactly? Is there a reason why you want to use this version of the Warrior instead of the newer one?
now,I built a PXE server, and edited preseed.cfg. I want to test if the PXE server can be used, but I just have one pc, so I used the vmware as the PXE client, but it still failed.
The preseed is intended to be used in Virtualbox to build a virtual machine appliance so there is specific hard disk configuration defined in build-vm.sh
that it will use. It is not intended to be used directly on physical hardware or PXE. Is there a reason why you want to PXE boot from this preseed? I recommend to boot from a OS supporting Docker containers such as CoreOS and then have the OS install the dockerfile.
The preseed is intended to be used in Virtualbox to build a virtual machine appliance so there is specific hard disk configuration defined in
build-vm.sh
that it will use. It is not intended to be used directly on physical hardware or PXE. Is there a reason why you want to PXE boot from this preseed? I recommend to boot from a OS supporting Docker containers such as CoreOS and then have the OS install the dockerfile.
I followed your (https://github.com/ArchiveTeam/warrior-preseed) and still prompt "no root file system". guoyanzhang@bogon:~/github$ cat build-vm.sh
VMNAME="debian9.6-vm" INSTALL_ISO="debian-9.6.0-amd64-netinst.iso"
VBoxManage createvm --name $VMNAME --ostype Linux_64 --register VBoxManage modifyvm $VMNAME \ --memory 400 \ --vram 1 \ --acpi on \ --ioapic on \ --cpus 1 \ --rtcuseutc on \ --cpuhotplug off \ --pae on \ --hwvirtex on \ --nestedpaging on \ --largepages off \ --accelerate3d off \ --nic1 nat \ --nictype1 82540EM \ --natpf1 "Web interface,tcp,127.0.0.1,8001,,8001" \ --audio none \ --clipboard disabled \ --usb off \ --usbehci off \ --mouse ps2 \ --keyboard ps2 \ --biosbootmenu menuonly
VBoxManage storagectl $VMNAME --name "SATA Controller" --add sata VBoxManage createhd --filename ${VMNAME}.vdi --size 61440 VBoxManage storageattach $VMNAME \ --storagectl "SATA Controller" \ --port 0 --device 0 --type hdd \ --medium archiveteam-warrior-3-sys.vdi
build-vm.sh didn't use what you did six years ago.Because the script runs and prompts for errors in some options, I used the one year ago you recommended to me. I don't use debian6 either. I use debian9.6. when I boot up virtualbox and press "ESC", run auto url ...., a little while. The interface prompts "no root file system". why? ISO version issue? build-vm.sh issue?
Sorry, I can't help fix this without a good reason because the scripts are obsolete and designed for older Debian and Virtualbox. Please, please tell me why you want to use this preseed when there are more modern alternatives.
I want to use preseed on vmware, but partitions always fail, prompting that there is no root file system