[re-adding the list]

On 2017-04-05 14:32, Patrik Strömblad wrote:
> Hi, 
> yes I am running the master checkout. I installed the default ubuntu
> 16.04 image (ubuntu-16.04.02-desktop-amd64.iso) on "/cdrom" with kernel
> 4.8.0-45-generic. 
> 
> I have updated grub2 with cmd line stuff as described, no ttyS0 memmap,
> etc. Built jailhouse latest in guest. 
> 
> I have tried with both qemu 2.7.0 and 2.9.0, and both using qemu-vm cell
> and gererated an own one, and both with or without audio driver:
> 
> $ /homes/past/qemu/qemu-2.9.0-rc2/x86_64-softmmu/qemu-system-x86_64
> -machine q35,kernel_irqchip=split -m 1G -drive
> file=ubuntu.qcow,format=qcow2,id=disk,if=none -smp 4 -device
> intel-iommu,intremap=on -cpu
> kvm64,-kvm_pv_eoi,-kvm_steal_time,-kvm_asyncpf,-kvmclock,+vmx -serial
> stdio -serial vc -netdev user,id=net -device e1000e,addr=2.0,netdev=net
> -device ide-hd,drive=disk -enable-kvm -device intel-hda,addr=1b.0
> -device hda-duplex 
> audio: Could not init `oss' audio driver
> 
> Initializing Jailhouse hypervisor v0.6 on CPU 2
> Code location: 0xfffffffff0000040
> Using x2APIC
> Page pool usage after early setup: mem 44/1480, remap 64/131072
> Initializing processors:
>  CPU 2... (APIC ID 2) OK
>  CPU 1... (APIC ID 1) OK
>  CPU 0... (APIC ID 0) OK
>  CPU 3... (APIC ID 3) OK
> DMAR unit @0xfed90000/0x1000
> Reserving 24 interrupt(s) for device ff00 at index 0
> Adding PCI device 00:01.0 to cell "QEMU-VM"
> Adding PCI device 00:02.0 to cell "QEMU-VM"
> Reserving 5 interrupt(s) for device 0010 at index 24
> Adding PCI device 00:1b.0 to cell "QEMU-VM"
> Reserving 1 interrupt(s) for device 00d8 at index 29
> Adding PCI device 00:1f.0 to cell "QEMU-VM"
> Adding PCI device 00:1f.2 to cell "QEMU-VM"
> Reserving 1 interrupt(s) for device 00fa at index 30
> Adding PCI device 00:1f.3 to cell "QEMU-VM"
> Adding PCI device 00:1f.7 to cell "QEMU-VM"
> Reserving 2 interrupt(s) for device 00ff at index 31
> Adding virtual PCI device 00:0e.0 to cell "QEMU-VM"
> Adding virtual PCI device 00:0f.0 to cell "QEMU-VM"
> Page pool usage after late setup: mem 254/1480, remap 65607/131072
> Activating hypervisor
> qemu-system-x86_64: terminating on signal 2
> 

OK, so we are stuck without further notices, which is different from the
other error.

> 
> $ /homes/past/qemu/qemu-2.9.0-rc2/x86_64-softmmu/qemu-system-x86_64
> -machine q35,kernel_irqchip=split -m 1G -drive
> file=ubuntu.qcow,format=qcow2,id=disk,if=none -smp 4 -device
> intel-iommu,intremap=on -cpu
> kvm64,-kvm_pv_eoi,-kvm_steal_time,-kvm_asyncpf,-kvmclock,+vmx -serial
> stdio -serial vc -netdev user,id=net -device e1000e,addr=2.0,netdev=net
> -device ide-hd,drive=disk -enable-kvm
> 
> Initializing Jailhouse hypervisor v0.6 on CPU 1
> Code location: 0xfffffffff0000040
> Using x2APIC
> Page pool usage after early setup: mem 73/16328, remap 64/131072
> Initializing processors:
>  CPU 1... (APIC ID 1) OK
>  CPU 2... (APIC ID 2) OK
>  CPU 3... (APIC ID 3) OK
>  CPU 0... (APIC ID 0) OK
> DMAR unit @0xfed90000/0x1000
> Reserving 24 interrupt(s) for device ff00 at index 0
> Adding PCI device 00:00.0 to cell "RootCell"
> Adding PCI device 00:01.0 to cell "RootCell"
> Adding PCI device 00:02.0 to cell "RootCell"
> Reserving 5 interrupt(s) for device 0010 at index 24
> Adding PCI device 00:1f.0 to cell "RootCell"
> Adding PCI device 00:1f.2 to cell "RootCell"
> Reserving 1 interrupt(s) for device 00fa at index 29
> Adding PCI device 00:1f.3 to cell "RootCell"
> Page pool usage after late setup: mem 278/16328, remap 65606/131072
> Activating hypervisor
> qemu-system-x86_64: terminating on signal 2
> 
> I am not able to escape qemu with ctrl-x a, alt-2 or any proposed escape
> sequence. :-) only ctrl-c. 
> Also have debug printout active (I think). Any way to get more
> information out? 

You could try building your own kernel using eg. the config I attached.
It's based on my latest jailhouse queue [1]

Jan

[1]
http://git.kiszka.org/?p=linux.git;a=shortlog;h=refs/heads/queues/jailhouse

> 
> I just wanted to run this example before targeting ARM...:-)
> 
> /Patrik
> 
> On Wed, Apr 5, 2017 at 7:22 AM, Jan Kiszka <[email protected]
> <mailto:[email protected]>> wrote:
> 
>     On 2017-04-04 22:50, Patrik Strömblad wrote:
>     > Hi Jan,
>     > we have met in Dublin, working with hybrid Linux/RTOS solutions. I
>     try to do the same reference example bringup of Jailhouse using
>     Ubuntu 16.04 in qemu, but it freezes after activating the
>     Hypervisor. It seems I get the same problem with the audio driver as
>     this thread. Did you come to any conclusion on the cause, or should
>     I try another version?
>     > Do you recommend any particular Linux distro to run the demo?
> 
>     We fixed a couple of issues in the hypervisor since then - are you
>     running the latest master checkout?
> 
>     Also, what are other parameters such as guest kernel version and config,
>     the qemu command line?
> 
>     Jan
> 
> 

-- 
You received this message because you are subscribed to the Google Groups 
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Attachment: config-qemu.xz
Description: application/xz

Reply via email to