Virtualbox Windows Xp Product Key

1 view
Skip to first unread message

Yiraika Daimaru

unread,
Aug 3, 2024, 6:11:19 PM8/3/24
to jaivelhighcor

Internet works perfectly on host (Ubuntu 13.04, 32 bit, fully updated) but cannot connect to internet on guest Windows 7 (under Virtualbox 4.2).Have tried NAT and Bridge Network - none worked. I had internet connection in the guest OS a couple of months ago, but I haven't tried the virtualbox since and now it's gone for some reason. I would be grateful if someone could help me re-connect the windows OS back online (without the need to format my computer or to uninstall and re-install the guest OS).Thanks!

At that point you should be able to start a web browser in your VM and get a connection. This video provided the information I listed above, even though they are using a Windows 7 host with a Windows Server guest.

Another solution: If you are on windows Host, Go to Control Panel\Network and Internet\Network Connections right click any of the Virtualbox adapter and select Diagnose, let it do its thing and if it finds some anomaly with the adapter it will give you a prompt to reset the adapter by Apply the recommended solution/changes , you opt in for that, after its done, you most probably should have the network back to normal in your virtual machine.

For wireless to work, in my machines anyway, the WiFi MAC address in Settings must match the hardware, and wlan0 must be selected (when host Internet comes through wireless).

I had the same problem with a VirtualBox VM (5.9.14) that was working previously and stopped working after a shutdown/reboot. In my case the VB option "cable connected" got disabled for some obscure reason.Enabling that again made everything work again (no need for promiscuous mode in this case since I'm not doing anything requiring this - no WireShark or anything of that kind)Bottom line: do not assume that the Network configuration for your VM is correct. If you have problems, review that part of the configuration.

I ended up finding that my issue was in regards to my Network Center. Ensure that the wifi you are connected to is sharing internet, with the VirtualBox wifi adapter. This configuration is under the adapter settings in Network and Sharing Center.

believe me I dislike Windows, but is not because I love it somuch that I need to have a windows container. My company heavily relies on Windows, that is not going to be matter of hours/days to move our products to a platform independent env.

If you must deploy a hypervisor, WSL2 or Hyper-V is a mess to deploy on a windows box that is nested in ESXi is a mess, and a real pain to get up and running. Virtualbox with Docker Toolbox maybe a valuable option here is the github.

Good post @rimelek !
Yes, shortly after I made that post I realized that docker toolbox is no longer supported by docker. Therefore I gave in and deployed Hyper-V with WSL2 (not sure if both are needed or not). Here are the instructions and links I followed to get it all done:

I have never used QEMU on Windows. Only on Linux with KVM, but I used UTM on MacOS to install a Linux OS and install Docker. UTM is based on QEMU. It worked but the performance will depend on your machine.

On the VM you would need to enable the sshd service sudo systemctl enable sshd.service and start the daemon sudo systemctl start sshd.service.
You also would need to verify that ssh is allowed through the firewall. I use the gui firewalld-config which would also need installed. sudo dnf install firewalld-config I do not remember whether ssh is allowed to port 22 by default or not.

I do think that using nat will be a hindrance unless you have configured the host to allow port forwarding. I use bridged on the VM and connect it to the default virbr0 device on my fedora host. I also use libvirt and QEMU on my fedora host. Cannot speak to what would work with a windows host and using virtualbox with a fedora VM.

This is how I got UNRAID registered version running happily under Virtualbox on my Windows machine. Main reason for doing this was to rationalise the number of boxes in the lounge. Performance is adequate, when I'm using Windows UNRAID is idling and when UNRAID is working serving my media then Windows is not doing much.

Being technically competent, but a bit old and slow when it comes to learning new stuff I did a lot of Googling. Of course there are loads of ways of getting this thing going, many are decidedly complex in nature. This is my distillation of that data.

[*]Take one USB memory stick (it does not necessarily need to be the one linked to your registration), make it bootable and install UNRAID on it in the usual manner, however do NOT name it UNRAID, I called mine UN-HDD.

In order to update your UNRAID version, no need to make a new VHD image. You can mount the VHD using the scripts here -and-unmount-a-vhd-file-in-windows-explorer-via-a-right-click/ copy the new files to the drive, and then unmount it (you need to stop the VM before doing anything), whilst you're at it delete the Config folder from the image (just to avoid confusion) all the configuration resides on the USB.

If you want to use real drives rather than virtual (for a real world application) I used the commands here -a-usb-flash-drive-in-virtualbox/ to discover the device number and to create a .VMDK for each of my storage drives (don't forget to give them different file names) and then attached them to the VM in the usual way.

I'm not in front of the box right now, but when I get home from this business trip I'll check actual speeds. It's more than adequately fast to send 2 x HD streams to my HTPC and bedroom TV (Samsung smart TV).

I am having trouble getting unRAID working in a VirtualBox. It boots up the VHD, is going through the long list of linux commands, but then hangs up on "waiting for USB subsystem," which it keeps repeating over and over again.

I've attached some physical drives using the vmdk method in the original post. However, my disk i/o speeds are horrendous, on the order of 5 MB/sec. I have attached these vmdks using a SATA controller in Storage. Has anyone had any luck in getting faster disk io speeds using Virtual Box and a virtualized unRAID server?

I am looking to convert my existing unraid setup from a standalone machine to a W7 VM. I understand that raw access can be done to give each physical disk a presence in the VM. Has anyone moved an existing installation to a VM, got any tips or pitfalls to be wary of?

Works great. I have done it (RDM) in both Windows host and unRAID host. You have to use the command line tools to do the RDM of drives in VirtualBox. Also that is the ONLY way to get the raw drive to the VM on a Windows HOST since pass through of PCIe devices only works on Linux host. It doesn't work and isn't available on a Windows host.

Thanks for the links and information. I would prefer to have the ability to spin down the drives and get the temps but I am more comfortable with windows and virtual box. I will do a bit more research first, still concerned about losing data from the drives but am sure it will go OK

I think the chances of shoe horning rdm into VB on windoze is far more likely to break than in Linux where it is designed to do this. Sticking with windoze because you're comfortable with it is the pussy option!

The only differences I can see are that I have defined SATA disks instead of IDE, and that I am actually using a slightly different NIC for the bridged adaptor - but I would not have thought either of those should really matter.

You do not mention what version of unRAID you are intending to try? If it is the new 6.2 beta which now includes a built-in GUI option then you can bring that up by editing the syslinux.cfg file on the boot device (I assume a VMDK) and moving the Default entry to the one to load the GUI. Editing the syslinux.cfg on the USB flash drive will not have the same effect (since VirtualBox does not supporting from USB then I assume you have this plugged in separately and passed through to the VM). This is the same GUI that you would get by connecting from outside the VM via a browser.

Dear good morning
I have the following problem after "installing sophos intercept x", selling the error of the image to the start of virtual machines in virtualbox, with the operating system of Windows 10 64bit, "tested on multiple computers". When uninstalling "install sophos intercept x" the error disappears and works correctly.
I tested it with others with Windows 7 and it works correctly.
Probe several Internet solutions such as: Disable the virtual machine peripherals, start decoupling the virtual machine, uninstall and install virtualbox with the latest version. And no function.

Prob varias soluciones de internet como: Deshabilitar perifricos de la maquina virtual, iniciar desacoplada la mquina virtual, desinstalar y instalar virtualbox con la ltima versin. Y ninguna funciono.

If it still fails, without the actually loading of the hmpalert DLL, then I imagine it must be the driver (hmpalert.sys) injected shell code (that loads the DLL) into the process that is the issue. To prove that you can rename the files back, then in the registry (hklm\system\currentcontrolset\hmpalert\) set start to 4 (remember the current value) then restart the computer.

Hello good afternoon
Thank you very much for your reply.
Rename the hmpalert.sys file and re-run the program and the problem even Persians.
In the path "hklm \ system \ currentcontrolset \" The registry "hmpalert"
I thank you if you can pass another test and we gladly do it.

Hola buenas tardes
Muchas gracias por su respuesta.
Renombramos el archivo hmpalert.sys y se volvio a ejecutar el programa y el problema aun persas.
En la ruta "hklm \ system \ currentcontrolset \" No se encontr el registro "hmpalert"
Le agradezco si puede pasarno otra prueba y con gusto la realizamos.

c80f0f1006
Reply all
Reply to author
Forward
0 new messages