Skip to content
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

start failed in vmware #196

Open
helloyan opened this issue Feb 8, 2023 · 5 comments
Open

start failed in vmware #196

helloyan opened this issue Feb 8, 2023 · 5 comments

Comments

@helloyan
Copy link

helloyan commented Feb 8, 2023

Environment

  • Elixir version (elixir -v): 1.14.3
  • Nerves environment: (mix nerves.env --info)
Nerves environment
  MIX_TARGET:   host
  MIX_ENV:      dev

NERVES_SYSTEM is unset
NERVES_TOOLCHAIN is unset
|nerves| Environment Variable List
  target:     host
  toolchain:  unset
  system:     unset
  app:        .

|nerves| Loadpaths End
  • Additional information about your host, target hardware or environment that
    may help

    i use the hello_nerves code from start guide, generate the firmware and export it to a img by mix firmware.burn -d x.img, and use StarWind V2V Converter convert it to vmdk, then run it at vmware workstation (16.2.3)

Current behavior

hangup up at tsc

Expected behavior

run well

default.mp4
@fhunleth
Copy link
Member

fhunleth commented Feb 9, 2023

I'm afraid that none of us use VMWare Workstation so we can't help with why this isn't working. My guess would be the Linux kernel configuration needs to be different for VMWare.

@helloyan
Copy link
Author

what device should to use for test?

@fhunleth
Copy link
Member

We generally recommend Raspberry Pis (but not the Pico) and Beaglebones for getting started.

@SteffenDE
Copy link

The thing is I'm also seeing the problem of infinite "Waiting for root device" with the kernel config in this repo using QEMU. It works fine with a custom base system that uses a completely different kernel config though (too large to really have a useful comparison). I'll try to investigate...

@SteffenDE
Copy link

So: my QEMU wrapper (UTM) used an IDE disk. Adding CONFIG_ATA_PIIX=y to the kernel config allows it to boot. As VMWare shows an IDE disk too, this could fix the problem there too. The easier solution would probably be to change the disk type to something else.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants