Hi, I''m debugging hvm guest S3 suspend/resume issue now. Currently when we use new qemu-xen w/ seabios, hvm s3 resume will block. However when we use old qemu-xen-traditional w/ rombios, hvm s3 works fine. Hence Seabios (xen version) is highly suspecious (We backport qemu-xen to standard qemu1.3.1 (standard qemu1.3.1 support guest s3 perfectly) -- but under xen, qemu1.3.1 + seabios (xen version) fail to support S3 resume). I try to define at config file as below to make qemu-xen co-work with old rombios, but obviously xl will fail: bios=''rombios'' device_model_override = ''/usr/local/lib/xen/bin/qemu-system-i386'' device_model_version = ''qemu-xen'' So my question is, can new qemu-xen co-work with old rombios? if yes, how can? Thanks, Jinsong
jacek burghardt
2013-Aug-05 18:01 UTC
Re: Question: can new qemu-xen co-work with old rombios?
You could patch xen with fedora patch to include custom location of bios file On Mon, Aug 5, 2013 at 10:01 AM, Liu, Jinsong <jinsong.liu@intel.com> wrote:> Hi, > > I''m debugging hvm guest S3 suspend/resume issue now. > Currently when we use new qemu-xen w/ seabios, hvm s3 resume will block. > However when we use old qemu-xen-traditional w/ rombios, hvm s3 works fine. > Hence Seabios (xen version) is highly suspecious (We backport qemu-xen to > standard qemu1.3.1 (standard qemu1.3.1 support guest s3 perfectly) -- but > under xen, qemu1.3.1 + seabios (xen version) fail to support S3 resume). > > I try to define at config file as below to make qemu-xen co-work with old > rombios, but obviously xl will fail: > bios=''rombios'' > device_model_override = ''/usr/local/lib/xen/bin/qemu-system-i386'' > device_model_version = ''qemu-xen'' > > So my question is, can new qemu-xen co-work with old rombios? if yes, how > can? > > Thanks, > Jinsong > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Ian Campbell
2013-Aug-05 18:17 UTC
Re: Question: can new qemu-xen co-work with old rombios?
On Mon, 2013-08-05 at 16:01 +0000, Liu, Jinsong wrote:> can new qemu-xen co-work with old rombios?No, this is not a supported combination. qemu-trad == rombios qemu-xen == seabios or ovmf. No other combinations are valid. Hopefully libxl/xl gave an error message when you tried? Ian.
Liu, Jinsong
2013-Aug-06 01:56 UTC
Re: Question: can new qemu-xen co-work with old rombios?
Ian Campbell wrote:> On Mon, 2013-08-05 at 16:01 +0000, Liu, Jinsong wrote: > >> can new qemu-xen co-work with old rombios? > > No, this is not a supported combination. > > qemu-trad == rombios > qemu-xen == seabios or ovmf. > > No other combinations are valid. Hopefully libxl/xl gave an error > message when you tried? > > Ian.Thanks Ian and Jacek! Yes, libxl does give error messages: libxl: error: libxl_dm.c:1300:libxl__destroy_device_model: could not find device-model''s pid for dom 1 libxl: error: libxl.c:1415:libxl__destroy_domid: libxl__destroy_device_model failed for 1 Thanks, Jinsong
Ian Campbell
2013-Aug-06 07:28 UTC
Re: Question: can new qemu-xen co-work with old rombios?
On Tue, 2013-08-06 at 01:56 +0000, Liu, Jinsong wrote:> Ian Campbell wrote: > > On Mon, 2013-08-05 at 16:01 +0000, Liu, Jinsong wrote: > > > >> can new qemu-xen co-work with old rombios? > > > > No, this is not a supported combination. > > > > qemu-trad == rombios > > qemu-xen == seabios or ovmf. > > > > No other combinations are valid. Hopefully libxl/xl gave an error > > message when you tried? > > > > Ian. > > Thanks Ian and Jacek! > > Yes, libxl does give error messages: > libxl: error: libxl_dm.c:1300:libxl__destroy_device_model: could not find device-model''s pid for dom 1 > libxl: error: libxl.c:1415:libxl__destroy_domid: libxl__destroy_device_model failed for 1Which version of Xen is this? Can you post the complete "xl -vvv create" output please, it really ought to be bailing with a message about the invalid combination of BIOS and qemu being attempted. I suspect the messages above are just benign messages printed as part of the attempt to tear down a partially built domain after the original failure. Ian.
Liu, Jinsong
2013-Aug-06 10:38 UTC
Re: Question: can new qemu-xen co-work with old rombios?
Ian Campbell wrote:> On Tue, 2013-08-06 at 01:56 +0000, Liu, Jinsong wrote: >> Ian Campbell wrote: >>> On Mon, 2013-08-05 at 16:01 +0000, Liu, Jinsong wrote: >>> >>>> can new qemu-xen co-work with old rombios? >>> >>> No, this is not a supported combination. >>> >>> qemu-trad == rombios >>> qemu-xen == seabios or ovmf. >>> >>> No other combinations are valid. Hopefully libxl/xl gave an error >>> message when you tried? >>> >>> Ian. >> >> Thanks Ian and Jacek! >> >> Yes, libxl does give error messages: >> libxl: error: libxl_dm.c:1300:libxl__destroy_device_model: could not >> find device-model''s pid for dom 1 libxl: error: >> libxl.c:1415:libxl__destroy_domid: libxl__destroy_device_model >> failed for 1 > > Which version of Xen is this? Can you post the complete "xl -vvv > create" output please, it really ought to be bailing with a message > about the invalid combination of BIOS and qemu being attempted. > > I suspect the messages above are just benign messages printed as part > of the attempt to tear down a partially built domain after the > original failure. > > Ian.My Xen git commit is 8f55cb0e360f977dc790adc393a6fd32b9933351. xl -vvv create xl.hvm output are: Parsing config from xl.hvm libxl: debug: libxl_create.c:1230:do_domain_create: ao 0x11238a0: create: how=(nil) callback=(nil) poller=0x1122f30 libxl: error: libxl_dm.c:1300:libxl__destroy_device_model: could not find device-model''s pid for dom 8 libxl: error: libxl.c:1415:libxl__destroy_domid: libxl__destroy_device_model failed for 8 libxl: debug: libxl_event.c:1569:libxl__ao_complete: ao 0x11238a0: complete, rc=-3 libxl: debug: libxl_create.c:1243:do_domain_create: ao 0x11238a0: inprogress: poller=0x1122f30, flags=ic libxl: debug: libxl_event.c:1541:libxl__ao__destroy: ao 0x11238a0: destroy xc: debug: hypercall buffer: total allocations:20 total releases:20 xc: debug: hypercall buffer: current allocations:0 maximum allocations:2 xc: debug: hypercall buffer: cache current size:2 xc: debug: hypercall buffer: cache hits:16 misses:2 toobig:2 BTW, just for test&debug purpose, is there any easy way to work around to make new qemu-xen co-work with old rombios? Thanks, Jinsong
Ian Campbell
2013-Aug-06 10:56 UTC
Re: Question: can new qemu-xen co-work with old rombios?
On Tue, 2013-08-06 at 10:38 +0000, Liu, Jinsong wrote:> Ian Campbell wrote: > > On Tue, 2013-08-06 at 01:56 +0000, Liu, Jinsong wrote: > >> Ian Campbell wrote: > >>> On Mon, 2013-08-05 at 16:01 +0000, Liu, Jinsong wrote: > >>> > >>>> can new qemu-xen co-work with old rombios? > >>> > >>> No, this is not a supported combination. > >>> > >>> qemu-trad == rombios > >>> qemu-xen == seabios or ovmf. > >>> > >>> No other combinations are valid. Hopefully libxl/xl gave an error > >>> message when you tried? > >>> > >>> Ian. > >> > >> Thanks Ian and Jacek! > >> > >> Yes, libxl does give error messages: > >> libxl: error: libxl_dm.c:1300:libxl__destroy_device_model: could not > >> find device-model''s pid for dom 1 libxl: error: > >> libxl.c:1415:libxl__destroy_domid: libxl__destroy_device_model > >> failed for 1 > > > > Which version of Xen is this? Can you post the complete "xl -vvv > > create" output please, it really ought to be bailing with a message > > about the invalid combination of BIOS and qemu being attempted. > > > > I suspect the messages above are just benign messages printed as part > > of the attempt to tear down a partially built domain after the > > original failure. > > > > Ian. > > My Xen git commit is 8f55cb0e360f977dc790adc393a6fd32b9933351. > > xl -vvv create xl.hvm output are: > Parsing config from xl.hvm > libxl: debug: libxl_create.c:1230:do_domain_create: ao 0x11238a0: create: how=(nil) callback=(nil) poller=0x1122f30 > libxl: error: libxl_dm.c:1300:libxl__destroy_device_model: could not find device-model''s pid for dom 8 > libxl: error: libxl.c:1415:libxl__destroy_domid: libxl__destroy_device_model failed for 8 > libxl: debug: libxl_event.c:1569:libxl__ao_complete: ao 0x11238a0: complete, rc=-3 > libxl: debug: libxl_create.c:1243:do_domain_create: ao 0x11238a0: inprogress: poller=0x1122f30, flags=ic > libxl: debug: libxl_event.c:1541:libxl__ao__destroy: ao 0x11238a0: destroy > xc: debug: hypercall buffer: total allocations:20 total releases:20 > xc: debug: hypercall buffer: current allocations:0 maximum allocations:2 > xc: debug: hypercall buffer: cache current size:2 > xc: debug: hypercall buffer: cache hits:16 misses:2 toobig:2Thanks. It turns out libxl__domain_build_info_setdefault is returning failure in this case, but not logging why. Something to fix I think.> BTW, just for test&debug purpose, is there any easy way to work around > to make new qemu-xen co-work with old rombios?I''m afraid not, you would need to do actual development work to fix up the various interactions. Ian.
Liu, Jinsong
2013-Aug-06 11:11 UTC
Re: Question: can new qemu-xen co-work with old rombios?
Ian Campbell wrote:> On Tue, 2013-08-06 at 10:38 +0000, Liu, Jinsong wrote: >> Ian Campbell wrote: >>> On Tue, 2013-08-06 at 01:56 +0000, Liu, Jinsong wrote: >>>> Ian Campbell wrote: >>>>> On Mon, 2013-08-05 at 16:01 +0000, Liu, Jinsong wrote: >>>>> >>>>>> can new qemu-xen co-work with old rombios? >>>>> >>>>> No, this is not a supported combination. >>>>> >>>>> qemu-trad == rombios >>>>> qemu-xen == seabios or ovmf. >>>>> >>>>> No other combinations are valid. Hopefully libxl/xl gave an error >>>>> message when you tried? >>>>> >>>>> Ian. >>>> >>>> Thanks Ian and Jacek! >>>> >>>> Yes, libxl does give error messages: >>>> libxl: error: libxl_dm.c:1300:libxl__destroy_device_model: could >>>> not find device-model''s pid for dom 1 libxl: error: >>>> libxl.c:1415:libxl__destroy_domid: libxl__destroy_device_model >>>> failed for 1 >>> >>> Which version of Xen is this? Can you post the complete "xl -vvv >>> create" output please, it really ought to be bailing with a message >>> about the invalid combination of BIOS and qemu being attempted. >>> >>> I suspect the messages above are just benign messages printed as >>> part of the attempt to tear down a partially built domain after the >>> original failure. >>> >>> Ian. >> >> My Xen git commit is 8f55cb0e360f977dc790adc393a6fd32b9933351. >> >> xl -vvv create xl.hvm output are: >> Parsing config from xl.hvm >> libxl: debug: libxl_create.c:1230:do_domain_create: ao 0x11238a0: >> create: how=(nil) callback=(nil) poller=0x1122f30 libxl: error: >> libxl_dm.c:1300:libxl__destroy_device_model: could not find >> device-model''s pid for dom 8 >> libxl: error: libxl.c:1415:libxl__destroy_domid: >> libxl__destroy_device_model failed for 8 >> libxl: debug: libxl_event.c:1569:libxl__ao_complete: ao 0x11238a0: >> complete, rc=-3 >> libxl: debug: libxl_create.c:1243:do_domain_create: ao 0x11238a0: >> inprogress: poller=0x1122f30, flags=ic >> libxl: debug: libxl_event.c:1541:libxl__ao__destroy: ao 0x11238a0: >> destroy >> xc: debug: hypercall buffer: total allocations:20 total releases:20 >> xc: debug: hypercall buffer: current allocations:0 maximum >> allocations:2 >> xc: debug: hypercall buffer: cache current size:2 >> xc: debug: hypercall buffer: cache hits:16 misses:2 toobig:2 > > Thanks. It turns out libxl__domain_build_info_setdefault is returning > failure in this case, but not logging why. Something to fix I think. > >> BTW, just for test&debug purpose, is there any easy way to work >> around >> to make new qemu-xen co-work with old rombios? > > I''m afraid not, you would need to do actual development work to fix up > the various interactions. > > Ian.Yes, but my purpose here is, at first step to make sure whether it''s a seabios bug or qemu-xen bug :) Seems the combination cannot work, I have to debug it step by step, both seabios and qemu-xen are suspicious. Thanks, Jinsong