Re: Alpine-virt vmd guest tsc directive
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 Message ‐‐‐ On Monday, June 29, 2020 3:14 PM, Dave Voutila wrote: > On Mon, Jun 29, 2020 at 10:57 AM Martin martin...@protonmail.com 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 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 count with P0 frequency! > > tsc: Fast TSC calibration failed > > tsc: Unable to calibrate against PIT > > tsc: No referece (HPET/PMTIMER) available > > tsc: Marking TSC unstable due to could not calculate TSC khz > > ... > > Honestly, chasing Linux tsc issues will waste your time. If you're > using a -current snapshot, build https://github.com/voutilad/vmm_clock > and load it as a Linux kernel module and give up chasing tsc > calibration issues for now unless you want to get intimately familiar > with the Linux kernel. > > > Dave, I've never asked about qcow2 or raw disks in any of my previous email. > > Apologies...saw another Martin (mar...@sukany.cz) reply to the same > subject and thought you were the same Martin :-) > > -Dave
Re: Alpine-virt vmd guest tsc directive
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.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
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 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 g.lis...@nodeunit.com 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
> > > > 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
Re: Alpine-virt vmd guest tsc directive
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 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 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).
>
> > 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 g.lis...@nodeunit.com 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 g.lis...@nodeunit.com 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 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
AMDGPU
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 as well, in that undergoing a CPU intensive task will freeze up the entire system. Disabling all power management options and setting the amdgpu_vm_update_mode to 3 lessens the occurrence of this, and using an HDMI connection instead of a DisplayPort with said modifications seemingly eliminates it. Just switching amdgpu_vm_update_mode to 3 without anything else leads to issues, in which when launching X in which only a small square of seemingly random pixels are displayed. Using a vanilla kernel, only "Waiting for fences timed out!" appears. However, turning on amdgpu_debug_vm in amdgpu_drv.c will output quite a few DRM errors for "gmc_v9_0_process_interrupt", sometimes in the tens of thousands. Any hang ups require a hard reboot. With amdgpu_vm_update_mode set to 3, the crash occurs differently in that whichever windows are using a bunch of GPU/CPU time turn a lime green color. They're completely functional at first, however if I keep putting heavy loads on both the screen becomes pixelated on any changed pixels for those windows. I have a huge amount of logs for these, however from a couple weeks of trying to fix it myself they didn't offer much beyond what was stated in this email. Best regards, Charlie
Re: AMDGPU
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. can you show the output when the 20200421 firmware failed to load? you are referring to the following in linux-firmware 20200619 and later? commit f73f82cd4b7506a22a9aa1aa19e009fac3092eef Author: Alex Deucher Date: Mon Jun 15 17:33:26 2020 -0400 amdgpu: add vega20 TA firmware from 20.20 release Based on internal commit: c6aa2bdaa30af815fc257f2b0e50f6c66d74045c Signed-off-by: Alex Deucher Signed-off-by: Josh Boyer amdgpu/vega20_ta.bin | Bin 0 -> 54016 bytes 1 file changed, 0 insertions(+), 0 deletions(-) commit 9ecaba882d78501d2ab2f6bd9407409128b351ed Author: Alex Deucher Date: Mon Jun 15 17:30:20 2020 -0400 amdgpu: update vega20 firmware from 20.20 release Based on internal commit: c6aa2bdaa30af815fc257f2b0e50f6c66d74045c Signed-off-by: Alex Deucher Signed-off-by: Josh Boyer amdgpu/vega20_asd.bin | Bin 147968 -> 160256 bytes amdgpu/vega20_ce.bin| Bin 9344 -> 9344 bytes amdgpu/vega20_me.bin| Bin 17536 -> 17536 bytes amdgpu/vega20_mec.bin | Bin 268048 -> 268048 bytes amdgpu/vega20_mec2.bin | Bin 268048 -> 268048 bytes amdgpu/vega20_pfp.bin | Bin 21632 -> 21632 bytes amdgpu/vega20_sdma.bin | Bin 17408 -> 17408 bytes amdgpu/vega20_sdma1.bin | Bin 17408 -> 17408 bytes amdgpu/vega20_smc.bin | Bin 262912 -> 262912 bytes amdgpu/vega20_sos.bin | Bin 170896 -> 174992 bytes 10 files changed, 0 insertions(+), 0 deletions(-) > There's also an issue that I've been unable to figure out for a while here > as well, in that undergoing a CPU intensive task will freeze up the entire > system. Disabling all power management options and setting the > amdgpu_vm_update_mode to 3 lessens the occurrence of this, and using an > HDMI connection instead of a DisplayPort with said modifications seemingly > eliminates it. Just switching amdgpu_vm_update_mode to 3 without anything > else leads to issues, in which when launching X in which only a small > square of seemingly random pixels are displayed. Using a vanilla kernel, > only "Waiting for fences timed out!" appears. However, turning on > amdgpu_debug_vm in amdgpu_drv.c will output quite a few DRM errors for > "gmc_v9_0_process_interrupt", sometimes in the tens of thousands. Any hang > ups require a hard reboot. With amdgpu_vm_update_mode set to 3, the crash > occurs differently in that whichever windows are using a bunch of GPU/CPU > time turn a lime green color. They're completely functional at first, > however if I keep putting heavy loads on both the screen becomes pixelated > on any changed pixels for those windows. I have a huge amount of logs for > these, however from a couple weeks of trying to fix it myself they didn't > offer much beyond what was stated in this email. this is similar to what is seen on vega10 and other parts
Re: Alpine-virt vmd guest tsc directive
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...@sukany.cz
l: https://www.linkedin.com/in/martins6
> 29. 6. 2020 v 21:53, George :
>
>
> 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 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
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
>>
signature.asc
Description: Message signed with OpenPGP
Re: AMDGPU
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 firmware "amdgpu/vega20_sos.bin" Jun 27 18:58:21 tabr /bsd: [drm] *ERROR* Failed to load psp firmware! Jun 27 18:58:21 tabr /bsd: [drm] *ERROR* sw_init of IP block failed -2 Jun 27 18:58:21 tabr /bsd: drm:pid0:amdgpu_device_init *ERROR* amdgpu_device_ip_init failed Jun 27 18:58:21 tabr /bsd: drm:pid0:amdgpu_attachhook *ERROR* Fatal error during GPU init That's with the old firmware, and yeah that's with the newest firmware. I had to use newer firmware on your newdrm branch as well. Let me know how I can help! :) On Mon, Jun 29, 2020 at 11:50 PM Jonathan Gray wrote: > 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. > > can you show the output when the 20200421 firmware failed to load? > you are referring to the following in linux-firmware 20200619 and later? > > commit f73f82cd4b7506a22a9aa1aa19e009fac3092eef > Author: Alex Deucher > Date: Mon Jun 15 17:33:26 2020 -0400 > > amdgpu: add vega20 TA firmware from 20.20 release > > Based on internal commit: > c6aa2bdaa30af815fc257f2b0e50f6c66d74045c > > Signed-off-by: Alex Deucher > Signed-off-by: Josh Boyer > > amdgpu/vega20_ta.bin | Bin 0 -> 54016 bytes > 1 file changed, 0 insertions(+), 0 deletions(-) > > commit 9ecaba882d78501d2ab2f6bd9407409128b351ed > Author: Alex Deucher > Date: Mon Jun 15 17:30:20 2020 -0400 > > amdgpu: update vega20 firmware from 20.20 release > > Based on internal commit: > c6aa2bdaa30af815fc257f2b0e50f6c66d74045c > > Signed-off-by: Alex Deucher > Signed-off-by: Josh Boyer > > amdgpu/vega20_asd.bin | Bin 147968 -> 160256 bytes > amdgpu/vega20_ce.bin| Bin 9344 -> 9344 bytes > amdgpu/vega20_me.bin| Bin 17536 -> 17536 bytes > amdgpu/vega20_mec.bin | Bin 268048 -> 268048 bytes > amdgpu/vega20_mec2.bin | Bin 268048 -> 268048 bytes > amdgpu/vega20_pfp.bin | Bin 21632 -> 21632 bytes > amdgpu/vega20_sdma.bin | Bin 17408 -> 17408 bytes > amdgpu/vega20_sdma1.bin | Bin 17408 -> 17408 bytes > amdgpu/vega20_smc.bin | Bin 262912 -> 262912 bytes > amdgpu/vega20_sos.bin | Bin 170896 -> 174992 bytes > 10 files changed, 0 insertions(+), 0 deletions(-) > > > There's also an issue that I've been unable to figure out for a while > here > > as well, in that undergoing a CPU intensive task will freeze up the > entire > > system. Disabling all power management options and setting the > > amdgpu_vm_update_mode to 3 lessens the occurrence of this, and using an > > HDMI connection instead of a DisplayPort with said modifications > seemingly > > eliminates it. Just switching amdgpu_vm_update_mode to 3 without anything > > else leads to issues, in which when launching X in which only a small > > square of seemingly random pixels are displayed. Using a vanilla kernel, > > only "Waiting for fences timed out!" appears. However, turning on > > amdgpu_debug_vm in amdgpu_drv.c will output quite a few DRM errors for > > "gmc_v9_0_process_interrupt", sometimes in the tens of thousands. Any > hang > > ups require a hard reboot. With amdgpu_vm_update_mode set to 3, the crash > > occurs differently in that whichever windows are using a bunch of GPU/CPU > > time turn a lime green color. They're completely functional at first, > > however if I keep putting heavy loads on both the screen becomes > pixelated > > on any changed pixels for those windows. I have a huge amount of logs for > > these, however from a couple weeks of trying to fix it myself they didn't > > offer much beyond what was stated in this email. > > this is similar to what is seen on vega10 and other parts >
Re: Alpine-virt vmd guest tsc directive
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 wrote: > On Mon, Jun 29, 2020 at 4:05 PM Martin martin...@protonmail.com 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 > > /home/vmm/guest.qcow2 guest > > I don't believe that syntax was ever correct for vmctl(8). Check your use of > -b.
Re: Alpine-virt vmd guest tsc directive
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 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 options have nothing to do > with each other and even with `vmctl start` it's a flag for a kernel > or custom bios...not an iso. > > > Please check https://man.openbsd.org/vmctl.8 > > Can it be a bug? > > No. > > -Dave
Re: Alpine-virt vmd guest tsc directive
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/update-extlinux.conf tsc=reliable tsc=noirqtime >From first view clock works excellent without any tsc kernel options. 'vmcl stop linux' command shut it down gracefully! Thanks for your work. Great job! Martin ‐‐‐ 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 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 options have nothing to do > with each other and even with `vmctl start` it's a flag for a kernel > or custom bios...not an iso. > > > Please check https://man.openbsd.org/vmctl.8 > > Can it be a bug? > > No. > > -Dave
Re: Alpine-virt vmd guest tsc directive
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 options have nothing to do with each other and even with `vmctl start` it's a flag for a kernel or custom bios...not an iso. > > Please check https://man.openbsd.org/vmctl.8 > > Can it be a bug? No. -Dave
Re: Alpine-virt vmd guest tsc directive
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.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...
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.
Martin
‐‐‐ Original Message ‐‐‐
On Monday, June 29, 2020 4:21 PM, George 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
> > 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
Re: Alpine-virt vmd guest tsc directive
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 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).
> 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 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 g.lis...@nodeunit.com 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 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
> > > > >
Re: Alpine-virt vmd guest tsc directive
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 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 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
Re: Alpine-virt vmd guest tsc directive
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 additional kernel module
build...
Martin
‐‐‐ Original Message ‐‐‐
On Monday, June 29, 2020 4:21 PM, George 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
> > 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
Re: An Athn ar9280 client seems to require cold boots of late?
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 toggling the few bios options but the issue still occurs. I shall try older firmware if newer snapshots or coreboot releases don't solve it. Rebooting it isn't a huge issue for now and I can't really afford any more time. Does anyone have any tips on the best pcengines apu4 bios settings for OpenBSD? I notice some extent acpipci, Perhaps of interest to someone. OpenBSD 6.7-current (GENERIC.MP) #313: Sun Jun 28 22:05:28 MDT 2020 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 1996484608 (1903MB) avail mem = 1921003520 (1832MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0x7ee9e020 (13 entries) bios0: vendor coreboot version "v4.12.0.1" date 05/29/2020 bios0: PC Engines apu4 acpi0 at bios0: ACPI 6.0 acpi0: sleep states S0 S1 S4 S5 acpi0: tables DSDT FACP SSDT MCFG APIC HEST SSDT SSDT HPET acpi0: wakeup devices PWRB(S4) PBR4(S4) PBR5(S4) PBR6(S4) PBR7(S4) PBR8(S4) UOH1(S3) UOH2(S3) UOH3(S3) UOH4(S3) UOH5(S3) UOH6(S3) XHC0(S4) acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimcfg0 at acpi0 acpimcfg0: addr 0xf800, bus 0-64 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD GX-412TC SOC, 998.40 MHz, 16-30-01 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TOPEXT,DBKP,PERFTSC,PCTRL3,ITSC,BMI1,XSAVEOPT cpu0: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 2MB 64b/line 16-way L2 cache cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative cpu0: TSC skew=0 observed drift=0 cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: AMD GX-412TC SOC, 998.19 MHz, 16-30-01 cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TOPEXT,DBKP,PERFTSC,PCTRL3,ITSC,BMI1,XSAVEOPT cpu1: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 2MB 64b/line 16-way L2 cache cpu1: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu1: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative cpu1: TSC skew=32 observed drift=0 cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 2 (application processor) cpu2: AMD GX-412TC SOC, 998.13 MHz, 16-30-01 cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TOPEXT,DBKP,PERFTSC,PCTRL3,ITSC,BMI1,XSAVEOPT cpu2: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 2MB 64b/line 16-way L2 cache cpu2: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu2: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative cpu2: TSC skew=31 observed drift=0 cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: AMD GX-412TC SOC, 998.14 MHz, 16-30-01 cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TOPEXT,DBKP,PERFTSC,PCTRL3,ITSC,BMI1,XSAVEOPT cpu3: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 2MB 64b/line 16-way L2 cache cpu3: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu3: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative cpu3: TSC skew=28 observed drift=0 cpu3: smt 0, core 3, package 0 ioapic0 at mainbus0: apid 4 pa 0xfec0, version 21, 24 pins ioapic1 at mainbus0: apid 5 pa 0xfec2, version 21, 32 pins acpihpet0 at acpi0: 14318180 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (PBR4) acpiprt2 at acpi0: bus 2 (PBR5) acpiprt3 at acpi0: bus 3 (PBR6) acpiprt4 at acpi0: bus 4 (PBR7) acpiprt5 at acpi0: bus 5 (PBR8) acpicpu0 at acpi0: C2(0@400 io@0x1771), C1(@1
Re: An Athn ar9280 client seems to require cold boots of late?
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 (1T1R), ROM rev 13, address 74:f0:6d:7a:42:7f > > Can't seem to shake it with a cold boot. Even if "cold boot" helped, the problem would still be narrowed down much further before it could be addressed. There's no obvious code change anyone could make based on the knowledge that something only works after a cold boot. > However no matter what I do I can't get a connection to my farmhouse > wireless router. It's a DIR822 Dlink. Of course I know that's a low end > router. Recently they recommended a firmware upgrade, and since then I > found that I was unable to set it up for no password, and had to add one, > and then add that password to all the other devices in the house. 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=159100149411516=2 Perhaps that applies to your situation? Could you check if a -current bsd.rd kernel is able to connect to this problematic AP?
Re: Dual boot problem
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.500a07510369b769 >> sd1: 488386MB, 512 bytes/sector, 1000215216 sectors, thin >> sd2 at scsibus1 targ 2 lun 0: >> naa.5002538844584d30 >> sd2: 244198MB, 512 bytes/sector, 500118192 sectors, thin >> >> ERR M basically means that biosboot(8), which is "tagged" with the >> physical location of /boot(8) on the disk, doesn't see the marker >> that indicates that what it is pointing at is actually /boot. The >> windows 10 boot loader is pulling from a disk other than sd0, the pbr >> is pointing at something "correct" if it were sd0, but the Windows >> boot loader is trying to pull it from whatever the new default disk >> is. Maybe. >> >> There may be some bcdedit magic that can say "boot from this other disk" >> which might solve your problem, but I have no idea. A lame way of >> doing this might be to shrink your Windows partition by 1G, and install >> your OpenBSD root partition there, and the rest on sd0. >> > > Rad, thanks Nick! I'm going to poke around with BCDEasy or whatever that > 3rd party software is since it'll be easier to figure out rather than > reading through all the bcdedit documentation. I swear back in the Windows > ntldr days that I was running Windows and OpenBSD on separate disks so I > think this should be doable with their current boot loader. > > Worse comes to worse I'll go with your last suggestion! > I couldn't find any magic with bcdedit/BCDEasy so I shrunk my Windows partition, did a minimal install of OpenBSD way out there at the end of sd2, copied over some of /etc, and it's all good. nihilanon$ fdisk sd2 Disk: sd2 geometry: 31130/255/63 [500118192 Sectors] Offset: 0 Signature: 0xAA55 Starting Ending LBA Info: #: id C H S - C H S [ start:size ] --- *0: 07 0 32 33 -191 24 25 [2048: 3067904 ] NTFS 1: 07191 56 58 - 30875 167 12 [ 3072000: 492945408 ] NTFS 2: A6 30875 167 13 - 31130 158 4 [ 496017408: 4096000 ] OpenBSD 3: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused Next up is OpenVPN, and deciding if I should stick with -stable (most probably) or start trying snapshots again.
iked: macos couldn't connect
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 connecting the VPN
server# ifconfig -a
lo0: flags=8049 mtu 32768
index 4 priority 0 llprio 3
groups: lo
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
inet 127.0.0.1 netmask 0xff00
bge0: flags=8843 mtu 1500
lladdr 50:65:f3:f0:9e:78
index 1 priority 0 llprio 3
groups: egress
media: Ethernet autoselect (1000baseT full-duplex)
status: active
inet6 fe80::5265:f3ff:fef0:9e78%bge0 prefixlen 64 scopeid 0x1
inet6 2a02:2b88:2:2::6e2c:1 prefixlen 64
inet 89.221.223.253 netmask 0xff00 broadcast 89.221.223.255
bge1: flags=8802 mtu 1500
lladdr 50:65:f3:f0:9e:79
index 2 priority 0 llprio 3
media: Ethernet autoselect (none)
status: no carrier
enc0: flags=41
index 3 priority 0 llprio 3
groups: enc
status: active
inet6 2001:470:8c78:a0::1 prefixlen 64
inet 172.24.24.1 netmask 0xff00
bridge0: flags=41
description: switch19-uplink
index 5 llprio 3
groups: bridge
priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp
tap1 flags=3
port 60 ifpriority 0 ifcost 0
tap10 flags=3
port 59 ifpriority 0 ifcost 0
tap6 flags=3
port 58 ifpriority 0 ifcost 0
tap4 flags=3
port 57 ifpriority 0 ifcost 0
tap7 flags=3
port 55 ifpriority 0 ifcost 0
tap3 flags=3
port 52 ifpriority 0 ifcost 0
tap2 flags=3
port 51 ifpriority 0 ifcost 0
tap9 flags=3
port 50 ifpriority 0 ifcost 0
tap8 flags=3
port 49 ifpriority 0 ifcost 0
tap5 flags=3
port 13 ifpriority 0 ifcost 0
tap0 flags=3
port 8 ifpriority 0 ifcost 0
vether0 flags=3
port 6 ifpriority 0 ifcost 0
vether0: flags=8943 mtu 1500
lladdr fe:e1:ba:d0:bd:33
index 6 priority 0 llprio 3
groups: vether
media: Ethernet autoselect
status: active
inet 10.0.0.1 netmask 0xff00 broadcast 10.0.0.255
pflog0: flags=141 mtu 33136
index 7 priority 0 llprio 3
groups: pflog
tap0: flags=8943 mtu 1500
lladdr fe:e1:ba:d1:50:86
description: vm3-if0-namer
index 8 priority 0 llprio 3
groups: tap
status: active
tap5: flags=8943 mtu 1500
lladdr fe:e1:ba:d6:76:2d
description: vm2-if0-klarasukana
index 13 priority 0 llprio 3
groups: tap
status: active
tap8: flags=8943 mtu 1500
lladdr fe:e1:ba:da:34:b7
description: vm5-if0-mail2
index 49 priority 0 llprio 3
groups: tap
status: active
tap9: flags=8943 mtu 1500
lladdr fe:e1:ba:db:53:5b
description: vm5-if1-mail2
index 50 priority 0 llprio 3
groups: tap
status: active
tap2: flags=8943 mtu 1500
lladdr fe:e1:ba:dc:97:99
description: vm4-if0-mail1
index 51 priority 0 llprio 3
groups: tap
status: active
tap3: flags=8943 mtu 1500
lladdr fe:e1:ba:dd:64:70
description: vm4-if1-mail1
index 52 priority 0 llprio 3
groups: tap
status: active
tap7: flags=8943 mtu 1500
lladdr fe:e1:ba:d0:e6:00
description: vm8-if0-xmpp
index 55 priority 0 llprio 3
groups: tap
status: active
tap4: flags=8943 mtu 1500
lladdr fe:e1:ba:d2:3e:83
description: vm7-if0-mda
index 57 priority 0 llprio 3
groups: tap
status: active
tap6: flags=8943 mtu 1500
lladdr fe:e1:ba:d3:f0:9d
description: vm1-if0-sukany
index 58 priority 0 llprio 3
groups: tap
status: active
tap10: flags=8943 mtu 1500
lladdr fe:e1:ba:d4:ba:41
description: vm9-if0-ubuntu
index 59 priority 0 llprio 3
groups: tap
status: active
tap1: flags=8943 mtu 1500
lladdr fe:e1:ba:d5:2b:25
description: vm6-if0-monitor
index 60 priority 0 llprio 3
groups: tap
status: active
This is my sysctl.conf settings:
net.inet.ip.forwarding=1
net.inet6.ip6.forwarding=1
There is my firewall settings
external="bge0"
internal="vether0"
vpn="enc0"
bridge="bridge0"
dns="10.0.0.2"
jabber="10.0.0.9"
jitsi="10.0.0.10"
tcp_pass_in= "{ 22 80 443 25 465 587 143 993 5232 5000 5222 5269 5280 }"
udp_pass_in=" { 53 } "
icmp_types = "{ echoreq, unreach }"
set skip on lo
set loginterface bge0
block in on $external all
set block-policy drop
set timeout {
Re: An Athn ar9280 client seems to require cold boots of late?
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=159100149411516=2 > Perhaps that applies to your situation? Could you check if a -current > bsd.rd kernel is able to connect to this problematic AP? After leaving this up all weekend, the issue seems to have occurred without an ifconfig down command too. Though the down triggers it immediately.
Re: Alpine-virt vmd guest tsc directive
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/update-extlinux.conf before console=ttyS0,115200 and updated it > accordingly. You don't mention which Alpine and kernel version you're using. Also, you don't mention which OpenBSD version...-current or 6.7? Some major fixes just went into -current and look like they were in last night's amd64 snapshots. > > It seems no changes in tsc usage prior to /dev/rtc0 as boot log shows: > ... > * Setting system clock using the hardware clock [UTC] ...hwclock: select() to > /dev/rtc0 to wait for clock tick timed out > * Failed to set the system clock /dev/rtc0 has nothing to do with the tsc or clocksource. This looks like a separate issue and your guest isn't properly using the emulated mc146818 device. I'm guessing there are bigger issues here. > ... > > Does somebody know some way how set tsc as default clock source in Alpine > 5.4.43-1-virt guest? > Add the linux boot arg: clocksource=tsc But in all honesty, if you want better Linux guest stability, you'll need to use a -current snapshot. Regarding your comment about disks in your other email...what you saw with qcow2 vs raw probably has nothing to do with the emulated disks and everything to do with the stability improvements now in -current. -Dave
Re: An Athn ar9280 client seems to require cold boots of late?
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 helps is: First: #/bin/sh /sbin/ifconfig athn0 /sbin/ifconfig athn0 down -inet -inet6 -join bbk1 -wpakey -chan -bssid /sbin/ifconfig athn0 Second: Disabling the hotspot on bbk1 and re-enabling it Third: sh -x /etc/netstart athn0 This prevents to do a coldboot on the APU2 - reducing downtime. AND: It works reliably everytime since month! Regards, Stefan > -Ursprüngliche Nachricht- > Von: owner-m...@openbsd.org Im Auftrag > von Austin Hook > Gesendet: Sonntag, 28. Juni 2020 23:43 > An: Kevin Chadwick > Cc: misc@openbsd.org > Betreff: Re: An Athn ar9280 client seems to require cold boots of late? > > > 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 (1T1R), ROM rev 13, address 74:f0:6d:7a:42:7f > > Can't seem to shake it with a cold boot. However I have some interesting > other effects. I have several wireless routers, one of which is quite old > and doesn't even do wpa. It's a UBNT antenna that I use to broadcast > around the farm. So without any password at all, even the old kind, if I > > ifconfig athn0 -wpakey > ifconfig athn0 nwid UBNT > dhclient athn0 > > That works fine. > > Now, I can also project wireless from my cellphone using wpa2. Sometimes it > works and sometimes it doesn't. I don't know if it's after a cold boot of the > laptop, but what does work for me it to just disable the hotspot from the > cellphone for a moment, and then re-enable it. Then it works fine with the > nwid I set up and the wpa2 password I require. > > However no matter what I do I can't get a connection to my farmhouse > wireless router. It's a DIR822 Dlink. Of course I know that's a low end > router. > Recently they recommended a firmware upgrade, and since then I found > that I was unable to set it up for no password, and had to add one, and then > add that password to all the other devices in the house. > > Just now I saw that I can enable projecting a separate "guest" zone network > from it, and that seems to allow having a null password. However neither > with a null password nor with an 8 letter password and can I get it to connect > to the ASUS athn0 > > I think I have had athn problems before with the ASUS, and I used to have a > spare USB wireless of some sort that was more reliable, but I gave it away, > after not having such problems with some other more recent releases (but > before 6.7). Wish I could remember what it was. > > If anyone has a recommendation for a reliable USB wireless stick that I can > find on eBay, and plays well with athn, I'd be grateful. > > Moreover, if anyone can fix the problem before I go to that extreme, I'll send > him the shirt off my back... Happens I have about 1,000 OpenBSD T-shirts :-) > > Austin > > > > On Fri, 26 Jun 2020, Kevin Chadwick wrote: > > > After upgrading via sysupgrade for a few releases, I have had to cold > > boot to get dhclient athn0 working on an ar9280 in client mode. > > > > Since my latest upgrade to a snapshot of Jun 17 kernel #275 with the > > previous kernel being from Jun 2nd #237. I seem to have to cold boot > > after running ifconfig athn0 down and then back up, where I'm *fairly* > > sure that I didn't need to before that Jun 17th upgrade. ifconfig > > debug mode shows the wireless handshake completing 4/4. Yet dhclient > can't establish a link until cold booted. > > A warm reboot does not resolve the problem. > > > > Has anyone else seen this or can reproduce it? > > > > I'll try a sysupgrade in the meantime but I'm not sure there has been > > any code changes in areas that could resolve it. > >
Re: 6.7 trouble reaching ipmi on supermicro atom
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 - where previously, from 6.6 going back into >> late 4.x land, these systems would hang on reboot until I reset the BMC. > > I stand corrected - the BMC was reset recently enough that I was fooled into > thinking everything was great with the system. Effectively, enabling ipmi in > the kernel in 6.7 doesnt let ipmitool attach to the ipmi I have, thus making > them quasi-not-so-useful boards with 6.7 as is. When I get time I will bisect > the 6.7 changes, I guess. Note that they ran 5.2 through 6.6 and let me > attach ipmitool. Supermicro X7SPE-HF-D525 for those interested, dmesg output > is posted at the start of this thread. /dev/ipmi access should be fixed in -current now thanks to a report from a user who spent the time to bisect.
iked: macos couldn't connect
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 connecting the VPN
server# ifconfig -a
lo0: flags=8049 mtu 32768
index 4 priority 0 llprio 3
groups: lo
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
inet 127.0.0.1 netmask 0xff00
bge0: flags=8843 mtu 1500
lladdr 50:65:f3:f0:9e:78
index 1 priority 0 llprio 3
groups: egress
media: Ethernet autoselect (1000baseT full-duplex)
status: active
inet6 fe80::5265:f3ff:fef0:9e78%bge0 prefixlen 64 scopeid 0x1
inet6 2a02:2b88:2:2::6e2c:1 prefixlen 64
inet 89.221.223.253 netmask 0xff00 broadcast 89.221.223.255
bge1: flags=8802 mtu 1500
lladdr 50:65:f3:f0:9e:79
index 2 priority 0 llprio 3
media: Ethernet autoselect (none)
status: no carrier
enc0: flags=41
index 3 priority 0 llprio 3
groups: enc
status: active
inet6 2001:470:8c78:a0::1 prefixlen 64
inet 172.24.24.1 netmask 0xff00
bridge0: flags=41
description: switch19-uplink
index 5 llprio 3
groups: bridge
priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp
tap1 flags=3
port 60 ifpriority 0 ifcost 0
tap10 flags=3
port 59 ifpriority 0 ifcost 0
tap6 flags=3
port 58 ifpriority 0 ifcost 0
tap4 flags=3
port 57 ifpriority 0 ifcost 0
tap7 flags=3
port 55 ifpriority 0 ifcost 0
tap3 flags=3
port 52 ifpriority 0 ifcost 0
tap2 flags=3
port 51 ifpriority 0 ifcost 0
tap9 flags=3
port 50 ifpriority 0 ifcost 0
tap8 flags=3
port 49 ifpriority 0 ifcost 0
tap5 flags=3
port 13 ifpriority 0 ifcost 0
tap0 flags=3
port 8 ifpriority 0 ifcost 0
vether0 flags=3
port 6 ifpriority 0 ifcost 0
vether0: flags=8943 mtu 1500
lladdr fe:e1:ba:d0:bd:33
index 6 priority 0 llprio 3
groups: vether
media: Ethernet autoselect
status: active
inet 10.0.0.1 netmask 0xff00 broadcast 10.0.0.255
pflog0: flags=141 mtu 33136
index 7 priority 0 llprio 3
groups: pflog
tap0: flags=8943 mtu 1500
lladdr fe:e1:ba:d1:50:86
description: vm3-if0-namer
index 8 priority 0 llprio 3
groups: tap
status: active
tap5: flags=8943 mtu 1500
lladdr fe:e1:ba:d6:76:2d
description: vm2-if0-klarasukana
index 13 priority 0 llprio 3
groups: tap
status: active
tap8: flags=8943 mtu 1500
lladdr fe:e1:ba:da:34:b7
description: vm5-if0-mail2
index 49 priority 0 llprio 3
groups: tap
status: active
tap9: flags=8943 mtu 1500
lladdr fe:e1:ba:db:53:5b
description: vm5-if1-mail2
index 50 priority 0 llprio 3
groups: tap
status: active
tap2: flags=8943 mtu 1500
lladdr fe:e1:ba:dc:97:99
description: vm4-if0-mail1
index 51 priority 0 llprio 3
groups: tap
status: active
tap3: flags=8943 mtu 1500
lladdr fe:e1:ba:dd:64:70
description: vm4-if1-mail1
index 52 priority 0 llprio 3
groups: tap
status: active
tap7: flags=8943 mtu 1500
lladdr fe:e1:ba:d0:e6:00
description: vm8-if0-xmpp
index 55 priority 0 llprio 3
groups: tap
status: active
tap4: flags=8943 mtu 1500
lladdr fe:e1:ba:d2:3e:83
description: vm7-if0-mda
index 57 priority 0 llprio 3
groups: tap
status: active
tap6: flags=8943 mtu 1500
lladdr fe:e1:ba:d3:f0:9d
description: vm1-if0-sukany
index 58 priority 0 llprio 3
groups: tap
status: active
tap10: flags=8943 mtu 1500
lladdr fe:e1:ba:d4:ba:41
description: vm9-if0-ubuntu
index 59 priority 0 llprio 3
groups: tap
status: active
tap1: flags=8943 mtu 1500
lladdr fe:e1:ba:d5:2b:25
description: vm6-if0-monitor
index 60 priority 0 llprio 3
groups: tap
status: active
This is my sysctl.conf settings:
net.inet.ip.forwarding=1
net.inet6.ip6.forwarding=1
There is my firewall settings
external="bge0"
internal="vether0"
vpn="enc0"
bridge="bridge0"
dns="10.0.0.2"
jabber="10.0.0.9"
jitsi="10.0.0.10"
tcp_pass_in= "{ 22 80 443 25 465 587 143 993 5232 5000 5222 5269 5280 }"
udp_pass_in=" { 53 } "
icmp_types = "{ echoreq, unreach }"
set skip on lo
set loginterface bge0
block in on $external all
set block-policy drop
set timeout {
Re: Alpine-virt vmd guest tsc directive
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 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 count with P0 frequency! > tsc: Fast TSC calibration failed > tsc: Unable to calibrate against PIT > tsc: No referece (HPET/PMTIMER) available > tsc: Marking TSC unstable due to could not calculate TSC khz > ... Honestly, chasing Linux tsc issues will waste your time. If you're using a -current snapshot, build https://github.com/voutilad/vmm_clock and load it as a Linux kernel module and give up chasing tsc calibration issues for now unless you want to get intimately familiar with the Linux kernel. > Dave, I've never asked about qcow2 or raw disks in any of my previous email. Apologies...saw another Martin (mar...@sukany.cz) reply to the same subject and thought you were the same Martin :-) -Dave
Alpine-virt vmd guest tsc directive
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 accordingly. It seems no changes in tsc usage prior to /dev/rtc0 as boot log shows: ... * Setting system clock using the hardware clock [UTC] ...hwclock: select() to /dev/rtc0 to wait for clock tick timed out * Failed to set the system clock ... Does somebody know some way how set tsc as default clock source in Alpine 5.4.43-1-virt guest? Martin ‐‐‐ Original Message ‐‐‐ On Wednesday, June 10, 2020 6:36 PM, George wrote: > 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
Re: Alpine-virt vmd guest tsc directive
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 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
Re: Alpine-virt vmd guest tsc directive
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 device,
otherwise you could expect the unexpectable behaviour :)
M>
>
>> 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
>
>
Re: Alpine-virt vmd guest tsc directive
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 count with P0 frequency! tsc: Fast TSC calibration failed tsc: Unable to calibrate against PIT tsc: No referece (HPET/PMTIMER) available tsc: Marking TSC unstable due to could not calculate TSC khz ... Dave, I've never asked about qcow2 or raw disks in any of my previous email. Martin ‐‐‐ Original Message ‐‐‐ On Monday, June 29, 2020 2:11 PM, Dave Voutila wrote: > On Mon, Jun 29, 2020 at 7:23 AM Martin martin...@protonmail.com 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/update-extlinux.conf before console=ttyS0,115200 and updated it > > accordingly. > > You don't mention which Alpine and kernel version you're using. Also, > you don't mention which OpenBSD version...-current or 6.7? Some major > fixes just went into -current and look like they were in last night's > amd64 snapshots. > > > It seems no changes in tsc usage prior to /dev/rtc0 as boot log shows: > > ... > > > > - Setting system clock using the hardware clock [UTC] ...hwclock: > > select() to /dev/rtc0 to wait for clock tick timed out > > - Failed to set the system clock > > /dev/rtc0 has nothing to do with the tsc or clocksource. This looks > like a separate issue and your guest isn't properly using the emulated > mc146818 device. I'm guessing there are bigger issues here. > > > ... > > Does somebody know some way how set tsc as default clock source in Alpine > > 5.4.43-1-virt guest? > > Add the linux boot arg: clocksource=tsc > > But in all honesty, if you want better Linux guest stability, you'll > need to use a -current snapshot. > > Regarding your comment about disks in your other email...what you saw > with qcow2 vs raw probably has nothing to do with the emulated disks > and everything to do with the stability improvements now in -current. > > -Dave
Re: Alpine-virt vmd guest tsc directive
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 > /home/vmm/guest.qcow2 guest I don't believe that syntax was ever correct for vmctl(8). Check your use of -b.
