Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Keep getting to the point in attached screen grab and hangs.
Quote:
root@xeon:/home/jogl# qemu-system-x86_64 -hda c.hd -drive format=raw,media=cdrom,readonly,file=/home/jogl/Downloads/freeDos/FD13-LiveCD/FD13LIVE.iso -boot d
WARNING: Image format was not specified for 'c.hd' and probing guessed raw.
Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
Specify the 'raw' format explicitly to remove the restrictions.
I don't know if the "raw c.hd" is the problem but I have been going through the qemu manual and cannot figure how to get rid of that error.
Would I be able to use a serial port with Dosbox? Ie.: the ttyS0 port with a DB9 connector.
What I am trying to do is get some files off of a very old (Compaq Contura) laptop. The floppy does not work on the laptop, but it has Laplink installed. So if I can just get a DOS anything working with a serial port I'm hoping that I can transfer files from the lappy.
Qemu and VirtualBox are not mutually exclusive. Though ease of use is relative. I find Qemu preferable to VirtualBox but have no recent experience with any form of DOS. If I recall correctly, the last time I did use a DOS was to use GRUB to boot into FreeDOS directly. So if you have a spare machine to boot, using GRUB might be another option. Though Qemu should boot FreeDOS with the right options.
Just in case you were still interested installing qemu-kvm I reformatted your original command:
Code:
qemu-system-x86_64 -hda c.hd -drive format=raw,media=cdrom,readonly,file=/home/jogl/Downloads/freeDos/FD13-LiveCD/FD13LIVE.iso -boot d
Using I was able to start the installation and the error that you got before did not appear.
Code:
qemu-system-x86_64 -blockdev driver=raw,node-name=disk,file.driver=file,file.filename=c.hd -drive format=raw,media=cdrom,readonly,file=/home/jogl/Downloads/freeDos/FD13-LiveCD/FD13LIVE.iso -boot d
On a side note, I ran the command as you listed earlier and although I got the error message that you got, the installation did start. I am using Debian. It is version 10. I am using the i3 window manager. I don't know if that may have any bearing on the situation though.
Well, even the official FreeDOS documentation seems to be out of date, with a few deprecated Qemu options, but it boots FreeDOS nevertheless, at least for now:
Code:
qemu-img create freedos.img 150M
after the giant drive is allocated, the following is mostly copied from the FreeDOS page linked above,
Then you'll have to boot three times. Once to partition the drive space, once to format the drive and install FreeDOS, then once again to actually boot from the designated drive space. The last choice can go with the options above and wait for the boot menu it presents, or by else change the one line from -boot d to -boot c once FreeDOS has been successfully installed.
I took a quick look at trying to use mount on the disk image, but made no progress to get past its complaints about wrong fs type, bad option, bad superblock, missing codepage or helper program, or whatever.
However, clicking on the FreeDOS disk image in the file manager seems to give positive results. So at least on a graphical system, like a desktop, you can get at your DOS files that way.
I am sorry, I didn't look at your screenshot from before. You seem to be using the wrong menu item on the install page. You need to choose Install to Harddisk. Like you said something simple being overlooked
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.