loopyloo (06-07-18)
Interesting...might be a difference in Desktop environment thing, using XFCE the output I get has the bottom line of this:
resources: irq:36 memory:e0000000-efffffff ioport:3000(size=256) memory:f0300000-f033ffff memory:c0000-dffff
Bit in brackets I believe is the memory size of mine.
As you probably discovered when looking there are many different ways of getting this info.
If you want a GUI program that gives all sorts of system information install the program HardInfo, some systems come with it already installed but have it named differently in the Menu, on mine (MX-17) it's called System Profiler and Benchmark.
To see if it's installed try entering hardinfo in Terminal.
I found Virtualbox too problematic over the years & now use QEMU instead.
loopyloo (06-07-18)
Yes that's one thing HardInfo lacks is showing the video memory size.
QEMU itself is Terminal only but there's a GUI available called AQEMU, which is set up very similar to how Virtualbox's GUI works.
I usually only install software through Synaptic and I think I just selected the AQEMU entry & it auto selected everything else it needed for the full QEMU with a GUI.
loopyloo (06-07-18)
could be red wine
loopyloo (06-07-18)
I have no idea, don't remember seeing that when I first set mine up.
I started using the Terminal instead of the GUI because I wanted to learn that method.
I've never actually set up an OS with the GUI, only used it to convert a HDD image I'd already created & run that.
There seems to be a fairly complete guide to using the GUI but it's in German.
Using the Chromuim browser it's just a matter of right clicking the page > Translate to English, haven't used Firefox for ages so not sure if it has that function or maybe it'll need a translater add-on.
If you still have dramas yell out & I'll put together the steps I do to create a virtual drive, run an OS's ISO and once installed, run the installed system all using the Terminal.
loopyloo (08-07-18)
Iv'e installed qemu, aqemu, virtual-manager and a few other things as I saw a couple of youtube vids about it but having trouble getting it to create the virtual drive and getting the windows dvd to run.
Just can't seem to figure out the settings.
eg at the moment when trying to run the windows install dvd (in virt-manager) it's trying to boot from the hdd not the dvd.
Last edited by loopyloo; 08-07-18 at 12:43 PM.
Here's how I get them working via Terminal in QEMU, just change your username, locations etc. etc. in the commands to suit.
First thing is create the virtual drive QEMU will use for the desired OS, which is a .img file
Choose the folder you want it in, then open Terminal & 'cd' to that desired folder.
On my setup to keep them all together I use the hidden .aqemu folder inside my home folder but the location can be anywhere, username I log in with is 'home'.
So to cd to there in Terminal cd /home/home/.aqemu hit Enter.
Next is the command to create the .img file, it can also be named whatever you want, I usually name them the same as the OS I'm installing to make it easier to keep track of things.
In this instance I'm using the iso for the MidnightBSD 64-bit operating system which I renamed to mbsd.iso.
sudo qemu-img create -f qcow2 mbsd.img 10G
The 10G is the size of the virtual drive, that can be any size you want so long as it's large enough for the system you want's install.
It won't initially show as 10 GB when created in the folder, QEMU expands this file as needed up to a maximum of the size specified.
Once created next step is boot the .iso.
My mbsd.iso file is located in my home folder, so to run it it's:
sudo qemu-system-x86_64 -m 2048 -boot d -enable-kvm -smp 2 -net nic -net user -hda mbsd.img -cdrom /home/home/mbsd.iso
Some of those options explained:
-m 2048 = amount of RAM to use, half what my system has.
-smp 2 = number of CPU cores to use.
-net nic -net user = this will enable an ethernet internet connection by default.
-hda mbsd.img = path for the virtual hard drive which will be used, in this case the .img file created earlier.
-cdrom /home/home/mbsd.iso = tells QEMU to boot the file mbsd.iso from the location /home/home.
More options can be found searching the web etc..
Once it's up and running just go through the install process as usual.
To run the installed OS from the virtual HD instead of again running the iso file, remove the -cdrom option.
sudo qemu-system-x86_64 -m 2048 -boot d -enable-kvm -smp 2 -net nic -net user -hda mbsd.img
Once again 'cd' Terminal to the location of that .img file before entering the command.
The above was for the x86_64 architecture but there are many others available, enter ls /usr/bin | grep qemu-system* in Terminal to see the other options.
If for example you wanted to use i386 architecture use:
sudo qemu-system-i386 -m 2048 -boot d -enable-kvm -smp 2 -net nic -net user -hda mbsd.img
If you want QEMU to boot a cd/dvd from the disk drive then after the .img is created it's:
sudo qemu-system-x86_64 -m 2048 -boot d -enable-kvm -smp 2 -net nic -net user -hda mbsd.img -cdrom /dev/cdrom
All the commands above will work without sudo but I found with both Win7 & Antix Linux installs the network connections/internet wouldn't work unless I ran them all using sudo.
I haven't had time to figure out how to get USB devices recognised by the guest OS via a command though apparently it's possible, when I tried I saw the same as you previously, the host OS mounted them & they weren't recognised by the QEMU guest OS.
So in a nutshell:
Cd Terminal to the desired location:
cd /home/home/.aqemu
Create the virtual drive:
sudo qemu-img create -f qcow2 mbsd.img 10G
Run the iso:
sudo qemu-system-x86_64 -m 2048 -boot d -enable-kvm -smp 2 -net nic -net user -hda mbsd.img -cdrom /home/home/mbsd.iso
After installation run the installed system:
sudo qemu-system-x86_64 -m 2048 -boot d -enable-kvm -smp 2 -net nic -net user -hda mbsd.img
Last edited by Jma; 09-07-18 at 01:13 AM. Reason: typo
loopyloo (09-07-18)
No probs.
Mine is dual core and it works ok with -smp 2, from memory I think the guide I originally found had it set at 3 on a 4 core machine, changed mine to 2 and left it at that for several different OS's without any hassles so far.
Memory I find makes more of a difference, memory too high in the guest slows the host to a crawl.
I wonder if we've reached the stage where the thread title could be reversed IE can instead of can't ?
well done
loopyloo (10-07-18)
Well the linux installation itself goes smoothly (for me at least) with the difficulties arising when you try to get software written for a different OS to run in it which requires a lot of workarounds if it's at all possible to do. This thread inspired me to work harder on getting some of my troublesome hardware (printers and scanners) working with ultimate success which is very satisfying.
Maybe we should ask admin to set up a Linux subforum.
I'm out of my mind, but feel free to leave a message...
loopyloo (10-07-18)
good idea
loopyloo (11-07-18)
What's the best PLC sim for linux ?
Bookmarks