-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AvatarPeripheral with x86 target #110
Comments
Hey! Unfortunately, the remote memory in the configurable machine is not supported for the i386 target.
|
Yay! |
So, for the record, I quick fixed it with the following patch and it seems to work (I haven't tested it extensively though and I'm definitely not sure about the hardcoded apic-id value)...
|
This seems correct. I suppose the apic-id would become an issue in case of creating multiple CPU. Thanks for your contribution! |
Sure, I'll do it tomorrow. :) |
Hey,
First, thanks for the really cool tool. :)
I'm currently trying my hand on it but I kind of struggle with few errors that might either be because I don't understand what I'm doing (insert here the dog-in-front-of-a-computer meme) or because of an issue with AvatarPeripheral.
Basically, here is a simplified example of what I'm doing:
It does work perfectly fine if my target architecture is ARM but fails with the following error with x86:
Do you have any idea about why I would obtain such behavior?
The text was updated successfully, but these errors were encountered: