>>> On 1/21/2014 at 08:47 AM, in message <52DE9695.AD9 : 120 : 30462>, Jan >>> Beulich wrote: > >>> On 21.01.14 at 16:37, Jim Fehlig <[email protected]> wrote: > > Charles Arnold wrote: > >>>>> On 1/20/2014 at 07:29 PM, in message <[email protected]>, Jim > >>>>> Fehlig > >>>>> > >> <[email protected]> wrote: > >> > >>> Hans Witvliet wrote: > >>> > >>>> Yes, i forgotten that xm/xend is depreceated. > >>>> Heard that a couple of times at several fosdems from Ian, > >>>> and when you mention "xm" at the xen-lists you are considered a relic > >>>> from a distant past.... > >>>> > >>>> > >>>> How ever: > >>>> When you do a fresh instalation of the xen-stuff in 13.1, and you try to > >>>> create a VM like one is used to do in previous versions, i still got a > >>>> warning that i had to check because "xend was not running" > >>>> > >>>> > >>> Charles, is there a check in {vm,virt}-install for xend running? I > >>> vaguely recall something along those lines, but suppose it was fixed > >>> long ago. > >>> > >> > >> Yes. vm-install does check for a running xend. This is how it knows > >> whether to use 'xm' to start VMs or if xend is not running it uses a > >> libvirt connection to start VMs. The only time vm-install uses 'xl' for > >> starting VMs is if xend is not running and it fails to connect to libvirt. > >> Failure to connect could mean libvirtd was not running or some other > >> error occurred when connecting to libvirtd. > >> > >> For virt-install, it only uses libvirt for starting VMs. It will try to > > default > >> to a xen connection if '/var/lib/xend' and '/proc/xen' exist otherwise it > >> > > > > It shouldn't look for /var/lib/xend, since that directory wont exist on > > a system without xend. > > But the presence of the directory doesn't tell whether xend (or > Xen itself) is running...
Correct. It is wrong for 'xl' based system and it also doesn't actually tell us if xend is running. I'll need to submit a fix for this upstream. - Charles -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
