riscv_vm issueshttp://opensource.ieee.org/alfredoh1234-sandbox/riscv_vm/-/issues2020-01-20T17:56:00Zhttp://opensource.ieee.org/alfredoh1234-sandbox/riscv_vm/-/issues/13Running with older Virtualbox, other VM software and other operating systems2020-01-20T17:56:00ZAlfredo HerreraRunning with older Virtualbox, other VM software and other operating systems*Created by: jeremybennett*
# Ubuntu
## Virtualbox
I was able to get the OVA image working with Ubuntu 17.10 and VirtualBox 5.1.34. You will need the Virtualbox extension pack:
```
sudo apt install virtualbox-ext-pack
```
I don't...*Created by: jeremybennett*
# Ubuntu
## Virtualbox
I was able to get the OVA image working with Ubuntu 17.10 and VirtualBox 5.1.34. You will need the Virtualbox extension pack:
```
sudo apt install virtualbox-ext-pack
```
I don't get a usable console, but with the default NAT settings I can
connect over SSH:
```
ssh -X -A user@192.168.56.101
```
which means I can then fire up Eclipse from the command line.
## Virtual Machine Manager
VMM cannot yet handle OVA files. However the OVA image is just a tar of a file image and some settings. Untar the OVA and you get a vmdk file, which VMM can convert and use.
# Fedora
## Virtualbox
We couldn't get the OVA image to work on Fedora 27. We can get Virtualbox to run, but when it loads the OVA image, it tries to use some Oracle kernel modules which are not signed.
## Virtual Machine Manager
We used exactly the same approach as with Ubuntu, and the system fired up just fine. However it didn't have a network adapter, so unlike Ubuntu we had no external network connectivity.
http://opensource.ieee.org/alfredoh1234-sandbox/riscv_vm/-/issues/14no adapter on macOS2020-01-20T18:14:57ZAlfredo Herrerano adapter on macOS*Created by: hossein1387*
Same as instruction for Ubuntu 18.04LTS host, the step 5 in Ubuntu 18.04LTS host instruction needs to be done on macOS hosts. *Created by: hossein1387*
Same as instruction for Ubuntu 18.04LTS host, the step 5 in Ubuntu 18.04LTS host instruction needs to be done on macOS hosts. http://opensource.ieee.org/alfredoh1234-sandbox/riscv_vm/-/issues/15How to connect to Serial port on board2020-01-20T17:56:52ZAlfredo HerreraHow to connect to Serial port on board*Created by: jonahgraham*
To connect to the serial port on the target board from the VM you need to do two things:
1. Set rules in VM to give normal user permission (extracted from StackOverflow) this creates a new file.
a. `sudo n...*Created by: jonahgraham*
To connect to the serial port on the target board from the VM you need to do two things:
1. Set rules in VM to give normal user permission (extracted from StackOverflow) this creates a new file.
a. `sudo nano /etc/udev/rules.d/50-myusb.rules`
b. Add this to the file:
```
KERNEL=="ttyUSB[0-9]*",MODE="0666"
KERNEL=="ttyACM[0-9]*",MODE="0666"
```
c. Save and exit
2. Connect the USB in VirtualBox to the VM
a. Open the VM in VirtualBox - you may need to take it out of headless mode to do this
b. From Devices menu -> USB -> Check "ARM DAPLink ..."
http://opensource.ieee.org/alfredoh1234-sandbox/riscv_vm/-/issues/12Zephyr requires dtc_1.4.6 or higher.2020-01-20T17:55:45ZAlfredo HerreraZephyr requires dtc_1.4.6 or higher.*Created by: jcps07*
Zephyr requires dtc_1.4.6 or higher. You could use the one from Zephyr SDK (not included in VM image) or easily update it with the following commands:
`curl -L http://mirrors.kernel.org/ubuntu/pool/main/d/device-...*Created by: jcps07*
Zephyr requires dtc_1.4.6 or higher. You could use the one from Zephyr SDK (not included in VM image) or easily update it with the following commands:
`curl -L http://mirrors.kernel.org/ubuntu/pool/main/d/device-tree-compiler/device-tree-compiler_1.4.7-1_amd64.deb > device-tree-compiler_1.4.7-1_amd64.deb`
`sudo apt install ./device-tree-compiler_1.4.7-1_amd64.deb`http://opensource.ieee.org/alfredoh1234-sandbox/riscv_vm/-/issues/11Cannot ssh to the VM from Windows host2020-01-20T17:55:31ZAlfredo HerreraCannot ssh to the VM from Windows host*Created by: MMI*
The VM appears to create the host only interface with an IP of 192.168.56.101.
However, ssh simply hangs and there's no evidence that VirtualBox set up an interface/route/whatever on the Windows side on that network.
...*Created by: MMI*
The VM appears to create the host only interface with an IP of 192.168.56.101.
However, ssh simply hangs and there's no evidence that VirtualBox set up an interface/route/whatever on the Windows side on that network.
Windows ipconfig tells me:
`Ethernet adapter VirtualBox Host-Only Network:
Connection-specific DNS Suffix . :
Autoconfiguration IPv4 Address. . : 169.254.156.233
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :`
**Solution**:
The problem here is that I had VirtualBox misconfigured... to fix, in the virtualbox manager GUI:
File->Host Network Manager...
Then change the properties for the VirtualBox Host-Only Ethernet Adapter to "Configure Adapter Automatically"
All good for me after thathttp://opensource.ieee.org/alfredoh1234-sandbox/riscv_vm/-/issues/10https://open-isa.org/get-started/ refers to old Eclipse installation2020-01-20T17:55:13ZAlfredo Herrerahttps://open-isa.org/get-started/ refers to old Eclipse installation*Created by: jonahgraham*
The https://open-isa.org/get-started/ has installation instructions for Eclipse, but refers to an old Eclipse that is a bit harder to get working properly.
What this repo installs in the VM is a newer Eclip...*Created by: jonahgraham*
The https://open-isa.org/get-started/ has installation instructions for Eclipse, but refers to an old Eclipse that is a bit harder to get working properly.
What this repo installs in the VM is a newer Eclipse with the GNU MCU tools already bundled.
https://github.com/openhwgroup/riscv_vm/blob/407a8d444f8a05ab21df1a68bcae4a9a4aaf0900/bin/eclipse-mcu_install.sh#L40
I recommend that toolset be used by anyone not using the VM, get it here: https://github.com/gnu-mcu-eclipse/org.eclipse.epp.packages/releases/tag/v4.5.1-20190101-2018-12http://opensource.ieee.org/alfredoh1234-sandbox/riscv_vm/-/issues/17Missing instruction on how to find out the IP address of the risc_vm to ssh i...2020-01-20T17:58:04ZAlfredo HerreraMissing instruction on how to find out the IP address of the risc_vm to ssh into.*Created by: alfredoh1234*
*Created by: alfredoh1234*
http://opensource.ieee.org/alfredoh1234-sandbox/riscv_vm/-/issues/8No instructions on running VM on Linux host2019-09-12T21:17:41ZAlfredo HerreraNo instructions on running VM on Linux host*Created by: jonahgraham*
At the moment the readme has Windows and Mac instructions, but not Linux.*Created by: jonahgraham*
At the moment the readme has Windows and Mac instructions, but not Linux.http://opensource.ieee.org/alfredoh1234-sandbox/riscv_vm/-/issues/9CMake Error with RISCV32GCC_DIR2020-01-20T17:54:51ZAlfredo HerreraCMake Error with RISCV32GCC_DIR*Created by: martinda*
What should be the value of the `RISCV32GCC_DIR` env var? (I tried installing the VM but could not, so I am following the steps from https://open-isa.org/get-started/ directly).
Commands:
```
cd rv32m1_sdk_r...*Created by: martinda*
What should be the value of the `RISCV32GCC_DIR` env var? (I tried installing the VM but could not, so I am following the steps from https://open-isa.org/get-started/ directly).
Commands:
```
cd rv32m1_sdk_riscv/boards/rv32m1_vega/demo_apps/hello_world/ri5cy/riscvgcc
./build_debug.sh
```
Result:
```
CMake Error at /home/martin/riscv/rv32m1_sdk_riscv/tools/cmake_toolchain_files/riscv32gcc.cmake:23 (MESSAGE):
***Please set RISCV32GCC_DIR in envionment variables***
Call Stack (most recent call first):
/usr/share/cmake-3.10/Modules/CMakeDetermineSystem.cmake:91 (include)
CMakeLists.txt
CMake Error: CMake was unable to find a build program corresponding to "Unix Makefiles". CMAKE_MAKE_PROGRAM is not set. You probably need to select a different build tool.
CMake Error: CMAKE_C_COMPILER not set, after EnableLanguage
CMake Error: CMAKE_CXX_COMPILER not set, after EnableLanguage
-- Configuring incomplete, errors occurred!
make: *** No targets specified and no makefile found. Stop.
```
http://opensource.ieee.org/alfredoh1234-sandbox/riscv_vm/-/issues/16windows installer download confusing2020-01-20T17:57:03ZAlfredo Herrerawindows installer download confusing*Created by: alfredoh1234*
It s not obvious how to download the Windows batch script to Windows and if it is required to have a GitHub account or not*Created by: alfredoh1234*
It s not obvious how to download the Windows batch script to Windows and if it is required to have a GitHub account or nothttp://opensource.ieee.org/alfredoh1234-sandbox/riscv_vm/-/issues/7Installing the riscv_vm tools directly on Ubuntu 18.04LT host (UNTESTED)2019-09-12T21:18:45ZAlfredo HerreraInstalling the riscv_vm tools directly on Ubuntu 18.04LT host (UNTESTED)*Created by: jonahgraham*
I think the script mentioned is what is used to build the VM. I don't think it is suitable for users to run on their own machine. I know it says UNTESTED, but here you go with some of the issues.
- Don't ru...*Created by: jonahgraham*
I think the script mentioned is what is used to build the VM. I don't think it is suitable for users to run on their own machine. I know it says UNTESTED, but here you go with some of the issues.
- Don't run apt-get autoremove --purge automatically for users - while normally safe this can have unintended side effects and can really trash someones system. Reality is that if autoremove does break system, there were some configuration problems already, but those problems were probably not causing an error until autoremove was run.
- https://github.com/openhwgroup/riscv_vm/blob/ed96452e24fe33e966ecbaee16be8c55dc7e0eb8/bin/ubuntu_post-install.sh#L57 assumes that normal user is called "user"
- https://github.com/openhwgroup/riscv_vm/blob/ed96452e24fe33e966ecbaee16be8c55dc7e0eb8/bin/ubuntu_post-install.sh#L66 ditto
- https://github.com/openhwgroup/riscv_vm/blob/ed96452e24fe33e966ecbaee16be8c55dc7e0eb8/bin/ubuntu_post-install.sh#L113 avoid changing user's editor
- https://github.com/openhwgroup/riscv_vm/blob/ed96452e24fe33e966ecbaee16be8c55dc7e0eb8/bin/ubuntu_post-install.sh#L84 does not make sense if user is running themself
- Make it more obvious that this script is going to significantly alter their system - I hope anyone would read the script before running it, but best to be upfront about what it does.
My recommendation is to remove the section, or to change it to something like (note the original was missing an S in 18.04LTS):
## Installing the riscv_vm tools directly on Linux
The VM is running Ubuntu 18.04 LTS, as such you can extract installation instructions for installing the tools directly in Linux by consulting the [ubuntu_post-install.sh](https://github.com/openhwgroup/riscv_vm/blob/master/bin/ubuntu_post-install.sh) script.
http://opensource.ieee.org/alfredoh1234-sandbox/riscv_vm/-/issues/5vm3 won't start - missing medium error2019-09-11T00:56:32ZAlfredo Herreravm3 won't start - missing medium error*Created by: rickoco*
On a Mac, vm3 won't start as follows:
_**Could not open the medium '/Users/rickoco/VirtualBox VMs/riscv_vm3/riscv_vm3-disk001.vdi'.
VD: error VERR_FILE_NOT_FOUND opening image file '/Users/rickoco/VirtualBox VM...*Created by: rickoco*
On a Mac, vm3 won't start as follows:
_**Could not open the medium '/Users/rickoco/VirtualBox VMs/riscv_vm3/riscv_vm3-disk001.vdi'.
VD: error VERR_FILE_NOT_FOUND opening image file '/Users/rickoco/VirtualBox VMs/riscv_vm3/riscv_vm3-disk001.vdi' (VERR_FILE_NOT_FOUND).
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
MediumWrap
Interface:
IMedium {ad47ad09-787b-44ab-b343-a082a3f2dfb1}**_
http://opensource.ieee.org/alfredoh1234-sandbox/riscv_vm/-/issues/4cloning repo creates doesn't run as expected from install scripts2019-09-12T21:19:28ZAlfredo Herreracloning repo creates doesn't run as expected from install scripts*Created by: alfredoh1234*
If cloning repository in an Ubuntu VM guest to build from scripts, the cloned repo will be in a "riscv_vm" sub-directory.
Scripts will fail if user name is not "user" as in *.ova appliance image. Scripts nee...*Created by: alfredoh1234*
If cloning repository in an Ubuntu VM guest to build from scripts, the cloned repo will be in a "riscv_vm" sub-directory.
Scripts will fail if user name is not "user" as in *.ova appliance image. Scripts need to be changed to use the current username instead of hardcoded one.http://opensource.ieee.org/alfredoh1234-sandbox/riscv_vm/-/issues/3Windows10 Device Guard/Credential Guard incompatible with VirtualBox2019-09-10T15:14:16ZAlfredo HerreraWindows10 Device Guard/Credential Guard incompatible with VirtualBox*Created by: alfredoh1234*
Windows10 Device Guard / Credential Guard is incompatible with the virtual machines software like VMware and VirtualBox.*Created by: alfredoh1234*
Windows10 Device Guard / Credential Guard is incompatible with the virtual machines software like VMware and VirtualBox.http://opensource.ieee.org/alfredoh1234-sandbox/riscv_vm/-/issues/6Typo in name of welcome.txt2019-09-12T21:18:59ZAlfredo HerreraTypo in name of welcome.txt*Created by: jonahgraham*
https://github.com/openhwgroup/riscv_vm/blob/ed96452e24fe33e966ecbaee16be8c55dc7e0eb8/bin/ubuntu_post-install.sh#L87 compare to line 122 https://github.com/openhwgroup/riscv_vm/blob/ed96452e24fe33e966ecbaee16be...*Created by: jonahgraham*
https://github.com/openhwgroup/riscv_vm/blob/ed96452e24fe33e966ecbaee16be8c55dc7e0eb8/bin/ubuntu_post-install.sh#L87 compare to line 122 https://github.com/openhwgroup/riscv_vm/blob/ed96452e24fe33e966ecbaee16be8c55dc7e0eb8/bin/ubuntu_post-install.sh#L122http://opensource.ieee.org/alfredoh1234-sandbox/riscv_vm/-/issues/2Not able to connect to VM through SSH2019-09-10T15:10:09ZAlfredo HerreraNot able to connect to VM through SSH*Created by: alfredoh1234*
After following the install instructions and launching the VM, I am unable to ssh into the VM from a terminal window*Created by: alfredoh1234*
After following the install instructions and launching the VM, I am unable to ssh into the VM from a terminal windowhttp://opensource.ieee.org/alfredoh1234-sandbox/riscv_vm/-/issues/1Host-only port preventing VM to start on Windows host2020-01-20T17:54:04ZAlfredo HerreraHost-only port preventing VM to start on Windows host*Created by: alfredoh1234*
The OVA-appliance image has two ethernet ports configured:
* **enp0s03** is a NAT port used to connect to the internet, but **NOT** the host
* **enp0s8** is a Host-only port used to communicate with ...*Created by: alfredoh1234*
The OVA-appliance image has two ethernet ports configured:
* **enp0s03** is a NAT port used to connect to the internet, but **NOT** the host
* **enp0s8** is a Host-only port used to communicate with the host to enable the X11 forwarding over ssh
* If the VM fails to launch after importing the *.ova appliance image, look at the logs by selecting:
- [Machine]->[Show Log…] from the VirtualBox menu
- or with the keyboard shortcut [Ctrl+L].
* Look for the an error message that starts with “Failed to open/create the internal network…”.