-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
tools/create-openbsd-gce-ci.sh: Add VMM configuration #722
Conversation
@mptre this shows the complete configuration of the the VM. These are the commands I run that fail to start the VM:
|
I am not merging this until we resolve the problems, right? |
Added verification of successful package install.
I simply reused the same image that I used to start the VM on GCE and demonstrated injection of freshly-built kcov-enabled kernel into the nested VM. The missing piece is VMM networking configuration, in case we need it. I can also work on creating smaller images for nested VMs as we hopefully shouldn't really need as much stuff on the small VMs as on the ci machine. |
The missing piece is VMM networking configuration, in case we need it.
Assuming the VM template has the `local interface` present, you should
be able to access the VM via `100.64.X.3` from the host where `X` is the
ID of the VM (check `vmctl status`).
|
Try to add -L flag to vmctl. I also don't have local networking without it. |
Yes, it's working just fine with -L and I can ssh into the nested VM via the address @mptre suggested. This is the command I was using: ci-openbsd$ vmctl start syzkaller-1 -t syzkaller -b /syzkaller/src/sys/arch/amd64/compile/SYZKALLER/obj/bsd -d /syzkaller/disk.raw -c -L I say this PR is good to go in as is and we'll go from there. |
Added verification of successful package install.
Related to #712
@mptre