NVMM not working, NetBSD 9x amd64
Hello,
I'm curious about the situation on the NVMM front. On its page it says
that it works both with Intel and AMD cpu's
(https://m00nbsd.net/4e0798b7f2620c965d0dd9d6a7a2f296.html), but I've
read elsewhere
(https://blog.netbsd.org/tnf/entry/the_hardware_assisted_virtualization_challenge)
that it only works on AMD - so who is right?
1. I tried it on my PC, but it didn't work. My CPU is Intel(R)
Core(TM)2 Duo CPU T9600, Vt-x enabled.
First I used the NetBSD 9.0 amd64 release version:
localhost# modload nvmm
modload: nvmm: Operation not permitted
/var/log/messages:
Apr 25 14:40:33 localhost /netbsd: [ 902.3991765] WARNING: module
error: use -f to reinstate builtin module `nvmm'
localhost# modload -f nvmm
modload: nvmm: Not supported
Apr 25 14:55:11 localhost /netbsd: [ 1781.0615600] [!] No implementation found
Apr 25 14:55:11 localhost /netbsd: [ 1781.0615600] WARNING: module
error: built-in module nvmm failed its MODULE_CMD_INIT, error 86
I took the current kernel (NetBSD 9.99.56), uncommented
"#pseudo-device nvmm" and compiled it, but after I booted it I got the
same errors when trying to load the module.
I'm not sure this is down to my CPU being not AMD, or am I wrong here?
2. Also I've got a question about qemu. The 'vanilla' qemu from pkgsrc
(that is recommended on the m00nbsd page) doesn't know the accelerator
'nvmm'.
localhost$ qemu-system-x86_64 -hda ubuntu.qcow -cdrom
/mnt/ubuntu-16.04.4-desktop-amd64.iso -m 1024M -accel nvmm
qemu-system-x86_64: -machine accel=nvmm: No accelerator found
Qemu-nvmm is deleted from pkgsrc/wip at the moment:
https://pkgsrc.se/wip/qemu-nvmm
3. Trying the nvmmctl utility ('nvmmctl identify' and 'nvmmctl list')
results in panic and following reboot after a long count, see
screenshots for output:
https://drive.google.com/open?id=1vT0WZbRp8x97qPjGIiNf0GF4PvBezu2H
https://drive.google.com/open?id=13hl3Z3FMkX6dLZcpL3LXydIMdSqq4qDZ
(Of course 2. and 3. refer to a situation without the nvmm module loaded)
Andrei
Re: Changes to PERL
Are you talking about Perl5 or Perl6? These are actually 2 different languages. вт, 14 апр. 2020 г. в 00:11, Todd Gruhn : > > Where is a good place to look for current PERL syntax and examples? > (been about 10yrs). > > Which books should be updated first? > (I have 4 of the O'Reilly PERL books)
Re: green lines hell
ср, 26 февр. 2020 г. в 20:15, Dave B : > > On Tue, Feb 25, 2020 at 11:35:31PM +0300, Andrei M. wrote: > > In all recent major versions of NetBSD/amd64, incl. NetBSD 9.0 error > > notifications from the kernel are forwarded in green colour to the > > first vt. In my case it mostly concerns notifications about hardware > > probing going on or when a connection change happens to the net card > > (I use an ASUS K70ID laptop). It happens every few minutes, looks > > terrible from the aesthetic point of view, when you're typing > > something and then this breaks your line, even within vi, and can even > > be some sort of security threat when it messes up the password prompt. > > > > It's usually recommended to switch to vt2, vt3 etc. in order to avoid > > seeing these notifications. But this is not possible, when you're > > installing the OS. Installation menus get broken by this green flood > > and then are redrawn below, turning the whole thing into a complete > > mishmash. Here's some screenshots: > ... > > I don't think this was already mentioned--my apologies if it was: > > "L" helps a lot when I start seeing pages in the installer > become disarrayed by the kernel's green output (it refreshes the > screen); and I'm not sure this feature is mentioned anywhere in the > installer's text. > > I doubt that's the full-fledged solution you're looking for... > however, maybe it'll make a helpful difference until you have an > answer that's closer to the mark. > > L is functional in a signifant portion of the installer. In > fact, a quick "thank you" to the installer's authors for having it > in there. Thanks! No, this wasn't mentioned, I'll keep this in mind next time I'll try to do installation. Andrei
Re: green lines hell
ср, 26 февр. 2020 г. в 12:04, Riccardo Mottola : > > Hi ANdrei, Hi Riccardo, > > It is "normal" for any BSD system I have seen to spit these out. > However, the issue for you here is that they should not repeat like this. > I think it is your mouse that is connecting/reconnecting several times. > I have seen that happen, coul d be bad power saving or something similar. > > Try changing mouse? Or disconnect it since you don't even need it. This is actually the 3d mouse I've been using so far, so I guess this has rather to do with the board. And it's not only down to the mouse, network card and the battery driver produce messages of the same kind. > Riccardo
Re: green lines hell
ср, 26 февр. 2020 г. в 13:33, Benny Siegert : > > On Tue, Feb 25, 2020 at 9:36 PM Andrei M. wrote: > > In all recent major versions of NetBSD/amd64, incl. NetBSD 9.0 error > > notifications from the kernel are forwarded in green colour to the > > first vt. In my case it mostly concerns notifications about hardware > > probing going on or when a connection change happens to the net card > > (I use an ASUS K70ID laptop). It happens every few minutes, looks > > terrible from the aesthetic point of view, when you're typing > > something and then this breaks your line, even within vi, and can even > > be some sort of security threat when it messes up the password prompt. > > When I last installed OpenBSD, it did the same, except in white on > blue. Worse, it would print it onto whichever console you were on (I > think). OK, I tried to install OpenBSD and FreeBSD on this laptop a few years ago and there wasn't issues like that. But as I decided to stick to NetBSD I haven't had experience with those OSes anymore. > In NetBSD, kernel messages go to a VT called "console", which is the > first VT by default. Once you finish the installation, you can edit > /etc/ttys, set console to "off" and ttyE0 to "on". This turns the > first VT into a regular VT, and kernel messages go nowhere by default. > Or you could connect the console to a serial port. Or if you run X, > Xconsole is typically able to show kernel messages in a window. Yes, thanks for this, that's not a problem as long as you're booted and can adjust the system. But not in the installer sadly. Then, I do a lot of stuff in Linux and I'm used to work in the first VT without thinking twice, where kernel messages just go to the system log.
green lines hell
In all recent major versions of NetBSD/amd64, incl. NetBSD 9.0 error notifications from the kernel are forwarded in green colour to the first vt. In my case it mostly concerns notifications about hardware probing going on or when a connection change happens to the net card (I use an ASUS K70ID laptop). It happens every few minutes, looks terrible from the aesthetic point of view, when you're typing something and then this breaks your line, even within vi, and can even be some sort of security threat when it messes up the password prompt. It's usually recommended to switch to vt2, vt3 etc. in order to avoid seeing these notifications. But this is not possible, when you're installing the OS. Installation menus get broken by this green flood and then are redrawn below, turning the whole thing into a complete mishmash. Here's some screenshots: https://drive.google.com/open?id=12YTQt7t8q5mX-X0uJ-sitTTKJWg5xSat https://drive.google.com/open?id=1Nkmpwfg6ybkpLfGHCbnkVwVIhMLgV-q9 https://drive.google.com/open?id=1MPKRrFCHCiBOwDWzuTA61wBcvK1TuDXn https://drive.google.com/open?id=1t0HG8NRywz6CmYZx0CBk8bx07WS3nV5h https://drive.google.com/open?id=1mM3cgyJZL2y20XX0B2T8iaJ9kMjx3kU5 https://drive.google.com/open?id=1ZdK8pzIgGJ1PmXDwxVBHhvkXOdE-kLcL https://drive.google.com/open?id=1r5u26pPmYx6Eeq_FZsnT4zrgDj6SnaC6 I've never seen anything like that in other BSD's or Linux distros that I've had on the same computer. So I'm wondering if these green notifications are of such importance to someone, why not to reserve for them one vt (not vt1) where no input from user would be assumed? And of course it would be good to shut them down in the installation system. Andrei
Re: Cannot boot NetBSD under qemu-kvm
пт, 21 февр. 2020 г. в 09:02, Julien Savard : > > Hi, > it seems that since my last fedora upgrade ( 30 -> 31 ) I cannot boot any > NetBSD Guest running on KVM-Qemu. > Actual version on Fedora 31 is qemu-kvm-4.1.1-1. > NetBSD 8.0/8.1 On HD hang on : "NetBSD/x86 ffsv2 Primary Bootstrap" > NetBSD 9.0 booting on CD(iso) hangs on "acpicpu1: at cpu1: ACPI CPU". > Booting with ACPI disabled ( boot -2) hangs on : "attimer0: attached to > pcppi0" > I tried on 2 different x86_64 hosts. One Intel ( Core 2) based and the other > AMD (Opteron) based. > Booting OpenBSD or Linux works wells Only NetBSD seems to be an issue. > Has anybody experienced this issue? I've got the same problem, tried to boot NetBSD 9.0-STABLE (latest as of 23.02.2002) via virt-manager/kvm and the installation froze on "acpicpu0 at cpu0: ACPI CPU". My system is Ubunto 16.04.4. Here's the screenshot that I made of the output: https://drive.google.com/open?id=115X4fpINsZ8tnPznWD5aqhhM7aikAtVA
Re: netbsd : internals : bach book : good to start-off?
чт, 25 июл. 2019 г. в 08:33, Germain Le Chapelain : > > On Mon, 22 Apr 2019 12:25:07 +0700 > Robert Elz wrote: > > > | i know and fully acknowledge that i will have to work hard to understand > > | netbsd internals, and the currently, the only way to do so is by reading > > | the source, over and over again till i get comfortable with it. > > > > Yes, nothing beats that. and for NetBSD, as there is no book that > > actually describes it (that I know of) that will, for many aspects, > > be the only choice. > > > There is a book litteraly called `NetBSD Internals' in the documentation > section of the website: > > http://netbsd.org/docs/internals/en/netbsd-internals.html > > > Sounds like the best complement to the Bach, since it focuses on the > implementation and extending NetBSD. Far from being complete though: 3.3. Processes and threads creation 3.3.1. fork, clone, and pthread_create usage XXX write me 3.3.2. Overview of fork code path XXX write me 3.3.3. Overview of pthread_create code path XXX write me 3.4. Processes and threads termination 3.4.1. exit, and pthread_exit usage XXX write me 3.4.2. Overview of exit code path XXX write me 3.4.3. Overview of pthread_exit code path XXX write me 3.5. Signal delivery 3.5.1. Deciding what to do with a signal XXX write me etc etc > > (I don't know why I get back to such old messages: I was checking for update > on my thread, came across this one and felt like sharing, > It's because this is one thing that drove me- or, more so, cemented me-to > NetBSD: its perfect website ;) ) > > > -- > Germain >
Re: Can not Download NetBSD 8.0 i386 USB Install Image
чт, 31 янв. 2019 г. в 18:14, JingYuan Chen : > > AhhI forgot to describe more detail about my problem. > I used Firefox to download i386 USB install image form NetBSD's download page. > > The URL is as follows : > https://cdn.netbsd.org/pub/NetBSD/NetBSD-8.0/images/NetBSD-8.0-i386-install.img.gz > > After clicking the link, firefox shows that the source file can not be > read. So that I try to download > i386 ISO image. But the error message is the same. > > There may be something wrong with amd64 ISO image. I had downloaded > amd64 ISO image last Sunday. > But I can not download it now. Firefox responds File not found. :( > > Is there something wrong with cdn.netbsd.org ??? > Has been happening to me today too. I've tried to download the following file 5 or 6 times: http://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-8/latest/images/NetBSD-8.0_STABLE-amd64-install.img.gz When download is 99,99% completed, it says 'Download failed' and cannot be resumed. Experienced in Firefox and Chrome, Ubuntu 64bit versions. Andrei
Re: NetBSD-7.1-amd64: IMG install problems / missing checksum
2017-05-26 0:04 GMT+03:00 Leonardo Taccari : > Hello Andrei! > > > Can you please try to use `/dev/sdb' instead of `/dev/sdb1'? > (WARNING: this will completely erase your USB drive!, but will > hopefully fix the problems you are seeing! :)) Thank you Leonardo! A silly mistake indeed, now everything is working. Nevertheless, hopefully there will be checksums for the .img files as well. Andrei
NetBSD-7.1-amd64: IMG install problems / missing checksum
Hello, I've downloaded NetBSD-7.1-amd64 install image: http://ftp.netbsd.org/pub/NetBSD/iso/7.1/NetBSD-7.1-i386-install.img.gz and put it to a USB drive: sudo dd if=/media/andrei/Storage/NetBSD-7.1-amd64-install.img of=/dev/sdb1 bs=1M Booting from the USB didn't go giving the following output: NetBSD MBR boot No Operating system When I tried to mount the flash drive (from within Linux): sudo modprobe ufs sudo mount -t ufs -o ufstype=44bsd /dev/sdb1 /mnt/netbsd I got "wrong fs type, bad option, bad superblock on /dev/sdb1". Dmesg says: "ufs: ufs_fill_super(): bad magic number". Unfortunately there's no checksum for .img in the SHA512 file (http://ftp.netbsd.org/pub/NetBSD/iso/7.1/SHA512), only for ISO's, so I can't check the image file, but I have downloaded it from two sources (the master site and torrent) and both downloads were identical. Has anyone had success with 7.1 using this particular install method? Andrei
NetBSD 7.1 amd64 boot failure on KVM
Hello all,
I've encountered a problem with running NetBSD 7.1 as guest on
KVM/qemu as experienced previously with 7.0:
https://mail-index.netbsd.org/netbsd-users/2015/12/31/msg017550.html
The output is practically the same, even the same values for registers:
vmt0 at cpu0: Unknown
vmware: open failed, eax=564d5868, ecx=001e, edx=5658
vmt0: failed to open backdoor RPC channel (TCLO protocol)
Host machine - Linux Ubuntu 64 bit, qemu-kvm 1:2.5+dfsg-5ubunbtu10.14,
the guest machine (NetBSD 7.1) run through Virtual Machine Manager.
I've tried different memory values, between 512 MB and 1.5 GB (I
wasn't allowed to set more, even though my PC has 4GB), with the same
result.
The output refers to the following lines in NetBSD/sys/arch/x86/x86/vmt.c:
306 vmt_attach (device_t parent, device_t self, void *aux):
...
336 if (vm_rpc_open(&sc->sc_tclo_rpc, VM_RPC_OPEN_TCLO) != 0) {
337aprint_error_dev(self, "failed to open backdoor RPC channel
(TCLO protocol)\n");
338goto free;
339}
http://bxr.su/NetBSD/sys/arch/x86/x86/vmt.c
Andrei
Re: Phoronix 8-way-BSD-install - NetBSD bombed
You know, despite all 7.0 has been a HUGE improvement performance-wise on my main laptop (it's the same one since 2010) compared to the 6.x series and whatever was before. I've just upgraded to 7.0.1, let's see how it works. 2016-09-14 18:17 GMT+03:00 : > I feel that for home users, -current may be a good choice. > > netbsd 7.0 is entirely unusable on much of my hardware. desktop was > extra bad. no USB3 means USB keyboard interrupts are lost or something, > need to boot with ACPI disabled (disables hyperthreading), cannot install > from USB, lack of graphical acceleration for nvidia cards means when > running old Xorg it took 1 minute to run a command like 'su', new Xorg > can handle until X is shut down once (all fixed in -current). >
Re: Phoronix 8-way-BSD-install - NetBSD bombed
2016-09-13 2:48 GMT+03:00 : > No USB3 support on NetBSD-7.0. I had the same. Requires twiddling with > BIOS options to even boot the installer. > Hopefully 7.1 will have merged by release (planned), -current already > does, and it works well. > In my case USB installation (7.0) didn't work either, the system didn't see my HD, only the USB disk. So CD was the only option.
Re: Phoronix 8-way-BSD-install - NetBSD bombed
2016-09-12 1:13 GMT+03:00 Michael van Elst :
> lingvofact...@gmail.com ("Andrei M.") writes:
>
>>> That's why it might be interesting to find out why ahcisata fails for you.
>
>>Are there any kernel debug facilities on the installation distro?
>
> Not much. You can boot the kernel with the -x parameter, but capturing
> the dmesg output without a serial console is difficult.
>
OK, I can try to record it on video :) Will try it shortly.
Andrei
Re: Phoronix 8-way-BSD-install - NetBSD bombed
2016-09-11 23:40 GMT+03:00 Michael van Elst :
> lingvofact...@gmail.com ("Andrei M.") writes:
>
>>As I previousy wrote, I switched from SATA to IDE mode in BIOS (after
>>which everything started working), so the system no longer recognizes
>>ahcisata. Here's the output for my HD and CD:
>
> That's why it might be interesting to find out why ahcisata fails for you.
Are there any kernel debug facilities on the installation distro?
> --
> --
> Michael van Elst
> Internet: mlel...@serpens.de
> "A potential Snark may lurk in every tree."
Re: Phoronix 8-way-BSD-install - NetBSD bombed
As I previousy wrote, I switched from SATA to IDE mode in BIOS (after
which everything started working), so the system no longer recognizes
ahcisata. Here's the output for my HD and CD:
wd0 at atabus0 drive 0
wd0:
wd0: drive supports 16-sector PIO transfers, LBA48 addressing
wd0: 465 GB, 969021 cyl, 16 head, 63 sec, 512 bytes/sect x 976773168 sectors
wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
atapibus0 at atabus1: 2 targets
cd0 at atapibus0 drive 0: cdrom removable
cd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100)
2016-09-11 12:33 GMT+03:00 Michael van Elst :
> lingvofact...@gmail.com ("Andrei M.") writes:
>
>>No, this happened when the installation CD was loading. I've had
>>exactly the same problem in the installation process last year, see
>>attachment.
>
> The screenshot shows
>
> two SATA devices that couldn't be recognized.
> one USB umass device.
>
> The information about the CD has either scrolled off, or it's
> one of the SATA devices, probably the latter (with only 1.5Gb/s on
> the second port).
>
> Can you identify your ahcisata controller? E.g.:
>
> ahcisata0 at pci0 dev 31 function 2: vendor 0x8086 product 0x8c02 (rev. 0x04)
> ahcisata0: interrupting at ioapic0 pin 19
> ahcisata0: 64-bit DMA
> ahcisata0: AHCI revision 1.30, 6 ports, 32 slots, CAP
> 0xc730ff45
>
> --
> --
> Michael van Elst
> Internet: mlel...@serpens.de
> "A potential Snark may lurk in every tree."
Re: Phoronix 8-way-BSD-install - NetBSD bombed
2016-09-10 18:05 GMT+03:00 Andrei M. : > No, this happened when the installation CD was loading. I've had > exactly the same problem in the installation process last year, see > attachment. > > > 2016-09-10 2:49 GMT+03:00 Michael van Elst : >> swiftgri...@gmail.com (Swift Griggs) writes: >> >>>I wonder what happened in his case. I can tell he's re-using the same box >>>and drive from his FreeBSD install, but I've done that many times and >>>never had a problem (other than being annoyed at 'dk' devices showing up). >>>I just wipe the disk and start over. >> >> Well, he didn't wipe the disk and either he just didn't recognize >> "root device:" as a prompt for input or, more probable, the keyboard >> driver (USB?) failed. >> >> But neither should happen during installation. My guess is that sysinst >> didn't clean the disk and the screenshot comes from booting the installed >> system. >> >> >> -- >> -- >> Michael van Elst >> Internet: mlel...@serpens.de >> "A potential Snark may lurk in every tree."
Re: Phoronix 8-way-BSD-install - NetBSD bombed
Mike Larabel of Phoronix had the same problem with installation of NetBSD 7.0 a year ago: http://www.phoronix.com/scan.php?page=news_item&px=BSD-Linux-Late-2015 In fact I experienced it last year myself, but some good guy told me to change the BIOS settings for HD from SATA to legacy/IDE and after that installation process indeed went on. Now it's about time for myself to register at Phoronix forum and give this advice to Larabel, hopefully he well pay more attention to NetBSD from this moment on. Andrei 2016-09-09 19:35 GMT+03:00 D'Arcy J.M. Cain : > On Fri, 9 Sep 2016 10:00:49 -0600 (MDT) > Swift Griggs wrote: >> http://www.phoronix.com/scan.php?page=article&item=trying-8-bsds&num=2 >> >> I wonder what happened in his case. I can tell he's re-using the same >> box and drive from his FreeBSD install, but I've done that many times >> and never had a problem (other than being annoyed at 'dk' devices >> showing up). I just wipe the disk and start over. > > I always dd nulls to a disk that was used for another OS before > starting a new install. > >> Phoronix is a pretty Linux-centric site. I have some suspicions is > > Specifically I have had issues installing NetBSD to a drive that had > Linux (Red Hat) on it. It's been a while but I think that the > behaviour he saw is what I saw. I ran dd to clean everything off the > drive and then it worked just fine. > > In any case I have my doubts about someone who claims to have written > 10,000 articles over the last twelve years. For what it's worth: > > http://jonimoose.net/2013/moronix-why-amd-wont-take-michael-larabel-seriously-and-you-shouldnt-either/ > > > -- > D'Arcy J.M. Cain > http://www.NetBSD.org/ IM:da...@vex.net
Re: tmux overhead
The Linux version of tmux is notorious for a noticeable CPU overload too (try Google 'tmux CPU usage'), something to do with the original design. 2016-01-22 1:59 GMT+03:00 John Klos : > Hi, all, > > Since tmux is part of a standard NetBSD install, I've been using it instead > of screen. So far, so good. However, I've noticed that it accumulates a LOT > of CPU time even when the underlying tty and shell are doing absolutely > nothing. On a 60 MHz m68060 system that's been up for 53 days, for instance, > and with a shell that's sitting at a quiet prompt: > > 25403 john 850 6144K 2312K kqueue44.1H 4.05% 4.05% tmux > > 44 HOURS? Wow. And while it's otherwise idle, it's taking around 4% CPU. > > Ideas about why this is so busy? > > John
Re: Firsts in NetBSD
Hello, NetBSD was among pioneers to support Xen, although I'm not sure it superceded Linux and others. Hope this helps, Andrei 2016-01-07 21:13 GMT+03:00 Swift Griggs : > > I'm writing some documentation for a class I'm teaching soon at my job. One > section covers various BSD's (each separate) contribution to features in the > collective endowment of Unix variants out there. > > Here are the things I believe NetBSD was first at doing. Can anyone else > think of ones that'd be worthy of note to a group of up-and-coming Unix > geeks ? > > * First with a USB stack (beat Linux didn't it?) > * First with TCP Auto tuning (Linux's autotune based on NetBSD's strategy) > * First with Free ports to Alpha, HPPA, and MIPS (true?) > > I know there are more NetBSD "first to do XYZ". Does anyone care to correct > those three or give me some more? Thanks in advance, friends. > > -Swift
