Installer doesn't see sd0 on qemu guest 6.5-current

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

Installer doesn't see sd0 on qemu guest 6.5-current

Maksym Sheremet
There is a 6.5-current VM running with QEMU on linux host. Usually the
VM is being updated to the latest snapshot once per 10 days. Everything
was OK with with 2019-04-21 snapshot. The problem has been appeared
since 2019-05-01 snapshot.

The VM is installed on a dedicated drive with FDE. It is detected as sd0
by bsd.rd booted from install65.iso. But once installer is started the
drive disappears. Here is full output:

>> OpenBSD/amd64 CDBOOT 3.43
boot>
cannot open cd0a:/etc/random.seed: No such file or directory
booting cd0a:/6.5/amd64/bsd.rd: 3691345+1532928+3889096+0+598016
[373454+128+451752+300829]=0xa58318
entry point at 0xffffffff81001000
Copyright (c) 1982, 1986, 1989, 1991, 1993
 The Regents of the University of California.  All rights reserved.
Copyright (c) 1995-2019 OpenBSD. All rights reserved.
 https://www.OpenBSD.org

OpenBSD 6.5-current (RAMDISK_CD) #50: Fri May 31 20:22:49 MDT 2019
    [hidden email]:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
real mem = 2130558976 (2031MB)
avail mem = 2062069760 (1966MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xf5b10 (9 entries)
bios0: vendor SeaBIOS version "1.12.0-20181126_142135-anatol"
date 04/01/2014
bios0: QEMU Standard PC (i440FX + PIIX, 1996)
acpi0 at bios0: rev 0
acpi0: tables DSDT FACP APIC
acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: QEMU Virtual CPU version 2.5+, 2295.00 MHz, 06-06-03
cpu0:
FPU,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,CX16,x2APIC,HV,NXE,LONG,LAHF,MELTDOWN
cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB
64b/line 16-way L2 cache
cpu0: ITLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
cpu0: DTLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
cpu0: apic clock running at 1000MHz
ioapic0 at mainbus0: apid 0 pa 0xfec00000, version 11, 24 pins
acpiprt0 at acpi0: bus 0 (PCI0)
acpicpu at acpi0 not configured
"ACPI0006" at acpi0 not configured
"PNP0A03" at acpi0 not configured
acpicmos0 at acpi0
"PNP0A06" at acpi0 not configured
"PNP0A06" at acpi0 not configured
"PNP0A06" at acpi0 not configured
"QEMU0002" at acpi0 not configured
"ACPI0010" at acpi0 not configured
pvbus0 at mainbus0: KVM
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel 82441FX" rev 0x02
"Intel 82371SB ISA" rev 0x00 at pci0 dev 1 function 0 not configured
pciide0 at pci0 dev 1 function 1 "Intel 82371SB IDE" rev 0x00: DMA,
channel 0 wired to compatibility, channel 1 wired to compatibility
pciide0: channel 0 disabled (no drives)
pciide0: channel 1 disabled (no drives)
uhci0 at pci0 dev 1 function 2 "Intel 82371SB USB" rev 0x01: apic 0
int 11
"Intel 82371AB Power" rev 0x03 at pci0 dev 1 function 3 not configured
vga1 at pci0 dev 2 function 0 "Bochs VGA" rev 0x02
vga1: aperture needed
wsdisplay1 at vga1 mux 1: console (80x25, vt100 emulation)
virtio0 at pci0 dev 3 function 0 "Qumranet Virtio Network" rev 0x00
vio0 at virtio0: address 08:00:27:77:c1:d5
virtio0: msix shared
virtio1 at pci0 dev 5 function 0 "Qumranet Virtio Storage" rev 0x00
vioblk0 at virtio1
scsibus0 at vioblk0: 2 targets
sd0 at scsibus0 targ 0 lun 0: <VirtIO, Block Device, > SCSI3 0/direct
fixed
sd0: 114473MB, 512 bytes/sector, 234441632 sectors
virtio1: msix shared
virtio2 at pci0 dev 6 function 0 "Qumranet Virtio Memory Balloon" rev
0x00
virtio2: no matching child driver; not configured
ahci0 at pci0 dev 7 function 0 "Intel 82801I AHCI" rev 0x02: apic 0
int 11, AHCI 1.0
ahci0: port 0: 1.5Gb/s
scsibus1 at ahci0: 32 targets
cd0 at scsibus1 targ 0 lun 0: <QEMU, QEMU DVD-ROM, 2.5+> ATAPI 5/cdrom
removable
usb0 at uhci0: USB revision 1.0
uhub0 at usb0 configuration 1 interface 0 "Intel UHCI root hub" rev
1.00/1.00 addr 1
isa0 at mainbus0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com0: console
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard, using wsdisplay1
softraid0 at root
scsibus2 at softraid0: 256 targets
root on rd0a swap on rd0b dump on rd0b
erase ^?, werase ^W, kill ^U, intr ^C, status ^T

Welcome to the OpenBSD/amd64 6.5 installation program.
(I)nstall, (U)pgrade, (A)utoinstall or (S)hell? s
# bioctl -c C -l /dev/sd0a softraid0
bioctl: could not open /dev/sd0a: No such file or directory
# ls /dev
MAKEDEV cua01   klog    rcd0c   rrd0c   rwd0g   rwd0o   ttyC0   wd0g    wd0o
bio     diskmap kmem    rd0a    rst0    rwd0h   rwd0p   urandom wd0h    wd0p
bpf     enrst0  ksyms   rd0c    rwd0a   rwd0i   stderr  wd0a    wd0i    wskbd0
bpf0    erst0   mem     rfd0a   rwd0b   rwd0j   stdin   wd0b    wd0j    wskbd1
cd0a    fd0a    nrst0   rfd0b   rwd0c   rwd0k   stdout  wd0c    wd0k    wskbd2
cd0c    fd0b    null    rfd0c   rwd0d   rwd0l   tty     wd0d    wd0l    xf86
console fd0c    random  rfd0i   rwd0e   rwd0m   tty00   wd0e    wd0m    zero
cua00   fd0i    rcd0a   rrd0a   rwd0f   rwd0n   tty01   wd0f    wd0n


Does anyone know the cause of this problem?

Thanks.

--
MS

Reply | Threaded
Open this post in threaded view
|

Re: Installer doesn't see sd0 on qemu guest 6.5-current

Patrick Wildt-3
As you can see in dmesg, it actually sees sd0, and it does not detach.
Instead, the device node just isn't in /dev, because the insaller does
create that on the fly.  Since you are not using the installer, you
have to manually type cd /dev && sh MAKEDEV sd0

On Sat, Jun 01, 2019 at 09:08:58PM +0300, Maksym Sheremet wrote:

> There is a 6.5-current VM running with QEMU on linux host. Usually the
> VM is being updated to the latest snapshot once per 10 days. Everything
> was OK with with 2019-04-21 snapshot. The problem has been appeared
> since 2019-05-01 snapshot.
>
> The VM is installed on a dedicated drive with FDE. It is detected as sd0
> by bsd.rd booted from install65.iso. But once installer is started the
> drive disappears. Here is full output:
>
> >> OpenBSD/amd64 CDBOOT 3.43
> boot>
> cannot open cd0a:/etc/random.seed: No such file or directory
> booting cd0a:/6.5/amd64/bsd.rd: 3691345+1532928+3889096+0+598016
> [373454+128+451752+300829]=0xa58318
> entry point at 0xffffffff81001000
> Copyright (c) 1982, 1986, 1989, 1991, 1993
>  The Regents of the University of California.  All rights reserved.
> Copyright (c) 1995-2019 OpenBSD. All rights reserved.
>  https://www.OpenBSD.org
>
> OpenBSD 6.5-current (RAMDISK_CD) #50: Fri May 31 20:22:49 MDT 2019
>     [hidden email]:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
> real mem = 2130558976 (2031MB)
> avail mem = 2062069760 (1966MB)
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xf5b10 (9 entries)
> bios0: vendor SeaBIOS version "1.12.0-20181126_142135-anatol"
> date 04/01/2014
> bios0: QEMU Standard PC (i440FX + PIIX, 1996)
> acpi0 at bios0: rev 0
> acpi0: tables DSDT FACP APIC
> acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: QEMU Virtual CPU version 2.5+, 2295.00 MHz, 06-06-03
> cpu0:
> FPU,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,CX16,x2APIC,HV,NXE,LONG,LAHF,MELTDOWN
> cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB
> 64b/line 16-way L2 cache
> cpu0: ITLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
> cpu0: DTLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
> cpu0: apic clock running at 1000MHz
> ioapic0 at mainbus0: apid 0 pa 0xfec00000, version 11, 24 pins
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpicpu at acpi0 not configured
> "ACPI0006" at acpi0 not configured
> "PNP0A03" at acpi0 not configured
> acpicmos0 at acpi0
> "PNP0A06" at acpi0 not configured
> "PNP0A06" at acpi0 not configured
> "PNP0A06" at acpi0 not configured
> "QEMU0002" at acpi0 not configured
> "ACPI0010" at acpi0 not configured
> pvbus0 at mainbus0: KVM
> pci0 at mainbus0 bus 0
> pchb0 at pci0 dev 0 function 0 "Intel 82441FX" rev 0x02
> "Intel 82371SB ISA" rev 0x00 at pci0 dev 1 function 0 not configured
> pciide0 at pci0 dev 1 function 1 "Intel 82371SB IDE" rev 0x00: DMA,
> channel 0 wired to compatibility, channel 1 wired to compatibility
> pciide0: channel 0 disabled (no drives)
> pciide0: channel 1 disabled (no drives)
> uhci0 at pci0 dev 1 function 2 "Intel 82371SB USB" rev 0x01: apic 0
> int 11
> "Intel 82371AB Power" rev 0x03 at pci0 dev 1 function 3 not configured
> vga1 at pci0 dev 2 function 0 "Bochs VGA" rev 0x02
> vga1: aperture needed
> wsdisplay1 at vga1 mux 1: console (80x25, vt100 emulation)
> virtio0 at pci0 dev 3 function 0 "Qumranet Virtio Network" rev 0x00
> vio0 at virtio0: address 08:00:27:77:c1:d5
> virtio0: msix shared
> virtio1 at pci0 dev 5 function 0 "Qumranet Virtio Storage" rev 0x00
> vioblk0 at virtio1
> scsibus0 at vioblk0: 2 targets
> sd0 at scsibus0 targ 0 lun 0: <VirtIO, Block Device, > SCSI3 0/direct
> fixed
> sd0: 114473MB, 512 bytes/sector, 234441632 sectors
> virtio1: msix shared
> virtio2 at pci0 dev 6 function 0 "Qumranet Virtio Memory Balloon" rev
> 0x00
> virtio2: no matching child driver; not configured
> ahci0 at pci0 dev 7 function 0 "Intel 82801I AHCI" rev 0x02: apic 0
> int 11, AHCI 1.0
> ahci0: port 0: 1.5Gb/s
> scsibus1 at ahci0: 32 targets
> cd0 at scsibus1 targ 0 lun 0: <QEMU, QEMU DVD-ROM, 2.5+> ATAPI 5/cdrom
> removable
> usb0 at uhci0: USB revision 1.0
> uhub0 at usb0 configuration 1 interface 0 "Intel UHCI root hub" rev
> 1.00/1.00 addr 1
> isa0 at mainbus0
> com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
> com0: console
> pckbc0 at isa0 port 0x60/5 irq 1 irq 12
> pckbd0 at pckbc0 (kbd slot)
> wskbd0 at pckbd0: console keyboard, using wsdisplay1
> softraid0 at root
> scsibus2 at softraid0: 256 targets
> root on rd0a swap on rd0b dump on rd0b
> erase ^?, werase ^W, kill ^U, intr ^C, status ^T
>
> Welcome to the OpenBSD/amd64 6.5 installation program.
> (I)nstall, (U)pgrade, (A)utoinstall or (S)hell? s
> # bioctl -c C -l /dev/sd0a softraid0
> bioctl: could not open /dev/sd0a: No such file or directory
> # ls /dev
> MAKEDEV cua01   klog    rcd0c   rrd0c   rwd0g   rwd0o   ttyC0   wd0g    wd0o
> bio     diskmap kmem    rd0a    rst0    rwd0h   rwd0p   urandom wd0h    wd0p
> bpf     enrst0  ksyms   rd0c    rwd0a   rwd0i   stderr  wd0a    wd0i    wskbd0
> bpf0    erst0   mem     rfd0a   rwd0b   rwd0j   stdin   wd0b    wd0j    wskbd1
> cd0a    fd0a    nrst0   rfd0b   rwd0c   rwd0k   stdout  wd0c    wd0k    wskbd2
> cd0c    fd0b    null    rfd0c   rwd0d   rwd0l   tty     wd0d    wd0l    xf86
> console fd0c    random  rfd0i   rwd0e   rwd0m   tty00   wd0e    wd0m    zero
> cua00   fd0i    rcd0a   rrd0a   rwd0f   rwd0n   tty01   wd0f    wd0n
>
>
> Does anyone know the cause of this problem?
>
> Thanks.
>
> --
> MS
>

Reply | Threaded
Open this post in threaded view
|

Re: Installer doesn't see sd0 on qemu guest 6.5-current

Theo de Raadt-2
In reply to this post by Maksym Sheremet
Maksym Sheremet <[hidden email]> wrote:

> The VM is installed on a dedicated drive with FDE. It is detected as sd0
> by bsd.rd booted from install65.iso. But once installer is started the
> drive disappears. Here is full output:
...

> (I)nstall, (U)pgrade, (A)utoinstall or (S)hell? s
> # bioctl -c C -l /dev/sd0a softraid0
> bioctl: could not open /dev/sd0a: No such file or directory
> # ls /dev
> MAKEDEV cua01   klog    rcd0c   rrd0c   rwd0g   rwd0o   ttyC0   wd0g    wd0o
> bio     diskmap kmem    rd0a    rst0    rwd0h   rwd0p   urandom wd0h    wd0p
> bpf     enrst0  ksyms   rd0c    rwd0a   rwd0i   stderr  wd0a    wd0i    wskbd0
> bpf0    erst0   mem     rfd0a   rwd0b   rwd0j   stdin   wd0b    wd0j    wskbd1
> cd0a    fd0a    nrst0   rfd0b   rwd0c   rwd0k   stdout  wd0c    wd0k    wskbd2
> cd0c    fd0b    null    rfd0c   rwd0d   rwd0l   tty     wd0d    wd0l    xf86
> console fd0c    random  rfd0i   rwd0e   rwd0m   tty00   wd0e    wd0m    zero
> cua00   fd0i    rcd0a   rrd0a   rwd0f   rwd0n   tty01   wd0f    wd0n
>
>
> Does anyone know the cause of this problem?

The Install script creates device nodes as required, because pre-creating
32 inodes per potential drive overflows the limited space inside the ramdisk.

Reply | Threaded
Open this post in threaded view
|

Re: Installer doesn't see sd0 on qemu guest 6.5-current

Roderick

On Sun, 2 Jun 2019, Theo de Raadt wrote:

> The Install script creates device nodes as required, because pre-creating
> 32 inodes per potential drive overflows the limited space inside the ramdisk.

Well, a very good reason not to put vi in bsd.rd

But ed is perhaps not the most comfortable in difficult situations ...

Rodrigo

Reply | Threaded
Open this post in threaded view
|

Re: Installer doesn't see sd0 on qemu guest 6.5-current

Theo de Raadt-2
Roderick <[hidden email]> wrote:

> > The Install script creates device nodes as required, because pre-creating
> > 32 inodes per potential drive overflows the limited space inside the ramdisk.
>
> Well, a very good reason not to put vi in bsd.rd
>
> But ed is perhaps not the most comfortable in difficult situations ...

The installer is meant for installation and upgrades.

It is not meant for anything else.  If people make their own changes
to extend the mandate, we actually don't want to hear about it, because
every proposal like that ignores the reality that additional features
will break the media on smaller machines.

Reply | Threaded
Open this post in threaded view
|

Re: Installer doesn't see sd0 on qemu guest 6.5-current

Maksym Sheremet
In reply to this post by Theo de Raadt-2
On Sun, Jun 02, 2019 at 08:27:04AM -0600, Theo de Raadt wrote:

> Maksym Sheremet <[hidden email]> wrote:
>
> > The VM is installed on a dedicated drive with FDE. It is detected as sd0
> > by bsd.rd booted from install65.iso. But once installer is started the
> > drive disappears. Here is full output:
> ...
> > (I)nstall, (U)pgrade, (A)utoinstall or (S)hell? s
> > # bioctl -c C -l /dev/sd0a softraid0
> > bioctl: could not open /dev/sd0a: No such file or directory
> > # ls /dev
> > MAKEDEV cua01   klog    rcd0c   rrd0c   rwd0g   rwd0o   ttyC0   wd0g    wd0o
> > bio     diskmap kmem    rd0a    rst0    rwd0h   rwd0p   urandom wd0h    wd0p
> > bpf     enrst0  ksyms   rd0c    rwd0a   rwd0i   stderr  wd0a    wd0i    wskbd0
> > bpf0    erst0   mem     rfd0a   rwd0b   rwd0j   stdin   wd0b    wd0j    wskbd1
> > cd0a    fd0a    nrst0   rfd0b   rwd0c   rwd0k   stdout  wd0c    wd0k    wskbd2
> > cd0c    fd0b    null    rfd0c   rwd0d   rwd0l   tty     wd0d    wd0l    xf86
> > console fd0c    random  rfd0i   rwd0e   rwd0m   tty00   wd0e    wd0m    zero
> > cua00   fd0i    rcd0a   rrd0a   rwd0f   rwd0n   tty01   wd0f    wd0n
> >
> >
> > Does anyone know the cause of this problem?
>
> The Install script creates device nodes as required, because pre-creating
> 32 inodes per potential drive overflows the limited space inside the ramdisk.
>

That makes sense. But it behaves different with 6.5-release. There is
sd0 in /dev without manual MAKEDEV.

Welcome to the OpenBSD/amd64 6.5 installation program.
(I)nstall, (U)pgrade, (A)utoinstall or (S)hell? s
# ls /dev
MAKEDEV fd0a    rcd0c   rsd0d   rsd0p   rwd0k   sd0g    stdout  wd0g   wskbd2
bio     fd0b    rd0a    rsd0e   rst0    rwd0l   sd0h    tty     wd0h   xf86
bpf     fd0c    rd0c    rsd0f   rwd0a   rwd0m   sd0i    tty00   wd0i   zero
bpf0    fd0i    rfd0a   rsd0g   rwd0b   rwd0n   sd0j    tty01   wd0j
cd0a    klog    rfd0b   rsd0h   rwd0c   rwd0o   sd0k    ttyC0   wd0k
cd0c    kmem    rfd0c   rsd0i   rwd0d   rwd0p   sd0l    urandom wd0l
console ksyms   rfd0i   rsd0j   rwd0e   sd0a    sd0m    wd0a    wd0m
cua00   mem     rrd0a   rsd0k   rwd0f   sd0b    sd0n    wd0b    wd0n
cua01   nrst0   rrd0c   rsd0l   rwd0g   sd0c    sd0o    wd0c    wd0o
diskmap null    rsd0a   rsd0m   rwd0h   sd0d    sd0p    wd0d    wd0p
enrst0  random  rsd0b   rsd0n   rwd0i   sd0e    stderr  wd0e    wskbd0
erst0   rcd0a   rsd0c   rsd0o   rwd0j   sd0f    stdin   wd0f    wskbd1

Is this related to any changes in -current?

--
MS

Reply | Threaded
Open this post in threaded view
|

Re: Installer doesn't see sd0 on qemu guest 6.5-current

Maksym Sheremet
In reply to this post by Patrick Wildt-3
On Sat, Jun 01, 2019 at 10:29:09PM +0200, Patrick Wildt wrote:
> As you can see in dmesg, it actually sees sd0, and it does not detach.
> Instead, the device node just isn't in /dev, because the insaller does
> create that on the fly.  Since you are not using the installer, you
> have to manually type cd /dev && sh MAKEDEV sd0

It works. Thank you.

--
MS