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.

Sign up for GitHub

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

Jump to bottom

Properly setup ssh access to qemu #3

Closed
5 tasks done
arichardson opened this issue Jan 28, 2016 · 0 comments
Closed
5 tasks done

Properly setup ssh access to qemu #3

arichardson opened this issue Jan 28, 2016 · 0 comments
Assignees
@arichardson

Comments

@arichardson
Copy link
Member

  • used port on host machine must be configurable
  • Install a ssh host key that doesn't change when disk image is rebuilt
  • setup the right authorized_keys entries so passwordless login works?
  • add mtree entries
  • add PermitRootLogin without-password to sshd_config
arichardson added a commit that referenced this issue Jan 28, 2016
@arichardson
setup rc.conf for SSH
58e538d 
First step towards getting #3 done
arichardson added a commit that referenced this issue Jan 28, 2016
@arichardson
Forward QEMU guest port 22 to host port 9999
fbc5a2a 
This allows initial ssh connections, but as there is only a root user
and sshd is setup to disallow root login it won't work yet (for #3)
@arichardson arichardson self-assigned this Jan 28, 2016
arichardson added a commit that referenced this issue Feb 16, 2016
@arichardson
Generate SSH host keys before building the disk image
b5b8399 
This way we don't always need to accept a new host key whenever we connect to
the virtual machine. To regenerate the host keys just delete the /etc/ssh
directory in the extra-files tree

One step closer to implementing #3
arichardson added a commit that referenced this issue Mar 11, 2016
@arichardson
Add PermitRootLogin without-password to /etc/ssh/sshd_config
c6a9d46 
Now we can really login as root on the cheribsd VM

Actually fixes #3
arichardson added a commit that referenced this issue Mar 4, 2020
@arichardson
Prefer full LTO (-flto) over ThinLTO for QEMU (-flto=thin)
1024f66 
This seems to be measurably faster and does not appear to impact compile
time too much.

hyperfine '~/cheribsd-boot-benchmark.sh /local/scratch/alr48/cheri/output/sdk/bin/qemu-system-cheri128.fulllto.8f17bc88e6b' '~/cheribsd-boot-benchmark.sh /local/scratch/alr48/cheri/output/sdk/bin/qemu-system-cheri128.thinlto.8f17bc88e6b' '~/cheribsd-boot-benchmark.sh /local/scratch/alr48/cheri/output/sdk/bin/qemu-system-cheri128.without-lto.8f17bc88e6b'
Benchmark #1: ~/cheribsd-boot-benchmark.sh /local/scratch/alr48/cheri/output/sdk/bin/qemu-system-cheri128.fulllto.8f17bc88e6b
  Time (mean ± σ):      2.395 s ±  0.062 s    [User: 2.233 s, System: 0.159 s]
  Range (min … max):    2.341 s …  2.545 s    10 runs

Benchmark #2: ~/cheribsd-boot-benchmark.sh /local/scratch/alr48/cheri/output/sdk/bin/qemu-system-cheri128.thinlto.8f17bc88e6b
  Time (mean ± σ):      2.470 s ±  0.015 s    [User: 2.311 s, System: 0.167 s]
  Range (min … max):    2.453 s …  2.502 s    10 runs

Benchmark #3: ~/cheribsd-boot-benchmark.sh /local/scratch/alr48/cheri/output/sdk/bin/qemu-system-cheri128.without-lto.8f17bc88e6b
  Time (mean ± σ):      2.520 s ±  0.024 s    [User: 2.367 s, System: 0.159 s]
  Range (min … max):    2.488 s …  2.563 s    10 runs

Summary
  '~/cheribsd-boot-benchmark.sh /local/scratch/alr48/cheri/output/sdk/bin/qemu-system-cheri128.fulllto.8f17bc88e6b' ran
    1.03 ± 0.03 times faster than '~/cheribsd-boot-benchmark.sh /local/scratch/alr48/cheri/output/sdk/bin/qemu-system-cheri128.thinlto.8f17bc88e6b'
    1.05 ± 0.03 times faster than '~/cheribsd-boot-benchmark.sh /local/scratch/alr48/cheri/output/sdk/bin/qemu-system-cheri128.without-lto.8f17bc88e6b'
@pig-pig-yang pig-pig-yang mentioned this issue Nov 29, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@arichardson arichardson

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@arichardson