On Mon, 29 Jun 2020 14:53:52 -0700
Mike Larkin wrote:
> On Mon, Jun 29, 2020 at 08:25:19PM +, 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 yo
For sure, whatever helps!
Jun 27 18:58:21 tabr /bsd: [drm] *ERROR* sdma_v4_0: Failed to load firmware
"amdgpu/vega20_sdma.bin"
Jun 27 18:58:21 tabr /bsd: [drm] *ERROR* Failed to load sdma firmware!
Jun 27 18:58:21 tabr /bsd: drm:pid0:psp_v11_0_init_microcode *ERROR* psp
v11.0: Failed to load firmwa
On Mon, Jun 29, 2020 at 11:13:49PM -0500, Charlie Burnett wrote:
> Hi,
>
> Wasn’t sure who to tell this to, but with Vega 20 hardware under -current,
> there is an issue with the firmware, where it cannot load. Manually
> installing the latest amdgpu firmware from kernel.org fixes this seemingly.
Hi,
Wasn’t sure who to tell this to, but with Vega 20 hardware under -current,
there is an issue with the firmware, where it cannot load. Manually
installing the latest amdgpu firmware from kernel.org fixes this seemingly.
There's also an issue that I've been unable to figure out for a while here
About a year ago I set Debian by difficult way from official distribution
without modifying official iso and preconfigured console output.
As Mike wrote, it is significantly better to find iso with virtio driver.
Martin
‐‐‐ Original Message ‐‐‐
On Monday, June 29, 2020 9:53 PM, Mike Lar
Dave,
Alpine 3.12 works excellent with your kernel drivers. Absolutely amazing!
I've just built all of them and solve ton of time without experimenting with
tsc kernel options.
virtio_vmmci
virtio_pci_obsd
vmm_clock
I followed all of your recommendations except adding tsc options to
/etc/upda
Thanks, found mistake. Works like a charm!
‐‐‐ Original Message ‐‐‐
On Monday, June 29, 2020 8:51 PM, Dave Voutila wrote:
> On Mon, Jun 29, 2020 at 4:46 PM Martin martin...@protonmail.com wrote:
>
> > According to man vmctl for both: -current and 6.7 -b should be used for
> > base image
According to man vmctl for both: -current and 6.7 -b should be used for base
images. -b works just before kernel+vmm+vmctl -current update.
Please check https://man.openbsd.org/vmctl.8
Can it be a bug?
Martin
‐‐‐ Original Message ‐‐‐
On Monday, June 29, 2020 8:28 PM, Dave Voutila wrot
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.
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.
There is quite nice article how to prepare own headless ISO — for Debian it’s
quite the same …
https://giocher.com/words/2018/ubuntu-on-openbsd-vmm/
S pozdravem / Kind regards
Martin Sukaný
UNIX Engineer, Developer, DevOps specialist
xmpp: mar...@sukany.cz
phone: +420 776 275 713
email: mar...@
Dave,
After build kernel+vmd+vmctl sources from -current I have an issue with
installing a system from *.iso images.
The command below works fine before update, but not now
$ doas vmctl start -m 1G -c -n vmlan -b /home/iso/install67.iso -d
/home/vmm/guest.qcow2 guest
Martin
‐‐‐ Original M
On Mon, Jun 29, 2020 at 08:25:19PM +, 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 s
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
Alpine has minimalist console ready install on ~40Mb *.iso initially if you
chose -virt release. Can be installed out of the box for headless environment.
With some additional env. binaries and configs + docker it grow up to 780Mb in
*.qcow2 image. I suppose it will be a bit higher after additio
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.
I set vmd Debian desktop guest a year ago with 5.2
On Mon, Jun 29, 2020 at 4:46 PM Martin wrote:
>
> According to man vmctl for both: -current and 6.7 -b should be used for base
> images. -b works just before kernel+vmm+vmctl -current update.
Re-read it. You're mixing the `vmctl start` and `vmctl create`
commands. They reuse options but the -b o
On Mon, Jun 29, 2020 at 4:05 PM Martin wrote:
> After build kernel+vmd+vmctl sources from -current I have an issue with
> installing a system from *.iso images.
> The command below works fine before update, but not now
>
> $ doas vmctl start -m 1G -c -n vmlan -b /home/iso/install67.iso -d
> /hom
Hi Dave,
Alpine kernel 5.4.43-1-virt guest openbsd 6.7 stable host. Try to compile vmd
from -current to improve linux guests stability.
set clocksource=tsc in /etc/update-extlinux.conf
run update-extlinux to install boot loader.
Next boot getting this in dmesg:
...
[Frimware Bug]: TSC doesn't
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 configu
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
incon
Hi list,
I'm using Alpine-virt linux (headless linux with 40Mb initial *.iso size) which
has tsc issues. Alpine uses syslinux lightweight boot loader by default. In
order to enable tsc I've added tsc=reliable tsc=noirqtime to
/etc/update-extlinux.conf before console=ttyS0,115200 and updated it
On Mon, Jun 29, 2020 at 10:57 AM Martin wrote:
>
> Hi Dave,
>
> Alpine kernel 5.4.43-1-virt guest openbsd 6.7 stable host. Try to compile vmd
> from -current to improve linux guests stability.
Are you also running a -current kernel? vmm(4) is in the OpenBSD
kernel...vmd(8) is in base.
>
> set c
On Mon, Jun 29, 2020 at 7:23 AM Martin wrote:
>
> Hi list,
>
> I'm using Alpine-virt linux (headless linux with 40Mb initial *.iso size)
> which has tsc issues. Alpine uses syslinux lightweight boot loader by
> default. In order to enable tsc I've added tsc=reliable tsc=noirqtime to
> /etc/upda
On 2020-06-28, obs...@loopw.com wrote:
>
>
>> On Jun 11, 2020, at 10:31 AM, obs...@loopw.com wrote:
>>
>> I didn’t have to bisect! Woo! While ipmitool no longer seems to function,
>> once I enable ipmi in my running kernel I can successfully reboot a 6.7
>> ipmi-of-this-vintage system now - whe
Hi there,
I’ve tried to set up the IKEV2 VPN for my overall devices.
I have the following network topology, where
- vether0 (10.0.0.0/24) network groups some VMs (bridge0 is used as L2 switch
grouping the appripriate tap devices)
- enc0 (172.24.24.0/24) network is intended for the devices connec
Hi,
I am using exactly the same WLE-200NX wifi card in an APU2B4. I have a
BlackBerry KeyONE
running at Android 8.1 / Version ABT975 which I use as hotspot for the APU2.
After setting athn0 down, it is impossible to establish the connection -
without further intervention -
a second time.
What
On 2020-06-29 08:35, Kevin Chadwick wrote:
> After leaving this up all weekend, the issue seems to have occurred without an
> ifconfig down command too. Though the down triggers it immediately.
Perhaps it's a hw issue. I have tried updating the coreboot firmware to see if
it helps as well as togg
Hi there,
I’ve tried to set up the IKEV2 VPN for my overall devices.
I have the following network topology, where
- vether0 (10.0.0.0/24) network groups some VMs (bridge0 is used as L2 switch
grouping the appripriate tap devices)
- enc0 (172.24.24.0/24) network is intended for the devices connec
On Sun, Jun 28, 2020 at 1:13 PM Greg Thomas
wrote:
> On Sun, Jun 28, 2020 at 9:25 AM Nick Holland
> wrote:
>
>>
>> from your dmesg:
>> sd0 at scsibus1 targ 0 lun 0:
>> naa.5000c500b98a130c
>> sd0: 953869MB, 512 bytes/sector, 1953525168 sectors, thin
>> sd1 at scsibus1 targ 1 lun 0:
>> naa.500a
On 2020-06-29 07:36, Stefan Sperling wrote:
> There is one interop problem in 6.7 which has been fixed in -current
> by reverting a change which was committted between 6.6 and 6.7:
> https://marc.info/?l=openbsd-cvs&m=159100149411516&w=2
> Perhaps that applies to your situation? Could you check if
On Sun, Jun 28, 2020 at 03:43:09PM -0600, Austin Hook wrote:
>
> I have a similar problem with the 6.7 release which I just installed today
> on an 8Tb drive I'm using with my older ASUS laptop.
>
> athn0 at pci3 dev 0 function 0 "Atheros AR9285" rev 0x01: apic 2 int 17
> athn0: AR9285 rev 2 (1T
31 matches
Mail list logo
