similar to: cannot attach device using libvirt

Hi, On a KVM host installed with following packages versions : [root@rhel6-roadster test_channels_OK]# rpm -qa | grep libvirt libvirt-devel-0.10.2-29.el6.x86_64 libvirt-0.10.2-29.el6.x86_64 libvirt-client-0.10.2-29.el6.x86_64 libvirt-java-0.4.9-1.el6.noarch libvirt-java-devel-0.4.9-1.el6.noarch libvirt-python-0.10.2-29.el6.x86_64 [root@rhel6-roadster test_channels_OK]# rpm -qa | grep qemu

于 2013/7/15 17:32, Gao feng 写道: > On 07/15/2013 05:18 PM, hzguanqiang wrote: >> Hi, Gao Feng >> >> I've tried what you said, but still exists the problem: >> >> ubuntu@lxc:~$ vir attach-disk instance-0000002c /dev/dm-0 sdb >> error: Failed to attach disk >> error: Unable to create device /proc/10366/root/dev/sdb: Permission denied >>

On 07/17/2013 04:15 PM, Gao feng wrote: > On 07/16/2013 01:29 PM, Guan Qiang wrote: >> 于 2013/7/15 17:32, Gao feng 写道: >>> On 07/15/2013 05:18 PM, hzguanqiang wrote: >>>> Hi, Gao Feng >>>> >>>> I've tried what you said, but still exists the problem: >>>> >>>> ubuntu@lxc:~$ vir attach-disk instance-0000002c

I just noticed the entries on attach-disk and attach-devices are a bit on the empty size. As I am just attaching a usb device to one of my vm clients, I was wondering if I could offer examples to those entries.

Hi, Gao Feng I've tried what you said, but still exists the problem: ubuntu@lxc:~$ vir attach-disk instance-0000002c /dev/dm-0 sdb error: Failed to attach disk error: Unable to create device /proc/10366/root/dev/sdb: Permission denied I think finding what it means by saying 'Unable to create device /proc/10366/root/dev/sdb: Permission denied' is the key. But anyway, thanks for

On Tue, Feb 27, 2018 at 09:53:00 +0100, Michal Privoznik wrote: > On 02/27/2018 03:06 AM, Star Guo wrote: > > Hello Everyone, > > > > > > > > My pc run in CentOS 7.4 and install libvirt-4.0.0 + Qemu-kvm 2.9.0 + Ceph > > 10.2.10 ALL-in-One. > > > > > > > > I use python-sdk with libvirt and run [self.domain.updateDeviceFlags(xml,

[Dropping libvir list and adding libvir-users list.] On Mon, Jan 19, 2015 at 04:12:46PM +0100, liedekef@telenet.be wrote: > Hi all, > > I had libvirt 1.2.10 running without issues together with the qemu package > qemu-kvm-0.12.1.2-2.415.el6_5.14.x86_64.rpm That's a really old QEMU and the libvirt you're using is relatively newer. > Now, after updating my server,

Hi Daniel, I noticed that the patch "Add support for hotplug/unplug of disk devices in LXC" you wrote had been merged into libvirt of version 1.0.2. But when I used this function, it report an error with details as following: ubuntu@lxc:~$ vir attach-device instance-0000002c disk.xml --config error: Failed to attach device from disk.xml error: Unable to create device

Hi, When i use "virsh attach-device rhel disk.xml" when the guest is booting,then i can't find the disk in the guest after booting.But i can find it by "virsh domblklist rhel",and when i want to detach it from the guest and use "virsh detach-disk rhel vdb", i still can find the disk by "virsh domblklist rhel" The disk.xml is like: <disk

On Fri, Mar 02, 2018 at 15:32:44 -0500, John Ferlan wrote: > > > On 03/02/2018 08:28 AM, Peter Krempa wrote: > > On Tue, Feb 27, 2018 at 09:53:00 +0100, Michal Privoznik wrote: > >> On 02/27/2018 03:06 AM, Star Guo wrote: > >>> Hello Everyone, > >>> > >>> > >>> > >>> My pc run in CentOS 7.4 and install

We're trying to re-configure the affinity unconditionally in cpu hotplug callback. This may lead the issue during resuming from s3/s4 since - virt queues haven't been allocated at that time. - it's unnecessary since thaw method will re-configure the affinity. Fix this issue by checking the config_enable and do nothing is we're not ready. The bug were introduced by commit

We're trying to re-configure the affinity unconditionally in cpu hotplug callback. This may lead the issue during resuming from s3/s4 since - virt queues haven't been allocated at that time. - it's unnecessary since thaw method will re-configure the affinity. Fix this issue by checking the config_enable and do nothing is we're not ready. The bug were introduced by commit

Add a cpu notifier to virtio-net, so that we can reset the virtqueue affinity if the cpu hotplug happens. It improve the performance through enabling or disabling the virtqueue affinity after doing cpu hotplug. Cc: Rusty Russell <rusty at rustcorp.com.au> Cc: "Michael S. Tsirkin" <mst at redhat.com> Cc: Jason Wang <jasowang at redhat.com> Cc: virtualization at

Add a cpu notifier to virtio-net, so that we can reset the virtqueue affinity if the cpu hotplug happens. It improve the performance through enabling or disabling the virtqueue affinity after doing cpu hotplug. Cc: Rusty Russell <rusty at rustcorp.com.au> Cc: "Michael S. Tsirkin" <mst at redhat.com> Cc: Jason Wang <jasowang at redhat.com> Cc: virtualization at

Can i assign static vnet* device for some guests?

On Thu, Oct 17, 2013 at 09:57:41AM +1030, Rusty Russell wrote: > Jason Wang <jasowang at redhat.com> writes: > > We're trying to re-configure the affinity unconditionally in cpu hotplug > > callback. This may lead the issue during resuming from s3/s4 since > > > > - virt queues haven't been allocated at that time. > > - it's unnecessary since thaw

On Thu, Oct 17, 2013 at 09:57:41AM +1030, Rusty Russell wrote: > Jason Wang <jasowang at redhat.com> writes: > > We're trying to re-configure the affinity unconditionally in cpu hotplug > > callback. This may lead the issue during resuming from s3/s4 since > > > > - virt queues haven't been allocated at that time. > > - it's unnecessary since thaw

On 07/16/2013 01:29 PM, Guan Qiang wrote: > 于 2013/7/15 17:32, Gao feng 写道: >> On 07/15/2013 05:18 PM, hzguanqiang wrote: >>> Hi, Gao Feng >>> >>> I've tried what you said, but still exists the problem: >>> >>> ubuntu@lxc:~$ vir attach-disk instance-0000002c /dev/dm-0 sdb >>> error: Failed to attach disk >>> error:

Hi All, I am facing the following issue, while using Libvirt version 0.8.4. (1) Libvirt API does not return, since the qemu-kvm process is hung up. Based on the information available on mail thread *https://bugzilla.redhat.com/show_bug.cgi?id=676205* (comment 26 - scenario 1), this has been fixed in later version of Libvirt, specifically in RHEL 6.2(libvirt 0.9.4). I have checked the

We're trying to re-configure the affinity unconditionally in cpu hotplug callback. This may lead the issue during resuming from s3/s4 since - virt queues haven't been allocated at that time. - it's unnecessary since thaw method will re-configure the affinity. Fix this issue by checking the config_enable and do nothing is we're not ready. The bug were introduced by commit