ubenmackin / ACVM

GUI frontend for qemu for Apple Silicon based Macs

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

the program do not respond after clicked start button

KiritoADM opened this issue · comments

the program do not respond after clicked start button

commented

What version of the program are you using? Also what computer do you have?

M1 macbook pro
11.1 Beta (20C5061b)
v1.1-2

commented

I just posted a new version, can you give that a try and let me know.

Also what vm are you trying to run?

Please note that this only runs arm based distributions, so arm linux or arm windows. It won't load up a x86/x64 based distributions of Windows.

still not working
it states turn to start for about 0.1 second and turn back to stopped, then the program lost respond
i'm using Windows10_InsiderPreview_Client_ARM64_en-us_20231.VHDX
and it works in the original fork program

i mean in this one KhaosT/ACVM

commented

Interesting. I know that there were some issues earlier on with the libraries, but we had gotten that cleaned up and the other users on the macrumors forum were able to start the application.

Can you open the Console application (it is in your Applications/Utilities folder). Click the Start button in the toolbar, and enter "ACVM" in the Search bar, and hit Enter on your keyboard. Then try and start a VM. It should output some lines. If you can grab them and paste them here, I should be able to see what is going on.

the console showed command not found.

commented

Which command was not found? Can you paste the contents of the console output here?

[找不到命令:ACVM]

[未能创建新的进程和打开伪终端(pseudo-tty)。]

commented

Very strange. Based on google translate, it says:

Command not found: ACVM

And then the next line is:

Failed to create new process and open pseudo terminal

I am not sure why it is saying it can't find ACVM, as it is the program itself you are running. Also, when pushing the Start button, it is trying to create a process called qemu-system-aarch64. There is no where that it is trying to start a new process called ACVM in the code.

Lets try a couple of other things. If you open the Terminal.app, and then drag the ACVM.app onto the terminal, you should see something like:

macbookair:~ kupan787$ /Applications/ACVM.app

Next, lets type in the rest of the command to run, so you should be left with:

macbookair:~ kupan787$ /Applications/ACVM.app/Contents/Resources/qemu-system-aarch64 --version

Now, run that command. What output do you get? For example, for myself I get:

QEMU emulator version 5.2.50 (v5.2.0-281-gf6029bb614-dirty)
Copyright (c) 2003-2020 Fabrice Bellard and the QEMU Project developers

Last login: Mon Dec 14 11:31:29 on ttys000
kiritoadm@IDITP499-1118 ~ % /Applications/ACVM.app/Contents/MacOS/ACVM ; exit;
2020-12-14 11:36:26.278 ACVM[728:11204] _TIPropertyValueIsValid called with 4 on nil context!
2020-12-14 11:36:26.278 ACVM[728:11204] imkxpc_getApplicationProperty:reply: called with incorrect property value 4, bailing.
2020-12-14 11:36:26.278 ACVM[728:11204] Text input context does not respond to _valueForTIProperty:
2020-12-14 11:36:26.280 ACVM[728:11204] _TIPropertyValueIsValid called with 4 on nil context!
2020-12-14 11:36:26.280 ACVM[728:11204] imkxpc_getApplicationProperty:reply: called with incorrect property value 4, bailing.
2020-12-14 11:36:26.280 ACVM[728:11204] Text input context does not respond to valueForTIProperty:
2020-12-14 11:36:26.293 ACVM[728:11204] TIPropertyValueIsValid called with 4 on nil context!
2020-12-14 11:36:26.293 ACVM[728:11204] imkxpc_getApplicationProperty:reply: called with incorrect property value 4, bailing.
2020-12-14 11:36:26.293 ACVM[728:11204] Text input context does not respond to valueForTIProperty:
2020-12-14 11:36:30.499 ACVM[728:11204] Warning: The declared constraints for <NSToolbarItemViewer: 0x13e7dd3e0 '1E744994-3CCA-4252-A1FA-17992A2EA52E'> were previously invalidated only because a declared constraint was snipped or manually deactivated. This indicates missing invalidation for a view's changing state that affects its declared constraints. To debug, set a breakpoint on _NSViewRemovedDeclaredConstraintBreakpoint
2020-12-14 11:36:30.500 ACVM[728:11204] Warning: The declared constraints for <NSToolbarItemViewer: 0x13e7d6f00 '430B4439-C059-4978-9339-B805E9ED2E54'> were previously invalidated only because a declared constraint was snipped or manually deactivated. This indicates missing invalidation for a view's changing state that affects its declared constraints. To debug, set a breakpoint on _NSViewRemovedDeclaredConstraintBreakpoint
2020-12-14 11:36:30.500 ACVM[728:11204] Warning: The declared constraints for <NSToolbarItemViewer: 0x13e7d3bd0 '5E0D43E0-C98D-48E8-8284-17C10A704996'> were previously invalidated only because a declared constraint was snipped or manually deactivated. This indicates missing invalidation for a view's changing state that affects its declared constraints. To debug, set a breakpoint on _NSViewRemovedDeclaredConstraintBreakpoint
2020-12-14 11:36:34.386 ACVM[728:11204] Warning: The declared constraints for <NSToolbarItemViewer: 0x13e7e3ad0 'EC81D573-6ED3-408A-89F2-03E3B5B2EBE3'> were previously invalidated only because a declared constraint was snipped or manually deactivated. This indicates missing invalidation for a view's changing state that affects its declared constraints. To debug, set a breakpoint on _NSViewRemovedDeclaredConstraintBreakpoint
2020-12-14 11:36:34.386 ACVM[728:11204] Warning: The declared constraints for <NSToolbarItemViewer: 0x13e7e0710 'D3C8E79D-DCBF-4248-ABCF-F8A5E7BB8A88'> were previously invalidated only because a declared constraint was snipped or manually deactivated. This indicates missing invalidation for a view's changing state that affects its declared constraints. To debug, set a breakpoint on _NSViewRemovedDeclaredConstraintBreakpoint
2020-12-14 11:36:34.386 ACVM[728:11204] Warning: The declared constraints for <NSToolbarItemViewer: 0x13e7dd3e0 '1E744994-3CCA-4252-A1FA-17992A2EA52E'> were previously invalidated only because a declared constraint was snipped or manually deactivated. This indicates missing invalidation for a view's changing state that affects its declared constraints. To debug, set a breakpoint on _NSViewRemovedDeclaredConstraintBreakpoint
2020-12-14 11:36:34.386 ACVM[728:11204] Warning: The declared constraints for <NSToolbarItemViewer: 0x13e7d6f00 '430B4439-C059-4978-9339-B805E9ED2E54'> were previously invalidated only because a declared constraint was snipped or manually deactivated. This indicates missing invalidation for a view's changing state that affects its declared constraints. To debug, set a breakpoint on _NSViewRemovedDeclaredConstraintBreakpoint
qemu-system-aarch64: -drive file=/Users/kiritoadm/Downloads/iMazing_2.12.7
[TNT].dmg,if=none,id=boot,cache=directsync: sector count 346288 for chunk 8 is larger than max (131072)
qemu-system-aarch64: -drive file=/Users/kiritoadm/Downloads/iMazing_2.12.7
[TNT].dmg,if=none,id=boot,cache=directsync: Could not open '/Users/kiritoadm/Downloads/iMazing_2.12.7
[TNT].dmg': Invalid argument
2020-12-14 11:36:37.465 ACVM[728:11204] _TIPropertyValueIsValid called with 4 on nil context!
2020-12-14 11:36:37.465 ACVM[728:11204] imkxpc_getApplicationProperty:reply: called with incorrect property value 4, bailing.
2020-12-14 11:36:37.465 ACVM[728:11204] Text input context does not respond to _valueForTIProperty:
2020-12-14 11:36:37.465 ACVM[728:11204] _TIPropertyValueIsValid called with 4 on nil context!
2020-12-14 11:36:37.465 ACVM[728:11204] imkxpc_getApplicationProperty:reply: called with incorrect property value 4, bailing.
2020-12-14 11:36:37.465 ACVM[728:11204] Text input context does not respond to _valueForTIProperty:
2020-12-14 11:36:37.472 ACVM[728:11204] Warning: The declared constraints for <NSToolbarItemViewer: 0x13e7e3ad0 'EC81D573-6ED3-408A-89F2-03E3B5B2EBE3'> were previously invalidated only because a declared constraint was snipped or manually deactivated. This indicates missing invalidation for a view's changing state that affects its declared constraints. To debug, set a breakpoint on _NSViewRemovedDeclaredConstraintBreakpoint
2020-12-14 11:36:37.472 ACVM[728:11204] Warning: The declared constraints for <NSToolbarItemViewer: 0x13e7e0710 'D3C8E79D-DCBF-4248-ABCF-F8A5E7BB8A88'> were previously invalidated only because a declared constraint was snipped or manually deactivated. This indicates missing invalidation for a view's changing state that affects its declared constraints. To debug, set a breakpoint on _NSViewRemovedDeclaredConstraintBreakpoint
2020-12-14 11:36:37.472 ACVM[728:11204] Warning: The declared constraints for <NSToolbarItemViewer: 0x13e7dd3e0 '1E744994-3CCA-4252-A1FA-17992A2EA52E'> were previously invalidated only because a declared constraint was snipped or manually deactivated. This indicates missing invalidation for a view's changing state that affects its declared constraints. To debug, set a breakpoint on _NSViewRemovedDeclaredConstraintBreakpoint
2020-12-14 11:36:37.472 ACVM[728:11204] Warning: The declared constraints for <NSToolbarItemViewer: 0x13e7d6f00 '430B4439-C059-4978-9339-B805E9ED2E54'> were previously invalidated only because a declared constraint was snipped or manually deactivated. This indicates missing invalidation for a view's changing state that affects its declared constraints. To debug, set a breakpoint on _NSViewRemovedDeclaredConstraintBreakpoint

/Applications/ACVM.app/Contents/MacOS/ACVM
i draged this one into console and clicked start button, the result is on above

commented

I think you have an issue with the disk image you are trying to use for the VM:

qemu-system-aarch64: -drive file=/Users/kiritoadm/Downloads/iMazing_2.12.7[TNT].dmg,if=none,id=boot,cache=directsync: sector count 346288 for chunk 8 is larger than max (131072)

It looks like you are trying to use an iMazing.dmg as your drive image. I'm not sure what iMazing is, but I don't think that dmg is support as image time for qemu. I believe you need to use iso, qcow2, raw, vhdx, or one of the other native formats. Earlier you said you were trying to use the Windows10_InsiderPreview_Client_ARM64_en-us_20231.VHDX for the VM. Can you redraw this into the VM Configuration as the Main Image, and then try again.

Also, I see this:

qemu-system-aarch64: -drive file=/Users/kiritoadm/Downloads/iMazing_2.12.7[TNT].dmg,if=none,id=boot,cache=directsync: Could not open '/Users/kiritoadm/Downloads/iMazing_2.12.7[TNT].dmg': Invalid argument

I have a feeling that the [] in the file name it doesn't like. I will work to add some logic to work around this, but I believe you have the wrong disk image selected for your VM.

ok, i put the wrong image in. what a silly mistake... after change the image, all things works right. Thankyou so much ^^

commented

No problem, happens to all of us :-)

And actually makes me want to redesign that screen more, as it is not at all clear what disk image you have selected. I'll try and work on that for the next release.