On Mon, 29 Jun 2020 14:53:52 -0700 Mike Larkin <[email protected]> wrote:
> On Mon, Jun 29, 2020 at 08:25:19PM +0000, Martin wrote: > > Setting up Debian as vmm guest is not a trivial procedure and > > require Debian Linux host with KVM installed first to install your > > guest with screen connected. > > Why do you believe this? Setting up debian in vmm is not any harder > than setting up any other distribution. You just need to make sure to > use their install iso that includes virtio. I think I used the > minimal install iso (can't recall the name, might have even been the > netinst one). I did try netinstall and netboot for Ubuntu all with the same result, namely the installer starts and I can see the first curses screen and then I can pick one of the options but no matter which one I do it all ends up the same freezes or errors out: https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-10.4.0-amd64-netinst.iso This one led to the same issue: +------------------------------------------------+ | Debian GNU/Linux installer menu (BIOS mode) | |------------------------------------------------| | Graphical install | | Install | | Advanced options > | | Accessible dark contrast installer menu > | | Help | | Install with speech synthesis | | | | | | | | | | | | | +------------------------------------------------+ Press ENTER to boot or TAB to edit a menu entry Undefined video mode number: 314 Press <ENTER> to see video modes available, <SPACE> to continue, or wait 30 sec Mode: Resolution: Type: 0 F00 80x25 CGA/MDA/HGC Enter a video mode or "scan" to scan for additional modes: and then I cannot type or do anything at all.. I was doing all the setup on OpenBSD 6.7 stable. Cheers, George > > > Once you have your host ready with KVM run a command to set iso up: > > > > qemu-img create -f qcow2 linux.qcow2 128G > > > > kvm -enable-kvm -vnc 127.0.0.1:0 -k en-us -monitor pty -m 2048 -net > > nic -net user -soundhw all -cdrom debian-linux.iso -boot -d -name > > linux -hda linux.qcow2 > > > > Install it and run the machine with VNC connection > > > > kvm -enable-kvm -vnc 127.0.0.1:0 -k en-us -nographic -monitor pty > > -m 2048 -net nic -net user -soundhw all -boot -d -name linux -hda > > linux.qcow > > You don't need to do any of this. > > -ml > > > Onece you do it please mail me back, I'll share next steps > > somewhere. > > > > Martin > > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > > On Monday, June 29, 2020 7:53 PM, George <[email protected]> > > wrote: > > > On 2020-06-29 12:54 p.m., Martin wrote: > > > > > > > George, thanks for your feedback! > > > > I'd prefer OpenBSD in 99% of situations, but now I need to roll > > > > out Docker. Docker = linux. So I have to solve all the major > > > > issues, especially with clock, and run it for a project using > > > > OpenBSD host of course. > > > > > > Work is an imposed 'choice' ;) and yes that is where > > > virtualization shines a little light in the tunnel. > > > > > > > I set vmd Debian desktop guest a year ago with 5.2.x kernel > > > > which boots headless on vmd. Virtual framebuffer used for VNC > > > > connection from the same OpenBSD host by vnc viewer. Works > > > > perfectly, except clock... > > > > > > I would be interested in any instructions you might have on > > > setting that up. > > > > Currently, rebuilt kernel and vmd from -current. Going to make > > > > 5.4.x related vmm_clock module for minimalist Alpine-virt Linux > > > > guest. I'll report about results once done. > > > > > > That would be great. > > > > > > Thanks. > > > > > > > Martin > > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > > > > On Monday, June 29, 2020 4:21 PM, George [email protected] > > > > wrote: > > > > > On 2020-06-29 8:51 a.m., Martin Sukany wrote: > > > > > > > > > > > Hi George, > > > > > > did you solved the issue? I remember that I faces similar > > > > > > thing when I installed headless ubuntu as a guest … My > > > > > > issue was related to the fact that I used ‚boot cdrom‘ > > > > > > directive inside my configuration (seems that there is a > > > > > > bit inconsistency between the man page and the real > > > > > > configuration). This is is a relevant piece of my config: > > > > > > vm "ubuntu" { memory 2G > > > > > > cdrom /data/vms/_iso/mini-serial.iso > > > > > > disk /data/vms/ubuntu.raw interface tap { switch "uplink" } > > > > > > disable } I had bad experience with usage of qcow2 disk > > > > > > format for Linux based guests — especially when you’re > > > > > > trying to do dozens of I/O operations — several disk > > > > > > containers crashed before I migrated them to raw format. if > > > > > > you have more than 4 vms, don’t forget to create > > > > > > another /dev/tap<X> device, otherwise you could expect the > > > > > > unexpectable behaviour :) > > > > > > M> > > > > > > Hello Martin, > > > > > > > > > > Thanks for the pointers. I abandoned my Linux efforts, too > > > > > many issue and things to learn no time now. My goals could be > > > > > satisfied by an OpenBSD VM and it is much better than most > > > > > Linuxes ;). I have been swimming against the current (read > > > > > using things/software/apis/os/tools etc. when people said it > > > > > is not what is supposed to be done) but as of late I find it > > > > > more relaxing going with it ;). Virtualization is such a ... > > > > > mess which like everything else in our lives nowadays is > > > > > designed to cover another mess ... I want to run Linux > > > > > software on OpenBSD because I don't want to dedicate a > > > > > machine to Linux and want to upgrade or run the version I > > > > > want until I want ... I should be free to make that choice > > > > > because of "I", sarcastic here, problem is CPU vendors and OS > > > > > developers have to jump some hoops and add some features to > > > > > make it happen ... and then things happen that the I does not > > > > > like. Thanks for adding this info albeit to the wrong thread, > > > > > I read it because I like Alpine and was thinking of it > > > > > myself, but they don't have a ready console install version > > > > > do they? Cheers, George > > > > > > > > > > > > > Hi guys, > > > > > > > > I apologize if this maybe out of topic even though it > > > > > > > > is truly related to VMM than Debian. > > > > > > > > I am trying to setup a VMM Debian based guest but I'm > > > > > > > > not able to get it to work. I found some description on > > > > > > > > the web about which settings to edit in grub.cfg to > > > > > > > > enable the serial console and created a VM with 10.3 in > > > > > > > > qcow2 disk format in KVM. Now I am trying to start the > > > > > > > > same on OpenBSD 6.7 but keep getting the connected > > > > > > > > message and then just "Rebooting " after I hit some > > > > > > > > keyboard keys seems like baud rate issue but not sure. > > > > > > > > After messing with it for a while now I am getting a > > > > > > > > new error: vmctl: could not open disk image(s) even > > > > > > > > thought the disk is there and readable to the user I > > > > > > > > have setup in vm.conf in fact I have another VM with > > > > > > > > the same configuration and disk with the same > > > > > > > > permissions and in the same location that works (it is > > > > > > > > OpenBSD based). I would greatly appreciate it if > > > > > > > > someone has gone this path and can share some config > > > > > > > > info with me. Cheers and thanks in advance, George > > > > >
