Problem to boot OSv under OmniOS and SmartOS (illumos)

[Frédéric Alix]

Hello,

I try to boot OSv with KVM under Omnios or SmartOS. They are Illumos distribution with KVM support

When i launch my startup script, nothing append after Booting on the Hard Drive....

Can you help me please ?

Frederic

My startup script:

#!/usr/bin/bash

# configuration

VNIC=osv1

VNC=3

MEM=4096

mac=`dladm show-vnic -po macaddress $VNIC`

/usr/bin/qemu-system-x86_64 \

-name osv \

-enable-kvm \

-no-acpi \

-nographic \

-vnc 0.0.0.0:$VNC \

-smp 2 \

-m $MEM \

-cpu host,+x2apic \

-no-hpet \

-localtime \

-drive index=0,if=virtio,media=disk,format=qcow2,file=/export/iso/osv-v0.04.qcow2 \

-net nic,vlan=0,name=net0,model=virtio,macaddr=$mac \

-net vnic,vlan=0,name=net0,ifname=$VNIC,macaddr=$mac \

-vga std \

-daemonize

if [ $? -gt 0 ]; then

    echo "Failed to start VM"

fi

port=`expr 5900 + $VNC`

public_nic=$(dladm show-vnic|grep vnic1|awk '{print $2}')

public_ip=$(ifconfig $public_nic|grep inet|awk '{print $2}')

echo "Started VM:"

echo "Public: ${public_ip}:${port}"

[Asias He]

On Jan 24, 2014, at 8:14 AM, Frédéric Alix <freder...@fredalix.com> wrote:

Hello,

I try to boot OSv with KVM under Omnios or SmartOS. They are Illumos distribution with KVM support

When i launch my startup script, nothing append after Booting on the Hard Drive....

Can you help me please ?

It would be helpful if you could paste the serial printout here.

Frederic

My startup script:

#!/usr/bin/bash

# configuration

VNIC=osv1

VNC=3

MEM=4096

mac=`dladm show-vnic -po macaddress $VNIC`

/usr/bin/qemu-system-x86_64 \

-name osv \

-enable-kvm \

-no-acpi \

-nographic \

-vnc 0.0.0.0:$VNC \

-smp 2 \

-m $MEM \

-cpu host,+x2apic \

-no-hpet \

Could you try dropping the -no-hpet option? HPET is needed.

-localtime \

-drive index=0,if=virtio,media=disk,format=qcow2,file=/export/iso/osv-v0.04.qcow2 \

v0.05 is out. Can you try it?

-net nic,vlan=0,name=net0,model=virtio,macaddr=$mac \

-net vnic,vlan=0,name=net0,ifname=$VNIC,macaddr=$mac \

-vga std \

-daemonize

if [ $? -gt 0 ]; then

    echo "Failed to start VM"

fi

port=`expr 5900 + $VNC`

public_nic=$(dladm show-vnic|grep vnic1|awk '{print $2}')

public_ip=$(ifconfig $public_nic|grep inet|awk '{print $2}')

echo "Started VM:"

echo "Public: ${public_ip}:${port}"

--
You received this message because you are subscribed to the Google Groups "OSv Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to osv-dev+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Pekka Enberg]

On Fri, Jan 24, 2014 at 2:14 AM, Frédéric Alix
<freder...@fredalix.com> wrote:
> I try to boot OSv with KVM under Omnios or SmartOS. They are Illumos
> distribution with KVM support
> When i launch my startup script, nothing append after Booting on the Hard
> Drive....

There's no VGA support so you're only supposed to see something on the
serial console or via SSH.

[Frédéric Alix]

Hello :-)

I disable no-graphic (i tested a lot configuration)

This is the serioul output.

Start bios (version 0.6.1.2-20110201_165504-titi)

Ram Size=0xe0000000 (0x0000000020000000 high)

CPU Mhz=3093

PCI: pci_bios_init_bus_rec bus = 0x0

PIIX3/PIIX4 init: elcr=00 0c

PCI: bus=0 devfn=0x00: vendor_id=0x8086 device_id=0x1237

PCI: bus=0 devfn=0x08: vendor_id=0x8086 device_id=0x7000

PCI: bus=0 devfn=0x09: vendor_id=0x8086 device_id=0x7010

region 4: 0x0000c000

PCI: bus=0 devfn=0x10: vendor_id=0x1013 device_id=0x00b8

region 0: 0xf0000000

region 1: 0xf2000000

region 6: 0xf2010000

PCI: bus=0 devfn=0x18: vendor_id=0x1af4 device_id=0x1000

region 0: 0x0000c020

region 1: 0xf2020000

region 6: 0xf2030000

PCI: bus=0 devfn=0x20: vendor_id=0x1af4 device_id=0x1001

region 0: 0x0000c040

region 1: 0xf2040000

Found 2 cpu(s) max supported 2 cpu(s)

MP table addr=0x000fdbe0 MPC table addr=0x000fdbf0 size=252

SMBIOS ptr=0x000fdbc0 table=0xdffffea0

Scan for VGA option rom

Running option rom at c000:0003

VGABios $Id$

Turning on vga text mode console

SeaBIOS (version 0.6.1.2-20110201_165504-titi)

Found 1 lpt ports

Found 1 serial ports

ATA controller 0 at 1f0/3f4/0 (irq 14 dev 9)

ATA controller 1 at 170/374/0 (irq 15 dev 9)

found virtio-blk at 0:4

ebda moved from 9fc00 to 9dc00

drive 0x000fdb70: PCHS=16383/16/63 translation=lba LCHS=1024/255/63 s=21176320

ata1-0: QEMU DVD-ROM ATAPI-4 DVD/CD

PS2 keyboard initialized

All threads complete.

Scan for option roms

Running option rom at c900:0003

pnp call arg1=60

pmm call arg1=0

pmm call arg1=2

pmm call arg1=0

Running option rom at c980:0003

Returned 61440 bytes of ZoneHigh

e820 map has 8 items:

  0: 0000000000000000 - 000000000009dc00 = 1

  1: 000000000009dc00 - 00000000000a0000 = 2

  2: 00000000000f0000 - 0000000000100000 = 2

  3: 0000000000100000 - 00000000dffff000 = 1

  4: 00000000dffff000 - 00000000e0000000 = 2

  5: 00000000feffc000 - 00000000ff000000 = 2

  6: 00000000fffc0000 - 0000000100000000 = 2

  7: 0000000100000000 - 0000000120000000 = 1

enter handle_19:

  NULL

Booting from Hard Disk...

Booting from 0000:7c00

2014/1/24 Pekka Enberg <pen...@cloudius-systems.com>

[Glauber Costa]

Do you have a -serial switch ?

That doesn't look like the normal serial output...

One thing I advise you to do is to look at run.py (even if you don't use it for running OSv) to see which command line we end up creating.

For me, printing all args right before executing yields the following:

['-vnc', ':1', '-gdb', 'tcp::1234,server,nowait', '-m', '2G', '-smp', '4', '-device', 'virtio-blk-pci,id=blk0,bootindex=0,drive=hd0,scsi=off', '-drive', 'file=/home/glauber/osv-clean/build/release/usr.img,if=none,id=hd0,aio=native,cache=none', '-netdev', 'tap,id=hn0,script=scripts/qemu-ifup.sh,vhost=on', '-device', 'virtio-net-pci,netdev=hn0,id=nic1', '-device', 'virtio-rng-pci', '-enable-kvm', '-cpu', 'host,+x2apic', '-chardev', 'stdio,mux=on,id=stdio,signal=off', '-mon', 'chardev=stdio,mode=readline,default', '-device', 'isa-serial,chardev=stdio']

[Pekka Enberg]

On Fri, Jan 24, 2014 at 10:41 AM, Frédéric Alix
<freder...@fredalix.com> wrote:
> Booting from Hard Disk...
> Booting from 0000:7c00

Looks like we don't even get to the early boot stuff in OSv.

It might be related to you disabling ACPI with "-no-acpi" because OSv
attempts to parse ACPI MADT very early in the boot.

Can you please try to boot without that command line option?

Pekka

[Frédéric Alix]

I already use -no-acpi.

I added -serial  file:/tmp/qemu-output.log \ and the message is

ACPI BIOS Bug: Error: A valid RSDP was not found (20130117/tbxfroot-307)

Aborted

2014/1/24 Pekka Enberg <pen...@cloudius-systems.com>

[Glauber Costa]

On Fri, Jan 24, 2014 at 1:00 PM, Frédéric Alix <freder...@fredalix.com> wrote:

I already use -no-acpi.

I added -serial  file:/tmp/qemu-output.log \ and the message is

ACPI BIOS Bug: Error: A valid RSDP was not found (20130117/tbxfroot-307)

Aborted

a-ha! Now we're getting somewhere.

So: since you were actively using -no-acpi, and I don't really know a lot about illumos,

is there any reason why you've used in in the first place ? Is it known broken or anything

like that ?
 

2014/1/24 Pekka Enberg <pen...@cloudius-systems.com>

On Fri, Jan 24, 2014 at 10:41 AM, Frédéric Alix
<freder...@fredalix.com> wrote:
> Booting from Hard Disk...
> Booting from 0000:7c00

Looks like we don't even get to the early boot stuff in OSv.

It might be related to you disabling ACPI with "-no-acpi" because OSv
attempts to parse ACPI MADT very early in the boot.

Can you please try to boot without that command line option?

                      Pekka

[Pekka Enberg]

On Fri, Jan 24, 2014 at 11:00 AM, Frédéric Alix
<freder...@fredalix.com> wrote:
> I already use -no-acpi.

Yes, I see that.

You should *not* use it because OSv requires ACPI to be present.

[Frédéric Alix]

yes, i uset it because i like zfs for store my vm files, i have network virtualisation too,and a good capping cpu and memory in the system heart.

Ok, perhaps in a futur illumos kvm update all will be fine :)

Thank you for your time :-)

Have a nice day !

Frederic

2014/1/24 Glauber Costa <glo...@cloudius-systems.com>

[Glauber Costa]

On Fri, Jan 24, 2014 at 1:08 PM, Frédéric Alix <freder...@fredalix.com> wrote:

yes, i uset it because i like zfs for store my vm files, i have network virtualisation too,and a good capping cpu and memory in the system heart.

I meant why did you use -no-acpi.

As Pekka said, at this point we need ACPI tables functional to run.

So I would like to know if it is known broken in Illumos, or if there is any other reason why you disabled it.

If ACPI tables are known to be broken in Illumos, we could still disable SMP and keep going.
 

[Frédéric Alix]

Oh sorry ! my english skill is not perfect...

I had some problem with centos or coreos with KVM and when i disable acpi, it's ok

This is the output when acpi is enable:

ACPI: RSDP 0xfdb90 00014 (v00 BOCHS )

ACPI: RSDT 0xdfffdb90 00034 (v01 BOCHS  BXPCRSDT 00000001 BXPC 00000001)

ACPI: FACP 0xdffffe20 00074 (v01 BOCHS  BXPCFACP 00000001 BXPC 00000001)

ACPI: DSDT 0xdfffde00 01FB7 (v01   BXPC   BXDSDT 00000001 INTL 20090123)

ACPI: FACS 0xdffffdc0 00040

ACPI: SSDT 0xdfffdd00 000FF (v01 BOCHS  BXPCSSDT 00000001 BXPC 00000001)

ACPI: APIC 0xdfffdc10 0007A (v01 BOCHS  BXPCAPIC 00000001 BXPC 00000001)

ACPI: HPET 0xdfffdbd0 00038 (v01 BOCHS  BXPCHPET 00000001 BXPC 00000001)

Assertion failed: cap & HPET_CAP_COUNT_SIZE (/home/penberg/osv/drivers/hpet.cc:

hpetclock: 118)

Aborted

I disable smp and know it's better :-D

ACPI: RSDP 0xfdba0 00014 (v00 BOCHS )

ACPI: RSDT 0xdfffdc40 00034 (v01 BOCHS  BXPCRSDT 00000001 BXPC 00000001)

ACPI: FACP 0xdffffe50 00074 (v01 BOCHS  BXPCFACP 00000001 BXPC 00000001)

ACPI: DSDT 0xdfffde40 01FB7 (v01   BXPC   BXDSDT 00000001 INTL 20090123)

ACPI: FACS 0xdffffe00 00040

ACPI: SSDT 0xdfffdda0 0009E (v01 BOCHS  BXPCSSDT 00000001 BXPC 00000001)

ACPI: APIC 0xdfffdcc0 00072 (v01 BOCHS  BXPCAPIC 00000001 BXPC 00000001)

ACPI: HPET 0xdfffdc80 00038 (v01 BOCHS  BXPCHPET 00000001 BXPC 00000001)

acpi 0 apic 0

APIC base fee00000

OSv v0.04 Copyright 2013 Cloudius Systems

locale works

ACPI: All ACPI Tables successfully acquired

VFS: mounting ramfs at /

VFS: mounting devfs at /dev

RAM disk at 0x0xffffc0003f69e000 (4096K bytes)

Initializing network stack...

Done!

eth0: ethernet address: 2:8:20:a8:96:75

VFS: mounting zfs at /zfs

zfs: mounting osv/zfs from device /dev/vblk0.1

VFS: mounting devfs at /dev

[I/22 dhcp]: Waiting for IP...

[I/301 dhcp]: Server acknowledged IP for interface eth0

[I/301 dhcp]: Configuring eth0: ip 192.168.0.114 subnet mask 255.255.255.0 gatew

ay 192.168.0.254

stub dlclose()

OpenJDK 64-Bit Server VM warning: Can't detect initial thread stack location - f

ind_vma failed

Using log file: /var/log/mgmt.log

device random not found

device random not found

  ____   _____

 / __ \ / ____|

| |  | | (_____   __

| |  | |\___ \ \ / /

| |__| |____) \ V /

 \____/|_____/ \_/

[/]% Puma 2.5.1 starting...

* Min threads: 0, max threads: 16

* Environment: development

* Listening on tcp://0.0.0.0:8080

== Sinatra/1.4.3 has taken the stage on 8080 for development with backup from Pu

ma

2014/1/24 Glauber Costa <glo...@cloudius-systems.com>

[Glauber Costa]

On Fri, Jan 24, 2014 at 1:16 PM, Frédéric Alix <freder...@fredalix.com> wrote:

Oh sorry ! my english skill is not perfect...

we 're happy to help you practice that too!

I had some problem with centos or coreos with KVM and when i disable acpi, it's ok

This is the output when acpi is enable:

ACPI: RSDP 0xfdb90 00014 (v00 BOCHS )

ACPI: RSDT 0xdfffdb90 00034 (v01 BOCHS  BXPCRSDT 00000001 BXPC 00000001)

ACPI: FACP 0xdffffe20 00074 (v01 BOCHS  BXPCFACP 00000001 BXPC 00000001)

ACPI: DSDT 0xdfffde00 01FB7 (v01   BXPC   BXDSDT 00000001 INTL 20090123)

ACPI: FACS 0xdffffdc0 00040

ACPI: SSDT 0xdfffdd00 000FF (v01 BOCHS  BXPCSSDT 00000001 BXPC 00000001)

ACPI: APIC 0xdfffdc10 0007A (v01 BOCHS  BXPCAPIC 00000001 BXPC 00000001)

ACPI: HPET 0xdfffdbd0 00038 (v01 BOCHS  BXPCHPET 00000001 BXPC 00000001)

Ok, so this means the table are sane. Good!
 

Assertion failed: cap & HPET_CAP_COUNT_SIZE (/home/penberg/osv/drivers/hpet.cc:

hpetclock: 118)

Aborted

If you are still using -no-hpet, you should remove that. If  Illumos does not support kvmclock,
we need hpet as a fallback

That is great! But  please try *not* disabling hpet (remove the -no-hpet switch)

[Pekka Enberg]

On Fri, Jan 24, 2014 at 11:20 AM, Glauber Costa
<glo...@cloudius-systems.com> wrote:
> If you are still using -no-hpet, you should remove that. If Illumos does
> not support kvmclock, we need hpet as a fallback

Does anyone know why there's no kvmclock on Illumos?

Pekka

[Frédéric Alix]

I'll contact Robert Mustacchi, the illumos KVM leader when he'll wake up.

I remove -no-hpet

The output is:

[Pekka Enberg]

On Fri, Jan 24, 2014 at 11:29 AM, Frédéric Alix
<freder...@fredalix.com> wrote:
> I'll contact Robert Mustacchi, the illumos KVM leader when he'll wake up.
>
> I remove -no-hpet
>
> The output is:
> ACPI: RSDP 0xfdba0 00014 (v00 BOCHS )
> ACPI: RSDT 0xdfffdc40 00034 (v01 BOCHS BXPCRSDT 00000001 BXPC 00000001)
> ACPI: FACP 0xdffffe50 00074 (v01 BOCHS BXPCFACP 00000001 BXPC 00000001)
> ACPI: DSDT 0xdfffde40 01FB7 (v01 BXPC BXDSDT 00000001 INTL 20090123)
> ACPI: FACS 0xdffffe00 00040
> ACPI: SSDT 0xdfffdda0 0009E (v01 BOCHS BXPCSSDT 00000001 BXPC 00000001)
> ACPI: APIC 0xdfffdcc0 00072 (v01 BOCHS BXPCAPIC 00000001 BXPC 00000001)
> ACPI: HPET 0xdfffdc80 00038 (v01 BOCHS BXPCHPET 00000001 BXPC 00000001)
> acpi 0 apic 0

You have SMP disabled, right? Can you please try with HPET *and* SMP
which is the configuration that wasn't working?

[Frédéric Alix]

Yes, right.

Now my config is:

/usr/bin/qemu-system-x86_64 \

-name osv \

-enable-kvm \

-vnc 0.0.0.0:$VNC \

-smp 2 \

-m $MEM \

-serial file:/var/tmp/output.log \

-cpu host,+x2apic \

-localtime \

-drive index=0,if=virtio,media=disk,format=qcow2,file=/export/iso/osv-v0.04.qcow2 \

-vga std \

-net nic,vlan=0,name=net0,model=virtio,macaddr=$mac \

-net vnic,vlan=0,name=net0,ifname=$VNIC,macaddr=$mac \

And the output is:

ACPI: RSDP 0xfdb90 00014 (v00 BOCHS )

ACPI: RSDT 0xdfffdb90 00034 (v01 BOCHS  BXPCRSDT 00000001 BXPC 00000001)

ACPI: FACP 0xdffffe20 00074 (v01 BOCHS  BXPCFACP 00000001 BXPC 00000001)

ACPI: DSDT 0xdfffde00 01FB7 (v01   BXPC   BXDSDT 00000001 INTL 20090123)

ACPI: FACS 0xdffffdc0 00040

ACPI: SSDT 0xdfffdd00 000FF (v01 BOCHS  BXPCSSDT 00000001 BXPC 00000001)

ACPI: APIC 0xdfffdc10 0007A (v01 BOCHS  BXPCAPIC 00000001 BXPC 00000001)

ACPI: HPET 0xdfffdbd0 00038 (v01 BOCHS  BXPCHPET 00000001 BXPC 00000001)

acpi 0 apic 0

acpi 1 apic 1

APIC base fee00000

OSv v0.04 Copyright 2013 Cloudius Systems

locale works

ACPI: All ACPI Tables successfully acquired

VFS: mounting ramfs at /

VFS: mounting devfs at /dev

RAM disk at 0x0xffffc0003f52d000 (4096K bytes)

Initializing network stack...

Done!

eth0: ethernet address: 2:8:20:a8:96:75

VFS: mounting zfs at /zfs

zfs: mounting osv/zfs from device /dev/vblk0.1

VFS: mounting devfs at /dev

[I/26 dhcp]: Waiting for IP...

[I/309 dhcp]: Server acknowledged IP for interface eth0

[I/309 dhcp]: Configuring eth0: ip 192.168.0.114 subnet mask 255.255.255.0 gatew

ay 192.168.0.254

stub dlclose()

OpenJDK 64-Bit Server VM warning: Can't detect initial thread stack location - f

ind_vma failed

Using log file: /var/log/mgmt.log

device random not found

device random not found

  ____   _____

 / __ \ / ____|

| |  | | (_____   __

| |  | |\___ \ \ / /

| |__| |____) \ V /

 \____/|_____/ \_/

[/]% Puma 2.5.1 starting...

* Min threads: 0, max threads: 16

* Environment: development

* Listening on tcp://0.0.0.0:8080

== Sinatra/1.4.3 has taken the stage on 8080 for development with backup from Pu

ma

2014/1/24 Pekka Enberg <pen...@cloudius-systems.com>

[Pekka Enberg]

On Fri, Jan 24, 2014 at 11:36 AM, Frédéric Alix
<freder...@fredalix.com> wrote:
> Yes, right.
>
> Now my config is:
>
> /usr/bin/qemu-system-x86_64 \
> -name osv \
> -enable-kvm \
> -vnc 0.0.0.0:$VNC \
> -smp 2 \
> -m $MEM \
> -serial file:/var/tmp/output.log \
> -cpu host,+x2apic \
> -localtime \
> -drive
> index=0,if=virtio,media=disk,format=qcow2,file=/export/iso/osv-v0.04.qcow2 \
> -vga std \
> -net nic,vlan=0,name=net0,model=virtio,macaddr=$mac \
> -net vnic,vlan=0,name=net0,ifname=$VNIC,macaddr=$mac \

Great, so SMP also works on Illumos with the HPET fallback.

Thanks for testing, Frédéric!

Pekka

[Frédéric Alix]

it is me who should thank you! 

I'm super excited to test OpenDJ, Rundeck, and many others with OSv !

Big big thank you !

2014/1/24 Pekka Enberg <pen...@cloudius-systems.com>