* Trying out vixen: qemu processes left behind
@ 2018-01-11 23:00 Andy Smith
2018-01-11 23:47 ` Anthony Liguori
0 siblings, 1 reply; 4+ messages in thread
From: Andy Smith @ 2018-01-11 23:00 UTC (permalink / raw)
To: xen-devel
Hi,
I'm giving Vixen a try by following the instructions in
https://xenbits.xen.org/xsa/xsa254/README.vixen
Debian jessie, xen 4.8.1 packages from jessie-backports with XSAs
applied.
I finally got a guest booted although its networking doesn't work.
Every time I've started a guest and had it crash it's left behind a
domain called "(null)" and a matching qemu process so I assume
that's the device model. I thought that was just because the guest
was failing to start.
Now that I have one which boots, even when I shut it down cleanly
there's still a domain left behind:
$ sudo xl list
Name ID Mem VCPUs State Time(s)
Domain-0 0 2048 2 r----- 104114.0
(null) 17 1 2 --ps-d 14.2
$ ps awux | grep qemu
root 3310 1.2 1.2 430648 24676 ? SLl 22:48 0:06 /usr/local/lib/xen/bin/qemu-system-i386 -xen-domid 17 -chardev socket,id=libxl-cmd,path=/var/run/xen/qmp-libxl-17,server,nowait -no-shutdown -mon chardev=libxl-cmd,mode=control -chardev socket,id=libxenstat-cmd,path=/var/run/xen/qmp-libxenstat-17,server,nowait -mon chardev=libxenstat-cmd,mode=control -nodefaults -no-user-config -name debtest1 -display none -serial pty -boot order=c -smp 2,maxcpus=2 -netdev type=tap,id=net0,ifname=vif17.0-emu,script=no,downscript=no -machine xenfv -cdrom /var/lib/xen/pvshim-sidecars/debtest1.iso -m 2552
If I kill the qemu process then the domain does away.
Is this expected? It doesn't seem workable if so.
Cheers,
Andy
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Trying out vixen: qemu processes left behind
2018-01-11 23:00 Trying out vixen: qemu processes left behind Andy Smith
@ 2018-01-11 23:47 ` Anthony Liguori
2018-01-12 1:56 ` Andy Smith
0 siblings, 1 reply; 4+ messages in thread
From: Anthony Liguori @ 2018-01-11 23:47 UTC (permalink / raw)
To: Andy Smith; +Cc: xen-devel
On Thu, Jan 11, 2018 at 3:00 PM, Andy Smith <andy@strugglers.net> wrote:
> Hi,
>
> I'm giving Vixen a try by following the instructions in
> https://xenbits.xen.org/xsa/xsa254/README.vixen
>
> Debian jessie, xen 4.8.1 packages from jessie-backports with XSAs
> applied.
>
> I finally got a guest booted although its networking doesn't work.
> Every time I've started a guest and had it crash it's left behind a
> domain called "(null)" and a matching qemu process so I assume
> that's the device model. I thought that was just because the guest
> was failing to start.
>
> Now that I have one which boots, even when I shut it down cleanly
> there's still a domain left behind:
>
> $ sudo xl list
> Name ID Mem VCPUs State Time(s)
> Domain-0 0 2048 2 r----- 104114.0
> (null) 17 1 2 --ps-d 14.2
> $ ps awux | grep qemu
> root 3310 1.2 1.2 430648 24676 ? SLl 22:48 0:06 /usr/local/lib/xen/bin/qemu-system-i386 -xen-domid 17 -chardev socket,id=libxl-cmd,path=/var/run/xen/qmp-libxl-17,server,nowait -no-shutdown -mon chardev=libxl-cmd,mode=control -chardev socket,id=libxenstat-cmd,path=/var/run/xen/qmp-libxenstat-17,server,nowait -mon chardev=libxenstat-cmd,mode=control -nodefaults -no-user-config -name debtest1 -display none -serial pty -boot order=c -smp 2,maxcpus=2 -netdev type=tap,id=net0,ifname=vif17.0-emu,script=no,downscript=no -machine xenfv -cdrom /var/lib/xen/pvshim-sidecars/debtest1.iso -m 2552
>
> If I kill the qemu process then the domain does away.
>
> Is this expected? It doesn't seem workable if so.
Usually this means there is a dangling backend that wasn't properly
terminated. It would be useful to xenstore-ls the domain and see
which backend is not in a disconnected state.
Regards,
Anthony Liguori
> Cheers,
> Andy
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xenproject.org
> https://lists.xenproject.org/mailman/listinfo/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Trying out vixen: qemu processes left behind
2018-01-11 23:47 ` Anthony Liguori
@ 2018-01-12 1:56 ` Andy Smith
2018-01-12 17:23 ` Wei Liu
0 siblings, 1 reply; 4+ messages in thread
From: Andy Smith @ 2018-01-12 1:56 UTC (permalink / raw)
To: Anthony Liguori; +Cc: xen-devel
Hi Anthony,
On Thu, Jan 11, 2018 at 03:47:25PM -0800, Anthony Liguori wrote:
> On Thu, Jan 11, 2018 at 3:00 PM, Andy Smith <andy@strugglers.net> wrote:
> > $ sudo xl list
> > Name ID Mem VCPUs State Time(s)
> > Domain-0 0 2048 2 r----- 104114.0
> > (null) 17 1 2 --ps-d 14.2
> > $ ps awux | grep qemu
> > root 3310 1.2 1.2 430648 24676 ? SLl 22:48 0:06 /usr/local/lib/xen/bin/qemu-system-i386 -xen-domid 17 -chardev socket,id=libxl-cmd,path=/var/run/xen/qmp-libxl-17,server,nowait -no-shutdown -mon chardev=libxl-cmd,mode=control -chardev socket,id=libxenstat-cmd,path=/var/run/xen/qmp-libxenstat-17,server,nowait -mon chardev=libxenstat-cmd,mode=control -nodefaults -no-user-config -name debtest1 -display none -serial pty -boot order=c -smp 2,maxcpus=2 -netdev type=tap,id=net0,ifname=vif17.0-emu,script=no,downscript=no -machine xenfv -cdrom /var/lib/xen/pvshim-sidecars/debtest1.iso -m 2552
> >
> > If I kill the qemu process then the domain does away.
> >
> > Is this expected? It doesn't seem workable if so.
>
> Usually this means there is a dangling backend that wasn't properly
> terminated. It would be useful to xenstore-ls the domain and see
> which backend is not in a disconnected state.
After halting that:
$ sudo xl list
Name ID Mem VCPUs State Time(s)
Domain-0 0 2048 2 r----- 104246.6
(null) 19 1 2 --ps-d 86.6
$ sudo xenstore-ls
tool = ""
xenstored = ""
local = ""
domain = ""
0 = ""
control = ""
feature-poweroff = "1"
feature-reboot = "1"
feature-suspend = "1"
domid = "0"
name = "Domain-0"
device-model = ""
vm = ""
libxl = ""
$ sudo xenstore-ls /local/domain/19
xenstore-ls: xs_directory (/local/domain/19): No such file or directory
Cheers,
Andy
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: Trying out vixen: qemu processes left behind
2018-01-12 1:56 ` Andy Smith
@ 2018-01-12 17:23 ` Wei Liu
0 siblings, 0 replies; 4+ messages in thread
From: Wei Liu @ 2018-01-12 17:23 UTC (permalink / raw)
To: Andy Smith; +Cc: xen-devel, Wei Liu, Anthony Liguori
On Fri, Jan 12, 2018 at 01:56:17AM +0000, Andy Smith wrote:
> Hi Anthony,
>
> On Thu, Jan 11, 2018 at 03:47:25PM -0800, Anthony Liguori wrote:
> > On Thu, Jan 11, 2018 at 3:00 PM, Andy Smith <andy@strugglers.net> wrote:
> > > $ sudo xl list
> > > Name ID Mem VCPUs State Time(s)
> > > Domain-0 0 2048 2 r----- 104114.0
> > > (null) 17 1 2 --ps-d 14.2
> > > $ ps awux | grep qemu
> > > root 3310 1.2 1.2 430648 24676 ? SLl 22:48 0:06 /usr/local/lib/xen/bin/qemu-system-i386 -xen-domid 17 -chardev socket,id=libxl-cmd,path=/var/run/xen/qmp-libxl-17,server,nowait -no-shutdown -mon chardev=libxl-cmd,mode=control -chardev socket,id=libxenstat-cmd,path=/var/run/xen/qmp-libxenstat-17,server,nowait -mon chardev=libxenstat-cmd,mode=control -nodefaults -no-user-config -name debtest1 -display none -serial pty -boot order=c -smp 2,maxcpus=2 -netdev type=tap,id=net0,ifname=vif17.0-emu,script=no,downscript=no -machine xenfv -cdrom /var/lib/xen/pvshim-sidecars/debtest1.iso -m 2552
> > >
> > > If I kill the qemu process then the domain does away.
> > >
> > > Is this expected? It doesn't seem workable if so.
> >
> > Usually this means there is a dangling backend that wasn't properly
> > terminated. It would be useful to xenstore-ls the domain and see
> > which backend is not in a disconnected state.
>
> After halting that:
>
> $ sudo xl list
> Name ID Mem VCPUs State Time(s)
> Domain-0 0 2048 2 r----- 104246.6
> (null) 19 1 2 --ps-d 86.6
> $ sudo xenstore-ls
> tool = ""
> xenstored = ""
> local = ""
> domain = ""
> 0 = ""
> control = ""
> feature-poweroff = "1"
> feature-reboot = "1"
> feature-suspend = "1"
> domid = "0"
> name = "Domain-0"
> device-model = ""
> vm = ""
> libxl = ""
> $ sudo xenstore-ls /local/domain/19
> xenstore-ls: xs_directory (/local/domain/19): No such file or directory
>
There is a bug in the dm wrapper that would cause QEMU to become
orphaned. An updated version will be provided.
Wei.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2018-01-12 17:23 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-01-11 23:00 Trying out vixen: qemu processes left behind Andy Smith
2018-01-11 23:47 ` Anthony Liguori
2018-01-12 1:56 ` Andy Smith
2018-01-12 17:23 ` Wei Liu
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.