Are any of you running 9legacy under the vmm hypervisor on OpenBSD? The kernel boots, but complains that it cannot find any fixed disks and panics. I was able to boot 9front, so it looks like 9legacy's virtio drivers might be lagging a bit? --lyndon ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Te13afbfe31e87665-M70c9221f3a817d77039678ed Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #1: Type: text/plain, Size: 1067 bytes --] hi Lyndon N. -- sounds like a lot of work... when oracles virtual box runs the .vhd (the hard drive thingey me bob...) Are you doing any good stuff on plan 9? i have 9vwm and acme appearing on my linux box for emergencies now too... pretty good (through the wine project (i think..)) possibly... -- gets around some of the little extra security features ;; nod nod on the containing window manager.... K.R.C:20225amish ps: looking for ne sponsorship? On Mon, Jan 10, 2022 at 11:31 PM Lyndon Nerenberg (VE7TFX/VE6BBM) < lyndon@orthanc.ca> wrote: > Are any of you running 9legacy under the vmm hypervisor on OpenBSD? > The kernel boots, but complains that it cannot find any fixed disks > and panics. > > I was able to boot 9front, so it looks like 9legacy's virtio > drivers might be lagging a bit? > > --lyndon ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Te13afbfe31e87665-M66a14e0847fb6b0c777db6b7 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription [-- Attachment #2: Type: text/html, Size: 2362 bytes --]
> Are any of you running 9legacy under the vmm hypervisor on OpenBSD? > The kernel boots, but complains that it cannot find any fixed disks > and panics. > > I was able to boot 9front, so it looks like 9legacy's virtio > drivers might be lagging a bit? The sdvirtio driver available as part of 9legacy is up to date compared to 9front, so the issue is probably elsewhere. -- David du Colombier ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Te13afbfe31e87665-M606545f448bd3155a0413649 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
could it be that it is using virtio1.0? see pc/sdvirtio10.c /* * virtio 1.0 disk driver * http://docs.oasis-open.org/virtio/virtio/v1.0/virtio-v1.0.html * * In contrast to sdvirtio.c, this driver handles the non-legacy * interface for virtio disk which uses mmio for all register accesses * and requires a laborate pci capability structure dance to get working. * * It is kind of pointless as it is most likely slower than * port i/o (harder to emulate on the pc platform). * * The reason why this driver is needed it is that vultr set the * disable-legacy=on option in the -device parameter for qemu * on their hypervisor. */ -- cinap ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Te13afbfe31e87665-Me558f02595a3f17cf54ed39e Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
Thanks cinap_lenrek. I've just imported Virtio 1.0 support to 9legacy. Lyndon, please try the latest CD image and let me know if it works for you. -- David du Colombier ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Te13afbfe31e87665-Mab724ba0f33e3df3a8d8aca4 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
David du Colombier writes: > I've just imported Virtio 1.0 support to 9legacy. > Lyndon, please try the latest CD image and let me know if it works for you. Hah! You beat me to it ;-) ISO downloading now, stay tuned ... ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Te13afbfe31e87665-M400da8e1482489f6e7c74e9c Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
It gets a bit further -- now it actually panics :-P : lyndon@orthanc:/u/vm; vmctl start -c clare Connected to /dev/ttyp2 (speed 115200) Boot failed: not a bootable disk PBSR...0000 F5CD 0000 00B2 Plan 9 from Bell Labsi8042: kbdinit failed no vga; serial console only disk loader cpu0: 5200MHz GenuineIntel Core i7 (cpuid: AX 0x206A1 DX 0x79BA97F) ELCR: 02E8 497M memory: 497M kernel data, 0M user, 18M swap panic: no disks (in #S) panic: no disks (in #S) dumpstack ktrace /kernel/path 80018529 81004b10 <<EOF estackx 81004f10 81004ab8=800182bd 81004ac8=8004e3e1 81004aec=800284c8 81004af8=80018529 81004b0c=80018529 81004b10=800182c1 81004b14=800287f1 81004b48=800459ab 81004b68=80056261 81004b70=8005654d 81004b80=80056047 81004b90=80055fde 81004ba4=80056261 81004bc4=80057c0e 81004bd8=80040555 81004be4=800580be 81004be8=800509ce 81004bec=800509e4 81004bf8=800408db 81004c00=80050ff6 81004c10=80041941 81004c14=80042540 81004c1c=80042560 81004c24=80042652 81004c38=8001ef42 81004e7c=80041910 81004e80=8001f64a 81004e94=8004c082 81004e98=8001f675 81004ea8=800142e7 81004ef4=00000000 81004ef8=800141f9 81004efc=00000000 81004f00=00000000 81004f04=00000000 81004f08=00000000 81004f0c=00000000 EOF cpu0: exiting Takes a licking and keeps on ticking... ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Te13afbfe31e87665-M8f40b228d6010ae3f8aaea7a Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
I think the issue is elsewhere, since I've tried on QEMU with both Virtio 1.0 and Virtio legacy and it worked as expected (386 and amd64 kernels). -- David du Colombier ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Te13afbfe31e87665-M0181d94be3c522e41e96f3cf Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
On 1/16/22, Lyndon Nerenberg (VE7TFX/VE6BBM) <lyndon@orthanc.ca> wrote: > It gets a bit further -- now it actually panics :-P > > [ ... ] > > cpu0: 5200MHz GenuineIntel Core i7 (cpuid: AX 0x206A1 DX 0x79BA97F) > ELCR: 02E8 > 497M memory: 497M kernel data, 0M user, 18M swap > panic: no disks (in #S) > panic: no disks (in #S) > dumpstack Why does it say "0M user"? Doesn't sound very promising. Lucio. ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Te13afbfe31e87665-M60bea51a3e90c6263cccd8b1 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
>> cpu0: 5200MHz GenuineIntel Core i7 (cpuid: AX 0x206A1 DX 0x79BA97F) >> ELCR: 02E8 >> 497M memory: 497M kernel data, 0M user, 18M swap >> panic: no disks (in #S) >> panic: no disks (in #S) >> dumpstack > > Why does it say "0M user"? Doesn't sound very promising. This message is displayed by the boot loader (pcboot). There is no user space at that point. -- David du Colombier ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Te13afbfe31e87665-M5757135b8010535605d0c636 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
David du Colombier writes: > I think the issue is elsewhere, since I've tried on QEMU with > both Virtio 1.0 and Virtio legacy and it worked as expected > (386 and amd64 kernels). That could very well be. vmm(4) is still relatively young, so the bug could very well be there. I think at this point we've ruled out the 9legacy kernel as the culprit. --lyndom ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Te13afbfe31e87665-Me20a6318a72ff59e0e01703d Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
>> I think the issue is elsewhere, since I've tried on QEMU with >> both Virtio 1.0 and Virtio legacy and it worked as expected >> (386 and amd64 kernels). > > That could very well be. vmm(4) is still relatively young, so the > bug could very well be there. I think at this point we've ruled > out the 9legacy kernel as the culprit. If it works with 9front, the issue is definitely on our side. Our Virtio drivers are very close to 9front's, so I suspect the issue may be somewhere else. -- David du Colombier ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Te13afbfe31e87665-M34936dda7bd3ea8e8f95aa5e Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
David du Colombier writes: > If it works with 9front, the issue is definitely on our side. > Our Virtio drivers are very close to 9front's, so I suspect > the issue may be somewhere else. If you think that's the case then I need to build out enough local infrastructure to be able to build 9legacy ISOs. Then I can start printfing in the kernel to see if I can track this down. That might take a while, though, as I'm quite hardware constrained right now (thus the attempt at the vmm-based VM). --lyndom ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Te13afbfe31e87665-M0efd869d756a7a4e1bb8945c Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #1: Type: text/plain, Size: 924 bytes --] David, How do your drivers handle a virtio-based CD-ROM? qemu by default uses IDE, or can be configured to use SATA CD-ROM devices, however, OpenBSD's vmd(8) strictly uses a virtio-based CD-ROM. I don't know how the interactions end up differing between hard drive and CD-ROM access in that case, but its something to look at if you weren't aware of it. From OpenBSD 6.9 booted using vmd(8) on OpenBSD 7.0. OpenBSD 6.9 (GENERIC) #464: Mon Apr 19 10:28:56 MDT 2021 ... virtio3 at pci0 dev 4 function 0 "Qumranet Virtio SCSI" rev 0x00 vioscsi0 at virtio3: qsize 128 scsibus2 at vioscsi0: 1 targets cd0 at scsibus2 targ 0 lun 0: <OpenBSD, VMM CD-ROM, 001> removable virtio3: irq 7 ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Te13afbfe31e87665-M1ac8a4dda788d54491c3dbe6 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription [-- Attachment #2: Type: text/html, Size: 1797 bytes --]
sdvirtio handles both block and scsi type devices. -- cianp ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Te13afbfe31e87665-Mbd3ba5c81eb0397f27674ee2 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
Wondering the same thing! Good to know - thx. > On Jan 24, 2022, at 10:01 AM, cinap_lenrek@felloff.net wrote: > > sdvirtio handles both block and scsi type devices. > > -- > cianp ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Te13afbfe31e87665-M067484d77e7bfbc89f4a7a57 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #1: Type: text/plain, Size: 1267 bytes --] I would like to run 9legacy on OpenBSD as well. Unfortunately, I'm still learning and even though finding and ideally contributing solutions to such bugs is a distant goal of mine, my only current option is to run on 9front. In the wiki (https://wiki.9front.org/openbsd-vmm) it says: "Since VMM doesn’t provide any display functionality, 9front’s console has to be redirected to virtual serial port by adding console=0 to plan9.ini. It makes sense to also use display=none while at it. Note that even though you might not have a chance to modify plan9.ini before booting, stopping boot process with an early hit of a key, typing an additional configuration in, and then boot<ENTER> is ought to work." Unfortunately, the only way I know to start a VM under OpenBSD is to set up the vm in /etc/vm.conf, enable and start vmd via rcctl and then connect via SSH or vmctl console. Could someone possibly help me out and explain how I can edit the plan9.ini during the boot process, please? Thank you very much in advance! ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Te13afbfe31e87665-M8fd548688b12d7af925e6fa9 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription [-- Attachment #2: Type: text/html, Size: 2006 bytes --]
[-- Attachment #1: Type: text/plain, Size: 753 bytes --] >>Unfortunately, the only way I know to start a VM under OpenBSD is to set up the vm in /etc/vm.conf, enable and start vmd via rcctl and then connect via SSH or vmctl console. >>Could someone possibly help me out and explain how I can edit the plan9.ini during the boot process, please?9boot allows changing boot args before booting.just type what you want and press enternot sure if it's possible on 9legacy butyou could also make a iso with custom plan9.inistarting vm using vmctl start -c vmname might be helpful for that ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Td42fc10286c3ba40-M45dc18e38daab152516c5962 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription [-- Attachment #2: Type: text/html, Size: 2333 bytes --]
Quoth sml@firstpost.pub: > Unfortunately, the only way I know to start a VM under OpenBSD is to set up the vm in /etc/vm.conf, enable and start vmd via rcctl and then connect via SSH or vmctl console. man vmctl. ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Te13afbfe31e87665-M12edf3a6cc29e7f53dec8c6b Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
When you do the initial install, interrupt the boot sequence and type console=0 as the documentation describes. Install the system as usual, then reboot and log in again using the consoole=0 dance. Once you're logged in you can mount the 9fat partition (9fs 9fat) and then edit /n/9fat/plan9.ini to add the console=0 line. The best way to deal with the vm console interface is to mark the vm as 'disabled' in vm.conf and then start it manually with 'vmctl -c start'. This will get you connected to the bios console early enough for you to interrupt the boot process to type those overrides. Once you have plan9.ini tuned to your satisfaction you can change the vm declaration to 'enabled' and let it autoboot. --lyndon ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Te13afbfe31e87665-M2db8c26d4737e829f7ec39c0 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #1: Type: text/plain, Size: 348 bytes --] can i update after install plan9.ini ? or i must setup OS ? and i can't setup hardware but correct setup on VirtualBox ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Te13afbfe31e87665-M2db22a4072a1cc6a4f32b7a8 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription [-- Attachment #2: Type: text/html, Size: 850 bytes --]