Forgot to say that it is not a matter of timeout :/, it's when pressing c
that it breaks

2015-01-04 1:07 GMT+01:00 Goonie Windy <monsieur.goo...@gmail.com>:

>  ok, I'm using the Upstream compiled in Xen so I created the file
> qemu-dbg, chmoded it etc...
>
>
>
> But that's as far as I can get:
>
>
> xl create result:
> WARNING: device model override given without specific DM version
> libxl: error: libxl_exec.c:421:spawn_middle_death: domain 32 device model
> [-1]: unexpectedly exited with exit status 0, when we were waiting for it
> to confirm startup
> libxl: error: libxl_dm.c:1490:device_model_spawn_outcome: domain 32 device
> model: spawn failed (rc=-3)
> libxl: error: libxl_create.c:1332:domcreate_devmodel_started: device model
> did not start: -3
> libxl: error: libxl_dm.c:1594:kill_device_model: Device Model already
> exited
>
>
> gdb output:
> target remote localhost:1234  c
> Remote debugging using localhost:1234  c
> Reading symbols from /lib64/ld-linux-x86-64.so.2...Reading symbols from
> /usr/lib/debug//lib/x86_64-linux-gnu/ld-2.19.so...done.
> done.
> Loaded symbols for /lib64/ld-linux-x86-64.so.2
> 0x00007ffff7ddd190 in _start () from /lib64/ld-linux-x86-64.so.2
> (gdb) c
> Continuing.
> [Inferior 1 (process 6455) exited with code 01]
>
>
>
> libxl_exec.c shows me
> 421(
>  else {
>         if (!status)
>             LOG(ERROR, "%s [%ld]: unexpectedly exited with exit status 0,"
>                 " when we were waiting for it to confirm startup",
>                 ss->what, (unsigned long)pid);
>         else if (status <= 127)
> )
>
>
> that it is a matter of status (?)  missing
>
>
> That's all I could find out.
>
> 2015-01-03 14:36 GMT+01:00 Fabio Fantoni <fabio.fant...@m2r.biz>:
>
>> 2015-01-03 1:24 GMT+01:00 Goonie Windy <monsieur.goo...@gmail.com>:
>>
>>> Fabio, actually I would have to compile qemu-dbg during compilation of
>>> xen, right?
>>> Because I uninstalled it for installing 4.5RC4.
>>>
>>
>> If you use qemu compiled in xen is not stripped is you have debug enabled
>> in xen config (enabled by default except stable release).
>> Qemu packages in debian seems not have -dbg package instead, I not
>> remember if are at least not stripped, if are stripped and without -dbg pkg
>> we should open a bugreport about in debian tracker.
>>
>>
>>>
>>> regards
>>>
>>> 2015-01-01 14:49 GMT+01:00 Fabio Fantoni <fabio.fant...@m2r.biz>:
>>>
>>>>
>>>> Il 01/01/2015 13:24, Goonie Windy ha scritto:
>>>>
>>>>  Hello Fabio, well same thing happens with remote-viewer,
>>>>
>>>>
>>>>  about not using dom0 as desktop, it's a laptop I'm using for those
>>>> tests,
>>>>
>>>>  Way to go is to use a blank machine with only Xen and then virtualise
>>>> all machines inside?
>>>>
>>>>
>>>> Try to post what version of qemu, spice ecc your are using, your domU
>>>> xl cfg and backtrace of the crash (following the howto I wrote should be
>>>> simple)
>>>>
>>>>
>>>>
>>>>
>>>> regards
>>>>
>>>>
>>>>
>>>> gregB
>>>>
>>>> 2015-01-01 12:45 GMT+01:00 Fabio Fantoni <fabio.fant...@m2r.biz>:
>>>>
>>>>>
>>>>> Il 01/01/2015 11:36, Goonie Windy ha scritto:
>>>>>
>>>>>  Actulally I have,
>>>>>
>>>>>  qemu-system-i38[13389]: segfault at 0 ip 00007fd3d166d801 sp
>>>>> 00007ffffc8595d0 error 4 in libspice-server.so.1.9.0[7fd3d1661000+11b000]
>>>>>
>>>>>  BTW happy new year
>>>>>
>>>>> 2015-01-01 11:30 GMT+01:00 Goonie Windy <monsieur.goo...@gmail.com>:
>>>>>
>>>>>>  Fabio,
>>>>>>
>>>>>>  ok for all concerning rombios ...
>>>>>>
>>>>>>  My spicec connection keeps on dying with
>>>>>>  "Spice-Warning **: red_peer.cpp:128:connect_to_peer: failed to
>>>>>> connect: Connexion refusée (111)"
>>>>>>  Then I can't access VM and have to destroy it.
>>>>>>
>>>>>>  I'm connecting with
>>>>>>  spicec -h 0.0.0.0 -p 6000
>>>>>>
>>>>>>  Any idea?
>>>>>>
>>>>>
>>>>>  spicec is very old and deprecated client and was already removed in
>>>>> spice git for next version.
>>>>> there are spicy and virt-viewer, the second is better.
>>>>> from address seems that you use dom0 as desktop, don't seems good for
>>>>> me^^''
>>>>>
>>>>> if you still have the qemu crash install spice debug package and take
>>>>> a backtrace with gdb.
>>>>>
>>>>> For use gdb on qemu as it child process is particular.
>>>>>
>>>>> Small help with gdb of qemu launched by xl:
>>>>> add the line below in domU's xl cfg:
>>>>> device_model_override="/usr/lib/xen/bin/qemu-gdb"
>>>>> vi /usr/lib/xen/bin/qemu-gdb # create the file, change the qemu path
>>>>> if needed
>>>>> #!/bin/sh
>>>>> exec gdbserver 0.0.0.0:1234 /usr/lib/xen/bin/qemu-system-i386 "$@"
>>>>> # after xl create with (qemu gdb), do it fast after xl create when
>>>>> arrive on qemu process launch (before timeout or xl create will fails)
>>>>> target remote localhost:1234 # prepare this command in other ssh to
>>>>> the xen dom0 and enter on xl create when arrive on qemu launch
>>>>> c # press immediatly
>>>>> bt full # when qemu stops with crash
>>>>>
>>>>>
>>>>>
>>>>>>
>>>>>> regards,
>>>>>>
>>>>>>  greg
>>>>>>
>>>>>> 2014-12-31 10:03 GMT+01:00 Fabio Fantoni <fabio.fant...@m2r.biz>:
>>>>>>
>>>>>>>  Il 31/12/2014 02:26, Goonie Windy ha scritto:
>>>>>>>
>>>>>>>  Ok Fabio, thanks to your configure, some bits of hacking the
>>>>>>> install part and lots of advises/support/encouragements ;) from Mark 
>>>>>>> Pryor
>>>>>>> I ended up
>>>>>>>   installing 4.5RC4 with QXL support on Deb8 unstable.
>>>>>>>
>>>>>>>
>>>>>>>  So now what do you want me to test fabio?
>>>>>>>  I have win7 x64 / win 2k8R2 vms in test mode ready to install
>>>>>>> drvers.
>>>>>>>
>>>>>>>  the numerous troubles I went through are related in the IRCcopy
>>>>>>> attached.
>>>>>>>  I actually couldn't build rombios and used seabios provided by the
>>>>>>> system -like you-
>>>>>>>  I should try to compile/find latest qxl now.
>>>>>>>
>>>>>>>
>>>>>>>  rombios is used only by qemu traditional that is very old, without
>>>>>>> spice support and hvm domUs have lower performance with it.
>>>>>>> qxl drivers in latest spice guest tools are signed and not require
>>>>>>> windows testsigning mode, same for james haper xen gplpv.
>>>>>>> If you want test new winpv drivers instead you need it.
>>>>>>>
>>>>>>> For me qxl is working good on w7 domUs except after save/restore
>>>>>>> when "freeze" 2-3 minutes on screen resolution change and I not found 
>>>>>>> the
>>>>>>> exact problem for now.
>>>>>>> I also not found how to have qxl working in linux domUs, on latest
>>>>>>> test xorg crash on start with qxl driver installed.
>>>>>>> Probably other changes are needed in hvmloader and/or xen hypervisor
>>>>>>> and/or qxl driver.
>>>>>>> Any help testing it is appreciated.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>  See you in 2K15.
>>>>>>>
>>>>>>>  greg B
>>>>>>>
>>>>>>> 2014-12-29 14:49 GMT+01:00 Fabio Fantoni <fabio.fant...@m2r.biz>:
>>>>>>>
>>>>>>>>  Il 29/12/2014 14:13, Goonie Windy ha scritto:
>>>>>>>>
>>>>>>>>   ok, I'm trying to patch the files with yours,
>>>>>>>>
>>>>>>>>
>>>>>>>>  I need to do it manually right?
>>>>>>>>
>>>>>>>> git apply is not working here.
>>>>>>>>
>>>>>>>>
>>>>>>>>  If the patch need a "refresh" the conflict should be solved
>>>>>>>> manually.
>>>>>>>> Taking the patch updated from here probably it can be applied to
>>>>>>>> latest 4.5-rc:
>>>>>>>> https://github.com/Fantu/Xen/commits/rebase/m2r-staging
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>  regards
>>>>>>>>
>>>>>>>>  greg
>>>>>>>>
>>>>>>>> 2014-12-29 13:46 GMT+01:00 Goonie Windy <monsieur.goo...@gmail.com>
>>>>>>>> :
>>>>>>>>
>>>>>>>>> There is an error in pageqs describing how to compile from sources
>>>>>>>>> as in 4.5
>>>>>>>>>
>>>>>>>>> cat .config
>>>>>>>>> PYTHON_PREFIX_ARG=--install-layout=deb
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> is in fact in .INSTALL
>>>>>>>>>
>>>>>>>>>
>>>>>>>>  If also you use debian you can use make debball that is better for
>>>>>>>> install/remove easy and fast test build.
>>>>>>>>
>>>>>>>> And for example I use this configure options with xen 4.5:
>>>>>>>> ./configure --prefix=/usr --disable-blktap1
>>>>>>>> --disable-qemu-traditional --disable-rombios
>>>>>>>> --with-system-seabios=/usr/share/seabios/bios-256k.bin
>>>>>>>> --with-extra-qemuu-configure-args="--enable-spice --enable-usb-redir"
>>>>>>>> --disable-blktap2
>>>>>>>> I use wheezy building updated packages from sid: seabios 1.7.5-1,
>>>>>>>> spice 0.12.5-1, spice-protocol 0.12.7-1 and usbredir 0.7-1.
>>>>>>>> If you use jessie instead you have all packages updated.
>>>>>>>>
>>>>>>>> About python I'm using this workaround (before execute configure)
>>>>>>>> even if probably is not the best:
>>>>>>>> Config.mk
>>>>>>>> -PYTHON_PREFIX_ARG ?= --prefix="$(PREFIX)"
>>>>>>>> +PYTHON_PREFIX_ARG ?=
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>> 2014-12-29 1:20 GMT+01:00 Goonie Windy <monsieur.goo...@gmail.com>
>>>>>>>>> :
>>>>>>>>>
>>>>>>>>>>  well figured out it is because you have to "enforce" locale:
>>>>>>>>>> export LC_ALL=en_US.utf-8 if keyboard mapping is else
>>>>>>>>>>
>>>>>>>>>> 2014-12-28 21:19 GMT+01:00 Goonie Windy <
>>>>>>>>>> monsieur.goo...@gmail.com>:
>>>>>>>>>>
>>>>>>>>>>>  Trying to compile xen 4.5RC4 in order to test your patch I end
>>>>>>>>>>> up with  these errors compiling the Seabios directories,
>>>>>>>>>>>
>>>>>>>>>>>  any idea?
>>>>>>>>>>>
>>>>>>>>>>>   Compiling to assembler out/src/asm-offsets.s
>>>>>>>>>>>   Generating offset file out/asm-offsets.h
>>>>>>>>>>>   Compiling (16bit) out/romlayout.o
>>>>>>>>>>>   Building ld scripts
>>>>>>>>>>> Version: rel-1.7.5-0-ge51488c-20141228_210340-E766
>>>>>>>>>>> Traceback (most recent call last):
>>>>>>>>>>>   File "./scripts/layoutrom.py", line 709, in <module>
>>>>>>>>>>>     main()
>>>>>>>>>>>   File "./scripts/layoutrom.py", line 671, in main
>>>>>>>>>>>     info16 = parseObjDump(infile16, '16')
>>>>>>>>>>>   File "./scripts/layoutrom.py", line 586, in parseObjDump
>>>>>>>>>>>     relocsection = sectionmap[sectionname]
>>>>>>>>>>> KeyError:
>>>>>>>>>>> '.text.asm./home/goon/xen/tools/firmware/seabios-dir-remote/src/fw/smp.c.79'
>>>>>>>>>>> Makefile:155: recipe for target 'out/romlayout16.lds' failed
>>>>>>>>>>> make[6]: *** [out/romlayout16.lds] Error 1
>>>>>>>>>>> make[6]: Leaving directory
>>>>>>>>>>> '/home/goon/xen/tools/firmware/seabios-dir-remote'
>>>>>>>>>>> /home/goon/xen/tools/firmware/../../tools/Rules.mk:116: recipe
>>>>>>>>>>> for target 'subdir-all-seabios-dir' failed
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> 2014-12-27 17:35 GMT+01:00 Goonie Windy <
>>>>>>>>>>> monsieur.goo...@gmail.com>:
>>>>>>>>>>>
>>>>>>>>>>>>   Hello Fabio,
>>>>>>>>>>>>
>>>>>>>>>>>> Sure thing I will help debug the win7 and the win8 versions.
>>>>>>>>>>>>  Where to start?
>>>>>>>>>>>>
>>>>>>>>>>>>  I'll try to see if I can patch with patch from
>>>>>>>>>>>> https://github.com/Fantu/Xen/commit/fadecf8d6ee0e8c7e421fafba67aa11879e8b8fe
>>>>>>>>>>>> and if not will post result.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> best regards,
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>  greg Bahde
>>>>>>>>>>>>
>>>>>>>>>>>> 2014-12-27 15:10 GMT+01:00 Fabio Fantoni <fabio.fant...@m2r.biz
>>>>>>>>>>>> >:
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Il 27/12/2014 02:15, Goonie Windy ha scritto:
>>>>>>>>>>>>>
>>>>>>>>>>>>>   I tried to install Qxl drivers under win7/win
>>>>>>>>>>>>> 2k8/win8.1         all       x64 versions, without any luck.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> admin message is as follow:
>>>>>>>>>>>>> Driver Management concluded the process to install driver
>>>>>>>>>>>>> FileRepository\qxl.inf_amd64_
>>>>>>>>>>>>> neutral_f0c429882d5c81ed\qxl.inf for Device Instance ID
>>>>>>>>>>>>> PCI\VEN_1013&DEV_00B8&SUBSYS_11001AF4&REV_00\3&267A616A&1&28 with 
>>>>>>>>>>>>> the
>>>>>>>>>>>>> following status: 0xe000022d.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>  Does
>>>>>>>>>>>>>
>>>>>>>>>>>>> http://lists.xen.org/archives/html/xen-devel/2014-05/msg03214.html
>>>>>>>>>>>>>
>>>>>>>>>>>>>  can it be installed on my xen stack?
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>  Yes but probably require a small refresh, I always posted the
>>>>>>>>>>>>> patch based on updated xen-unstable.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Here qxl patch refreshed for xen 4.5 if needed:
>>>>>>>>>>>>>
>>>>>>>>>>>>> https://github.com/Fantu/Xen/commit/fadecf8d6ee0e8c7e421fafba67aa11879e8b8fe
>>>>>>>>>>>>>
>>>>>>>>>>>>> Here the latest spice guest tools for windows with qxl driver
>>>>>>>>>>>>> included:
>>>>>>>>>>>>>
>>>>>>>>>>>>> http://www.spice-space.org/download/binaries/spice-guest-tools/spice-guest-tools-0.74.exe
>>>>>>>>>>>>>
>>>>>>>>>>>>> Windows >=8 and similar require a new qxl drivers, there are a
>>>>>>>>>>>>> beta build but latest tried some months ago have serious bug and 
>>>>>>>>>>>>> I not
>>>>>>>>>>>>> found recent build full working on windows 8.
>>>>>>>>>>>>>
>>>>>>>>>>>>> On xen windows 7 domUs qxl works good except a problem after
>>>>>>>>>>>>> save/restore and on linux domUs is not working, for now I not 
>>>>>>>>>>>>> found exactly
>>>>>>>>>>>>> cause and solution.
>>>>>>>>>>>>> On mailing list up to 2 years ago you can find many my mails
>>>>>>>>>>>>> about.
>>>>>>>>>>>>> Any help to test it is appreciated.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Sorry for my bad english.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Also, can  I get invited at xendevel irc ?
>>>>>>>>>>>>> regards
>>>>>>>>>>>>>
>>>>>>>>>>>>>  Greg
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>  _______________________________________________
>>>>>>>>>>>>> Xen-devel mailing 
>>>>>>>>>>>>> listxen-de...@lists.xen.orghttp://lists.xen.org/xen-devel
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Reply via email to