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

[Dom0] Error at first boot #2981

Closed
wocsigint opened this Issue Aug 6, 2017 · 2 comments

Comments

Projects
None yet
3 participants
@wocsigint

wocsigint commented Aug 6, 2017

Qubes OS version (e.g., R3.2): 4.0 Rc1

Affected TemplateVMs (e.g., fedora-23, if applicable): Dom0


Expected behavior: Creating default VM

Actual behavior: here is the error message :

['/usr/bin/qvm-start', 'sys-firewall'] failed:
stdout: ""
stderr : "Start failed: invalid argument cuold not find capabilities for arch=x86_64

Steps to reproduce the behavior:

General notes:

I run Qubes as a VM (VMware).


Related issues:

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Aug 6, 2017

Member

I run Qubes as a VM (VMware).

Since this is not officially supported, it's possible that this issue will be a wontfix.

Member

andrewdavidwong commented Aug 6, 2017

I run Qubes as a VM (VMware).

Since this is not officially supported, it's possible that this issue will be a wontfix.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Aug 6, 2017

Member

Specifically, the error is caused by missing VT-x. Not sure if VMware support VT-x emulation, but anyway this is unsupported configuration.

Member

marmarek commented Aug 6, 2017

Specifically, the error is caused by missing VT-x. Not sure if VMware support VT-x emulation, but anyway this is unsupported configuration.

@marmarek marmarek closed this Aug 6, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment