bhyve Windows 7 x64 bit virtualized with bhyve : several problems to face up before having a working vm.

Hello.

I'm trying to virtualize Windows 7 x64 bit with bhyve and I have several problems to fix. I have so many problems that I don't know what to do :(

Problem n. 1 : The most annoying one is that I can't use the parameter below with bhyve. If I do that,the mouse pointer will not move at all inside the VM. So it is not supported.

Code:
-s 30,xhci,tablet \

Problem n. 2 : Without the parameter above,when I move my mouse inside the VM,the pointer movements don't match with the screen coordinates. And I can't configure anything inside the VM.

Problem n. 3 : With bhyve I can use this parameter :

Code:
-s 4,fbuf,tcp=0.0.0.0:5901,w=1920,h=1080,wait \

but then,inside the VM the resolution is fixed to 1024x768. Also for this reason I think that I'm not able to fix the problem 2.

Problem n. 4 : I've passed thru my Renesas USB controller inside the VM,with this parameter :

Code:
-s 6,passthru,10/0/0 \

unfortunately windows 7 needs that I make the installation of the driver,otherwise it will not work. But I can't do that because the problem n. 2

Problem n. 5 : I'm not able to manage the Windows 7 settings using only the keyboard : It is very umcomfortable for me ! :(

Problem n. 6 : In the past I tried to configure Windows 7 under Linux / qemu / KVM and when I had solved the previous problems,I would have assigned the VM to bhyve,but I've realized that bhyve does not like this behavior and the consequence is that the VM closes all the time suddenly.

So, I would gather some ideas from you about what I can do to overcome some of the problems I have. My ultimate goal is to be able to install the latest nvidia driver for Windows 7 because I want to see if it gives the error 43.
 
I'll save you the speech about using an outdated OS with bhyve and assume you know what you're doing.

Not sure about the tablet driver; if memory serves, doesn't that just "click" where you're clicking in VNC? Have you tried whether clicking works even though the mouse pointer isn't moving?

Also, if you have gotten network running, have you tried accessing your VM via RDP instead? If you're using Windows 10 Professional (or better), Remote Desktop should be included. You might have to turn it on in the System properties, however.
 
Ah, got it. So it does move. Just not with the right speed.

While it's only a workaround fighting the symptom instead of an actual solution - maybe you want to give this a try?

This might be possible to get activated via keyboard? It would then probably allow you to install the USB driver and use a mouse via that controller, I suppose.
 
With the keyboard I've installed the nvidia driver inside the windows 7 vm and I've disabled the framebuffer (this was exactly the experiment). The vm closes after some time and everytime I launch it,with and without the framebuffer. Project terminated.
 
Use the KVM at the standard resolution, and then login with freerdp to get your desired high res.

In the windows graphics settings, make sure you have size of text and other items as 100%, or else the scaling will be wrong when you login with rdp.

Although I use windows 10 in bhyve now, I seem to remember that -s 30,xhci,tablet did work on windows 7.
 
To get the Windows 7 mouse cursor synced you'll need to use RDP, and not VNC + "xhci,tablet" (so the desktop of Win7 Home Edition isn't usable with bhyve).
 
I can't do anything anymore because the installation of the nvidia driver 472 made the windows 7 VM totally not usable. The VM closes every single time I launch it and I think there isn't any easy workaround to fix this behavior.
 
If you are able to pass a video card into a VM (like you insist in all your threads), you should be able to connect that video card to display directly instead of this vnc/rdp/whatever stuff.
 
I create also different threads,heh. Not only this kind of threads. Just look better,thanks. anyway,yes,I insist so much on this argument because I'm trying to help Corvin to understand what's missing inside bhyve in relation with the nvidia driver to be compatible with windows. My feeling is that it could be at least one windows version able to accept the nvidia driver. Now I'm focused on windows 7 and on windows PE 7.0. I don't know the reasons why the windows 7 VM after the installation of the nvidia driver closes everytime. To be honest I expected a different behavior. I mean,that the windows 7 VM booted correctly at least and then I would have installed ssh inside it and from outside I would have tried to understand the error reported by Windows 7 in relation with the nvidia driver. Actually I'm not sure if it is the 43.
 
AFAIK you need `-s 30,xhci` for Windows7, without ',tablet`

but is not the "tablet" parameter that gives the absolute movements to the mouse ? without it,it has not so much sense. With qemu I use tablet everytime because with it the movements of my mouse are precise,without it not.
 
Back
Top