Re: [Qemu-discuss] Device not tied to a QemuConsole.

2017-10-07 Thread José Pekkarinen
On Thursday, 5 October 2017 21:40:14 EEST José Pekkarinen wrote:
>   Hi list,
> 
>   I'm currently toying around with vfio mediated devices in qemu, and I'm
> having troubles defining a display through vnc for the mediated device. The
> error in question is this:
> 
> qemu-system-x86_64: -display vnc=0:1,display=video.1: Failed to start VNC
> server: Device video.1 (head 0) is not bound to a QemuConsole
> 
>   The qemu parameters are like this:
> 
> sudo qemu-system-x86_64 -enable-kvm -cpu host -smp 2,cores=1,threads=2 \
> -m 8G -mem-path /mnt/hugepages -vga qxl -display vnc=0:0 -display
> vnc=0:1,display=video.1 \
> -device
> vfio-pci,id=video.1,sysfsdev=/sys/class/mdev_bus/:00:02.0/
> $uuid,bus=pci.0,addr=06.0,rombar=0 \
> -netdev user,id=user.0,smb=/home/pekkari/share -device
> e1000,netdev=user.0 \
> -device ich9-usb-uhci3,id=uhci -device usb-ehci,id=ehci -device nec-
> usb-xhci,id=xhci \
> -device virtio-serial -device usb-tablet -device ich9-intel-hda -
> device hda-duplex \
> -object input-linux,id=kbd,evdev=/dev/input/by-path/platform-i8042-
> serio-0-event-kbd \
> -chardev
> socket,path=/tmp/virtio-serial.sock,server,nowait,id=serial- log \
> -device virtserialport,chardev=serial-log,name=ant.port.0 \
> -cdrom /home/pekkari/machines/win8/virtio-win-0.1.141.iso \
> -drive file=win8.img,format=raw,cache=none,aio=native,if=virtio
> 
>   This is piece of a script that sets uuid to a value, and the vm is a
> windows 8.1 vm with RH qxl and intel qxl device driver.
> 
>   Previously I tried using spice, replacing all -displays with the
> following:
> 
>   -spice port=5900,disable-ticketing
> 
>   The result was that just one display turn up, and intel was tied to a 
> non
> pnp display that I wouldn't see. Switching the main display to it make the
> vm almost unusable, as everything renders in the invisible display.
> 
>   Thanks in advance for any suggestions.
> 
>   José.

Adding vfio-users mailing list in case anyone knows what I may be doing 
wrong.

Thanks!

José.



Re: [Qemu-discuss] [vfio-users] Device not tied to a QemuConsole.

2017-10-07 Thread Alex Williamson
On Sat, 07 Oct 2017 15:38:57 +0300
José Pekkarinen  wrote:

> On Thursday, 5 October 2017 21:40:14 EEST José Pekkarinen wrote:
> > Hi list,
> > 
> > I'm currently toying around with vfio mediated devices in qemu, and I'm
> > having troubles defining a display through vnc for the mediated device. The
> > error in question is this:
> > 
> > qemu-system-x86_64: -display vnc=0:1,display=video.1: Failed to start VNC
> > server: Device video.1 (head 0) is not bound to a QemuConsole
> > 
> > The qemu parameters are like this:
> > 
> > sudo qemu-system-x86_64 -enable-kvm -cpu host -smp 2,cores=1,threads=2 \
> > -m 8G -mem-path /mnt/hugepages -vga qxl -display vnc=0:0 -display
> > vnc=0:1,display=video.1 \
> > -device
> > vfio-pci,id=video.1,sysfsdev=/sys/class/mdev_bus/:00:02.0/
> > $uuid,bus=pci.0,addr=06.0,rombar=0 \
> > -netdev user,id=user.0,smb=/home/pekkari/share -device
> > e1000,netdev=user.0 \
> > -device ich9-usb-uhci3,id=uhci -device usb-ehci,id=ehci -device nec-
> > usb-xhci,id=xhci \
> > -device virtio-serial -device usb-tablet -device ich9-intel-hda -
> > device hda-duplex \
> > -object input-linux,id=kbd,evdev=/dev/input/by-path/platform-i8042-
> > serio-0-event-kbd \
> > -chardev
> > socket,path=/tmp/virtio-serial.sock,server,nowait,id=serial- log \
> > -device virtserialport,chardev=serial-log,name=ant.port.0 \
> > -cdrom /home/pekkari/machines/win8/virtio-win-0.1.141.iso \
> > -drive file=win8.img,format=raw,cache=none,aio=native,if=virtio
> > 
> > This is piece of a script that sets uuid to a value, and the vm is a
> > windows 8.1 vm with RH qxl and intel qxl device driver.
> > 
> > Previously I tried using spice, replacing all -displays with the
> > following:
> > 
> > -spice port=5900,disable-ticketing
> > 
> > The result was that just one display turn up, and intel was tied to a 
> > non
> > pnp display that I wouldn't see. Switching the main display to it make the
> > vm almost unusable, as everything renders in the invisible display.
> > 
> > Thanks in advance for any suggestions.
> > 
> > José.  
> 
>   Adding vfio-users mailing list in case anyone knows what I may be doing 
> wrong.

You need a time machine because the thing you're trying to do hasn't
been implemented yet, it's under discussion upstream.  Thanks,

Alex



Re: [Qemu-discuss] SunOS 4.1.4 on Qemu 2.10.0 on Mac OS X 10.12.6 on mid 2012 Intel MBP w/16GB RAM

2017-10-07 Thread Will Senn
After much trial and error and after being reenergized by Mike's 
confirmation that it wasn't hopeless, I figured out what the problem was 
- apparently unselecting the ethernet device before setting it causes 
the install to misconfigure the nic and this causes the rpc problem 
during boot. Instead, just click x to select le0 even though it is 
already selected and then provide your ip address. With 'ansi' chosen as 
the terminal, there are some weird behaviors, 'xterms' is a better 
choice of terminal.


Thanks,

Will

On 10/6/17 2:23 PM, Mike Russo wrote:

I followed the instructions in the wiki and it worked for me.


/usr/local/bin/qemu-system-sparc --version

QEMU emulator version 2.9.0

Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers

/usr/local/bin/qemu-system-sparc -monitor tcp::,server,nowait -bios 
ss5-170.bin -m 32 -nographic -hda sunos414.img


qemu-system-sparc: -hda sunos414.img: warning: bus=0,unit=0 is deprecated with 
this machine type


Power-ON Reset



MB86907 POST 2.2.3 03SEP96


Probing system memory: 32  0  0  0  0  0  0  0

Config = 8802

0Kb ecache detected


initializing TLB

initializing cache


Allocating SRMMU Context Table

Setting SRMMU Context Register

Setting SRMMU Context Table Pointer Register

Allocating SRMMU Level 1 Table

Mapping RAM

Mapping ROM


ttya initialized

Probing Memory Bank #0 32 Megabytes

Probing Memory Bank #1 Nothing there

Probing Memory Bank #2 Nothing there

Probing Memory Bank #3 Nothing there

Probing Memory Bank #4 Nothing there

Probing Memory Bank #5 Nothing there

Probing Memory Bank #6 Nothing there

Probing Memory Bank #7 Nothing there

Incorrect configuration checksum;

Setting NVRAM parameters to default values.

Setting diag-switch? NVRAM parameter to true

Probing CPU FMI,MB86907

Probing 
/iommu@0,1000/sbus@0,10001000 at 
5,0  espdma esp sd st SUNW,bpp ledma le

Probing 
/iommu@0,1000/sbus@0,10001000 at 
4,0  SUNW,CS4231 power-management

Probing 
/iommu@0,1000/sbus@0,10001000 at 
1,0  Nothing there

Probing 
/iommu@0,1000/sbus@0,10001000 at 
2,0  Nothing there

Probing 
/iommu@0,1000/sbus@0,10001000 at 
3,0  SUNW,tcx

Probing 
/iommu@0,1000/sbus@0,10001000 at 
0,0  Nothing there

Probing Memory Bank #0 32 Megabytes

Probing Memory Bank #1 Nothing there

Probing Memory Bank #2 Nothing there

Probing Memory Bank #3 Nothing there

Probing Memory Bank #4 Nothing there

Probing Memory Bank #5 Nothing there

Probing Memory Bank #6 Nothing there

Probing Memory Bank #7 Nothing there

Incorrect configuration checksum;

Setting NVRAM parameters to default values.

Setting diag-switch? NVRAM parameter to true

Probing CPU FMI,MB86907

Probing 
/iommu@0,1000/sbus@0,10001000 at 
5,0  espdma esp sd st SUNW,bpp ledma le

Probing 
/iommu@0,1000/sbus@0,10001000 at 
4,0  SUNW,CS4231 power-management

Probing 
/iommu@0,1000/sbus@0,10001000 at 
1,0  Nothing there

Probing 
/iommu@0,1000/sbus@0,10001000 at 
2,0  Nothing there

Probing 
/iommu@0,1000/sbus@0,10001000 at 
3,0  SUNW,tcx

Probing 
/iommu@0,1000/sbus@0,10001000 at 
0,0  Nothing there


SPARCstation 5, No Keyboard

ROM Rev. 2.29, 32 MB memory installed, Serial #1193046.

Ethernet address 52:54:0:12:34:56, Host ID: 80123456.




Boot device: 
/iommu/sbus/ledma@5,8400010/le@5,8c0
  File and args:

Internal loopback test -- Wrong packet length; expected 36, observed 64


Can't open boot device


Type  help  for more information

ok boot disk0

Boot device: 
/iommu/sbus/espdma@5,840/esp@5,880/sd@0,0
  File and args:

root on 
/iommu@0,1000/sbus@0,10001000/espdma@5,840/esp@5,880/sd@0,0:a
 fstype 4.2

Boot: vmunix

Size: 1548288+463688+225704 bytes

VAC ENABLED

SunOS Release 4.1.4 (GENERIC) #2: Fri Oct 14 11:09:47 PDT 1994

Copyright (c) 1983-1993, Sun Microsystems, Inc.

cpu = SUNW,SPARCstation-5

mod0 = FMI,MB86907 (mid = 0)

mem = 32396K (0x1fa3000)

avail mem = 28839936

entering uniprocessor mode

Ethernet address = 52:54:0:12:34:56

espdma0 at  SBus slot 5 0x840

esp0 at  SBus slot 5 0x880 pri 4 (onboard)

sd3:non-CCS device found at target 0 lun 0 on esp0

sd3 at esp0 target 0 lun 0

sd3: 

Warning! System Clock freq out of range!

ledma0 at  SBus slot 5 0x8400010

le0

Re: [Qemu-discuss] [vfio-users] Device not tied to a QemuConsole.

2017-10-07 Thread José Pekkarinen
> You need a time machine because the thing you're trying to do hasn't
> been implemented yet, it's under discussion upstream.  Thanks,

Wow! Where is my flux capacitor when I need it...

Out of curiosity, is the vnc use case something that depends in 
anything 
else but Qemu? I guess the spice case might need some support from intel or 
qxl driver to handle the display.

For now, mediated devices are usable for linux guests and in windows 
may 
be for opencl and background rendering, right?

Thanks Alex for the clarification!

José.