similar to: Reg: <operation not permitted><netlink socket><Qemu device>

Hello Han, Thanks for the response. The XML option with qemu:commandline works if the device is added during the VM creation. But I would like to hot-plug the device to the running VM. I can add the device using the command line <virsh qemu-monitor-command --hmp VM-Name device_add edu,id=edu0> But I would like to add the device using the XML file, like <virsh attach-device VM-Name

On Wed, Oct 23, 2019 at 4:27 PM bharath paulraj <bharathpaul@gmail.com> wrote: > Hello Han, > > Thanks for the response. The XML option with qemu:commandline works if the > device is added during the VM creation. But I would like to hot-plug the > device to the running VM. I can add the device using the command line > <virsh qemu-monitor-command --hmp VM-Name

Hi Team, I am exploring "edu" device in QEMU to add my own custom device. I am able to add the device using the command line. Would it be possible to add the device using XML file through libvirt? -- Regards, Bharath

On Tue, Oct 22, 2019 at 5:41 PM bharath paulraj <bharathpaul@gmail.com> wrote: > Hi Team, > > I am exploring "edu" device in QEMU to add my own custom device. I am able > to add the device using the command line. Would it be possible to add the > device using XML file through libvirt? > Hello, edu device is not implemented to libvirt xml. However you can use it

Hi! I am trying libvirt on POWERPC64 with the default settings such as selinux enabled. It is all good till I move images out of /var/lib/libvirt/images/. http://libvirt.org/drvqemu.html#securityselinux is saying that "If attempting to use disk images in another location, the user/administrator must ensure the directory has be given this requisite label. Likewise physical block devices

Hi Team, I am doing a small testing and I don't know if my expectation is correct or not. Pardon me if I am ignorant. I created a VM and the VM is running. In the hypervisor I have created ".img" file and attached this .img file to the VM. My expectation is that, if VM is writing files to the attached disk, then it should reflect in the .img file created in the hypervisor. But It is

On Wed, Aug 07, 2019 at 09:57:02PM +0530, bharath paulraj wrote: > Hi Team, > > I am doing a small testing and I don't know if my expectation is correct or > not. Pardon me if I am ignorant. > I created a VM and the VM is running. In the hypervisor I have created > ".img" file and attached this .img file to the VM. > My expectation is that, if VM is writing

I recently began getting periodic emails from SEalert that SELinux is preventing /usr/libexec/qemu-kvm "getattr" access from the directory I store all my virtual machines for KVM. All VMs are stored under /vmstore , which is it's own mount point, and every file and folder under /vmstore currently has the correct context that was set by doing the following: semanage fcontext -a -t

Hi, I have been trying to figure out how pid namespaces interact with netlink. netlink uses pids (or really tids I hope?) to address sockets associated with processes. The netlink code passes around pids without caring much about the pid namespace. It does pass around some information about the network namespace, but that doesn't help here because the pid namespace is not necessarily

Hi, I have been trying to figure out how pid namespaces interact with netlink. netlink uses pids (or really tids I hope?) to address sockets associated with processes. The netlink code passes around pids without caring much about the pid namespace. It does pass around some information about the network namespace, but that doesn't help here because the pid namespace is not necessarily

Hey all, I''m looking for more detailed info on the netlink api. I''ve read Andi Kleen''s man pages (which describe themselves as lacking and incomplete), rfc3549 -- Linux Netlink as an IP Services Protocol (which was a nice general overview, but lacking in implementation detail), both the iproute2/ip/tc source and the kernel source (which have no usable

Thanks for the advice. I had played with NT4 a little bit to see if I could use it for setting up a resource domain for windows 2003 machines- since it looks like you can join Windows 2003 machines to an NT4 domain (so why PCNL can't I don't know), and then establish trusts between NT4 and PCNL. I didn't really want to have NT4 machines in my enviroment any longer than necessary so

From: Leon Romanovsky <leonro at nvidia.com> In netdev common pattern, xxtack pointer is forwarded to the drivers to be filled with error message. However, the caller can easily overwrite the filled message. Instead of adding multiple "if (!extack->_msg)" checks before any NL_SET_ERR_MSG() call, which appears after call to the driver, let's add this check to common code.

Hi Sambas, I have been using the latest Sun version of Samba on my Solaris 9 SPARC Ultra 10 for a long time now. I connect with my W2K PC to mainly play music and make backups. I recently foolishly installed the Sun Solaris PC NetLink 2.0 as an experiment. The NetLink worked but I couldn't easily work out the security - basically I don't use any as it is a home system with only myself

Hi Laine, Sorry to disturb you. It seemed this issue had been fixed in libvirt-1.2.2/libnl-3.2.22/linux-3.12. But we still got the error on PowerPC platform. I'll appreciate if you could give any suggestion. We are not sure if any netlink implementation in kernel space is missed. The scenario is a little complicated. We installed internal PF and VF kernel modules and want to use

In netdev common pattern, extack pointer is forwarded to the drivers to be filled with error message. However, the caller can easily overwrite the filled message. Instead of adding multiple "if (!extack->_msg)" checks before any NL_SET_ERR_MSG() call, which appears after call to the driver, let's add new macro to common code. [1] https://lore.kernel.org/all/Y9Irgrgf3uxOjwUm at

https://bugzilla.netfilter.org/show_bug.cgi?id=995 Bug ID: 995 Summary: netlink: Error: Unknown data type in set key 31 Product: nftables Version: unspecified Hardware: x86_64 OS: other Status: NEW Severity: normal Priority: P5 Component: nft Assignee: pablo at netfilter.org

On Mon, May 27, 2019 at 01:30:05PM +0200, Martin Kletzander wrote: > While svirt_t can be used for sockets it does not always guarantee that it will > be accessible from a virtual machine. The VM might be running under svirt_tcg_t > context which will need a svirt_tcg_t label on the socket in order to access it. I don't really know enough about SELinux or the sVirt policy to comment

Hi, I have a process which is running as a linux service and assigns IP addresses using netlink to configued interface in linux. For IPv4 addresses i do not see any issue with this assignment. When i try to assign an IPv6 address, the address gets assigned successfully to the interface, but the Neighbour Solication request received for that address is not responded with and hence ping6 from a

While svirt_t can be used for sockets it does not always guarantee that it will be accessible from a virtual machine. The VM might be running under svirt_tcg_t context which will need a svirt_tcg_t label on the socket in order to access it. There is, however, another label, svirt_socket_t, which is accessible from virt_domain: # sesearch -A -s svirt_t -c unix_stream_socket -p connectto ...