[TestDay] F20 Xen 4.4 RC3 Spice support

[TestDay] F20 Xen 4.4 RC3 Spice support

[Eric Houby]

Xen list,

I am trying to boot a F20 guest and connect using Spice but have run
into an issue.  

My VM config file includes:
spice = 1
spicehost='0.0.0.0'
spiceport=6001
spicedisable_ticketing=1


Is Spice supported with qemu-xen-traditional? 


[root@xen ~]# xl -vvv create f20.xl
Parsing config from f20.xl
libxl: debug: libxl_create.c:1342:do_domain_create: ao 0x795750: create:
how=(nil) callback=(nil) poller=0x794e10
libxl: verbose: libxl_create.c:134:libxl__domain_build_info_setdefault:
qemu-xen is unavailable, use qemu-xen-traditional instead: No such file
or directory
libxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: Disk
vdev=hda spec.backend=unknown
libxl: debug: libxl_device.c:286:libxl__device_disk_set_backend: Disk
vdev=hda, using backend phy
libxl: debug: libxl_create.c:797:initiate_domain_create: running
bootloader
libxl: debug: libxl_bootloader.c:321:libxl__bootloader_run: not a PV
domain, skipping bootloader
libxl: debug: libxl_event.c:607:libxl__ev_xswatch_deregister: watch
w=0x795af8: deregister unregistered
libxl: debug: libxl_numa.c:475:libxl__get_numa_candidate: New best NUMA
placement candidate found: nr_nodes=1, nr_cpus=8, nr_vcpus=4,
free_memkb=14131
libxl: detail: libxl_dom.c:195:numa_place_domain: NUMA placement
candidate with 1 nodes, 8 cpus and 14131 KB free selected
xc: detail: elf_parse_binary: phdr: paddr=0x100000 memsz=0x9e704
xc: detail: elf_parse_binary: memory: 0x100000 -> 0x19e704
xc: detail: VIRTUAL MEMORY ARRANGEMENT:
  Loader:        0000000000100000->000000000019e704
  Modules:       0000000000000000->0000000000000000
  TOTAL:         0000000000000000->00000000ffc00000
  ENTRY ADDRESS: 0000000000100000
xc: detail: PHYSICAL MEMORY ALLOCATION:
  4KB PAGES: 0x0000000000000200
  2MB PAGES: 0x00000000000003fd
  1GB PAGES: 0x0000000000000002
xc: detail: elf_load_binary: phdr 0 at 0x7f87b7100000 -> 0x7f87b719558d
libxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: Disk
vdev=hda spec.backend=phy
libxl: debug: libxl_event.c:559:libxl__ev_xswatch_register: watch
w=0x796f68 wpath=/local/domain/0/backend/vbd/3/768/state token=3/0:
register slotnum=3
libxl: debug: libxl_create.c:1356:do_domain_create: ao 0x795750:
inprogress: poller=0x794e10, flags=i
libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0x796f68
wpath=/local/domain/0/backend/vbd/3/768/state token=3/0: event
epath=/local/domain/0/backend/vbd/3/768/state
libxl: debug: libxl_event.c:646:devstate_watch_callback:
backend /local/domain/0/backend/vbd/3/768/state wanted state 2 still
waiting state 1
libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0x796f68
wpath=/local/domain/0/backend/vbd/3/768/state token=3/0: event
epath=/local/domain/0/backend/vbd/3/768/state
libxl: debug: libxl_event.c:642:devstate_watch_callback:
backend /local/domain/0/backend/vbd/3/768/state wanted state 2 ok
libxl: debug: libxl_event.c:595:libxl__ev_xswatch_deregister: watch
w=0x796f68 wpath=/local/domain/0/backend/vbd/3/768/state token=3/0:
deregister slotnum=3
libxl: debug: libxl_event.c:607:libxl__ev_xswatch_deregister: watch
w=0x796f68: deregister unregistered
libxl: debug: libxl_device.c:1022:device_hotplug: calling hotplug
script: /etc/xen/scripts/block add
libxl: debug: libxl_event.c:607:libxl__ev_xswatch_deregister: watch
w=0x796ff0: deregister unregistered
libxl: debug: libxl_event.c:607:libxl__ev_xswatch_deregister: watch
w=0x796ff0: deregister unregistered
libxl: debug: libxl_dm.c:1303:libxl__spawn_local_dm: Spawning
device-model /usr/lib/xen/bin/qemu-dm with arguments:
libxl: debug:
libxl_dm.c:1305:libxl__spawn_local_dm:   /usr/lib/xen/bin/qemu-dm
libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm:   -d
libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm:   3
libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm:   -domain-name
libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm:   f20
libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm:   -videoram
libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm:   4
libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm:   -boot
libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm:   c
libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm:   -acpi
libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm:   -vcpus
libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm:   2
libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm:   -vcpu_avail
libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm:   0x03
libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm:   -net
libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm:
nic,vlan=0,macaddr=00:16:00:00:11:22,model=e1000
libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm:   -net
libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm:
tap,vlan=0,ifname=vif3.0-emu,bridge=br0,script=no,downscript=no
libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm:   -M
libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm:   xenfv
libxl: debug: libxl_event.c:559:libxl__ev_xswatch_register: watch
w=0x795d30 wpath=/local/domain/0/device-model/3/state token=3/1:
register slotnum=3
libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0x795d30
wpath=/local/domain/0/device-model/3/state token=3/1: event
epath=/local/domain/0/device-model/3/state
libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0x795d30
wpath=/local/domain/0/device-model/3/state token=3/1: event
epath=/local/domain/0/device-model/3/state
libxl: debug: libxl_event.c:595:libxl__ev_xswatch_deregister: watch
w=0x795d30 wpath=/local/domain/0/device-model/3/state token=3/1:
deregister slotnum=3
libxl: debug: libxl_event.c:607:libxl__ev_xswatch_deregister: watch
w=0x795d30: deregister unregistered
libxl: debug: libxl_event.c:559:libxl__ev_xswatch_register: watch
w=0x79a038 wpath=/local/domain/0/backend/vif/3/0/state token=3/2:
register slotnum=3
libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0x79a038
wpath=/local/domain/0/backend/vif/3/0/state token=3/2: event
epath=/local/domain/0/backend/vif/3/0/state
libxl: debug: libxl_event.c:646:devstate_watch_callback:
backend /local/domain/0/backend/vif/3/0/state wanted state 2 still
waiting state 1
libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0x79a038
wpath=/local/domain/0/backend/vif/3/0/state token=3/2: event
epath=/local/domain/0/backend/vif/3/0/state
libxl: debug: libxl_event.c:642:devstate_watch_callback:
backend /local/domain/0/backend/vif/3/0/state wanted state 2 ok
libxl: debug: libxl_event.c:595:libxl__ev_xswatch_deregister: watch
w=0x79a038 wpath=/local/domain/0/backend/vif/3/0/state token=3/2:
deregister slotnum=3
libxl: debug: libxl_event.c:607:libxl__ev_xswatch_deregister: watch
w=0x79a038: deregister unregistered
libxl: debug: libxl_device.c:1022:device_hotplug: calling hotplug
script: /etc/xen/scripts/vif-bridge online
libxl: debug: libxl_event.c:607:libxl__ev_xswatch_deregister: watch
w=0x79a0c0: deregister unregistered
libxl: debug: libxl_device.c:1022:device_hotplug: calling hotplug
script: /etc/xen/scripts/vif-bridge add
libxl: debug: libxl_event.c:607:libxl__ev_xswatch_deregister: watch
w=0x79a0c0: deregister unregistered
libxl: debug: libxl_event.c:607:libxl__ev_xswatch_deregister: watch
w=0x79a0c0: deregister unregistered
libxl: debug: libxl_event.c:1729:libxl__ao_progress_report: ao 0x795750:
progress report: ignored
libxl: debug: libxl_event.c:1559:libxl__ao_complete: ao 0x795750:
complete, rc=0
libxl: debug: libxl_event.c:1531:libxl__ao__destroy: ao 0x795750:
destroy
xc: debug: hypercall buffer: total allocations:1097 total releases:1097
xc: debug: hypercall buffer: current allocations:0 maximum allocations:4
xc: debug: hypercall buffer: cache current size:4
xc: debug: hypercall buffer: cache hits:1089 misses:4 toobig:4
[root@xen ~]# 

The QEMU command line created is:

/usr/lib/xen/bin/qemu-dm -d 3 -domain-name f20 -videoram 4 -boot c -acpi
-vcpus 2 -vcpu_avail 0x03 -net
nic,vlan=0,macaddr=00:16:00:00:11:22,model=e1000 -net
tap,vlan=0,ifname=vif3.0-emu,bridge=br0,script=no,downscript=no -M xenfv



Thanks,

Eric

Re: [TestDay] F20 Xen 4.4 RC3 Spice support

[Fabio Fantoni]

Il 04/02/2014 16:41, Eric Houby ha scritto:
> Xen list,
>
> I am trying to boot a F20 guest and connect using Spice but have run
> into an issue.
>
> My VM config file includes:
> spice = 1
> spicehost='0.0.0.0'
> spiceport=6001
> spicedisable_ticketing=1
>
>
> Is Spice supported with qemu-xen-traditional?

No, only with upstream qemu and if compile xen and qemu from source you 
also enable spice support on qemu build, for example on my xen build 
tests I add:

tools/Makefile
@@ -201,6 +201,8 @@ subdir-all-qemu-xen-dir: qemu-xen-dir-find
          --datadir=$(SHAREDIR)/qemu-xen \
          --localstatedir=/var \
          --disable-kvm \
+        --enable-spice \
+        --enable-usb-redir \
          --disable-docs \
          --disable-guest-agent \
          --python=$(PYTHON) \

If you use upstream qemu from distribution package probably have already 
spice build-in, for example, on debian I've already tested and working.

>
>
> [root@xen ~]# xl -vvv create f20.xl
> Parsing config from f20.xl
> libxl: debug: libxl_create.c:1342:do_domain_create: ao 0x795750: create:
> how=(nil) callback=(nil) poller=0x794e10
> libxl: verbose: libxl_create.c:134:libxl__domain_build_info_setdefault:
> qemu-xen is unavailable, use qemu-xen-traditional instead: No such file
> or directory
> libxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: Disk
> vdev=hda spec.backend=unknown
> libxl: debug: libxl_device.c:286:libxl__device_disk_set_backend: Disk
> vdev=hda, using backend phy
> libxl: debug: libxl_create.c:797:initiate_domain_create: running
> bootloader
> libxl: debug: libxl_bootloader.c:321:libxl__bootloader_run: not a PV
> domain, skipping bootloader
> libxl: debug: libxl_event.c:607:libxl__ev_xswatch_deregister: watch
> w=0x795af8: deregister unregistered
> libxl: debug: libxl_numa.c:475:libxl__get_numa_candidate: New best NUMA
> placement candidate found: nr_nodes=1, nr_cpus=8, nr_vcpus=4,
> free_memkb=14131
> libxl: detail: libxl_dom.c:195:numa_place_domain: NUMA placement
> candidate with 1 nodes, 8 cpus and 14131 KB free selected
> xc: detail: elf_parse_binary: phdr: paddr=0x100000 memsz=0x9e704
> xc: detail: elf_parse_binary: memory: 0x100000 -> 0x19e704
> xc: detail: VIRTUAL MEMORY ARRANGEMENT:
>    Loader:        0000000000100000->000000000019e704
>    Modules:       0000000000000000->0000000000000000
>    TOTAL:         0000000000000000->00000000ffc00000
>    ENTRY ADDRESS: 0000000000100000
> xc: detail: PHYSICAL MEMORY ALLOCATION:
>    4KB PAGES: 0x0000000000000200
>    2MB PAGES: 0x00000000000003fd
>    1GB PAGES: 0x0000000000000002
> xc: detail: elf_load_binary: phdr 0 at 0x7f87b7100000 -> 0x7f87b719558d
> libxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: Disk
> vdev=hda spec.backend=phy
> libxl: debug: libxl_event.c:559:libxl__ev_xswatch_register: watch
> w=0x796f68 wpath=/local/domain/0/backend/vbd/3/768/state token=3/0:
> register slotnum=3
> libxl: debug: libxl_create.c:1356:do_domain_create: ao 0x795750:
> inprogress: poller=0x794e10, flags=i
> libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0x796f68
> wpath=/local/domain/0/backend/vbd/3/768/state token=3/0: event
> epath=/local/domain/0/backend/vbd/3/768/state
> libxl: debug: libxl_event.c:646:devstate_watch_callback:
> backend /local/domain/0/backend/vbd/3/768/state wanted state 2 still
> waiting state 1
> libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0x796f68
> wpath=/local/domain/0/backend/vbd/3/768/state token=3/0: event
> epath=/local/domain/0/backend/vbd/3/768/state
> libxl: debug: libxl_event.c:642:devstate_watch_callback:
> backend /local/domain/0/backend/vbd/3/768/state wanted state 2 ok
> libxl: debug: libxl_event.c:595:libxl__ev_xswatch_deregister: watch
> w=0x796f68 wpath=/local/domain/0/backend/vbd/3/768/state token=3/0:
> deregister slotnum=3
> libxl: debug: libxl_event.c:607:libxl__ev_xswatch_deregister: watch
> w=0x796f68: deregister unregistered
> libxl: debug: libxl_device.c:1022:device_hotplug: calling hotplug
> script: /etc/xen/scripts/block add
> libxl: debug: libxl_event.c:607:libxl__ev_xswatch_deregister: watch
> w=0x796ff0: deregister unregistered
> libxl: debug: libxl_event.c:607:libxl__ev_xswatch_deregister: watch
> w=0x796ff0: deregister unregistered
> libxl: debug: libxl_dm.c:1303:libxl__spawn_local_dm: Spawning
> device-model /usr/lib/xen/bin/qemu-dm with arguments:
> libxl: debug:
> libxl_dm.c:1305:libxl__spawn_local_dm:   /usr/lib/xen/bin/qemu-dm
> libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm:   -d
> libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm:   3
> libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm:   -domain-name
> libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm:   f20
> libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm:   -videoram
> libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm:   4
> libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm:   -boot
> libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm:   c
> libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm:   -acpi
> libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm:   -vcpus
> libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm:   2
> libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm:   -vcpu_avail
> libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm:   0x03
> libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm:   -net
> libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm:
> nic,vlan=0,macaddr=00:16:00:00:11:22,model=e1000
> libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm:   -net
> libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm:
> tap,vlan=0,ifname=vif3.0-emu,bridge=br0,script=no,downscript=no
> libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm:   -M
> libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm:   xenfv
> libxl: debug: libxl_event.c:559:libxl__ev_xswatch_register: watch
> w=0x795d30 wpath=/local/domain/0/device-model/3/state token=3/1:
> register slotnum=3
> libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0x795d30
> wpath=/local/domain/0/device-model/3/state token=3/1: event
> epath=/local/domain/0/device-model/3/state
> libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0x795d30
> wpath=/local/domain/0/device-model/3/state token=3/1: event
> epath=/local/domain/0/device-model/3/state
> libxl: debug: libxl_event.c:595:libxl__ev_xswatch_deregister: watch
> w=0x795d30 wpath=/local/domain/0/device-model/3/state token=3/1:
> deregister slotnum=3
> libxl: debug: libxl_event.c:607:libxl__ev_xswatch_deregister: watch
> w=0x795d30: deregister unregistered
> libxl: debug: libxl_event.c:559:libxl__ev_xswatch_register: watch
> w=0x79a038 wpath=/local/domain/0/backend/vif/3/0/state token=3/2:
> register slotnum=3
> libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0x79a038
> wpath=/local/domain/0/backend/vif/3/0/state token=3/2: event
> epath=/local/domain/0/backend/vif/3/0/state
> libxl: debug: libxl_event.c:646:devstate_watch_callback:
> backend /local/domain/0/backend/vif/3/0/state wanted state 2 still
> waiting state 1
> libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0x79a038
> wpath=/local/domain/0/backend/vif/3/0/state token=3/2: event
> epath=/local/domain/0/backend/vif/3/0/state
> libxl: debug: libxl_event.c:642:devstate_watch_callback:
> backend /local/domain/0/backend/vif/3/0/state wanted state 2 ok
> libxl: debug: libxl_event.c:595:libxl__ev_xswatch_deregister: watch
> w=0x79a038 wpath=/local/domain/0/backend/vif/3/0/state token=3/2:
> deregister slotnum=3
> libxl: debug: libxl_event.c:607:libxl__ev_xswatch_deregister: watch
> w=0x79a038: deregister unregistered
> libxl: debug: libxl_device.c:1022:device_hotplug: calling hotplug
> script: /etc/xen/scripts/vif-bridge online
> libxl: debug: libxl_event.c:607:libxl__ev_xswatch_deregister: watch
> w=0x79a0c0: deregister unregistered
> libxl: debug: libxl_device.c:1022:device_hotplug: calling hotplug
> script: /etc/xen/scripts/vif-bridge add
> libxl: debug: libxl_event.c:607:libxl__ev_xswatch_deregister: watch
> w=0x79a0c0: deregister unregistered
> libxl: debug: libxl_event.c:607:libxl__ev_xswatch_deregister: watch
> w=0x79a0c0: deregister unregistered
> libxl: debug: libxl_event.c:1729:libxl__ao_progress_report: ao 0x795750:
> progress report: ignored
> libxl: debug: libxl_event.c:1559:libxl__ao_complete: ao 0x795750:
> complete, rc=0
> libxl: debug: libxl_event.c:1531:libxl__ao__destroy: ao 0x795750:
> destroy
> xc: debug: hypercall buffer: total allocations:1097 total releases:1097
> xc: debug: hypercall buffer: current allocations:0 maximum allocations:4
> xc: debug: hypercall buffer: cache current size:4
> xc: debug: hypercall buffer: cache hits:1089 misses:4 toobig:4
> [root@xen ~]#
>
> The QEMU command line created is:
>
> /usr/lib/xen/bin/qemu-dm -d 3 -domain-name f20 -videoram 4 -boot c -acpi
> -vcpus 2 -vcpu_avail 0x03 -net
> nic,vlan=0,macaddr=00:16:00:00:11:22,model=e1000 -net
> tap,vlan=0,ifname=vif3.0-emu,bridge=br0,script=no,downscript=no -M xenfv
>
>
>
> Thanks,
>
> Eric
>
>
>
>
>
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

Re: [TestDay] F20 Xen 4.4 RC3 Spice support

[Eric Houby]

On Tue, 2014-02-04 at 17:01 +0100, Fabio Fantoni wrote:
> Il 04/02/2014 16:41, Eric Houby ha scritto:
> > Xen list,
> >
> > I am trying to boot a F20 guest and connect using Spice but have run
> > into an issue.
> >
> > My VM config file includes:
> > spice = 1
> > spicehost='0.0.0.0'
> > spiceport=6001
> > spicedisable_ticketing=1
> >
> >
> > Is Spice supported with qemu-xen-traditional?
> 
> No, only with upstream qemu and if compile xen and qemu from source you 
> also enable spice support on qemu build, for example on my xen build 
> tests I add:
> 
> tools/Makefile
> @@ -201,6 +201,8 @@ subdir-all-qemu-xen-dir: qemu-xen-dir-find
>           --datadir=$(SHAREDIR)/qemu-xen \
>           --localstatedir=/var \
>           --disable-kvm \
> +        --enable-spice \
> +        --enable-usb-redir \
>           --disable-docs \
>           --disable-guest-agent \
>           --python=$(PYTHON) \
> 
> If you use upstream qemu from distribution package probably have already 
> spice build-in, for example, on debian I've already tested and working.
> 

It is my understanding that the qemu package in F20 does not support xen
so I compiled xen from source per the RC3 Test Day instructions and the
instructions here:

http://wiki.xenproject.org/wiki/Compiling_Xen_From_Source

After adding --enable-spice and --enable-usb-redir to tools/Makefile I
see the following error when I make xen:

ERROR: User requested feature spice
       configure was not able to find it

The build finishes and xen works fine but spice obviously does not work.
More complete log is below.

Thanks,

Eric


if test -d git://xenbits.xen.org/qemu-upstream-unstable.git ; then \
        mkdir -p qemu-xen-dir; \
else \
        export GIT=git; \
        /root/src/xen/tools/../scripts/git-checkout.sh
git://xenbits.xen.org/qemu-upstream-unstable.git q
emu-xen-4.4.0-rc3 qemu-xen-dir ; \
fi
if test -d git://xenbits.xen.org/qemu-upstream-unstable.git ; then \
        source=git://xenbits.xen.org/qemu-upstream-unstable.git; \
else \
        source=.; \
fi; \
cd qemu-xen-dir; \
$source/configure --enable-xen --target-list=i386-softmmu \
        --enable-debug --enable-trace-backend=stderr \
        --prefix=/usr/local \
        --source-path=$source \
        --extra-cflags="-I/root/src/xen/tools/../tools/include \
        -I/root/src/xen/tools/../tools/libxc \
        -I/root/src/xen/tools/../tools/xenstore \
        -I/root/src/xen/tools/../tools/xenstore/compat \
        " \
        --extra-ldflags="-L/root/src/xen/tools/../tools/libxc \
        -L/root/src/xen/tools/../tools/xenstore" \
        --bindir=/usr/local/lib/xen/bin \
        --datadir=/usr/local/share/qemu-xen \
        --localstatedir=/var \
        --disable-kvm \
        --enable-spice \
        --enable-usb-redir \
        --disable-docs \
        --disable-guest-agent \
        --python=python \
        ; \
make all

ERROR: User requested feature spice
       configure was not able to find it

make[3]: Entering directory `/root/src/xen/tools/qemu-xen-dir-remote'
make[3]: Leaving directory `/root/src/xen/tools/qemu-xen-dir-remote'

Re: [TestDay] F20 Xen 4.4 RC3 Spice support

[Sander Eikelenboom]

Wednesday, February 5, 2014, 5:00:08 AM, you wrote:

> On Tue, 2014-02-04 at 17:01 +0100, Fabio Fantoni wrote:
>> Il 04/02/2014 16:41, Eric Houby ha scritto:
>> > Xen list,
>> >
>> > I am trying to boot a F20 guest and connect using Spice but have run
>> > into an issue.
>> >
>> > My VM config file includes:
>> > spice = 1
>> > spicehost='0.0.0.0'
>> > spiceport=6001
>> > spicedisable_ticketing=1
>> >
>> >
>> > Is Spice supported with qemu-xen-traditional?
>> 
>> No, only with upstream qemu and if compile xen and qemu from source you 
>> also enable spice support on qemu build, for example on my xen build 
>> tests I add:
>> 
>> tools/Makefile
>> @@ -201,6 +201,8 @@ subdir-all-qemu-xen-dir: qemu-xen-dir-find
>>           --datadir=$(SHAREDIR)/qemu-xen \
>>           --localstatedir=/var \
>>           --disable-kvm \
>> +        --enable-spice \
>> +        --enable-usb-redir \
>>           --disable-docs \
>>           --disable-guest-agent \
>>           --python=$(PYTHON) \
>> 
>> If you use upstream qemu from distribution package probably have already 
>> spice build-in, for example, on debian I've already tested and working.
>> 

> It is my understanding that the qemu package in F20 does not support xen
> so I compiled xen from source per the RC3 Test Day instructions and the
> instructions here:

> http://wiki.xenproject.org/wiki/Compiling_Xen_From_Source

> After adding --enable-spice and --enable-usb-redir to tools/Makefile I
> see the following error when I make xen:

> ERROR: User requested feature spice
>        configure was not able to find it

Do you have the libspice-dev packages installed for your distro ?

> The build finishes and xen works fine but spice obviously does not work.
> More complete log is below.

> Thanks,

> Eric


> if test -d git://xenbits.xen.org/qemu-upstream-unstable.git ; then \
>         mkdir -p qemu-xen-dir; \
> else \
>         export GIT=git; \
>         /root/src/xen/tools/../scripts/git-checkout.sh
> git://xenbits.xen.org/qemu-upstream-unstable.git q
> emu-xen-4.4.0-rc3 qemu-xen-dir ; \
> fi
> if test -d git://xenbits.xen.org/qemu-upstream-unstable.git ; then \
>         source=git://xenbits.xen.org/qemu-upstream-unstable.git; \
> else \
>         source=.; \
> fi; \
> cd qemu-xen-dir; \
> $source/configure --enable-xen --target-list=i386-softmmu \
>         --enable-debug --enable-trace-backend=stderr \
>         --prefix=/usr/local \
>         --source-path=$source \
>         --extra-cflags="-I/root/src/xen/tools/../tools/include \
>         -I/root/src/xen/tools/../tools/libxc \
>         -I/root/src/xen/tools/../tools/xenstore \
>         -I/root/src/xen/tools/../tools/xenstore/compat \
>         " \
>         --extra-ldflags="-L/root/src/xen/tools/../tools/libxc \
>         -L/root/src/xen/tools/../tools/xenstore" \
>         --bindir=/usr/local/lib/xen/bin \
>         --datadir=/usr/local/share/qemu-xen \
>         --localstatedir=/var \
>         --disable-kvm \
>         --enable-spice \
>         --enable-usb-redir \
>         --disable-docs \
>         --disable-guest-agent \
>         --python=python \
>         ; \
> make all

> ERROR: User requested feature spice
>        configure was not able to find it

> make[3]: Entering directory `/root/src/xen/tools/qemu-xen-dir-remote'
> make[3]: Leaving directory `/root/src/xen/tools/qemu-xen-dir-remote'

Re: [TestDay] F20 Xen 4.4 RC3 Spice support

[Eric Houby]

On Wed, 2014-02-05 at 09:06 +0100, Sander Eikelenboom wrote:
> Wednesday, February 5, 2014, 5:00:08 AM, you wrote:
> 
> > On Tue, 2014-02-04 at 17:01 +0100, Fabio Fantoni wrote:
> >> Il 04/02/2014 16:41, Eric Houby ha scritto:
> >> > Xen list,
> >> >
> >> > I am trying to boot a F20 guest and connect using Spice but have run
> >> > into an issue.
> >> >
> >> > My VM config file includes:
> >> > spice = 1
> >> > spicehost='0.0.0.0'
> >> > spiceport=6001
> >> > spicedisable_ticketing=1
> >> >
> >> >
> >> > Is Spice supported with qemu-xen-traditional?
> >> 
> >> No, only with upstream qemu and if compile xen and qemu from source you 
> >> also enable spice support on qemu build, for example on my xen build 
> >> tests I add:
> >> 
> >> tools/Makefile
> >> @@ -201,6 +201,8 @@ subdir-all-qemu-xen-dir: qemu-xen-dir-find
> >>           --datadir=$(SHAREDIR)/qemu-xen \
> >>           --localstatedir=/var \
> >>           --disable-kvm \
> >> +        --enable-spice \
> >> +        --enable-usb-redir \
> >>           --disable-docs \
> >>           --disable-guest-agent \
> >>           --python=$(PYTHON) \
> >> 
> >> If you use upstream qemu from distribution package probably have already 
> >> spice build-in, for example, on debian I've already tested and working.
> >> 
> 
> > It is my understanding that the qemu package in F20 does not support xen
> > so I compiled xen from source per the RC3 Test Day instructions and the
> > instructions here:
> 
> > http://wiki.xenproject.org/wiki/Compiling_Xen_From_Source
> 
> > After adding --enable-spice and --enable-usb-redir to tools/Makefile I
> > see the following error when I make xen:
> 
> > ERROR: User requested feature spice
> >        configure was not able to find it
> 
> Do you have the libspice-dev packages installed for your distro ?
> 

I do now. I also have the usbredir-devel package. 

Thanks for the help.

Re: [TestDay] F20 Xen 4.4 RC3 Spice support

[Eric Houby]

On Wed, 2014-02-05 at 17:17 -0700, Eric Houby wrote:
> On Wed, 2014-02-05 at 09:06 +0100, Sander Eikelenboom wrote:
> > Wednesday, February 5, 2014, 5:00:08 AM, you wrote:
> > 
> > > On Tue, 2014-02-04 at 17:01 +0100, Fabio Fantoni wrote:
> > >> Il 04/02/2014 16:41, Eric Houby ha scritto:
> > >> > Xen list,
> > >> >
> > >> > I am trying to boot a F20 guest and connect using Spice but have run
> > >> > into an issue.
> > >> >
> > >> > My VM config file includes:
> > >> > spice = 1
> > >> > spicehost='0.0.0.0'
> > >> > spiceport=6001
> > >> > spicedisable_ticketing=1
> > >> >
> > >> >
> > >> > Is Spice supported with qemu-xen-traditional?
> > >> 
> > >> No, only with upstream qemu and if compile xen and qemu from source you 
> > >> also enable spice support on qemu build, for example on my xen build 
> > >> tests I add:
> > >> 
> > >> tools/Makefile
> > >> @@ -201,6 +201,8 @@ subdir-all-qemu-xen-dir: qemu-xen-dir-find
> > >>           --datadir=$(SHAREDIR)/qemu-xen \
> > >>           --localstatedir=/var \
> > >>           --disable-kvm \
> > >> +        --enable-spice \
> > >> +        --enable-usb-redir \
> > >>           --disable-docs \
> > >>           --disable-guest-agent \
> > >>           --python=$(PYTHON) \
> > >> 
> > >> If you use upstream qemu from distribution package probably have already 
> > >> spice build-in, for example, on debian I've already tested and working.
> > >> 
> > 
> > > It is my understanding that the qemu package in F20 does not support xen
> > > so I compiled xen from source per the RC3 Test Day instructions and the
> > > instructions here:
> > 
> > > http://wiki.xenproject.org/wiki/Compiling_Xen_From_Source
> > 
> > > After adding --enable-spice and --enable-usb-redir to tools/Makefile I
> > > see the following error when I make xen:
> > 
> > > ERROR: User requested feature spice
> > >        configure was not able to find it
> > 
> > Do you have the libspice-dev packages installed for your distro ?
> > 
> 
> I do now. I also have the usbredir-devel package. 
> 
> Thanks for the help.
> 

Is there a knob for qxl support?

[root@xen ~]# cat /var/log/xen/qemu-dm-f20.log
qemu-system-i386: -vga qxl: invalid option

Re: [TestDay] F20 Xen 4.4 RC3 Spice support

[Fabio Fantoni]

[-- Attachment #1.1: Type: text/plain, Size: 3138 bytes --]

2014-02-06 5:23 GMT+01:00 Eric Houby <ehouby@yahoo.com>:

> On Wed, 2014-02-05 at 17:17 -0700, Eric Houby wrote:
> > On Wed, 2014-02-05 at 09:06 +0100, Sander Eikelenboom wrote:
> > > Wednesday, February 5, 2014, 5:00:08 AM, you wrote:
> > >
> > > > On Tue, 2014-02-04 at 17:01 +0100, Fabio Fantoni wrote:
> > > >> Il 04/02/2014 16:41, Eric Houby ha scritto:
> > > >> > Xen list,
> > > >> >
> > > >> > I am trying to boot a F20 guest and connect using Spice but have
> run
> > > >> > into an issue.
> > > >> >
> > > >> > My VM config file includes:
> > > >> > spice = 1
> > > >> > spicehost='0.0.0.0'
> > > >> > spiceport=6001
> > > >> > spicedisable_ticketing=1
> > > >> >
> > > >> >
> > > >> > Is Spice supported with qemu-xen-traditional?
> > > >>
> > > >> No, only with upstream qemu and if compile xen and qemu from source
> you
> > > >> also enable spice support on qemu build, for example on my xen build
> > > >> tests I add:
> > > >>
> > > >> tools/Makefile
> > > >> @@ -201,6 +201,8 @@ subdir-all-qemu-xen-dir: qemu-xen-dir-find
> > > >>           --datadir=$(SHAREDIR)/qemu-xen \
> > > >>           --localstatedir=/var \
> > > >>           --disable-kvm \
> > > >> +        --enable-spice \
> > > >> +        --enable-usb-redir \
> > > >>           --disable-docs \
> > > >>           --disable-guest-agent \
> > > >>           --python=$(PYTHON) \
> > > >>
> > > >> If you use upstream qemu from distribution package probably have
> already
> > > >> spice build-in, for example, on debian I've already tested and
> working.
> > > >>
> > >
> > > > It is my understanding that the qemu package in F20 does not support
> xen
> > > > so I compiled xen from source per the RC3 Test Day instructions and
> the
> > > > instructions here:
> > >
> > > > http://wiki.xenproject.org/wiki/Compiling_Xen_From_Source
> > >
> > > > After adding --enable-spice and --enable-usb-redir to tools/Makefile
> I
> > > > see the following error when I make xen:
> > >
> > > > ERROR: User requested feature spice
> > > >        configure was not able to find it
> > >
> > > Do you have the libspice-dev packages installed for your distro ?
> > >
> >
> > I do now. I also have the usbredir-devel package.
> >
> > Thanks for the help.
> >
>
> Is there a knob for qxl support?
>
> [root@xen ~]# cat /var/log/xen/qemu-dm-f20.log
> qemu-system-i386: -vga qxl: invalid option
>
>
>
>
>
Here there is a patch that add qxl support in libxl updated to xen 4.4-rc3
if you want add it:
https://github.com/Fantu/Xen/commit/f1e3f78f7b9580700591cebd98e9263645bff56b
Or you can simply compile from this already ready for spice/qxl testing:
https://github.com/Fantu/Xen/commits/rebase/m2r-testing

Is not upstream for now because there is something on xen that make it not
working on linux domUs with qxl driver active and working with high
performance problem on windows domUs.
I spent several days without finding the exact problem to be solved :(
If you want you can try it out and see if anything changes using Fedora instead
of Debian as dom0, differents kernel domUs etc.
Maybe you could even find some new informations/errors useful for solving the
problem.

[-- Attachment #1.2: Type: text/html, Size: 5475 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [TestDay] F20 Xen 4.4 RC3 Spice support

[Eric Houby]

On Thu, 2014-02-06 at 08:35 +0100, Fabio Fantoni wrote:


>         Is there a knob for qxl support?
>         
>         [root@xen ~]# cat /var/log/xen/qemu-dm-f20.log
>         qemu-system-i386: -vga qxl: invalid option

> 
> Here there is a patch that add qxl support in libxl updated to xen
> 4.4-rc3 if you want add it:
> https://github.com/Fantu/Xen/commit/f1e3f78f7b9580700591cebd98e9263645bff56b
> 
> Or you can simply compile from this already ready for spice/qxl
> testing:
> https://github.com/Fantu/Xen/commits/rebase/m2r-testing
> 
> 
> 
> Is not upstream for now because there is something on xen that make it
> not working on linux domUs with qxl driver active and working with
> high performance problem on windows domUs.
> I spent several days without finding the exact problem to be solved :(
> If you want you can try it out and see if anything changes using
> Fedora instead of Debian as dom0, differents kernel domUs etc.
> Maybe you could even find some new informations/errors useful for
> solving the problem.
> 

I am not very familiar with compiling nor with github, but I did learn
that by adding .patch to your first link, it was possible to get the
changes in a patch file format.  Applying the patch generated these
errors:

[root@xen xen]# patch -p1 < patch1.txt 
patching file docs/man/xl.cfg.pod.5
Hunk #2 FAILED at 1085.
1 out of 2 hunks FAILED -- saving rejects to file
docs/man/xl.cfg.pod.5.rej
patching file tools/libxl/libxl_create.c
Hunk #1 FAILED at 229.
Hunk #2 FAILED at 252.
2 out of 2 hunks FAILED -- saving rejects to file
tools/libxl/libxl_create.c.rej
patching file tools/libxl/libxl_dm.c
Hunk #1 succeeded at 217 with fuzz 2 (offset -3 lines).
Hunk #2 succeeded at 517 with fuzz 2 (offset -5 lines).
patching file tools/libxl/libxl_types.idl
Hunk #1 FAILED at 154.
1 out of 1 hunk FAILED -- saving rejects to file
tools/libxl/libxl_types.idl.rej
patching file tools/libxl/xl_cmdimpl.c
Hunk #1 FAILED at 1669.
1 out of 1 hunk FAILED -- saving rejects to file
tools/libxl/xl_cmdimpl.c.rej

By inspecting the code, I could tell that there were some missing
patches (VGA interface type none was missing) compared to the RC3 source
that I have.  Would you mind helping with the additional patches that I
need?  Is so, I will try to help with the qxl issue.

Thanks,

Eric

Re: [TestDay] F20 Xen 4.4 RC3 Spice support

[Fabio Fantoni]

[-- Attachment #1.1: Type: text/plain, Size: 2790 bytes --]

2014-02-07 6:03 GMT+01:00 Eric Houby <ehouby@yahoo.com>:

> On Thu, 2014-02-06 at 08:35 +0100, Fabio Fantoni wrote:
>
>
> >         Is there a knob for qxl support?
> >
> >         [root@xen ~]# cat /var/log/xen/qemu-dm-f20.log
> >         qemu-system-i386: -vga qxl: invalid option
>
> >
> > Here there is a patch that add qxl support in libxl updated to xen
> > 4.4-rc3 if you want add it:
> >
> https://github.com/Fantu/Xen/commit/f1e3f78f7b9580700591cebd98e9263645bff56b
> >
> > Or you can simply compile from this already ready for spice/qxl
> > testing:
> > https://github.com/Fantu/Xen/commits/rebase/m2r-testing
> >
> >
> >
> > Is not upstream for now because there is something on xen that make it
> > not working on linux domUs with qxl driver active and working with
> > high performance problem on windows domUs.
> > I spent several days without finding the exact problem to be solved :(
> > If you want you can try it out and see if anything changes using
> > Fedora instead of Debian as dom0, differents kernel domUs etc.
> > Maybe you could even find some new informations/errors useful for
> > solving the problem.
> >
>
> I am not very familiar with compiling nor with github, but I did learn
> that by adding .patch to your first link, it was possible to get the
> changes in a patch file format.  Applying the patch generated these
> errors:
>
> [root@xen xen]# patch -p1 < patch1.txt
> patching file docs/man/xl.cfg.pod.5
> Hunk #2 FAILED at 1085.
> 1 out of 2 hunks FAILED -- saving rejects to file
> docs/man/xl.cfg.pod.5.rej
> patching file tools/libxl/libxl_create.c
> Hunk #1 FAILED at 229.
> Hunk #2 FAILED at 252.
> 2 out of 2 hunks FAILED -- saving rejects to file
> tools/libxl/libxl_create.c.rej
> patching file tools/libxl/libxl_dm.c
> Hunk #1 succeeded at 217 with fuzz 2 (offset -3 lines).
> Hunk #2 succeeded at 517 with fuzz 2 (offset -5 lines).
> patching file tools/libxl/libxl_types.idl
> Hunk #1 FAILED at 154.
> 1 out of 1 hunk FAILED -- saving rejects to file
> tools/libxl/libxl_types.idl.rej
> patching file tools/libxl/xl_cmdimpl.c
> Hunk #1 FAILED at 1669.
> 1 out of 1 hunk FAILED -- saving rejects to file
> tools/libxl/xl_cmdimpl.c.rej
>
> By inspecting the code, I could tell that there were some missing
> patches (VGA interface type none was missing) compared to the RC3 source
> that I have.  Would you mind helping with the additional patches that I
> need?  Is so, I will try to help with the qxl issue.
>
> Thanks,
>
> Eric
>
>
>
Yes, fail because is applied after vga none patch that modified neighboring
lines.
Apply vga none before and qxl patch after should make both applicable
without conflict.
Should not cause problems because both have already been reviewed by thelibxl
/qemu maintainers and improved following their advices.

[-- Attachment #1.2: Type: text/html, Size: 4215 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [TestDay] F20 Xen 4.4 RC3 Spice support

[Dario Faggioli]

[-- Attachment #1.1: Type: text/plain, Size: 2272 bytes --]

On gio, 2014-02-06 at 08:35 +0100, Fabio Fantoni wrote:
> 2014-02-06 5:23 GMT+01:00 Eric Houby <ehouby@yahoo.com>:

>         Is there a knob for qxl support?
>         
>         [root@xen ~]# cat /var/log/xen/qemu-dm-f20.log
>         qemu-system-i386: -vga qxl: invalid option
>
> 
> Here there is a patch that add qxl support in libxl updated to xen
> 4.4-rc3 if you want add it:
> https://github.com/Fantu/Xen/commit/f1e3f78f7b9580700591cebd98e9263645bff56b
> 
> Or you can simply compile from this already ready for spice/qxl
> testing:
> https://github.com/Fantu/Xen/commits/rebase/m2r-testing
> 
> 
> 
> Is not upstream for now because there is something on xen that make it
> not working on linux domUs with qxl driver active and working with
> high performance problem on windows domUs.
>
Right.

> I spent several days without finding the exact problem to be solved :(
> If you want you can try it out and see if anything changes using
> Fedora instead of Debian as dom0, differents kernel domUs etc.
> Maybe you could even find some new informations/errors useful for
> solving the problem.
>
Yep, that would help... let us know! :-)

Anyway, first of all, sorry for my spice/qxl ignorance.

What I just wanted to say is this: searching the wiki, all I found about
spice and QXL is this section in the QEMU Upstream page:
http://wiki.xen.org/wiki/QEMU_Upstream#SPICE_.2F_QXL

Perhaps someone of you can double check whether the information there is
still fresh and accurate enough? Perhaps it's also worth adding
references to the patches mentioned above (with the proper disclaimer
about the known issues, of course)?

Also, maybe for the next DocsDay, this would be a nice one to have too:
http://wiki.xen.org/wiki/Xen_Document_Days/TODO#Spice_Config_Example_for_upstream_QEMU

If keen on doing any of the above that involves modifying the wiki, send
me a note, and I think I can provide the necessary permissions.

Thanks and Regards,
Dario

-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)


[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [TestDay] F20 Xen 4.4 RC3 Spice support

[Fabio Fantoni]

Il 07/02/2014 10:08, Dario Faggioli ha scritto:
> On gio, 2014-02-06 at 08:35 +0100, Fabio Fantoni wrote:
>> 2014-02-06 5:23 GMT+01:00 Eric Houby <ehouby@yahoo.com>:
>>          Is there a knob for qxl support?
>>          
>>          [root@xen ~]# cat /var/log/xen/qemu-dm-f20.log
>>          qemu-system-i386: -vga qxl: invalid option
>>
>>
>> Here there is a patch that add qxl support in libxl updated to xen
>> 4.4-rc3 if you want add it:
>> https://github.com/Fantu/Xen/commit/f1e3f78f7b9580700591cebd98e9263645bff56b
>>
>> Or you can simply compile from this already ready for spice/qxl
>> testing:
>> https://github.com/Fantu/Xen/commits/rebase/m2r-testing
>>
>>
>>
>> Is not upstream for now because there is something on xen that make it
>> not working on linux domUs with qxl driver active and working with
>> high performance problem on windows domUs.
>>
> Right.
>
>> I spent several days without finding the exact problem to be solved :(
>> If you want you can try it out and see if anything changes using
>> Fedora instead of Debian as dom0, differents kernel domUs etc.
>> Maybe you could even find some new informations/errors useful for
>> solving the problem.
>>
> Yep, that would help... let us know! :-)
>
> Anyway, first of all, sorry for my spice/qxl ignorance.
>
> What I just wanted to say is this: searching the wiki, all I found about
> spice and QXL is this section in the QEMU Upstream page:
> http://wiki.xen.org/wiki/QEMU_Upstream#SPICE_.2F_QXL
>
> Perhaps someone of you can double check whether the information there is
> still fresh and accurate enough? Perhaps it's also worth adding
> references to the patches mentioned above (with the proper disclaimer
> about the known issues, of course)?
>
> Also, maybe for the next DocsDay, this would be a nice one to have too:
> http://wiki.xen.org/wiki/Xen_Document_Days/TODO#Spice_Config_Example_for_upstream_QEMU
>
> If keen on doing any of the above that involves modifying the wiki, send
> me a note, and I think I can provide the necessary permissions.

The wiki should be updated, the qxl patch for libxl part is complete and 
correct and can be used for tests:
https://github.com/Fantu/Xen/commit/f1e3f78f7b9580700591cebd98e9263645bff56b
the actual problem is off of libxl.
Probably are on hvmloader, qemu and/or kernel.

The latest mail about qxl problem that I send:
http://lists.xen.org/archives/html/xen-devel/2013-12/msg00758.html

Shortly in the latest tests I have got:
- on windows 7 domU with xen_platform_pci=0 the worse video refresh 
performance with qxl seems was "solved" but unfortunately is a problem 
without pv drivers (neeeded for xl save/restore/shutdown).
- on Saucy (ubuntu 13.10) domU with "xen/pvhvm: If xen_platform_pci=0 is 
set don't blow up" patch even with xen_platform_pci=0 I got a 100% cpu 
X.org and black screen. So there is probably another problem on linux 
domUs kernel-side and/or xorg's qxl drivers.
- on Fedora19 domU, comparing kvm and xen hosts the only difference I 
have found is the following error in /var/log/messages:
> ioremap error for 0xfc001000-0xfc002000, requested 0x10, got 0x0

There also this from old tests:
> And about xen hypervisor logs (with xl dmesg) the only difference 
> between stdvga and qxl (same domU) is that qxl log has 3 "pci dev bar" 
> more.
Which may be useful to understand if further hvmloader modification are 
needed.
I have not knowledge about it to say anything certain.

If someone want help me, please reply if further tests/data needed and 
I'll post them.

Thanks for any reply.

>
> Thanks and Regards,
> Dario
>

Re: [TestDay] F20 Xen 4.4 RC3 Spice support

[Eric Houby]

On Fri, 2014-02-07 at 11:52 +0100, Fabio Fantoni wrote:
> Il 07/02/2014 10:08, Dario Faggioli ha scritto:
> > On gio, 2014-02-06 at 08:35 +0100, Fabio Fantoni wrote:

> 
> The wiki should be updated, the qxl patch for libxl part is complete and 
> correct and can be used for tests:
> https://github.com/Fantu/Xen/commit/f1e3f78f7b9580700591cebd98e9263645bff56b
> the actual problem is off of libxl.
> Probably are on hvmloader, qemu and/or kernel.
> 
> The latest mail about qxl problem that I send:
> http://lists.xen.org/archives/html/xen-devel/2013-12/msg00758.html
> 

I have everything built and would like to make a quick observation.
>From what I have read, the qxl minimum and default video ram is 128MB
but the qemu command line is showing 64MB even when set to 128MB in the
xl config file.

spice = 1
spicehost = '0.0.0.0'
spiceport = 6001
spicedisable_ticketing = 1
spicevdagent = 1
videoram = 128
vga = 'qxl'

/usr/local/lib/xen/bin/qemu-system-i386 -xen-domid 18 -chardev
socket,id=libxl-cmd,path=/var/run/xen/qmp-libxl-18,server,nowait -mon
chardev=libxl-cmd,mode=control -nodefaults -name f20 -serial pty -spice
port=6001,tls-port=0,addr=0.0.0.0,disable-ticketing,agent-mouse=on
-device virtio-serial -chardev spicevmc,id=vdagent,name=vdagent -device
virtserialport,chardev=vdagent,name=com.redhat.spice.0 -device
qxl-vga,vram_size_mb=64,ram_size_mb=64 -boot order=c -smp 2,maxcpus=2
-device virtio-net,id=nic0,netdev=net0,mac=00:16:00:00:11:22 -netdev
type=tap,id=net0,ifname=vif18.0-emu,script=no,downscript=no -machine
xenfv -m 3968 -drive
file=/dev/mapper/xen_vm-f20pvhvm,if=ide,index=0,media=disk,format=raw,cache=writeback

Commenting out the videoram=128 line still shows 64MB in the qemu
command line.

-Eric

Re: [TestDay] F20 Xen 4.4 RC3 Spice support

[Fabio Fantoni]

[-- Attachment #1.1: Type: text/plain, Size: 2887 bytes --]

2014-02-08 0:37 GMT+01:00 Eric Houby <ehouby@yahoo.com>:

> On Fri, 2014-02-07 at 11:52 +0100, Fabio Fantoni wrote:
> > Il 07/02/2014 10:08, Dario Faggioli ha scritto:
> > > On gio, 2014-02-06 at 08:35 +0100, Fabio Fantoni wrote:
>
> >
> > The wiki should be updated, the qxl patch for libxl part is complete and
> > correct and can be used for tests:
> >
> https://github.com/Fantu/Xen/commit/f1e3f78f7b9580700591cebd98e9263645bff56b
> > the actual problem is off of libxl.
> > Probably are on hvmloader, qemu and/or kernel.
> >
> > The latest mail about qxl problem that I send:
> > http://lists.xen.org/archives/html/xen-devel/2013-12/msg00758.html
> >
>
> I have everything built and would like to make a quick observation.
> From what I have read, the qxl minimum and default video ram is 128MB
> but the qemu command line is showing 64MB even when set to 128MB in the
> xl config file.
>
> spice = 1
> spicehost = '0.0.0.0'
> spiceport = 6001
> spicedisable_ticketing = 1
> spicevdagent = 1
> videoram = 128
> vga = 'qxl'
>
> /usr/local/lib/xen/bin/qemu-system-i386 -xen-domid 18 -chardev
> socket,id=libxl-cmd,path=/var/run/xen/qmp-libxl-18,server,nowait -mon
> chardev=libxl-cmd,mode=control -nodefaults -name f20 -serial pty -spice
> port=6001,tls-port=0,addr=0.0.0.0,disable-ticketing,agent-mouse=on
> -device virtio-serial -chardev spicevmc,id=vdagent,name=vdagent -device
> virtserialport,chardev=vdagent,name=com.redhat.spice.0 -device
> qxl-vga,vram_size_mb=64,ram_size_mb=64 -boot order=c -smp 2,maxcpus=2
> -device virtio-net,id=nic0,netdev=net0,mac=00:16:00:00:11:22 -netdev
> type=tap,id=net0,ifname=vif18.0-emu,script=no,downscript=no -machine
> xenfv -m 3968 -drive
>
> file=/dev/mapper/xen_vm-f20pvhvm,if=ide,index=0,media=disk,format=raw,cache=writeback
>
> Commenting out the videoram=128 line still shows 64MB in the qemu
> command line.
>
> -Eric
>
>
>
Is correct, see also comment on patch... QXL have 2 ram regions, ram and
vram
I not found anymore the old qemu patch on one mailing list which describes in
detail the qxl structure :(
In shortly, if I remember correctly was:
First region contain basic framebuffer, default 16 mb and up to half of
region that is the used also without qxl driver active (when working as
standard vga), and the other two part of this region contain commands and
cache.
Second region contains the cache of render and various advanced operations,
when it was written that I had read the description it seems to me that had
not yet been implemented.
Is very likely to have done something wrong in the description that I do
not remember.
However, the parameters are correct, I had confirmation from developers qemu
/ spice last year and I also remember that it was better not to go with the
ram under 64 MB for the first region so I set the minimum to 128 total.
If I'll find the official and detailed qxl description I'll post it.

[-- Attachment #1.2: Type: text/html, Size: 5588 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [TestDay] F20 Xen 4.4 RC3 Spice support

[Dario Faggioli]

On Wed, Feb 5, 2014 at 5:00 AM, Eric Houby <ehouby@yahoo.com> wrote:
> It is my understanding that the qemu package in F20 does not support xen
> so I compiled xen from source per the RC3 Test Day instructions and the
> instructions here:
>
Yes, we figured out that was the case during the previous TestDay.
Michael, any news on this? Who should we be talking with to have Xen
enabled in default Fedora qemu package build? I guess it won't be a
F20 thing anyway, but let's make sure we will have that enable in the
next Fedora release! :-)

Regards,
Dario

Re: [TestDay] F20 Xen 4.4 RC3 Spice support

[George Dunlap]

On Tue, Feb 4, 2014 at 4:01 PM, Fabio Fantoni <fabio.fantoni@m2r.biz> wrote:
> Il 04/02/2014 16:41, Eric Houby ha scritto:
>
>> Xen list,
>>
>> I am trying to boot a F20 guest and connect using Spice but have run
>> into an issue.
>>
>> My VM config file includes:
>> spice = 1
>> spicehost='0.0.0.0'
>> spiceport=6001
>> spicedisable_ticketing=1
>>
>>
>> Is Spice supported with qemu-xen-traditional?
>
>
> No, only with upstream qemu and if compile xen and qemu from source you also
> enable spice support on qemu build, for example on my xen build tests I add:
>
> tools/Makefile
> @@ -201,6 +201,8 @@ subdir-all-qemu-xen-dir: qemu-xen-dir-find
>          --datadir=$(SHAREDIR)/qemu-xen \
>          --localstatedir=/var \
>          --disable-kvm \
> +        --enable-spice \
> +        --enable-usb-redir \
>          --disable-docs \
>          --disable-guest-agent \
>          --python=$(PYTHON) \
>
> If you use upstream qemu from distribution package probably have already
> spice build-in, for example, on debian I've already tested and working.

It might be nice at some point to have this integrated into the
top-level configure, possibly enabled by default (gated on the
appropriate development libraries being enabled).

 -George

Re: [TestDay] F20 Xen 4.4 RC3 Spice support

[Fabio Fantoni]

Il 10/02/2014 18:05, George Dunlap ha scritto:
> On Tue, Feb 4, 2014 at 4:01 PM, Fabio Fantoni <fabio.fantoni@m2r.biz> wrote:
>> Il 04/02/2014 16:41, Eric Houby ha scritto:
>>
>>> Xen list,
>>>
>>> I am trying to boot a F20 guest and connect using Spice but have run
>>> into an issue.
>>>
>>> My VM config file includes:
>>> spice = 1
>>> spicehost='0.0.0.0'
>>> spiceport=6001
>>> spicedisable_ticketing=1
>>>
>>>
>>> Is Spice supported with qemu-xen-traditional?
>>
>> No, only with upstream qemu and if compile xen and qemu from source you also
>> enable spice support on qemu build, for example on my xen build tests I add:
>>
>> tools/Makefile
>> @@ -201,6 +201,8 @@ subdir-all-qemu-xen-dir: qemu-xen-dir-find
>>           --datadir=$(SHAREDIR)/qemu-xen \
>>           --localstatedir=/var \
>>           --disable-kvm \
>> +        --enable-spice \
>> +        --enable-usb-redir \
>>           --disable-docs \
>>           --disable-guest-agent \
>>           --python=$(PYTHON) \
>>
>> If you use upstream qemu from distribution package probably have already
>> spice build-in, for example, on debian I've already tested and working.
> It might be nice at some point to have this integrated into the
> top-level configure, possibly enabled by default (gated on the
> appropriate development libraries being enabled).
>
>   -George

I already did a patch to do it time ago in three different ways but all 
rejected :(
A one reason was the lack of needed libraries on many distros versions 
used with xen.
Now all newer versions have the needed spice and usbredir libraries 
included, so if you would like reconsider the path please point me in 
the right direction in order to have this done correctly.
The three way I did were:
- enabled by default
- Added optional build configs for qemu upstream (debug part now no more 
needed because already present) 
http://lists.xen.org/archives/html/xen-devel/2012-03/msg00506.html
- Autoconf: add variable for pass arbitrary options to qemu upstream 
http://lists.xen.org/archives/html/xen-devel/2012-03/msg01677.html
Probably there are also newer versions of these patches that I not found 
anymore.

Thanks for any reply.

Re: [TestDay] F20 Xen 4.4 RC3 Spice support

[Fabio Fantoni]

Il 11/02/2014 10:56, Fabio Fantoni ha scritto:
> Il 10/02/2014 18:05, George Dunlap ha scritto:
>> On Tue, Feb 4, 2014 at 4:01 PM, Fabio Fantoni <fabio.fantoni@m2r.biz> 
>> wrote:
>>> Il 04/02/2014 16:41, Eric Houby ha scritto:
>>>
>>>> Xen list,
>>>>
>>>> I am trying to boot a F20 guest and connect using Spice but have run
>>>> into an issue.
>>>>
>>>> My VM config file includes:
>>>> spice = 1
>>>> spicehost='0.0.0.0'
>>>> spiceport=6001
>>>> spicedisable_ticketing=1
>>>>
>>>>
>>>> Is Spice supported with qemu-xen-traditional?
>>>
>>> No, only with upstream qemu and if compile xen and qemu from source 
>>> you also
>>> enable spice support on qemu build, for example on my xen build 
>>> tests I add:
>>>
>>> tools/Makefile
>>> @@ -201,6 +201,8 @@ subdir-all-qemu-xen-dir: qemu-xen-dir-find
>>>           --datadir=$(SHAREDIR)/qemu-xen \
>>>           --localstatedir=/var \
>>>           --disable-kvm \
>>> +        --enable-spice \
>>> +        --enable-usb-redir \
>>>           --disable-docs \
>>>           --disable-guest-agent \
>>>           --python=$(PYTHON) \
>>>
>>> If you use upstream qemu from distribution package probably have 
>>> already
>>> spice build-in, for example, on debian I've already tested and working.
>> It might be nice at some point to have this integrated into the
>> top-level configure, possibly enabled by default (gated on the
>> appropriate development libraries being enabled).
>>
>>   -George
>
> I already did a patch to do it time ago in three different ways but 
> all rejected :(
> A one reason was the lack of needed libraries on many distros versions 
> used with xen.
> Now all newer versions have the needed spice and usbredir libraries 
> included, so if you would like reconsider the path please point me in 
> the right direction in order to have this done correctly.

> The three way I did were:
> - enabled by default
> - Added optional build configs for qemu upstream (debug part now no 
> more needed because already present) 
> http://lists.xen.org/archives/html/xen-devel/2012-03/msg00506.html
> - Autoconf: add variable for pass arbitrary options to qemu upstream 
> http://lists.xen.org/archives/html/xen-devel/2012-03/msg01677.html
> Probably there are also newer versions of these patches that I not 
> found anymore.
>
> Thanks for any reply.

Ping

Re: [TestDay] F20 Xen 4.4 RC3 Spice support

[Fabio Fantoni]

Il 11/02/2014 10:56, Fabio Fantoni ha scritto:
> Il 10/02/2014 18:05, George Dunlap ha scritto:
>> On Tue, Feb 4, 2014 at 4:01 PM, Fabio Fantoni <fabio.fantoni@m2r.biz> 
>> wrote:
>>> Il 04/02/2014 16:41, Eric Houby ha scritto:
>>>
>>>> Xen list,
>>>>
>>>> I am trying to boot a F20 guest and connect using Spice but have run
>>>> into an issue.
>>>>
>>>> My VM config file includes:
>>>> spice = 1
>>>> spicehost='0.0.0.0'
>>>> spiceport=6001
>>>> spicedisable_ticketing=1
>>>>
>>>>
>>>> Is Spice supported with qemu-xen-traditional?
>>>
>>> No, only with upstream qemu and if compile xen and qemu from source 
>>> you also
>>> enable spice support on qemu build, for example on my xen build 
>>> tests I add:
>>>
>>> tools/Makefile
>>> @@ -201,6 +201,8 @@ subdir-all-qemu-xen-dir: qemu-xen-dir-find
>>>           --datadir=$(SHAREDIR)/qemu-xen \
>>>           --localstatedir=/var \
>>>           --disable-kvm \
>>> +        --enable-spice \
>>> +        --enable-usb-redir \
>>>           --disable-docs \
>>>           --disable-guest-agent \
>>>           --python=$(PYTHON) \
>>>
>>> If you use upstream qemu from distribution package probably have 
>>> already
>>> spice build-in, for example, on debian I've already tested and working.
>> It might be nice at some point to have this integrated into the
>> top-level configure, possibly enabled by default (gated on the
>> appropriate development libraries being enabled).
>>
>>   -George


>
> I already did a patch to do it time ago in three different ways but 
> all rejected :(
> A one reason was the lack of needed libraries on many distros versions 
> used with xen.
> Now all newer versions have the needed spice and usbredir libraries 
> included, so if you would like reconsider the path please point me in 
> the right direction in order to have this done correctly.
> The three way I did were:
> - enabled by default
> - Added optional build configs for qemu upstream (debug part now no 
> more needed because already present) 
> http://lists.xen.org/archives/html/xen-devel/2012-03/msg00506.html
> - Autoconf: add variable for pass arbitrary options to qemu upstream 
> http://lists.xen.org/archives/html/xen-devel/2012-03/msg01677.html
> Probably there are also newer versions of these patches that I not 
> found anymore.
>
> Thanks for any reply.

Ping.
Added also Ian Campbell and Ian Jackson to cc, which have been take part 
to the discussion about 2 years ago.

Thanks for any reply.

Re: [TestDay] F20 Xen 4.4 RC3 Spice support

[George Dunlap]

On Thu, Apr 10, 2014 at 1:26 PM, Fabio Fantoni <fabio.fantoni@m2r.biz> wrote:
> Il 11/02/2014 10:56, Fabio Fantoni ha scritto:
>>
>> Il 10/02/2014 18:05, George Dunlap ha scritto:
>>
>>> On Tue, Feb 4, 2014 at 4:01 PM, Fabio Fantoni <fabio.fantoni@m2r.biz>
>>> wrote:
>>>>
>>>> Il 04/02/2014 16:41, Eric Houby ha scritto:
>>>>
>>>>> Xen list,
>>>>>
>>>>> I am trying to boot a F20 guest and connect using Spice but have run
>>>>> into an issue.
>>>>>
>>>>> My VM config file includes:
>>>>> spice = 1
>>>>> spicehost='0.0.0.0'
>>>>> spiceport=6001
>>>>> spicedisable_ticketing=1
>>>>>
>>>>>
>>>>> Is Spice supported with qemu-xen-traditional?
>>>>
>>>>
>>>> No, only with upstream qemu and if compile xen and qemu from source you
>>>> also
>>>> enable spice support on qemu build, for example on my xen build tests I
>>>> add:
>>>>
>>>> tools/Makefile
>>>> @@ -201,6 +201,8 @@ subdir-all-qemu-xen-dir: qemu-xen-dir-find
>>>>           --datadir=$(SHAREDIR)/qemu-xen \
>>>>           --localstatedir=/var \
>>>>           --disable-kvm \
>>>> +        --enable-spice \
>>>> +        --enable-usb-redir \
>>>>           --disable-docs \
>>>>           --disable-guest-agent \
>>>>           --python=$(PYTHON) \
>>>>
>>>> If you use upstream qemu from distribution package probably have already
>>>> spice build-in, for example, on debian I've already tested and working.
>>>
>>> It might be nice at some point to have this integrated into the
>>> top-level configure, possibly enabled by default (gated on the
>>> appropriate development libraries being enabled).
>>>
>>>   -George
>
>
>
>>
>> I already did a patch to do it time ago in three different ways but all
>> rejected :(
>> A one reason was the lack of needed libraries on many distros versions
>> used with xen.
>> Now all newer versions have the needed spice and usbredir libraries
>> included, so if you would like reconsider the path please point me in the
>> right direction in order to have this done correctly.
>> The three way I did were:
>> - enabled by default
>> - Added optional build configs for qemu upstream (debug part now no more
>> needed because already present)
>> http://lists.xen.org/archives/html/xen-devel/2012-03/msg00506.html
>> - Autoconf: add variable for pass arbitrary options to qemu upstream
>> http://lists.xen.org/archives/html/xen-devel/2012-03/msg01677.html
>> Probably there are also newer versions of these patches that I not found
>> anymore.
>>
>> Thanks for any reply.
>
>
> Ping.
> Added also Ian Campbell and Ian Jackson to cc, which have been take part to
> the discussion about 2 years ago.

I think you'll need to rebase and re-post those patches if want us to
discuss them after 2 years.

 -George

Re: [TestDay] F20 Xen 4.4 RC3 Spice support

[Fabio Fantoni]

Il 10/04/2014 18:21, George Dunlap ha scritto:
> On Thu, Apr 10, 2014 at 1:26 PM, Fabio Fantoni <fabio.fantoni@m2r.biz> wrote:
>> Il 11/02/2014 10:56, Fabio Fantoni ha scritto:
>>> Il 10/02/2014 18:05, George Dunlap ha scritto:
>>>
>>>> On Tue, Feb 4, 2014 at 4:01 PM, Fabio Fantoni <fabio.fantoni@m2r.biz>
>>>> wrote:
>>>>> Il 04/02/2014 16:41, Eric Houby ha scritto:
>>>>>
>>>>>> Xen list,
>>>>>>
>>>>>> I am trying to boot a F20 guest and connect using Spice but have run
>>>>>> into an issue.
>>>>>>
>>>>>> My VM config file includes:
>>>>>> spice = 1
>>>>>> spicehost='0.0.0.0'
>>>>>> spiceport=6001
>>>>>> spicedisable_ticketing=1
>>>>>>
>>>>>>
>>>>>> Is Spice supported with qemu-xen-traditional?
>>>>>
>>>>> No, only with upstream qemu and if compile xen and qemu from source you
>>>>> also
>>>>> enable spice support on qemu build, for example on my xen build tests I
>>>>> add:
>>>>>
>>>>> tools/Makefile
>>>>> @@ -201,6 +201,8 @@ subdir-all-qemu-xen-dir: qemu-xen-dir-find
>>>>>            --datadir=$(SHAREDIR)/qemu-xen \
>>>>>            --localstatedir=/var \
>>>>>            --disable-kvm \
>>>>> +        --enable-spice \
>>>>> +        --enable-usb-redir \
>>>>>            --disable-docs \
>>>>>            --disable-guest-agent \
>>>>>            --python=$(PYTHON) \
>>>>>
>>>>> If you use upstream qemu from distribution package probably have already
>>>>> spice build-in, for example, on debian I've already tested and working.
>>>> It might be nice at some point to have this integrated into the
>>>> top-level configure, possibly enabled by default (gated on the
>>>> appropriate development libraries being enabled).
>>>>
>>>>    -George
>>
>>
>>> I already did a patch to do it time ago in three different ways but all
>>> rejected :(
>>> A one reason was the lack of needed libraries on many distros versions
>>> used with xen.
>>> Now all newer versions have the needed spice and usbredir libraries
>>> included, so if you would like reconsider the path please point me in the
>>> right direction in order to have this done correctly.
>>> The three way I did were:
>>> - enabled by default
>>> - Added optional build configs for qemu upstream (debug part now no more
>>> needed because already present)
>>> http://lists.xen.org/archives/html/xen-devel/2012-03/msg00506.html
>>> - Autoconf: add variable for pass arbitrary options to qemu upstream
>>> http://lists.xen.org/archives/html/xen-devel/2012-03/msg01677.html
>>> Probably there are also newer versions of these patches that I not found
>>> anymore.
>>>
>>> Thanks for any reply.
>>
>> Ping.
>> Added also Ian Campbell and Ian Jackson to cc, which have been take part to
>> the discussion about 2 years ago.
> I think you'll need to rebase and re-post those patches if want us to
> discuss them after 2 years.
>
>   -George

I think the best option would be to identify which one of the three 
methods is best before do updated and improve patch for it:
- spice and usbredir enabled by default in qemu upstream build
- optional spice and usbredir build configs for qemu upstream
- Autoconf: add variable for pass arbitrary build options to qemu upstream

Thanks for any reply.

Re: [TestDay] F20 Xen 4.4 RC3 Spice support

[George Dunlap]

[-- Attachment #1.1: Type: text/plain, Size: 4219 bytes --]

On 04/11/2014 08:52 AM, Fabio Fantoni wrote:
> Il 10/04/2014 18:21, George Dunlap ha scritto:
>> On Thu, Apr 10, 2014 at 1:26 PM, Fabio Fantoni 
>> <fabio.fantoni@m2r.biz> wrote:
>>> Il 11/02/2014 10:56, Fabio Fantoni ha scritto:
>>>> Il 10/02/2014 18:05, George Dunlap ha scritto:
>>>>
>>>>> On Tue, Feb 4, 2014 at 4:01 PM, Fabio Fantoni <fabio.fantoni@m2r.biz>
>>>>> wrote:
>>>>>> Il 04/02/2014 16:41, Eric Houby ha scritto:
>>>>>>
>>>>>>> Xen list,
>>>>>>>
>>>>>>> I am trying to boot a F20 guest and connect using Spice but have 
>>>>>>> run
>>>>>>> into an issue.
>>>>>>>
>>>>>>> My VM config file includes:
>>>>>>> spice = 1
>>>>>>> spicehost='0.0.0.0'
>>>>>>> spiceport=6001
>>>>>>> spicedisable_ticketing=1
>>>>>>>
>>>>>>>
>>>>>>> Is Spice supported with qemu-xen-traditional?
>>>>>>
>>>>>> No, only with upstream qemu and if compile xen and qemu from 
>>>>>> source you
>>>>>> also
>>>>>> enable spice support on qemu build, for example on my xen build 
>>>>>> tests I
>>>>>> add:
>>>>>>
>>>>>> tools/Makefile
>>>>>> @@ -201,6 +201,8 @@ subdir-all-qemu-xen-dir: qemu-xen-dir-find
>>>>>>            --datadir=$(SHAREDIR)/qemu-xen \
>>>>>>            --localstatedir=/var \
>>>>>>            --disable-kvm \
>>>>>> +        --enable-spice \
>>>>>> +        --enable-usb-redir \
>>>>>>            --disable-docs \
>>>>>>            --disable-guest-agent \
>>>>>>            --python=$(PYTHON) \
>>>>>>
>>>>>> If you use upstream qemu from distribution package probably have 
>>>>>> already
>>>>>> spice build-in, for example, on debian I've already tested and 
>>>>>> working.
>>>>> It might be nice at some point to have this integrated into the
>>>>> top-level configure, possibly enabled by default (gated on the
>>>>> appropriate development libraries being enabled).
>>>>>
>>>>>    -George
>>>
>>>
>>>> I already did a patch to do it time ago in three different ways but 
>>>> all
>>>> rejected :(
>>>> A one reason was the lack of needed libraries on many distros versions
>>>> used with xen.
>>>> Now all newer versions have the needed spice and usbredir libraries
>>>> included, so if you would like reconsider the path please point me 
>>>> in the
>>>> right direction in order to have this done correctly.
>>>> The three way I did were:
>>>> - enabled by default
>>>> - Added optional build configs for qemu upstream (debug part now no 
>>>> more
>>>> needed because already present)
>>>> http://lists.xen.org/archives/html/xen-devel/2012-03/msg00506.html
>>>> - Autoconf: add variable for pass arbitrary options to qemu upstream
>>>> http://lists.xen.org/archives/html/xen-devel/2012-03/msg01677.html
>>>> Probably there are also newer versions of these patches that I not 
>>>> found
>>>> anymore.
>>>>
>>>> Thanks for any reply.
>>>
>>> Ping.
>>> Added also Ian Campbell and Ian Jackson to cc, which have been take 
>>> part to
>>> the discussion about 2 years ago.
>> I think you'll need to rebase and re-post those patches if want us to
>> discuss them after 2 years.
>>
>>   -George
>
> I think the best option would be to identify which one of the three 
> methods is best before do updated and improve patch for it:
> - spice and usbredir enabled by default in qemu upstream build
> - optional spice and usbredir build configs for qemu upstream
> - Autoconf: add variable for pass arbitrary build options to qemu 
> upstream

Looking at that thread, it seems IanJ is in favor of something like your 
final approach (" [PATCH 
v3]Autoconf:addvariableforpassarbitraryoptionstoqemuupstream"); he 
apparently just dropped the thread.  (Or perhaps didn't realize that 
Roger had actually asked you to do the opposite of what he'd asked you 
to do -- it wasn't obvious to me the first time I went through it.)

Normally the thing to do would be to reply "Ping" to that patch, but 
given how long ago it was, it's probably a better idea to take the patch 
as it is, rebase it, and send it again (with [PATCH RESEND] in the 
subject line).

A couple of additional comments while I'm looking at it:
* After the v1->v2 change, you're no longer passing arbitrary options, 
so you should probably change the title of the patch again
* Don't include the patch version number in the commit message

  -George

[-- Attachment #1.2: Type: text/html, Size: 16520 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel