Re: [Bug 1583009] Re: Error starting domain since update

> Sorry about the confusion. Never mind, now things are clear - thanks! > 1- update libvirt > 2- virst list (I see running vms) > 3- try to stop the vm with nova, "openstack server stop uuid" > 4- virsh list. (now it hangs) > I'd need insight from the OpenStack Team on this how nova might

[Bug 1583009] Re: Error starting domain since update

Sorry about the confusion. 1- update libvirt 2- virst list (I see running vms) 3- try to stop the vm with nova, "openstack server stop uuid" 4- virsh list. (now it hangs) after restarting virtlogd and libvirtd, everything seems to work correctly again. anyhow, how does a reload of those process

[Bug 1583009] Re: Error starting domain since update

I used virsh to start/stop them as that is how comment #28 described it. "virsh just hangs". With more context is it that you interact with nova on it - and then while that is kind of "in transaction" virsh is hung by it? -- You received this bug notification because you are a member of Ubuntu

[Bug 1583009] Re: Error starting domain since update

did you use virsh to stop/start the vms ? or you did it via Nova ? In my case I can list the vm just fine after a libvirtd restart, it's only when nova is trying to stop/start or create new instance that it hangs. -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1583009] Re: Error starting domain since update

Newton->Ocata would be libvirt 1.3.1 (Xenial) -> 2.5 Upgrade (Zesty). I tried two updates: 1. X-Newton -> X-Ocata 2. Xenial -> Zesty (EOL, so used Artful with 3.6 here) Test according to commend #28 was: 1. get on X/X-N a guest 2. check status of virtlogd 3. upgrade 4. virsh shutdown/start after

[Bug 1583009] Re: Error starting domain since update

Just had this issue with upgrading from Newton > Ocata via Openstack- ansible. the issue I noticed it that is seems that only a reload "systemctl reload virtlogd.service" isn't enough. after instlalling the update, I can list the instances with "virsh list" but when I use nova to interract with

[Bug 1583009] Re: Error starting domain since update

I still think this is a "new" issue and we should keep the old one fix released and upen a new bug, but for a minor discussion here an update: If the socket is not around usually the service isn't running. Which would make sense for the workaround in comment #14 that essentially restarted

[Bug 1583009] Re: Error starting domain since update

There is something else I find confusing: the output I get from lsof doesn't agree with what I see in the file system. At this point, my knowledge of sockets is getting stretched. root@jeff-desktop:/home/jeffs/work/juniper/vmx-17.2R.13# pgrep virt 21491

[Bug 1583009] Re: Error starting domain since update

I think I am having the same problem. I am running 16.04.3 LTS. I tried apt-get update and apt-get upgrade, but the software revision levels did not change, still at 1.3.1. root@jeff-desktop:/home/jeffs/work/juniper/vmx-17.2R.13# dpkg -l "*libvirt*" Desired=Unknown/Install/Remove/Purge/Hold |

[Bug 1583009] Re: Error starting domain since update

@zioproto - also given that the fixes were for Yakkety's dev version 1.3.4 (release with 2.1) and you are seeing this on Trusty(Mitaka?)->Xenial (right?) this might be a different bug we would want to file differently. -- You received this bug notification because you are a member of Ubuntu

[Bug 1583009] Re: Error starting domain since update

It seems I have no rights whatsoever on UCA bugs, so I pinged on IRC -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1583009 Title: Error starting domain since update To manage notifications about

[Bug 1583009] Re: Error starting domain since update

Well I can't bump prio, but I'll assign just to get a hit in ones inbox to look for this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1583009 Title: Error starting domain since update To manage

[Bug 1583009] Re: Error starting domain since update

Thanks Saverio for your ping on this. I wonder why I haven't seen this yet out of a openstack context, might be just the scale of it but I still wonder. I run all sort of libvirt/qemu upgrade tests on a regular cadence and among others this includes Trusty->Xenial and so far none hit this issue

[Bug 1583009] Re: Error starting domain since update

I confirm the workaround on commment 14 worked also for me. I had this bug after upgrading from Trusty to Xenial using Openstack Mitaka. You can see the problem in nova-compute.log For Openstack this is very nasty bug because everything will fail to be scheduled on that compute-node, but the

[Bug 1583009] Re: Error starting domain since update

I just had the same symptoms after upgrading Ubuntu 16.04 OpenStack Mitaka cluster packages to latest. Some servers had no problems. Very few had the "Failed to connect socket" error when you try to e.g. 'virsh list --all'. Note that libvirtd itself did start, and had no apparent errors. Package

[Bug 1583009] Re: Error starting domain since update

rror starting domain: Failed to connect socket to '/var/run/libvirt /virtlogd-sock': No such file or directory Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 90, in cb_wrapper callback(asyncjob, *args, **kwargs) File

[Bug 1583009] Re: Error starting domain since update

I found now one difference: On the working installation, I have "/etc/init.d/libvirt-bin", while this file is "/etc/init.d/libvirtd" on the not working installation. Below is a diff of the two files. The most important difference might be the "Provides" line? The others are related to the name.

[Bug 1583009] Re: Error starting domain since update

This is actually a bit strange as I have now two very similar computers with similar setup, but this issue of virtlogd only appears on one of them. Both have all updates installed. If anyone can point me to relevant startupscripts/configuration files I can post the content from both machines to

[Bug 1583009] Re: Error starting domain since update

Hey mogliii, Than you very much. It worked. I first did on the controller node: $ apt-get upgrade And then on every compute node: $ sudo service virtlogd restart * Restarting libvirt logging daemon /usr/sbin/virtlogd $ sudo service libvirt-bin restart libvirt-bin stop/waiting libvirt-bin

[Bug 1583009] Re: Error starting domain since update

As a workaround I do the following after each restart of the host: # systemctl start virtlogd # systemctl start libvirtd Ubuntu 16.04 with latest packages installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1583009] Re: Error starting domain since update

Hi there, I am also having same troubles. This is in the controller /var/log/nova /nova-conductor.log file after trying to create a new instance as described in http://docs.openstack.org/mitaka/install-guide-ubuntu /launch-instance-provider.html: 2016-06-29 13:27:03.084 2828 ERROR

Re: [Bug 1583009] Re: Error starting domain since update

Hi, If you are seeing this problem can you give me the versions of libvirt and qemu you are using? Thanks, --chris On Mon, Jun 13, 2016 at 5:20 PM, Thiago Martins wrote: > I'm seeing this problem while trying to launch an Instance on OpenStack > Mitaka on Xenial. > >

[Bug 1583009] Re: Error starting domain since update

I'm seeing this problem while trying to launch an Instance on OpenStack Mitaka on Xenial. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1583009 Title: Error starting domain since update To manage

[Bug 1583009] Re: Error starting domain since update

and broken again -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1583009 Title: Error starting domain since update To manage notifications about this bug go to:

[Bug 1583009] Re: Error starting domain since update

This bug was fixed in the package libvirt - 1.3.4-1ubuntu4 --- libvirt (1.3.4-1ubuntu4) yakkety; urgency=medium * Re-enable the upstart job by renaming the file. * Include patchby @guessi to continally wait for libvirtd to start when using sysvinit or upstart. (LP: #1571209)

[Bug 1583009] Re: Error starting domain since update

mmk - so when I go look at the versions I've got and check them against packages.ubuntu.com, then remove them all, and reinstall - I get different versions. Not sure how I did - I suspect yesterday and grabbing stuff from -proposed. Long and short is - it works with what I *now* have installed.

[Bug 1583009] Re: Error starting domain since update

ii libvirt-bin1.3.4-1ubuntu2 ii libvirt-clients1.3.4-1ubuntu2 ii libvirt-daemon 1.3.4-1ubuntu2 ii libvirt-daemon-system 1.3.4-1ubuntu2 ii libvirt-glib-1.0-0:amd64 0.2.2-0.1ubuntu1 ii libvirt0:amd64

[Bug 1583009] Re: Error starting domain since update

Just did an update again and things work for me. Can you confirm which versions of virt-manager/libvirt you are using? In addition is it the same error message? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1583009] Re: Error starting domain since update

Got updates to virtinst and virt-manager today - issue is back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1583009 Title: Error starting domain since update To manage notifications about this

[Bug 1583009] Re: Error starting domain since update

Thanks - grabbed it from -proposed :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1583009 Title: Error starting domain since update To manage notifications about this bug go to:

[Bug 1583009] Re: Error starting domain since update

Uploaded a fix for Yakkety. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1583009 Title: Error starting domain since update To manage notifications about this bug go to:

[Bug 1583009] Re: Error starting domain since update

I can reproduce this bug. ** Changed in: libvirt (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1583009 Title: Error starting domain since update To

[Bug 1583009] Re: Error starting domain since update

** Changed in: libvirt (Ubuntu) Assignee: (unassigned) => Chris J Arges (arges) ** Changed in: libvirt (Ubuntu) Status: New => Triaged ** Changed in: libvirt (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs,