[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [TESTDAY] xl restore gives an error too soon after xl save


  • To: Paul Durrant <paul@xxxxxxx>
  • From: George Dunlap <George.Dunlap@xxxxxxxxxx>
  • Date: Tue, 9 Jun 2020 17:03:49 +0000
  • Accept-language: en-GB, en-US
  • Authentication-results: esa6.hc3370-68.iphmx.com; dkim=none (message not signed) header.i=none
  • Cc: Anthony Perard <anthony.perard@xxxxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>, Wei Liu <wl@xxxxxxx>, Ian Jackson <Ian.Jackson@xxxxxxxxxx>
  • Delivery-date: Tue, 09 Jun 2020 17:04:04 +0000
  • Ironport-sdr: 92YMmYdspaKsWWzegUN3uFD6ESQEIgFua+4qZ0ywgpc64TVLM0al/RlOZl3l2teMO31/lNXJk7 1vfNOu84G62JnaOpJxooihgzYRedx7++mtvtG0E29DvblK+esMHkk/VIUM8gx49pyaiDgfvsCf gYYJALZUIiBdXKBHY912AMtzhJz/kvkASlyC3ozN2LVERfjwYiBrYEq4YiBaPozMphty+4p1hX NTBVO5sJhR7prrkdWlKZJjYHtOw/srvh/s7j1aRPvFyP85ultgB9N721bCdCXD+23UBJ86yniP XxQ=
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
  • Thread-index: AQHWPn1DuBRhzpMk9UKX8zBgGqSl9KjQXzkAgAACKIA=
  • Thread-topic: [TESTDAY] xl restore gives an error too soon after xl save


> On Jun 9, 2020, at 5:56 PM, Paul Durrant <xadimgnik@xxxxxxxxx> wrote:
> 
>> -----Original Message-----
>> From: George Dunlap <George.Dunlap@xxxxxxxxxx>
>> Sent: 09 June 2020 17:45
>> To: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>
>> Cc: Paul Durrant <paul@xxxxxxx>; Ian Jackson <Ian.Jackson@xxxxxxxxxx>; Wei 
>> Liu <wl@xxxxxxx>; Anthony
>> Perard <anthony.perard@xxxxxxxxxx>
>> Subject: [TESTDAY] xl restore gives an error too soon after xl save
>> 
>> Somewhat surprising that if you save with -D, you get mysterious error 
>> messages for the next so-many
>> seconds:
>> 
>> root@immortal:/images# xl save -D c6-01 /images/tmp/c6-01.save
>> Saving to /images/tmp/c6-01.save new xl format (info 0x3/0x0/950)
>> xc: info: Saving domain 19505, type x86 PV
>> xc: Frames: 524288/524288  100%
>> xc: End of stream: 0/0    0%
>> root@immortal:/images# xl restore tmp/c6-01.save
>> Loading new save file tmp/c6-01.save (new xl fmt info 0x3/0x0/950)
>> Savefile contains xl domain config in JSON format
>> Parsing config from <saved>
>> libxl: error: libxl_create.c:692:libxl__domain_make: Domain 19505:domain id 
>> recently used: No such
>> file or directory
>> libxl: error: libxl_create.c:1233:initiate_domain_create: Domain 
>> 19505:cannot make domain: -3
>> libxl: error: libxl_domain.c:1182:libxl__destroy_domid: Domain 
>> 19505:Non-existant domain
>> libxl: error: libxl_domain.c:1136:domain_destroy_callback: Domain 
>> 19505:Unable to destroy guest
>> libxl: error: libxl_domain.c:1063:domain_destroy_cb: Domain 
>> 19505:Destruction of domain failed
>> root@immortal:/images# xl restore tmp/c6-01.save
>> Loading new save file tmp/c6-01.save (new xl fmt info 0x3/0x0/950)
>> Savefile contains xl domain config in JSON format
>> Parsing config from <saved>
>> libxl: error: libxl_create.c:692:libxl__domain_make: Domain 19505:domain id 
>> recently used: No such
>> file or directory
>> libxl: error: libxl_create.c:1233:initiate_domain_create: Domain 
>> 19505:cannot make domain: -3
>> libxl: error: libxl_domain.c:1182:libxl__destroy_domid: Domain 
>> 19505:Non-existant domain
>> libxl: error: libxl_domain.c:1136:domain_destroy_callback: Domain 
>> 19505:Unable to destroy guest
>> libxl: error: libxl_domain.c:1063:domain_destroy_cb: Domain 
>> 19505:Destruction of domain failed
>> 
>> [A few minutes pass]
>> 
> 
> Yes, this is because it is not 'safe' to re-create the domain with the same 
> domid until it is deemed not 'recently used'. This
> should indeed be documented.

…and probably have a more informative error message. :-)

I can see why you wouldn’t want to start a *new* domain with a previous domain, 
but surely if you’re restoring the *same* domain, that check should be skipped?

 -George

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.