| Hej there,
is there a way to expedite implementation of this PR? This is classified as „non-critical“ and low priority. But for me it looks more like medium or even high priority and it is indeed serious. Without a viogpu netbsd cannot be installed or properly repaired/maintained on hosting services thet do not offer a real serial remote console, only vnc style consoles.
I could not find a way to bump this on gnats, so please, would someone just incorporate that code into -curent and upcoming releases? I am under the assumption that vio is supposed to be generic, given the recent changes in the config files. Since I do not know wether this change has an effect on other architectures that aarch64, that should be considered. I compiled 10.99.14 for amd64 which seems ok, but I do not run that architecture on kvm systems other than netbsd xen…
Cheers Oskar
Greetings, I apologize for bumping such an old thread, but I hope this may be found useful. On 12/18/23 22:47, oskar%fessel.org@localhost wrote: netcup support tinkered around with the images i sent them and came to the same > conclusion that Lloyd suggested in a private conversation: the vm expects kernel > messages and in effect any interaction with the console using graphics calls to the > gpu instead of just a plain text console. There is no plan on implementing that, > currently. And i think, we don't plan to implement console over GPU, right?
The wscons driver for the virtio-gpu device ported in this PR should allow console interaction in your case: https://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=58681I would think the patch included in the PR should apply to the 10.0 sources. Without console access, it is possible you could take an approach similar to the one detailed here, assuming netcup has something analagous to Hetzner's rescue mode (or another means of accessing the root disk from another OS): https://www.unitedbsd.com/d/1262-howto-run-netbsd-on-hetzner-cloud Regards, George
|