similar to: libvirtd terminates running instances after monitor's socket inode id is changed

On 15 February 2017 at 00:57, Daniel P. Berrange <berrange@redhat.com> wrote: > What is the actual error you're getting during startup. # virsh -d0 start instance-0000037c start: domain(optdata): instance-0000037c start: found option <domain>: instance-0000037c start: <domain> trying as domain NAME error: Failed to start domain instance-0000037c error: monitor socket did

On Wed, Feb 15, 2017 at 10:27:46AM +0100, Michal Privoznik wrote: > On 02/15/2017 03:43 AM, Blair Bethwaite wrote: > > On 15 February 2017 at 00:57, Daniel P. Berrange <berrange@redhat.com> wrote: > >> What is the actual error you're getting during startup. > > > > # virsh -d0 start instance-0000037c > > start: domain(optdata): instance-0000037c >

Hi, please see following backtrace. How to reproduce: start qemu guest w/attached console, execute migration, get a crash at the end. Program received signal SIGSEGV, Segmentation fault. virHashRemoveEntry (table=0x7fa0e0003e90, name=0x7fa0ec00ca60) at /var/tmp/build/libvirt/libvirt-0.9.13/./src/util/virhash.c:463 bt #0 virHashRemoveEntry (table=0x7fa0e0003e90, name=0x7fa0ec00ca60) at

Currently in the VM XML, I am passing the following command line argument as a passthrough argument: -netdev type=tap,id=net1,script=no,downscript=no,ifname=port3,vhost=on -device virtio-net-pci,netdev=net1,mac=00:00:00:00:00:01,csum=off,gso=off,guest_tso4=off,guest_tso6=off,guest_ecn=off Is there another way to represent this in the XML file? maybe that may solve the problem. On 24 July 2014

Hi all, In IRC last night Dan helpfully confirmed my analysis of an issue we are seeing attempting to launch high memory KVM guests backed by hugepages... In this case the guests have 240GB of memory allocated from two host NUMA nodes to two guest NUMA nodes. The trouble is that allocating the hugepage backed qemu process seems to take longer than the 30s QEMU_JOB_WAIT_TIME and so libvirt then

On 02/15/2017 03:43 AM, Blair Bethwaite wrote: > On 15 February 2017 at 00:57, Daniel P. Berrange <berrange@redhat.com> wrote: >> What is the actual error you're getting during startup. > > # virsh -d0 start instance-0000037c > start: domain(optdata): instance-0000037c > start: found option <domain>: instance-0000037c > start: <domain> trying as

On 15 February 2017 at 20:40, Daniel P. Berrange <berrange@redhat.com> wrote: > On Wed, Feb 15, 2017 at 10:27:46AM +0100, Michal Privoznik wrote: >> On 02/15/2017 03:43 AM, Blair Bethwaite wrote: >> > On 15 February 2017 at 00:57, Daniel P. Berrange <berrange@redhat.com> wrote: >> >> What is the actual error you're getting during startup. >> >

I''m getting more and more "execution expired" as systems checking and hit puppetdb for the first time (switching from a mysql instance). The command queue isn''t long (1-5, if anything, all the time), and ym master itself seems to be dealing well enough. I have seen the collection time growing higher and higher though. This is a ~2K node deployment, and one of the few

so when I''m reading the pick axe book second edition I don''t see anything like the syntax you see people using in rails code. Specifically when you see. belongs_to :Person has_many :Phones etc these are methods on ActiveRecord right? Why is this invocation syntax never described in the Pick Axe book? I do see things like attr_reader :some_attribute etc but you

Asterisk Project Security Advisory - AST-2011-001 Product Asterisk Summary Stack buffer overflow in SIP channel driver Nature of Advisory Exploitable Stack Buffer Overflow Susceptibility Remote Authenticated Sessions Severity Moderate

I am trying to connect a KVM-QEMU VM to OVS-DPDK vhostuser port. But, I am encountering a few errors. Since I am very new to libvrt and Linux I am not able to sort them out. Any guidance in this regard would be a great help. These are my System Logs: Mar 28 18:03:04 dpdk-OptiPlex-5040 libvirtd.service: 1529: debug : virCommandRunAsync:2429 : About to run LIBVIRT_LOG_OUTPUTS=3:stderr

On 4/29/19 5:42 PM, lameventanas@gmail.com wrote: > > > On 29/04/2019 22.01, Michal Privoznik wrote: >> On 4/29/19 1:06 PM, lameventanas@gmail.com wrote: >>> I want to run libvirtd as a special user, and allowing users that belong >>> to a special group to connect via qemu+unix:///system (eg: unix socket). >>> >>> I did everything necessary to

On 4/29/19 1:06 PM, lameventanas@gmail.com wrote: > I want to run libvirtd as a special user, and allowing users that belong > to a special group to connect via qemu+unix:///system (eg: unix socket). > > I did everything necessary to do so: created a libvirt user and group, > added the libvirt user to the kvm group, added my normal user to the > libvirt group, and made sure the

On Tue, Apr 30, 2019 at 10:45:03AM +0100, Peter Crowther wrote: > On Tue, 30 Apr 2019 at 10:40, Michal Privoznik <mprivozn@redhat.com> wrote: > > > Is there any problem running libvirtd as root? > > > > Yes, in the regulated environment in which I work! I have to do far more > thorough threat analysis than I would do if I knew which capabilities it > had. So

On 4/30/19 3:15 PM, Peter Crowther wrote: > On Tue, 30 Apr 2019 at 10:48, Daniel P. Berrangé <berrange@redhat.com> > wrote: > >> On Tue, Apr 30, 2019 at 10:45:03AM +0100, Peter Crowther wrote: >>> On Tue, 30 Apr 2019 at 10:40, Michal Privoznik <mprivozn@redhat.com> >> wrote: >>> >>>> Is there any problem running libvirtd as root?

On Tue, 30 Apr 2019 at 10:40, Michal Privoznik <mprivozn@redhat.com> wrote: > Is there any problem running libvirtd as root? > > Yes, in the regulated environment in which I work! I have to do far more thorough threat analysis than I would do if I knew which capabilities it had. So far, we've accepted the extra work; but it would be wonderful to be able to run a locked-down

I want to run libvirtd as a special user, and allowing users that belong to a special group to connect via qemu+unix:///system (eg: unix socket). I did everything necessary to do so: created a libvirt user and group, added the libvirt user to the kvm group, added my normal user to the libvirt group, and made sure the socket is owned by libvirt:libvirt with permissions set to 770. libvirtd starts

Let me clarify my question, I am using unmodified stock qemu (1.4.0) and only the location of vhost file descriptor is different from default (I don't remove the default /dev/vhost-net directory) The VHOST file descriptor is present in "/dev/vhost-0" directory instead of the default "/dev/vhost-net". When I try to give vhostfd in the XML I get a different error:

On Tue, 30 Apr 2019 at 10:48, Daniel P. Berrangé <berrange@redhat.com> wrote: > On Tue, Apr 30, 2019 at 10:45:03AM +0100, Peter Crowther wrote: > > On Tue, 30 Apr 2019 at 10:40, Michal Privoznik <mprivozn@redhat.com> > wrote: > > > > > Is there any problem running libvirtd as root? > > > > > > Yes, in the regulated environment in which I

Borders show it has to be ordered but Amazon says they have it but don''t show any reviews so what exactly is the true availability of the second edition? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to