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://
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 t
Quoth s...@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://
>>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?9boo
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
Wondering the same thing! Good to know - thx.
> On Jan 24, 2022, at 10:01 AM, cinap_len...@felloff.net wrote:
>
> sdvirtio handles both block and scsi type devices.
>
> --
> cianp
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/Te13a
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
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,
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
>> 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
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
>> 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
On 1/16/22, Lyndon Nerenberg (VE7TFX/VE6BBM) 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
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-M
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... F5CD 00B2
Plan 9 from Bell Labsi8042: kbdinit failed
no vga; serial console only
disk loader
cpu0: 5200MHz
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://
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
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
*
> 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 9leg
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...
--
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
--
9fa
21 matches
Mail list logo