Floppy in VMWare for lbu, config not loading on boot
-
- Offline
- 2 years 4 months ago
- 2015-09-03
Hi!
I am trying to set up alpine linux 3.2.3 as a VMWare Workstation 11 image.
Booting from the normal 32bit iso and using a virtual floppy disk for persistence.
I followed the VMWare guide in the wiki. Even there the mount command fails if the file system type is not specified. After specifying -t vfat it mounts alright, setup-alpine and lbu ci floppy can be performed, an archive and cache folder are created on the floppy image.
On the next boot I am back to square one, no configuration loaded from the lbu file.
Tried to format the floppy as both vfat and ext2, no luck.
/etc fstab has no entry for the floppy disk, only cdrom and usb mountpoints.
Any ideas, pointers on how to fix it or other ideas for minimal persistence of the config options?
I want to use it as a router/firewall in a virtual setup, and would like to avoid as much persistent storage as possible, plan B would probably be to have a vmdk disk image and restore it to snapshot on each boot.
Best regards
Fabian
Hi, I've the same problem with Alpine 3.2.3. After reboot floppy is not read and so the machine startup with the ISO settings and not with the configuration committed on the virtual floppy.
Is there anyone who was able to start the VM so builded?
Thanks a lot.
Greetings.
Davide
The floppy configuration load works on Alpine 2.x. For an unknown reason the most recent versions do not boot load the floppy module anymore.
Look the contents of their /proc/cmdline:
[ 2.7.7 ]
BOOT_IMAGE=/boot/grsec initrd=/boot/grsec.gz alpine_dev=cdrom:iso9660 modules=loop,squashfs,sd-mod,usb-storage,floppy,sr-mod quiet
[ 3.3.1 ]
BOOT_IMAGE=/boot/vmlinuz-grsec initrd=/boot/initramfs-grsec modloop=/boot/modloop-grsec modules=loop,squashfs,sd-mod,usb-storage quiet
Any resolution on this?
Negative.
not good, would have been great if it worked as advertised. Tried to get answer in IRC, no dice either. Sad.
I woudl recommend to create a boot disk. Make it 500MB - 1G. Then boot cdrom, use fdisk to create a single parition and make it bootable. apk add dosfsprogs and mkfs.vfat /dev/vda1 and finally you use setup-bootable /dev/vda1.
Then you have a boot disk where you can store the apkovl.
(I dont know if you get vda or sda in vmware)
thank you. I moved on to Open-E DSS Lite as I just needed an NFS server which AL was nice and light for. For Open-E, did something similar with two disks, one for boot and the other for data. I will see how it performs (has nice GUI, but I think AL also has one) and then give AL a try again.
To understand the simplest of circumstances under VMware, I have created some virtual DOS machines successfully. Now, suddenly, when I try to create a single, VMware does not recognize my floppy drive (a DOS boot floppy sit there).
While the virtual machine booting, I skip the BIOS settings of the machine. Everything looks fine. The floppy drive is the first boot device. VMware 2V0-620 Dumps
It does not appear that any configuration files in the directory program or any configuration information in the registry is clear.
The problem first appeared after I had a conflict between 2 virtual machine trying to access the same physical driver. My message appeared that said the campaign would be disabled for the virtual machine.
Improve your credibility and provide business value to your organization through VCP6-DCV certification. This industry-recognized certification confirms that you know how to manage and troubleshoot vSphere V6 infrastructures, 2V0-620 Exam Questions Answers leveraging best practices to provide a scalable and reliable virtualization platform for your business.
Just click on 2V0-621D Dumps and get accurate and more valuable 2V0-621D real exam questions and answers with best-helping study material. We provide an easy and fine way to pass this exam in the first attempt.
I can confirm this is still a problem as of the latest version. The floppy is not mounted at boot, so there are no cfg files at /media/floppy
Hi Guys,
Is there a fix for this? I have confirmed that this is still a problem and need a diskless install for VMware. Any ideas? I'm happy to do some legwork, but I would not know where to begin.
Cheers,
- Steve