Difference between revisions of "Vnx-rootfsopenbsd"
(Created page with "{{Title|How to create a KVM OpenBSD root filesystem for VNX}} Follow this procedure to create a KVM OpenBSD based root filesystem for VNX. The procedure has been tested with ...") |
(→Basic installation) |
||
Line 27: | Line 27: | ||
The OS installer will offer to reboot, but do not do that. Instead, kill the VM window and then, in the host OS, interrupt with Ctrl-C the kvm program. | The OS installer will offer to reboot, but do not do that. Instead, kill the VM window and then, in the host OS, interrupt with Ctrl-C the kvm program. | ||
+ | |||
+ | |||
+ | == Configuration == | ||
+ | |||
+ | <ul> | ||
+ | <li>Start the system with the following command:</li> | ||
+ | vnx --modify-rootfs vnx_rootfs_kvm_openbsd.qcow2 --update-aced --mem 512M --arch x86_64 | ||
+ | Note: ignore the errors "timeout waiting for response on VM socket". | ||
+ | |||
+ | |||
+ | <li>Access the system through the text console to easy the copy-paste of commands:</li> |
Revision as of 17:54, 2 May 2016
How to create a KVM OpenBSD root filesystem for VNX
Follow this procedure to create a KVM OpenBSD based root filesystem for VNX. The procedure has been tested with OpenBSD 5.8.
Basic installation
- Create the filesystem disk image:
qemu-img create -f qcow2 vnx_rootfs_kvm_openbsd.qcow2 12G
wget http://ftp.eu.openbsd.org/pub/OpenBSD/5.8/amd64/install58.iso cp install58.iso /almacen/iso
vnx --create-rootfs vnx_rootfs_kvm_openbsd64.qcow2 --install-media /almacen/iso/openbsd-install58.iso --mem 512M --arch=x86_64
tty00 "/usr/libexec/getty std.9600" dialup off secure
to:
tty00 "/usr/libexec/getty std.9600" vt100 on secure
chroot /mnt config -ef /bsd disable mpbios quit
halt -p
The OS installer will offer to reboot, but do not do that. Instead, kill the VM window and then, in the host OS, interrupt with Ctrl-C the kvm program.
Configuration
- Start the system with the following command:
vnx --modify-rootfs vnx_rootfs_kvm_openbsd.qcow2 --update-aced --mem 512M --arch x86_64
Note: ignore the errors "timeout waiting for response on VM socket".