-
Notifications
You must be signed in to change notification settings - Fork 11
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
Installing development environment on Windows #49
Comments
Fortunately, MO doesn't require serial ports! :)
…On Mon, Feb 20, 2023 at 12:54 PM Joseph D. Cohen ***@***.***> wrote:
I'm leaving this note here in case others run into this problem.
(I think it's a problem on the Windows side, not the MO side
PS C:\Users\jdcoh\developer-startup> vagrant upBringing machine 'mo-focal-2022-12-21' up with 'virtualbox' provider...
==> mo-focal-2022-12-21: Booting VM
...There was an error while executing `VBoxManage`, a CLI used by Vagrantfor controlling VirtualBox. The command and stderr is shown below.
Command: ["startvm", "9536f7c4-e979-4ea4-9918-7feaf5327754", "--type", "headless"]
Stderr: VBoxManage.exe: error: RawFile#0 failed to create the raw output file \dev\null (VERR_PATH_NOT_FOUND)VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole
The workaround seems to be disabling serial ports in VirtualBox. But I
wonder if this will cause problems later on.
—
Reply to this email directly, view it on GitHub
<#49>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAYTNNONWAWUQGN5F4BMPM3WYOVWTANCNFSM6AAAAAAVCE2X4A>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
That's good to know. Thanks.
On Mon, Feb 20, 2023 at 10:05 AM Jason Hollinger ***@***.***>
wrote:
… Fortunately, MO doesn't require serial ports! :)
On Mon, Feb 20, 2023 at 12:54 PM Joseph D. Cohen ***@***.***>
wrote:
> I'm leaving this note here in case others run into this problem.
> (I think it's a problem on the Windows side, not the MO side
>
> PS C:\Users\jdcoh\developer-startup> vagrant upBringing machine
'mo-focal-2022-12-21' up with 'virtualbox' provider...
> ==> mo-focal-2022-12-21: Booting VM
> ...There was an error while executing `VBoxManage`, a CLI used by
Vagrantfor controlling VirtualBox. The command and stderr is shown below.
> Command: ["startvm", "9536f7c4-e979-4ea4-9918-7feaf5327754", "--type",
"headless"]
> Stderr: VBoxManage.exe: error: RawFile#0 failed to create the raw output
file \dev\null (VERR_PATH_NOT_FOUND)VBoxManage.exe: error: Details: code
E_FAIL (0x80004005), component ConsoleWrap, interface IConsole
>
> The workaround seems to be disabling serial ports in VirtualBox. But I
> wonder if this will cause problems later on.
>
> —
> Reply to this email directly, view it on GitHub
> <#49>, or
> unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/AAYTNNONWAWUQGN5F4BMPM3WYOVWTANCNFSM6AAAAAAVCE2X4A
>
> .
> You are receiving this because you are subscribed to this thread.Message
> ID: ***@***.***>
>
—
Reply to this email directly, view it on GitHub
<#49 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAALDFFPG7Y2FLURCGL2ZTLWYOW5NANCNFSM6AAAAAAVCE2X4A>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm leaving this note here in case others run into this problem.
(I think it's a problem on the Windows side, not the MO side
The workaround seems to be disabling serial ports in VirtualBox. But I wonder if this will cause problems later on.
The text was updated successfully, but these errors were encountered: