[Xen-devel] null scheduler bug

[Stefano Stabellini <sstabellini@xxxxxxxxxx>]

Hi Dario,

Milan has just found a bug in the null scheduler: apparently it is not
possible to start a VM again after it has been destroyed.

My initial suspicion was that the VM wasn't properly destroyed, but I
asked Milan to double check with xl list, and the VM doesn't show in the
list anymore.

Any ideas?

Cheers,

Stefano

On Wed, 12 Sep 2018, Milan Boberic wrote:
> I double checked it, when I remove sched=null and vwfi=native I can create 
> and destroy bare-metal application as many times as I
> want. 
> When I include sched=null and vwfi=native I can create it once and when I 
> destroy it I can't create it again, again the same
> error.
>
> root@uz3eg-iocc-2018-2:~# xl create bm1.cfg
> Parsing config from bm1.cfg
> (XEN) IRQ 48 is already used by domain 1
> libxl: error: libxl_create.c:1278:domcreate_launch_dm: Domain 2:failed give 
> domain access to irq 48: Device or resource busy
> libxl: error: libxl_domain.c:1003:libxl__destroy_domid: Domain 2:Non-existant 
> domain
> libxl: error: libxl_domain.c:962:domain_destroy_callback: Domain 2:Unable to 
> destroy guest
> libxl: error: libxl_domain.c:889:domain_destroy_cb: Domain 2:Destruction of 
> domain failed

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel