Re: Virtualbox Windows 98 Se Video Driver
Lahoma Helmy
After creating a vhd and going through that process i'm unable to install win7 x64. I've went through various settings and trying to get it right. It'll boot the windows install but then indicate the following error (image included too):
You can set a passthrough but this is also where you can point to an ISO file of your disc. I used an ISO because it makes the OS install much much faster and passthrough gets a lot of hiccups for long read times. Think of it as playing hot potato with 3 people instead of just 2.
It can be complaining because some of the virtualiced hardware is not compatible out-of-the-box with Windows 7. The most likely problem is the network card, if it was another componente Windows will just connect to internet to try to download the driver.
This problem can also occur if your ISO or DVD is corrupted. At the company I attempted to download a Windows form the MSDN subscriptions download center. Due to a network issue only half of the ISO was downloaded. The installer started, but complained the same way you mentioned.
i am an absolute Linux fan and use Manjaro XFCE.
But: Unfortunately the CAD Software Fusion 360 of Autodesk is only available for Windows.
So i set up a VM Iso of WIndows 10 and installed Fusion 360.
Unfortunately the graphic performance is very bad.
So i downloaded the latest NVIDIA graphic driver for my card (Geforce gtx 1050 ti) and tried to install them on windows), cause at the moment on ly a standard windows display driver is installed.
I'm running Arch as my host system and Windows 7 in a VirtualBox. I want to use Atmel Studio with my Arduino Atmega 2560. To get the right USB Drivers for Win7 I've installed the Arduino IDE in the guest and shared my Arduino as USB Device. But when I try to install the right windows driver I get the error "Couldn't start the devie (Code 10)".
I've already tried to change the permissions of /dev/ttyACM0 (where my Arduino is mounted), but it doesn't make any difference. I've also noticed that when I share the device /dev/ttyACM0 vanishes. Is there any other point where virtualbox mounts the device?
Solution: I found the solution for my problem today. I had to change the USB Controller under Machine Settings -> USB to USB 2.0 (EHCI) Controller. I guess the driver or the USB support does only work with version 2.0.
I think you are trying to push a rope here. First, may I ask if there is a reason why you need to run the IDE in a VM? It is written in Java and the native version for Linux works perfectly. And it looks almost identical to the Windows version.
When you say you share the device, I assume you mean you told VirtualBox to use that device. At that point, it no longer is seen by userspace in Linux. It is like it was unplugged from Arch, and was plugged into Windows.
On with the problem... It appears you are not passing the ownership of the USB device to the VM, but rather are mounting it under Linux to /dev/ttyACM0. That means you would have to tell Vitualbox to map a "COM" port to /dev/ttyACM0. Then the Arduino IDE under windows would talk to that "COM" port. There is a big problem here. The Arduinos have two methods of implementing their "Serial" interfaces. One is to use a real life FTDI serial to USB bridge chip. Then, the Arduino processor uses actual serial communications to talk to that bridge chip. Newer Arduinos, including (I think) the one you referenced don't actually use a separate FTDI chip. They have intrinsic USB controllers and present themselves to the USB bus as a serial bridge, but the serial communications never actual go over a wire. Streams on the Arduino are just directly converted to packets and are sent over USB. The problem is that, unlike the older Arduinos, when the processor is reset, the USB stack vanishes as the USB bus disconnects. During the restart, the Arduino reconnects to the bus and enumeration and negotiation start anew. This means that every time the device is reset, /dev/ttyACM0 will disappear and reappear. The IDE itself understands this behavior and can deal with it.
This is bad. This will confuse VirtualBox because the "File" (Pipe) it had open and was forwarding to Windows disappears. It probably will not reestablish the link automatically. On the other hand, it you have the device dedicated to the VM, that is fine, but when the disconnect occurs, it vanishes on the Windows side. The rub is that when it reconnects, it shows up initially on the Linux side and will remain there until you share it again.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Ok, I see the problem. Based on your reply I tried to set a "serial port pipe" in VirtualBox. Now my mircocontroller is available at COM1, but when I try to install the driver I still get this error message, which I've mentioned above. It seems to me like the virtual machine can't pass any data out to my mC, so I tried to change the permissions again, but no change..
I would also note that even with a VM running fedora on a fedora hosted machine it seems not possible to use true graphics acceleration unless there is an extra GPU installed that can be directly passed into the VM so that the OS of the VM is using its own drivers to manage the hardware acceleration.
I would not know what may have been changed with your update, you would need to check what packages were changed, but I would suspect that this is related to interaction between the kernel drivers and the graphics of both VMware and VirtualBox. Was windows updated at about the same time?
I just tried downgrading mesa from 23.3.2-7 to 23.2.1-2 and accelerated 3D works fine in VMPlayer with this version of mesa. I suspect that some change in mesa is out of sync with the part of open-vm-tools that provides accelerated 3D support.
I found all hardware drivers that vmware 15 and virtualbox 6.0 emulated for windowsxp except Intel hd audio for virtualbox.I tried lots of intel audio drivers and winxp itself hd audio driver,but all of them can't work.So could anybody have this driver to share it for me?
It seems VirtualBox authors are not keen on addressing the issue, and just tell users to use AC'97 on Windows XP:
=38886
Can you provide the device ID for the HD Audio that VirtualBox emulates?
The moderators over at the VBox forums talk about HD busses, codecs, and whatnot, but fail to explain properly why a (supposedly) properly emulated device won't work. And to put an end, they just say "we don't want to waste time on that old OS, use AC97".
Not to wake an old thread, but has there been any progress on this? One of my XP installations is currently being virtualized on Virtualbox and indeed I'm stuck with AC97 at 44100Hz 16bit PCM stereo 2.0 routed all the way through to Pipewire/Wireplumber on Linux, upmixed to 5.1, upsampled to 48000Hz PCM 24bit and then delivered to my sound card and on to my subwoofer. That... kinda sucks.
2. As another attempt at installing win10 - at that dialog inside the windows install process where you decide where to install win10 on what drive, I did all these steps also mentioned also there. Was not very intuitive and did not display "Baloon installed" or "Network card" installed. It just reverted back to the empty dialog where you decide what disk to install win10 on ....until i got to the viostor inf and it picked up the disk controller and the win10 install continued.
You don't have to install the inf files manually. During the windows install only point to the viostor drivers as you said for the disk to show up. After the you have installed windows, go to the device manager, right click each device with missing drivers and simply point to the virtio iso and tick the box for also search the subfolders and it will find the depending drivers.
I have my test environment setup running on Unbuntu with OpenNebula and KVM. Can anyone point me in the right direction on some documentation of guidance on how to create a windows VM? I have been able to spin up a CentOS VM, but for the life of me I cant figure out a Windows one.
Im working with a proconfigured image that I created with virtualbox. So the VirtIo drivers are already installed and I enabled remote control.
After creating the image I converted it to the qcow2 format using qemu-img.
[oneadmin@vdicone01 100]$ cat /var/log/one/17.log
Sun Feb 5 01:06:13 2017 [Z0][VM][I]: New state is ACTIVE
Sun Feb 5 01:06:13 2017 [Z0][VM][I]: New LCM state is PROLOG
Sun Feb 5 01:07:18 2017 [Z0][VM][I]: New LCM state is BOOT
Sun Feb 5 01:07:18 2017 [Z0][VMM][I]: Generating deployment file: /var/lib/one/vms/17/deployment.0
Sun Feb 5 01:07:19 2017 [Z0][VMM][I]: Successfully execute transfer manager driver operation: tm_context.
Sun Feb 5 01:07:19 2017 [Z0][VMM][I]: ExitCode: 0
Sun Feb 5 01:07:19 2017 [Z0][VMM][I]: Successfully execute network driver operation: pre.
Sun Feb 5 01:07:19 2017 [Z0][VMM][I]: Command execution fail: cat
> Sun Feb 12 20:04:50 2017 [Z0][VMM][D]: Message received: LOG I 17 error: unsupported configuration: guest and host CPU are not compatible: Host CPU does not provide required features: monitor
Not sure if needed when running the USB port in pass-through mode to a VM in VirtualBox under Windows 10 but normally when wanting to access the adapter direct under Windows 10 you would need to install drivers:
d3342ee215