EDIT: Virtual Box 7.1.4

Hello, running Windows 11 Pro 23H2 64 bit version, iv'e tried with both hyper v on and off. i've installed all windows c++ redistributables. even tried to register and unregister windows installer, this is the log. https://www.mediafire.com/file/rlv57isnwiy1bv6/installer.log/file

I've been trying to get Bootcamp to run on VirtualBox but I am hitting a snag when I try to start the machine. Bootcamp works perfectly in Parallels, and from boot. But not in VirtualBox.

I have unmounted the partition. I have changed permissions on the .vmdk file and on the disk partition to 777. I have made the relevant access changes in Mac System Settings that I was prompted to do. I have run Virtual Box with root privileges .. but I always end up with an error when I try to start it.

This is the error I get in the right side of virtualbox when I start up

MacOS 15.1
Trying to run Bootcamp with Windows 10
Not sure how to check VT-x/AMD-V but I know it works in Parallels
No additions or extensions

Any thoughts??

Thanks!

 Powering VM up ...

 VM Name: Bootcamp

 VD: error

 VERR_NOT_SUPPORTED

 opening image file '/Users/Andy/bootcamp.vmdk'(VERR_NOT_SUPPORTED).

 VD: error

 VERR_NOT_SUPPORTED

 opening image file '/Users/Andy/bootcamp.vmdk'(VERR_NOT_SUPPORTED).

 Failed to open image '/Users/Andy/bootcamp.vmdk' in read-write mode (VERR_NOT_SUPPORTED).

 AHCI: Failed to attach drive to Port0(VERR_NOT_SUPPORTED).

 Result Code NS_ERROR_FAILURE(0x80004005)

 Component: ConsoleWrap

 Interface: IConsole{6ac83d89-6ee7-4e33-8ae6-b257b2e81be8}

Initially when I boot up Kali it runs very nicely. Snappy and responsive and smooth. After about 30-60 minutes it is laggy and choppy. The ram usage doesnt change, ive given it 16gb, the host has 64g. Assigned 2 cores. Hardware accelleration is on, no green turtle. Tried changing cores assigned, ram. Guest additions is installed and working. VirtualBox 7.1.4 running on Windows 11. 256mb for the video memory. I cant see a memory leak if there is one... Thanks!!

Hi everyone, I've been having this problem for some time. Virtual box once worked for me but then I don't remember how it doesn't work anymore. When I open VB the software does not open, the same for Vmware, I see the services working but the software does not open, Please give me a hand and I will be grateful.

I am running Ubuntu through VirtualBox and I am trying to interface with a software-defined radio (the USRP N210). My laptop doesn't have an ethernet port so I connected the radio to a Dell dockstation by ethernet and connected the dockstation to my laptop with USB-C. When I run commands on the command terminal to list connected devices it says no device connected. Is the issue:
A) device not being able to interface with the radio at all because of the dockstation
B) Virtual Box not having access to ethernet connections
or
C) Radio and device need their IPs configured somehow?

VirtualBox Version 6.1.50_Ubuntu r161033
on Ubuntu Ubuntu 22.04.5
with Kernel 6.8.0-48

VMs dont start (no matter if Linux or Windows guest), I don't even find a clear error message in the logs. Going back to kernel 6.8.0-45, it works again.

Anyone else have the same problem?

Edit: "Going back to kernel 6.8.0-45 ..."

I have OKD/k8s cluster on my laptop (hp dev one with kubuntu 22.04) in Virtualbox. 3 masters, 2 workers, 1 "services" node, and also DNS (bind) node and openwrt node as a router. This is all connected together with NAT Network which makes it a separate "virtual LAN". It works.

What i want to do is to add more nodes to the cluster. But i have no resources for that - almost 60 of 64GB ram is taken when cluster is up and i can't add more RAM. I would love to add some additional (portable) machine (laptop? minipc?), connect it with cable with my laptop, install VBox there, create those additional machines and connect it to this NAT Network. I already have "work" laptop with windows with 32gb ram. It would be ideal for that.

So far the only idea i have is VPN -> create server (Wireguard? OpenVPN?) in Nat Network and forward port to it in openwrt. But that will complicate my setup a lot. And i don't know how it will work with okd.

So is there easier way to do it? Like some clever bridging?

EDIT:
Currently i found some info about UDPTunnel and VDE. Yet i don't see such options under "Generic Driver".
https://forums.virtualbox.org/viewtopic.php?p=468778#p468778

I got an error code vmugfx I’m Brand new to anything code.. mlooking for a fix , or should I trash and start over

Hi! I'm studying to be a network engineer, and at my university, they wipe the computers every week. This causes a bit of an issue and wastes time because I have to keep downloading Debian and installing it on the VM each time.

I'm wondering if there’s a way to make this process smoother. Specifically, instead of just putting the Debian ISO file on my USB, is it possible to put the entire OS on the USB so I can run it directly from there? Alternatively, could I transfer the Debian OS from my USB to the existing C:/VM directory on the lab computers?

Hi, is it possible to change the physical disk UniqueID as returned by Get-PhysicalDisk | Select-Object SerialNumber,Size,UniqueId ?

When I run that command in a virtualbox VM I get "ATAVBOX HARDDISK" for all the physical drives. Which is not unique.

This does not seem to be the same as the diskpart uniqueid. Changing the diskpart disk uniqueid does not affect the uniqueid returned by Get-PhysicalDisk.

A non-uniqueid for multiple drives seems to cause some problems with Windows Storage Spaces.

VirtualBox versions: 7.0.20 and latest 6.1.

Host: Windows 10, Windows 10 IoT Enterprise LTSC 2021.

Guest: various - Windows Server 2019, WIndow Server 2022,.

VT-X/AMD-V enabled for all hosts.

Nested VT-X/AMD-V - some guests enabled, some not.

Guest Additions - some installed, some not.

This is my first ever virtual machine, I have been wanting to further my computer science degree with some penetration testing and decided to go with Kali Linux on VirtualBox. I had everything running mint about an hour ago but I ran an nmap command to start playing around with a device on my network before realizing I was running in an isolated environment. So I went back into VirtualBox and changed my VM's network setting from NAT to "Bridged Adapter." Little did I know that would blow everything up.

I've gone back and forth between those network settings to try and get my VM working again to no avail, that is the only thing I've changed so far, I don't want to mess anything up further. What it is doing currently is loading into Kali, it says "welcome to grub" then loads up a Kali OS loading screen, then keeps loading for a bit with the graphic dragon (the one with the blue highlight traversing it), then it very briefly says "My VM Name Login: _" in what looks like a full screen terminal and then that disappears and all that's left on the screen is a flashing cursor in the top left and all black. Also no inputs are read by that cursor, whenever I type anything or press enter nothing happens.

How does changing the network type destroy the entire OS of my virtual machine? Before it would just load up the OS and then give me a UI for my login and then I'd be on my desktop. Does anyone know anything about this? I've checked stack exchange and here and no one else has this specific problem.

Also, there was one instance where I had this black screen issue and was thrown into a terminal with a weird username but it was because I was loading the hardware in the wrong order but I fixed that a while ago and it is still loading the hard disk first.

I've always run Virtualbox on a PC but thought I might as well add it to my Mac also. I have a MacBook Air M1. I know a couple years ago it wasn't supported but now I see it is so I downloaded the Silicon 7.1.4 version.

When I go to create a new machine I am used to seeing Windows in the TYPE field and Windows XP in the SUB field. The only options I get are Linux and BSD and Other. How are you supposed to load the Wndows .iso?

Hello,

I'm not familiar with Ubuntu at all and i'm not sure this is even the right t place to post this. I am using Oracle virtual box on MacOS and importing Ubuntu there to use it. This is for my 4th year uni project. However, when i try to launch Ubuntu i get the following error message and I'm not sure what it means or how to fix it.

Failed to open a session for the virtual machine Ubuntu.

|| || |Callee RC:|VBOX_E_PLATFORM_ARCH_NOT_SUPPORTED (0x80bb0012)|

Any suggestions or help would be appreciated.

Edit: Host OS: MacOS Sequoia 15.1

Guest OS: Ubuntu.ova not sure the version as it was shared to me by a lecturer.

Not enabled VT-x/AMD-V

Hey guys, I must be missing something here, probably something well known with Windows virtualization, but I'm a Linux and KVM guy so bare with me.

Putting a Linux VM in my kids PC with VBox, two different distros now and the performance is pathetic, slow to boot, laggy as hell, even mouse cursor is laggy. Guest additions are installed, let's me turn up resolution but not to the right one, and overall terrible performance.

Only thing I've changed at install was the disk from vdi to qcow since that's just what I'm used to with KVM, could that be it? With KVM disk type can have a huge performance impact so not sure if its that, my my screwing around laptop (Thinkpad T560) has some VMs that run like they're on bare metal with crap graphics and 16GB ram, my kids comp has 64GB, tons more CPU cores and real graphics, let runs like compete trash. I've googled around and not coming up with much. Obviously virtualization is enabled in EFI and not sure what else Windows needs to do this right.

Windows 11 VB 7.1.4 Virtualization enabled Guest additions installed

When I restore the saved state VM, I get 7 instances of the error. Note these errors do not appear during a full startup but appear when a VM is restored from a saved state

Failed to acquire machine parameter.

Callee RC:

NS_ERROR_NOT_IMPLEMENTED (0x80004001)

After clearing the errors, the VM works just fine. Virtual Box version 7.1.4, Host Ubuntu MATE 24.04 LTS, Guest Ubuntu MATE 24.10. VT-x/AMD-V is enabled. Guest editions are installed. I have done extensive research on the internet, tried redoing the VM from scratch. Like I said, th error doesn't seem to affect the running machine. This error did not occur on the VM that was last loaded on it Ubuntu MATE 24.04. I did not upgrade from 24.04 to 24.10, and I recently upgraded (for the first time -- My guest is now Ubuntu MATE 25.04 and again it's working fine even with the errors. I have run the update Guest Editions.

Any thoughts or ideas please let me know

Screen shot of the errors in VM

I'm on Zorin17 (ubuntu22.04 based) and using virtualbox 7.1.4 r165100. When I try to start vbox with virtualbox -platform wayland, the following error was returned:

Qt WARNING: Could not find the Qt platform plugin "wayland" in ""
Qt FATAL: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: xcb.

[1]    6154 IOT instruction  virtualbox -platform wayland

Installing qt6-wayland and qt5-wayland doesn't work.

I wanna use Wayland because XWayland gave a poor support for fractional scaling, and vbox interface just became blurry under XWayland.

Is there any solution for this? thx a lot.

I am using virtualbox 7.0.10 on windows 11 and I am trying to create a virtualmachine of windows 11. I don't have VT-x/AMD-v (the software itself does not allow me to enable it). I turned off HyperV. I have not installed any guest or host additions.

I was trying to create a windows 11 virtual machine but it keeps on getting stuck on the booting screen that only says virtualbox. I turned off HyperV after researching. I bumped up the processor from 2 to 4 and gave it 4gb of ram with 80 gb storage.

I don't know what else I can do. I tried looking for solutions but could not find any in google. Can someone pls help me

SOLVED (sort of): I tried a different brand MIDI keyboard it works in my Windows guest.

------

My virtual guest Windows 10 machine software is not seeing my midi keyboard. I really want to get my midi keyboard device (m-audio keystation 49) working on my Windows guest machine.

Linux Mint 64 host is running virtualbox 7.0.20 and with a Windows 10 Home x64 guest. I have virtualization enabled in the BIOS. I have guest additions installed. I have my usb midi keyboard showing up in the footer of my virtual machine GUI after adding it to the virtual machine usb settings. I am a member of the virtualbox group on my Linux machine.

I recently upgraded VirtualBox from 7.0.20 to 7.1.4 on my Windows 10 host that runs two Windows 10 guests and an Ubuntu guest, no extension packs used. VT-x/AMD-V is on, Hyper-V is not installed.

Installation finished, fired up the VMs, updated guest additions.

The Ubuntu guest seems to be fine, but after rebooting the Windows guests the problems started. On startup I get a E_ACCESSDENIED display error message in the side bar in both of them, this one, which apparently has been known since September.

Probably related, though there is no way of knowing for sure: the graphics performance is pretty bad. I get a very noticeable (to the point where it's immensely distracting) mouse input lag and in general it looks like the display is run at 30 Hz.

One of the two guests also auto-mounts some host drives, which has been working fine for years and through lots of VB versions, but now stopped. I checked the logs, they show an error message with VERR_NET_PATH_NOT_FOUND and when I Google for it, I get exactly one search result, which is this one that indeed matches my log error messages.

After searching a bit more I found multiple reports of guest addition issues for VB 7.1.* and also noticed that I had the same thing happen to me that others reported for example here: My old 7.0.20 were still shown as being installed in Windows, alongside the new 7.1.4 version. Apparently the new version wasn't uninstalling the old one properly.

I tried uninstalling 7.1.4, rolling back to 7.0.20, installing the guest additions, then uninstalling them again (hopefully this time in a clean way), then upgrading again to 7.1.4 and install the guest additions again. Now I had a seemingly good state, with only 7.1.4 guest additions installed.

However, the problems remained, bad graphics performance, display error message, no auto-mounting.

I rolled back to 7.0.20 once again and everything is fine again, good performance, no display error message, auto-mounting working fine.

Before you ask: yes, I actually wanted to post to the VirtualBox forums I linked. Even took my time machine and traveled to the 90s to make an Oracle account where certain special characters are not allowed in the password and the mail address is deemed invalid when it contains the word "oracle" within the name part (before the "@"), lol.

....only to find that when I try to login to the VirtualBox forums with it, this ends up with "400 Bad Request - Your browser sent a request that this server could not understand." - since I couldn't find a browser from the 90s that quickly, I thought I'd rather post here now and see whether I am the only one with that experience?

I've been updating these VB installations for a long time without any issues, what's going on with the 7.1.* line now?

I am trying to run the windows 7 setup in a vm (MacBook Air M2, 2022) and every single time its getting stuck at the "windows is loading files stage" at the very start, at the end of the second time the bar fully fills. I have tried changing the hard drive size, the CPUs, the RAM and the ISO, and it just will not get past that stage, would someone please give me some advice on what to do

I am willing to pay $ to buy a much faster CPU, GPU, etc., if needed to speed up my virtualbox Windows 10 Home (Linux Mint host). I would not have to dual boot if I can have a smooth/fast virtual Windows 10 on my Linux host. What I am wondering is what are the top three things (ranked) I could do to improve performance on my virtualized Windows 10 system? Audio is critical, the main reason I am using a virtual box Windows 10 on a Linux Host; so that I can use high end music composing software and sampled instrument libraries. I simply can not use such software and instrument libraries on Linux.

My current system is a dual boot Windows and Linux Mint system, running virtual box Version 7.0.20 r163906 (Qt5.15.3) with a Windows 10 guest on Linux as the host. As I type this, now I am unsure if I have guest-additions installed on the Windows 10 guest-- I will check on that today, but beyond guest additions, what is the #1, #2 thing I can do to improve performance? A more expensive CPU? My system already has 128GB of RAM, and all my drives are internal SSD drives. My current CPU is an AMD Ryzen 9 3900X 12-core, 24-thread.

i need some help. Today i downloaded some intel drivers on my main pc, and now my vm keeps freezing every 10 seconds or so, it doesnt crash just doesnt move anything, a temp fix is changing the resolutions on the window but it comes back quickly. i already restored the pc to a state without the drivers and no help. Is there a way to restore the vm without losing any data?
im using a windows 7 64 bit image the host is a win 11, i use 4gb of ram for the vm, it doesnt take all the pc ram so i dont think thats the problem, 256 mb of vram and im not using 3d acceleration. im on virtual box 7.0.20
thanks in advantage
Edit: Found out the problem, when i downloaded docker desktop it enabled hyperv and it made Vbox run slow. Hope this helps for someone in the future

I want to start using Virtualbox, but I read that the Expansion Pack sends user data to the US government. Is that true?

Some time ago my VM (Win11 host, Rocky Linux 8 guest) started to randomly abort. Usually, I just minimize the window, do something else and then notice that it's gone. So far, I wasn't ever able to "catch" it in the act (i.e. when I'm actively interacting with VM) and VM doesn't do any tasks when it gets aborted (just some windows open).

I have 64GB RAM and I tied lowering VM RAM from 42GB to 32GB with no success. Also tried VBoxInternal/RamPreAlloc 1 option in case it was OoM issue and that didn't help.

There is nothing in the logs either (they end with "resuming" event when I resume it then there is nothing for hours until the VM is aborted).

Not sure if the issue was caused by some VBox update but it wasn't a problem at the start. Currently I'm on 7.0.20 (I had to revert from 7.1 since that's a broken mess).

Any tips on how to diagnose it and fix it?

Virtualbox version 7.1.4

Host Windows 11

Guest Debian Linux

Host Extensions installed

I have an on-board mediatek MT7922 wifi device built into the motherboard that I don't generally use on the host machine. I would like to do a complete pass-through of the device to a VM, so that the VM can use it and see all of the wifi SSIDs in the area and connect to them in the VM itself. I don't want to simply connect to an SSID on the host machine and bridge the connection... how can this be done?

-Virtualbox is 6.1 (I will update after I figure out this os issue) -Host OS: Windows 10 -Guest OS: Windows 10 -My other VMs like Ubuntu work fine. -VT-X/AMD-V is greyed out -I don't know what my HyperV setting is but I changed it recently and nothing worked so it's on or off or whatever option it's supposed to be.

Also I'm not sure about Host Extension but Guest Additions but again the VM was working perfectly normal before.

ISSUE: I haven't used the VM for a year. I have since built a new computer. There was a saved state that I could see the VM's windows 10 desktop (greyed out) but would immediately crash due to errors like GuestAdditions being missing. I relocated GuestAdditions.

Then I get a invalid display error in settings as it was set to VBoxVGA and has to be changed to VBoxSVGA. I changed the Network Adapter since it's a new PC.

I tried cloning it and going back to a previous snapshots and it just hangs on the blue windows logo screen that seems to freeze ever few seconds as loading symbol goes in circles indefinitely. I left it for a few hours and nothing. (Honestly I'm not sure if I've ever restarted the VM before today).

I don't even know how to troubleshoot from here. What else is there to try? Unfortunately I don't have the windows boot media as it was some "install windows 10 free iso" program that Microsoft released and the program no longer even launches.

here's some of the logs if that matters:

0:00:07.069310 VMSVGA3d: cap[81]=0x000000c1 {SURFACEFMT_Z_D24S8_INT}
00:00:07.069311 VMSVGA3d: cap[82]=failed rc=VERR_INVALID_PARAMETER! {SURFACEFMT_BC4_UNORM}
00:00:07.069311 VMSVGA3d: cap[83]=failed rc=VERR_INVALID_PARAMETER! {SURFACEFMT_BC5_UNORM}
00:00:07.069321 AIOMgr: Endpoints without assigned bandwidth groups:
00:00:07.069375 AIOMgr:     C:\Users\VirtualBox\Win10\Snapshots/{c6a51219-3785-4c8f-9f0c-5fef65ad9dda}.vdi
00:00:07.069381 AIOMgr:     C:\Users\VirtualBox\Win10\Snapshots/{4051ff7a-29ef-498a-8f34-d4b8078d955d}.vdi
00:00:07.069383 AIOMgr:     C:\Users\VirtualBox\Win10\Snapshots/{8d2bcc60-dfca-44b0-b52a-de47e7a9901a}.vdi
00:00:07.069386 AIOMgr:     C:\Users\VirtualBox\Win10\Snapshots/{ca149dd4-0cc9-4790-8009-dea7cc472534}.vdi
00:00:07.069388 AIOMgr:     C:\Users\VirtualBox\Win10\Win10.vdi
00:00:07.069567 Changing the VM state from 'POWERING_ON' to 'RUNNING'
00:00:07.069588 Console: Machine state changed to 'Running'
00:00:07.072036 VMMDev: Guest Log: BIOS: VirtualBox 6.1.34
00:00:07.072208 PCI: Setting up resources and interrupts
00:00:07.084074 GUI: Machine-window #0 activated
00:00:07.084271 GUI: Capturing keyboard on focus in
00:00:07.084326 GUI: Machine-view #0 focused, reason=3
00:00:07.091462 ERROR [COM]: aRC=VBOX_E_VM_ERROR (0x80bb0003) aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=-37
00:00:07.195099 PIT: mode=2 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:00:07.251664 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0 flags=0x0 origin=0,0
00:00:07.252924 VMMDev: Guest Log: CPUID EDX: 0x178bfbff
00:00:07.253436 VMMDev: Guest Log: BIOS: No PCI IDE controller, not probing IDE
00:00:07.253849 AHCI#0: Reset the HBA
00:00:07.253858 VD#0: Cancelling all active requests
00:00:07.253917 AHCI#0: Port 0 reset
00:00:07.253932 VD#0: Cancelling all active requests
00:00:07.254875 VMMDev: Guest Log: BIOS: AHCI 0-P#0: PCHS=16383/16/63 LCHS=1024/255/63 0x0000000004800000 sectors
00:00:07.254955 AHCI#0: Port 1 reset
00:00:07.257056 PIT: mode=2 count=0x48d3 (18643) - 64.00 Hz (ch=0)
00:00:07.277855 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=000000000e000000 w=640 h=480 bpp=32 cbLine=0xA00 flags=0x0 origin=0,0
00:00:07.574383 GUI: UIMachineViewNormal::resendSizeHint: Restoring guest size-hint for screen 0 to 1745x865
00:00:07.581520 GUI: 2D video acceleration is disabled
00:00:07.581726 GUI: HID LEDs sync is enabled
00:00:07.594403 GUI: Machine-window #0 deactivated
00:00:07.594421 GUI: Releasing mouse on focus out
00:00:07.594428 GUI: Releasing keyboard on focus out
00:00:07.596644 GUI: Machine-view #0 unfocused, reason=3
00:00:07.596702 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=5
00:00:09.734391 PIT: mode=2 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:00:09.734607 VMMDev: Guest Log: BIOS: Boot : bseqnr=1, bootseq=0032
00:00:09.735426 VMMDev: Guest Log: BIOS: Booting from Hard Disk...
00:00:09.736895 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0 flags=0x0 origin=0,0
00:00:10.263241 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=000000000e000000 w=1024 h=768 bpp=24 cbLine=0xC00 flags=0x0 origin=0,0
00:00:11.723300 GIM: HyperV: Guest OS reported ID 0x1040a0000271b
00:00:11.723319 GIM: HyperV: Open-source=false Vendor=0x1 OS=0x4 (Windows NT or derivative) Major=10 Minor=0 ServicePack=0 Build=10011
00:00:11.723350 GIM: HyperV: Enabled hypercall page at 0x0000000000210000
00:00:11.724771 GIM: HyperV: Queried extended hypercall capabilities 0x1 at 0x0000000000007000
00:00:11.724824 GIM: HyperV: Enabled TSC page at 0x000000000000c000 - u64TscScale=0xcd9f5700000000 u64TscKHz=0x30a201 (3 187 201) Seq=1
00:00:11.724829 TM: Host/VM is not suitable for using TSC mode 'RealTscOffset', request to change TSC mode ignored
00:00:11.724880 GIM0: HyperV: Enabled APIC-assist page at 0x000000000000d000
00:00:11.857063 RTC: period=0x10 (16) 2048 Hz
00:00:12.692500 RTC: Stopped the periodic timer
00:00:12.692712 RTC: period=0x10 (16) 2048 Hz
00:00:12.712608 GIM1: HyperV: Enabled APIC-assist page at 0x000000003ffff000
00:00:12.717481 GIM2: HyperV: Enabled APIC-assist page at 0x000000003fffe000
00:00:12.720480 GIM3: HyperV: Enabled APIC-assist page at 0x000000003fffd000
00:01:06.202473 GUI: Machine-window #0 activated
00:01:06.202633 GUI: Capturing keyboard on focus in
00:01:06.202674 GUI: Machine-view #0 focused, reason=3
00:01:07.082331 GUI: Machine-window #0 deactivated
00:01:07.082374 GUI: Releasing mouse on focus out
00:01:07.082392 GUI: Releasing keyboard on focus out
00:01:07.086288 GUI: Machine-view #0 unfocused, reason=3
00:01:12.595734 GUI: Machine-window #0 activated
00:01:12.595884 GUI: Capturing keyboard on focus in
00:01:12.595922 GUI: Machine-view #0 focused, reason=3
00:01:13.039339 GUI: Machine-window #0 deactivated
00:01:13.039359 GUI: Releasing mouse on focus out
00:01:13.039368 GUI: Releasing keyboard on focus out
00:01:13.041525 GUI: Machine-view #0 unfocused, reason=3
00:01:13.181329 GUI: Machine-window #0 activated
00:01:13.181406 GUI: Capturing keyboard on focus in
00:01:13.181520 GUI: Machine-view #0 focused, reason=3
00:01:13.689433 GUI: Machine-window #0 deactivated
00:01:13.689470 GUI: Releasing mouse on focus out
00:01:13.689483 GUI: Releasing keyboard on focus out
00:01:13.692559 GUI: Machine-view #0 unfocused, reason=3
00:01:16.232829 GUI: Machine-window #0 activated
00:01:16.232880 GUI: Capturing keyboard on focus in
00:01:16.232893 GUI: Machine-view #0 focused, reason=3
00:01:16.909058 AHCI#0: Reset the HBA
00:01:16.909082 VD#0: Cancelling all active requests
00:01:16.938627 VMMDev: Guest Log: VBoxGuest: Windows version 10.0, build 17134
00:01:16.943578 VMMDev: Guest Additions information report: Version 5.1.18 r114002 '5.1.18'
00:01:16.943695 VMMDev: Guest Additions information report: Interface = 0x00010004 osType = 0x0003B100 (Windows 10, 64-bit)
00:01:16.943790 VMMDev: Guest Additions capability report: (0x0 -> 0x0) seamless: no, hostWindowMapping: no, graphics: no
00:01:16.943862 VMMDev: vmmDevReqHandler_HeartbeatConfigure: No change (fHeartbeatActive=false)
00:01:16.943874 GUI: UISession::sltAdditionsChange: GA state change event came, notifying listeners
00:01:16.943894 VMMDev: Heartbeat flatline timer set to trigger after 4 000 000 000 ns
00:01:16.943904 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=5
00:01:16.943937 GUI: UISession::sltAdditionsChange: GA state really changed, notifying listeners
00:01:16.943946 GUI: UIMachineViewNormal::adjustGuestScreenSize: Adjust guest-screen size if necessary
00:01:16.943968 GUI: UISession::sltAdditionsChange: GA state change event came, notifying listeners
00:01:16.943971 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=5
00:01:16.944067 GUI: UISession::sltAdditionsChange: GA state change event came, notifying listeners
00:01:16.944071 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=5
00:01:16.975725 AIOMgr: Async flushes not supported
00:01:24.942530 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:01:25.614720 VMMDev: GuestHeartBeat: Guest is alive (gone 4 672 683 642 ns)
00:01:29.633665 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:01:41.107542 TM: Giving up catch-up attempt at a 60 000 412 101 ns lag; new total: 60 000 412 101 ns
00:01:41.901698 VMMDev: GuestHeartBeat: Guest is alive (gone 16 268 051 353 ns)
00:01:46.935253 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:01:50.614999 VMMDev: GuestHeartBeat: Guest is alive (gone 7 679 783 783 ns)
00:01:54.944530 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:02:29.593456 VMMDev: GuestHeartBeat: Guest is alive (gone 38 649 435 919 ns)
00:02:31.489609 GUI: Machine-window #0 deactivated
00:02:31.489644 GUI: Releasing mouse on focus out
00:02:31.489664 GUI: Releasing keyboard on focus out
00:02:31.495038 GUI: Machine-view #0 unfocused, reason=3

installed VirtualBox 7.14 in on macOS sonoma 14.6.1. (Intel Mac - 3.8 GHz 8-Core Intel Core i7 - AMD Radeon Pro 5700 XT 16 GB - 64 GB RAM > Installed Windows 10 with allocated 4096 MB RAM and 2 CPU = can run Windows (but sluggish)

Installed Guest Additions ISO - I added the iso and installed many tries even tried dl older version VBoxGuestAdditions_7.1.0.iso for VirtualBox-7.1.4-165100-OSX.dmg - but default or older do exact same thing ----> Run as Admin > it gets 3/4 way through - soon after the video blink - it crashes and back in Manager it says Aborted. Then in Windows just a non functioning greyd out VM Addons icon is in system tray. i do find it Program Files / Oracle / VirtualBox Guest Additions but no change to Windows functions. Can not complete install without the crash.

in host VirtualBox Menu > Activity > Preferences = CPU load, Network Rate and Disk i/o all have readings but RAM Usage greyed out and says: This metric requires Guest additions to work

net effect is sluggish even running no apps (laggy even with various ram and cpu settings). dont know if just sluggish because mac based or if crash on install = somehow incomplete and not functioning at 100%

I've been using this vm with Linux Mint 22 Cinnamon to test nginx, but today I'm facing a lot of crashes for apparently no reason, at the beginning it looked like the problem was when copy-pasting between host and guest, so i disabled it, but now i just booted, opened the terminal, and it crashed
I don't know what might be the problem, here's the log

My host OS is Windows 10 Pro 22H2, I'm using the 7.0.14 r161095 version, because any newer version for some reason refuses to install, and i use guest additions, even tho i think they aren't the problem because i set it when creating the vm and it didn't give any problems before

Full disclosure, I have a limited background in IT (coming out of sales) but I've been wanting to learn Python, Linux, and ethical hacking to hopefully switch into pen testing soon:

I kicked things off by picking a 1TB external drive for storage and I used Microsoft co-pilot to walk me thru the entire process. I downloaded GParted to create partitions for Ubuntu and Kali Linux. Then, I made a bootable USB with Rufus.

Next, I entered the BIOS & set the USB as the primary boot device, and enabled virtualization from the boot menu. Installed VirtualBox, created VMs for Ubuntu and Kali, then booted from the .iso files.

From there, I watched Ubuntu install, set up user accounts, and got it running. I did the same thing for Kali Linux.

Finally, I configured the network adapters to use NAT for secure internet (I found that adding a VPN slowed it down and kept disconnecting me from the server). I also had to manage the disk space allocation in Virtual Box because it kept crashing.

Step 1: Setting Up the Drive

• Drive Selection: I had a 1TB external drive for storage but it was write-only so that was a P.I.T.A!
• Partition Creation: Used GParted to create separate partitions for Ubuntu and Kali Linux.
• Bootable USB Creation: Rufus created bootable USBs from downloaded ISO files for both OSs.

Step 2: BIOS Configuration

• Accessing BIOS: Rebooted the PC and entered BIOS setup.
• Boot Order Adjustment: Set USB as the primary boot device to enable OS installation from USB drives.

Step 3: VirtualBox Setup

• VirtualBox Installation: Downloaded and installed VirtualBox on the PC.
• VM Creation for Ubuntu and Kali Linux:
  • Created a new VM for each OS in VirtualBox.
  • Allocated resources (RAM, CPU, disk space).
  • Loaded the respective ISO files for installation.

Step 4: Deploying Ubuntu

• ISO Boot: Started the Ubuntu VM and booted from the ISO.
• Installation Process: Followed the on-screen instructions to install Ubuntu on the virtual hard disk.
• User Setup: Created user accounts and configured initial settings.

Step 5: Deploying Kali Linux

• ISO Boot: Started the Kali Linux VM and booted from the ISO.
• Installation Process: Followed the prompts to install Kali on a separate virtual hard disk.
• User Setup: Set up user accounts and configured initial settings for ethical hacking.

Step 6: Post-Installation Configuration

• Network Setup: Configured network adapters to use NAT for secure internet access.
• Resource Management: Monitored disk space and cleaned up unnecessary files to optimize performance.
• Snapshot Management: Created snapshots for both VMs to preserve current states and facilitate easy rollbacks.

Step 7: Ongoing Maintenance

• Regular Updates: Kept both Ubuntu and Kali Linux up to date with regular updates and security patches.
• Disk Cleanup: Periodically ran commands to clear cache, logs, and unnecessary packages.
• Space Management: Regularly checked disk usage and managed snapshots to free up space.

This might not seem like a big deal to some but I'm pretty proud of myself for not knowing anything about virtualization & deployments and then building a home VM on the first go!

I have a few virtual machines configured in a Vagrant file. They all have a private network declared, and associated IP addresses to go along. However, the network isn't created on either of them. The following default network device is created: [root@ol ~]# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 08:00:27:d2:59:71 brd ff:ff:ff:ff:ff:ff altname enp0s3 inet 10.0.2.15/24 brd 10.0.2.255 scope global dynamic noprefixroute eth0 valid_lft 85972sec preferred_lft 85972sec inet6 fd00::a00:27ff:fed2:5971/64 scope global dynamic noprefixroute valid_lft 86175sec preferred_lft 14175sec inet6 fe80::a00:27ff:fed2:5971/64 scope link noprefixroute valid_lft forever preferred_lft forever

Running VBox 7.1.4 with the same version of Extension Pack, on Windows 11 PRO, Hyper-V disabled, AMD-V enabled, Vagrant 2.4.1.