Opened 2 years ago

Last modified 2 years ago

#12599 assigned Task/To do item

setup new virtual guest

Reported by: https://id.mayfirst.org/jamie Owned by: https://id.mayfirst.org/jaimev
Priority: High Component: Tech
Keywords: Cc:
Sensitive: no

Description

We have a new member who needs a virtual guest setup.

They don't want us to have access at all, so you can use a pp file like vandana.pp for a template.

Please leave the parent email address empty and I'll fill it in.

At this point, I think cleaver is the best host for new guests.

Let's set it up with 3GB of RAM and 75 GB disk.

Please do the full debian install, but leave it as is after the initial reboot (console login screen).

Then, add the following ssh key to the non-privileged user account on cleaver:

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQCtvADNc4hbjKTqddkLEKLyca7epK+qMYbNGm/1h9uv/sG2EJ7j9Y15ebWokmAdZ7wFxgpBcse7Tt+1MLlqOUKuCg9Sf6f6bEpHuVH8KIcHJz+u953posyDQcuX7W2qfGJkvOcmHShjwumHpX/QQygiSVS82BEP5ZU8/y08NLDjosLBsr6acWVu77D086oZMWzjRvNxYPVZcOj1aN5CXK0rLxxrvOibbR8tpZ4voZyBU+W2+k5o9zYybzjq2B9Mnrj1pA4K2Chr1frQcUx/+m1poJmaXTvRdftEKB6w/p4X+rJFsJd6uBWddYD+0NZm4XYBRTQ0wQAX1SSLcy8QFiykPvcoMGKkBeifc4KMrvQoqOjVoDmxeT+pXtWRZLThGfsR0WM4iU7MM0zuPpcLNzGku4xrlc32F43egVVU4ij0WDPqWKaS32u+1ZoxGxqSKyT0v82fWiO4DwTuVeUDIIPlsSeZDnsX/LcwHBwR5LWjU74YGBwUUJreZN03WztX4ZRPC8RNQ2qQsNjfrS7x4Vkq2f9AyHOzy+wsvHO/3sy/5EMsQwIutqIJyG+R3agCTmnG5iK/wfMdkbRqNQAyGioLPHO+qC9gQx4qkqMzhwiajBblxVfk8g/eI7MWaF06mXxKu4vtmEAPbqNfk/LuNGSXOb+shM+LkAyUdYCI3+rxIw==
faciallyrecognized@riseup.net

After setup, re-assign to me and I can notify.

Thanks!

jamie

Change History (8)

comment:1 Changed 2 years ago by https://id.mayfirst.org/jamie

  • Owner set to https://id.mayfirst.org/jaimev
  • Status changed from new to assigned
  • Type changed from Bug/Something is broken to Task/To do item

comment:2 Changed 2 years ago by https://id.mayfirst.org/jaimev

Getting the following from the installer for new vm nanny on cleaver.

        ┌───────────────────┤ [!!] Partition disks ├───────────────────┐
        │                                                              │
        │ The attempt to mount a file system with type ext4 in LVM VG  │
        │ vg_nanny0, LV root at / failed.                              │
        │                                                              │
        │ You may resume partitioning from the partitioning menu.      │
        │                                                              │
        │ Do you want to resume partitioning?                          │
        │                                                              │
        │     <Go Back>                              <Yes>    <No>     │
        │                                                              │
        └──────────────────────────────────────────────────────────────┘

comment:3 Changed 2 years ago by https://id.mayfirst.org/jaimev

This was in the installer output at the beginning of the install, not sure if it is related.

mount: mounting /dev/vda on /media failed: Invalid argument
umount: can't umount /media: Invalid argument
mount: mounting /dev/vda on /media failed: Invalid argument
mount: mounting /dev/vda on /media failed: Invalid argument
umount: can't umount /media: Invalid argument
mount: mounting /dev/vda on /media failed: Invalid argument
mount: mounting /dev/fd0 on /media failed: No such file or directory
umount: can't umount /media: Invalid argument
mount: mounting /dev/fd0 on /media failed: No such file or directory

comment:4 Changed 2 years ago by https://id.mayfirst.org/jaimev

These bug reports suggest our debian-installer image might need to use a newer kernel.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852012

https://bugs.kali.org/view.php?id=3701

comment:5 Changed 2 years ago by https://id.mayfirst.org/jaimev

I've run updates on cleaver without rebooting. I tried deleting the iso and running freepuppet-run again to build a new ISO on but got the same result from the new iso.

comment:6 Changed 2 years ago by https://id.mayfirst.org/jaimev

I found ticket #5263 and followed solution to delete both /usr/local/share/ISOs/default.iso and <guestname>.iso before regenerating with freepuppet-run. That solved the above problem.

comment:7 Changed 2 years ago by https://id.mayfirst.org/jaimev

I've finished the install, placed the above key in /var/lib/monkeysphere/authorized_keys/nanny and sent an e-mail

Will that file will be rewritten by future updates vía monkeysphere?

comment:8 Changed 2 years ago by https://id.mayfirst.org/jaimev

Oh... just realized you actually can place a key in ~/.ssh/authorized_keys and when monkeysphere-authentication update-user is run it will be included in the above file.

Please login to add comments to this ticket.

Note: See TracTickets for help on using tickets.