Pages

Showing posts with label VirtualBox. Show all posts
Showing posts with label VirtualBox. Show all posts

Sunday, July 30, 2023

Fedora 39 : Resize the vdi file for VirtualBox.

NOTE : This will not change the size of the Linux partition. I tried to change the size in fedora linux with specific commands, but I didn't succeed. The distribution I tried was a server without a graphical environment so I could also try gparted software.
It is good to use the Fedora Linux distribution for tests and feedback to the Fedora team on a hardware system, such as an old laptop.
For quick tests and to save time, you can also install a version on VirtualBox, and sometimes you may not have enough space on the virtual disk.
You can try a tool called VBoxManage with this command to your named vdi file:
VBoxManage modifyhd "C:\Fedora\Fedora.vdi" --resize 81920
You may receive this error:
0%...VBOX_E_NOT_SUPPORTED
VBoxManage.exe: error: Failed to resize medium
VBoxManage.exe: error: Resizing to new size 190756945920 is not yet supported for medium 'C:\Fedora\Fedora.vdi'
VBoxManage.exe: error: Details: code VBOX_E_NOT_SUPPORTED (0x80bb0009), component MediumWrap, interface IMedium
VBoxManage.exe: error: Context: "enum RTEXITCODE __cdecl handleModifyMedium(struct HandlerArg *)" at line 937 of
file VBoxManageDisk.cpp
You can check information about the vdi file on which the Fedora distribution is installed with this command:
VBoxManage showhdinfo "C:\Fedora\Fedora.vdi"
Make a clone of the vdi file.
VBoxManage clonehd "C:\Fedora\Fedora.vdi" "C:\Fedora\Fedoracloned.vdi"
...
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Clone medium created in format 'VDI'. UUID: ...
Resize this cloned virtual disk with this command:
VBoxManage modifyhd "C:\Users\catafest\VirtualBox VMs\Fedora\Fedoracloned.vdi" --resize 30000
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%

Thursday, July 20, 2023

Fedora 39 : Solve copy-paste in VirtualBox.

I'm using the Fedora 39 Linux distribution on an HP laptop and I also have it installed on a VirtualBox on my work computer. Today I will show you a way to solve copy paste between content on your computer and Fedora 39 on VirtualBox.
This requires Virtual Box to be set to bridge network as in the attached image.
The next step is to have the Cockpit tool installed, see instructions here.
Open the web address created by the Cockpit tool in your computer browser and go to the Terminal section. This way you will be able to transfer text content using your computer's browser and not the VirtualBox settings.
See the next image:

Tuesday, May 23, 2023

Fedora 39 : Share folder with Fedora on VirtualBox.

To share a folder called share between the Windows operating system and Fedora 39 using VirtualBox, the folder must be created and added to the settings as follows:
In VirtualBox, make sure the Fedora virtual machine is stopped.
Select the Fedora virtual machine in the list of virtual machines and click the "Settings" button on the top bar of the VirtualBox window.
In the "Settings" window of the virtual machine, select the "Shared Folders" category.
Click the "+" button on the right to add a new shared folder.
In the "Add Share" window, specify the following details:
Folder Path: Browse to and select the C:\share folder on the host.
Folder Name: You can enter a name for the shared folder.
Select the access options you want, such as "Auto-mount" and "Make Permanent".
Click the "OK" button to save the settings.
Start the Fedora virtual machine and on the Fedora virtual machine, open a terminal and run the following command to mount the shared folder:
You can see the file test.txt is visible in Fedora.

Thursday, January 25, 2018

Fedora 27 : About storage management and LVM.

About storage management offering flexibility like a complex task and LVM contributes to this complexity.
If you have seen incorrect usage of LVM many times and users are often neither aware of the possibilities or alternatives for the particular storage stacks.
If you use a VirtualBox software the you can increase the vdi file:
VBoxManage modifyhd fedora.vdi --resize 30960
About LVM
The wikipedia tell us:
In Linux, Logical Volume Manager is a device mapper target that provides logical volume management for the Linux kernel. Most modern Linux distributions are LVM-aware to the point of being able to have their root file systems on a logical volume.

To create a LVM, we need to run through the following steps:
  • Select the physical storage devices for LVM 
  • Create the Volume Group from Physical Volumes 
  • Create Logical Volumes from Volume Group
All linux commands start in this case with lv and pv .
If you want to have a good management of storage then one most common task is :

The resize the PV (Physical Volume) with all free space.

All LVM commands start with lv so try to find all into your terminal by type lv ant then use keys TAB+TAB.
To resize the LVM use this commands:
$sudo su 
# pvs
  PV         VG              Fmt  Attr PSize   PFree
...
# lvdisplay
  --- Logical volume ---
  LV Path                /dev/fedora/root
  LV Name                
...
# lvextend -l+100%FREE /dev/fedora/root 
...
# df -Th
If you use Volume group on LVM then you need to use:
vgextend your_vg /dev/sda...

Saturday, July 15, 2017

Fedora 26 server 64bit - tested VM.

I install Fedora 26 into simple way with the Netinstall Image (64-bit 484MB ) from here.
I used the last VirtualBox to test this Fedora 26 net image.
It took some time because the hardware used is without the dedicated video card and an I5 processor. The basic idea of this test was to see how to install it.
It's interesting to watch: the number of packages installed per time unit, the startup steps for the base installation and the work environment.
The other steps are more complex because it matters what you want to do with this linux. It depends on how much you want to adapt it to your hardware machine or whether you will make it a web server, ftp, sftp or a graphics rendering or video rendering station.
The total installation time in VirtualBox was one hour and seven minutes. The resulting video was modified by changing the number of frames for a faster viewing, (from 72 to 172).
The reason was the first steps to install Fedora not to set a specific linux server.
I use linux command under root account to install and set Fedora 26:
#dnf update 
#dnf upgrade 
#dnf grouplist 
#dnf grouplist -v
#dnf install @cinnamon-desktop
#dnf -y group install "Fedora Workstation"
#dnf install setroubleshoot
#sestatus
#sestatus -v
#getenforce
#dnf install clamtk
#echo "exec /usr/bin/cinnamon-session" >> ~/.xinitrc
#startx
Let's see the record video of this test install :

Tuesday, September 13, 2016

Fedora 25 Alpha - VirtualBox and packer.

NOTE: This project tutorial is not finish. After I install the Fedora and reboot the installation has restart with default iso file. Need to fix this issue.

Today I tested Fedora 25 Alpha under Windows 10 with VirtualBox from Oracle and packer.
The VirtualBox can be found here.
The packer software can be found here.
Because I used Vagrant from here used the default folder vagrant to test Fedora 25 Alpha , see tree command:

C:\HashiCorp\Vagrant\bin>tree
Folder PATH listing
Volume serial number is 0000003D 9A67:3A80
C:.
├───.vagrant
│   └───machines
│       └───default
│           └───virtualbox
├───build
│   └───Fedora_25_Alpha
└───packer_cache
I install VirtualBox the last version and I put packer.exe into bin folder.
 The packer use two config files:
- the packer.config - looks for %APPDATA%/packer.config ,if the file doesn't exist, then Packer ignores it and just uses the default configuration;
- the packer.json -I used fedora25alpha.json file for settings.
My fedora25alpha.json file come with this settings:
{ "variables": { "iso_location": "https://download.fedoraproject.org/pub/fedora/linux/releases/test/25_Alpha/Workstation/x86_64/iso", "harddisk_size": "40960", "vm_name": "Fedora_25_Alpha", "outputfile": "Fedora_25_Alpha.box", "compression": "6" }, "builders": [{ "vm_name": "{{user `vm_name`}}", "output_directory": "build/{{user `vm_name`}}", "type": "virtualbox-iso", "virtualbox_version_file": ".vbox_version", "headless": false, "guest_os_type": "Fedora_64", "hard_drive_interface": "sata", "disk_size": "{{user `harddisk_size`}}", "iso_url": "{{user `iso_location`}}/Fedora-Workstation-netinst-x86_64-25-Alpha-1.2.iso", "iso_checksum": "ba181dd271cda2ac709a4327258683bc3b6e5635a0fd69548dc6f957d25927d9", "iso_checksum_type": "sha256", "boot_wait": "12s", "http_directory": "http", "guest_additions_path": "VBoxGuestAdditions_{{.Version}}.iso", "ssh_username": "vagrant", "ssh_password": "vagrant", "ssh_port": 22, "ssh_wait_timeout": "10000s", "vboxmanage": [ ["modifyvm", "{{.Name}}", "--memory", "1024"], ["modifyvm", "{{.Name}}", "--cpus", "1"] ], "shutdown_command": "echo 'vagrant'|sudo -S /sbin/halt -h -p" }], "post-processors": [ { "type": "vagrant", "output": "build/{{user `outputfile`}}", "compression_level": "{{user `compression`}}" } ] } I add also the path to the Windows enviroment with powershell:
$env:PACKER_LOG=1
$env:PACKER_LOG_PATH="packerlog.txt"
You can also use the set command to do that.
The next step is to use two commands for packer.
First command will validate your settings and the last command will start the virtualization process:
packer validate fedora25alpha.json
packer build fedora25alpha.json

The output of this is virtual running of Fedora 25 Alpha.

Tuesday, August 9, 2016

How to deal with your Fedora distro and Windows 10 using usb stick.

Today I will told about one great way to test it Fedora distro with one usb stick and Windows 10.
I don't want to make one video tutorial because you will try to follow the images and is more good for you to understend the steps.
This method of getting your usb stick with your Fedora distro and deal under your Windows 10 to make this goal:
Upload your Fedora into your usb stick then make copy of usb stick (vmdk file) to run under Windows 10.
First the usb stick will need to have a good size great than 15 or 20GB (with autopartition).
Also usb device legacy support 2.0 and great will be very good.
My CPU is this and working well: >wmic cpu get caption Caption Intel64 Family 6 Model 58 Stepping 9
I have a NVIDIA GPU , but fedora come with default nouveau graphics device driver.
You can use some tutorial to replace it with proprietary Nvidia/ATI video driver.
I used the VirtualBox with usb enable and this allow me to select the usb stick for Fedora instalation, see:
 
I download the Fedoara 24 distro with a light enviroment.You can use MATE , XFCE enviroments.
Take a look also to Fedora Spins.
To make this easy for you - just get the Fedora Live from here.
If you want to used Fedora 24 with 64-bit or any 64-bit Linux and Windows then select under your BIOS to enable options: Intel (R) Virtualization Technology was enabled and Intel (R) VT-d Feature was also enabled.
Select from Windows the Hyper-V option to be enable for 64-bit Live CD with Windows Key + q to open the Search box and typed in: turn windows features.
The window will be come with one Hyper-V checkbox and then you need to select that enabled.
Make new Virtual Machine with Fedora select from settings your video , memory and check the usb driver. Select from Storage - Controller IDE and check enable LiveCD and upload the .iso file image with the OpenDialog.
Your virtual hard disk will be great than 8 Gb and also can be any type.
This just allow you to run Fedora Live CD to install Fedora into your usb stick.
After install you can create one virtual file from your usb stick. C:\Program Files\Oracle\VirtualBox>VBoxManage.exe internalcommands createrawvmdk -filename C:\usb.vmdk -rawdisk \\.\PhysicalDrive1 RAW host disk access VMDK file C:\usb.vmdk created successfully.
This file can be run under VirtualBox also by using create one new virtual machine with usb stick vmdk file.
Make same settings with usb checked and video and memory.
When you need to select the virtual hard disk then select: Use existing hard disk and select your .vmdk file.
To be able to deal with fedora the you can read also this:Installation_Guide.
This will show how to customize all into Fedora distro.

Thursday, June 23, 2016

Upgrading Fedora distro to Fedora 24.

I make this video tutorial about how to upgrading Fedora distro.
# dnf upgrade --refresh 
# dnf install dnf-plugin-system-upgrade 
# dnf system-upgrade download --releasever=24 
# dnf system-upgrade reboot
If all is done then into your linux... type reboot command like into my video:
# reboot

Thursday, May 26, 2016

Fedora 24 alpha - VirtualBox and FreeCAD software.


Today I tested the FreeCAD under Fedora 24 alpha with VirtualBox.
First I update my system using the standard updater for your desktop:

sudo dnf update --refresh
sudo dnf install dnf-plugin-system-upgrade
dnf install freecad freecad-data


About this software the official webpage told us: FreeCAD is a parametric 3D modeler made primarily to design real-life objects of any size. Parametric modeling allows you to easily modify your design by going back into your model history and changing its parameters. FreeCAD is open-source and highly customizable, scriptable and extensible.

Is working well and you can read more from here.
I have some problems with sound under my VirtualBox.

I think something block the memory when I try to make some screenshot.
See this video:


Saturday, April 30, 2016

New version of Virtual Box software.


The date of this release was: 2016-04-28.
This software has been released like a maintenance release.
This software come with this changes.

Friday, April 29, 2016

News: About Fedora 24 Alpha.


I used Fedora 24 Alpha because is a great operating system.
First I will share some links with more info about Fedora 24 Alpha.

If you want to read about the release schedule for Fedora 24, then take a look at Fedora 24 - Releases Schedule.
What is Alpha a release?
A release contains all the features of Fedora editions in a form that anyone can help test.
Where you can get it?
You can read and download this release from here.
...now about testing the new Fedora 24.
You can make one Live DVD /CD or just use one virtual machine software like Virtual Box.
The Virtual Box software from Oracle it is an x86 virtualization software not just for Linux distro but also for any operating system. You find many tutorials about how to do that.

So, I install the new Fedora 24 Alpha and I test it. 
First, the team makes a great job with this features:
- not many packages ;
- the speed of my VirtualBox is good with virtual Hyper-V, enabled 3D - Acceleration and 64 Mb on video was under 1 min to see the first screen and almost 2 min to start the GUI install on a hard disk with my old Intel(R) Pentium(R) CPU 2117U has 1.80GHz;
- the design starts with a beautiful wallpaper; 
- the installation GUI is simple;
- the size on disk to make the first update I used is 15Gb - is too much for me;
- the initial size of the installation comes with ~6Gb;
- the last Virtual Box version 5.0.18 r106667 come with full network settings so you can use the internet to update Fedora packages and use the browser.
I don't use this distro with Live DVD or install on my HDD but you can do that...
I want to make this article more complex but is enough for now ...

Regards. 

 

Saturday, July 11, 2015

The VirtualBox and Fedora 22.



I used the VirtualBox - version 4.3.28.xxxx and Fedora Linux 22.
The main reason was to test how fast it's the  Fedora 22 over VirtualBox.
And the answer was just a few minutes.
My hardware come with NVIDIA video card Geforce 740M, CPU: 2117U -1.80Ghz and 4Gb RAM.
I used Fedora-Workstation-netinst-x86_64-22.iso.
This will take some time when you install because this will use the network to download all packages.
You need to set one new  Linux os over Virtual Box and make this setting:
Load the Fedora .iso and start it with Show/Play button.

After that, if all packages are on your computer then the next step comes with unloading the .iso file and select the virtual drive.
This can be seen under Controler: SATA. Let all settings under Network: NAT.
Start it with Show button and you will see working well.


I like very much the new Virtual Box and Fedora also, because it's fast (~ 1 min) and I don't need to start another hardware to test my linux stuff.