1 |
On Saturday, 20 August 2022 18:57:38 BST Walter Dnes wrote: |
2 |
> On Sat, Aug 20, 2022 at 09:05:32AM +0100, Michael wrote |
3 |
> |
4 |
> > I've noticed the same problem with a MSWindows VM on a laptop, |
5 |
> > but only when the screen resolution for the VM is anything other |
6 |
> > than full screen on the host. |
7 |
> |
8 |
> Thanks. That clue finally got me going with QEMU, but there are a few |
9 |
> head scratchers that I'll gladly ignore now that QEMU is working. |
10 |
> |
11 |
> Head scratcher #1) After a "native install" of the ArcaOS VM on the |
12 |
> Thinkpad, the bootup on the Thinkpad screams about multiple missing |
13 |
> drivers for ArcaOS, "Press Enter to continue". Meanwhile a copy of the |
14 |
> install on my Dell desktop PC boots up just fine on the ThinkPad (but |
15 |
> has mouse problems). |
16 |
> |
17 |
> Head scratcher #2) The "native install" of ArcaOS VM on the Thinkpad has |
18 |
> multiple video resolution options, but it does *NOT* have 1280x800 to |
19 |
> match the Thinkpad. Meanwhile, the ArcaOS VM I copied from my desktop |
20 |
> (1920x1080 monitor) does have a 1280x800 option! |
21 |
> |
22 |
> Head scratcher #3) After struggling with the mouse, I finally managed to |
23 |
> change the ArcaOS install (copied from my desktop to the ThinkPad) to |
24 |
> 1280x800, and then rebooted the VM. Once I fire up the VM, it works OK |
25 |
> with the USB mouse *AS LONG AS I DO NOT GO FULLSCREEN {CTRL-ALT-F}*. If |
26 |
> I go fullscreen, the mouse goes super-flakey again. Since both the VM |
27 |
> and the laptop screen are 1280x800, I'm missing very little screen real |
28 |
> estate. Just a thin white strip across the top with the QEMU menu bar |
29 |
> ("Machine View"). |
30 |
> |
31 |
> So far, so good. If you don't hear back from me, assume that I'm |
32 |
> happy with the way things are going. Once again, thanks for pointing me |
33 |
> in the right direction. |
34 |
|
35 |
You're welcome, I'm glad you got somewhere. TBH I don't claim this is the |
36 |
right way to go about it, just the workarounds I have come up with after |
37 |
trying different resolutions on the QEMU TianoCore EFI menu, then the MSWindows |
38 |
desktop resolution menu and then switching back and forth between full screen |
39 |
and the default VM window size. Unless I escape the TianoCore boot process to |
40 |
select Reset, the window of the VM ends up being smaller than full screen, |
41 |
inheriting the size of the TianoCore menu window, no matter what the |
42 |
resolution of either the TianoCore or the MSWindows desktop has been set at |
43 |
and the mouse is jumpy and displaced an inch or so from where I end up |
44 |
clicking. |
45 |
|
46 |
With VBox, while it worked, I had no such problems once VBox Additions were |
47 |
installed on the guest. |
48 |
|
49 |
Regarding the head scratchers with your ArcaOS it may be different the guests |
50 |
graphics drivers and settings are made available/configured at installation |
51 |
time, as long as the VM container can detect these from the host. Perhaps an |
52 |
inherited full screen is necessary for the installation to assume the |
53 |
appropriate window resolution dimensions. |