similar to: pci-assign fails with read error on config-space file

On 10/28/2016 07:28 AM, Henning Schild wrote: > Hey, > > i am running an unusual setup where i assign pci devices behind the > back of libvirt. I have two options to do that: > 1. a wrapper script for qemu that takes care of suid-root and appends > arguments for pci-assign > 2. virsh qemu-monitor-command ... 'device_add pci-assign...' With any reasonably modern

Vincent JARDIN <vincent.jardin at 6wind.com> writes: > On 10/06/2014 18:48, Henning Schild wrote:> Hi, >> In a first prototype i implemented a ivshmem[2] device for the >> hypervisor. That way we can share memory between virtual machines. >> Ivshmem is nice and simple but does not seem to be used anymore. >> And it >> does not define higher level devices,

Vincent JARDIN <vincent.jardin at 6wind.com> writes: > On 10/06/2014 18:48, Henning Schild wrote:> Hi, >> In a first prototype i implemented a ivshmem[2] device for the >> hypervisor. That way we can share memory between virtual machines. >> Ivshmem is nice and simple but does not seem to be used anymore. >> And it >> does not define higher level devices,

Hi, I'm running into some problems with libvirt and hoping someone can point me at some instructions or maybe even help me out. First, are there any requirements on qemu version in order to use the "numatune" and/or "cpu/numa/cell" elements? Or do they use cgroups and not the native qemu numa support? Second, are there any instructions on how to set up cgroups? I

Hi I tried to restrict usage of some running VM by cpu.shares (i.e. set to 10 from original 1024) on loaded system and it seem doesn't work as I expected... all running processes has same CPU usage (by htop) :-/ Does anyone has same experience? Fedora 19, libvirt-1.0.5.9-1.fc19.x86_64 Thanks a lot Martin -- Martin Pavlásek <mpavlase@redhat.com> OpenStack QA Associate/Red Hat

On 10/28/16 13:28, Henning Schild wrote: > Hey, > > i am running an unusual setup where i assign pci devices behind the > back of libvirt. I have two options to do that: > 1. a wrapper script for qemu that takes care of suid-root and appends > arguments for pci-assign > 2. virsh qemu-monitor-command ... 'device_add pci-assign...' > > I know i should probably

Good morning, there is a typo in my description; the line <address domain='0x0' bus='0x1' slot='0x00' function='0x0'/> should be <address domain='0x0' bus='0x2' slot='0x00' function='0x0'/> That was correct in my xml-file. Isn't there anybody how can help me with that? Regards Michael Weis Von:

Hello, Everybody. I encounter a problem when i using my guest. I booting my guest without HDMI primarily, Then i add it, but my guest is be rebooted. To know what cause it, i do it again, especially i check my guest is running normal or not with "ping" before plugging, that's well. What i was suffer? can you help me solve it? Following message is detailed!!! Guest: window 7

Hi, I'm running OpenStack to manage LXC instance through libvirt. The same setting runs perfectly well on Ubuntu 12.04, while on CentOS 6u3, libvirt dumped following message when starting lxc instance. virsh -c lxc:/// start instance-00000032 error: internal error The 'cpuacct', 'devices' & 'memory' cgroups controllers must be mounted Really appreciated if

Hi Pierre, thanks for your reply. I am using kernel 3.10.0-123.8.1.el7.x86_64. The kernel modul used after nodedev-detach is vfio-pci This is the output of lspci -vv after I did a virsh nodedev-detatch pci_0000_02_00_0 02:00.0 Ethernet controller: PLX Technology, Inc. Device 235e Subsystem: PLX Technology, Inc. Device 235e Control: I/O- Mem- BusMaster- SpecCycle- MemWINV-

Hi, i am working on the jailhouse[1] project and am currently looking at inter-VM communication. We want to connect guests directly with virtual consoles based on shared memory. The code complexity in the hypervisor should be minimal, it should just make the shared memory discoverable and provide a signaling mechanism. We would like to reuse virtio so that Linux-guests will eventually just work

Hi, i am working on the jailhouse[1] project and am currently looking at inter-VM communication. We want to connect guests directly with virtual consoles based on shared memory. The code complexity in the hypervisor should be minimal, it should just make the shared memory discoverable and provide a signaling mechanism. We would like to reuse virtio so that Linux-guests will eventually just work

On 2014-06-12 04:27, Rusty Russell wrote: > Henning Schild <henning.schild at siemens.com> writes: >> Hi, >> >> i am working on the jailhouse[1] project and am currently looking at >> inter-VM communication. We want to connect guests directly with virtual >> consoles based on shared memory. The code complexity in the hypervisor >> should be minimal, it

On 2014-06-12 04:27, Rusty Russell wrote: > Henning Schild <henning.schild at siemens.com> writes: >> Hi, >> >> i am working on the jailhouse[1] project and am currently looking at >> inter-VM communication. We want to connect guests directly with virtual >> consoles based on shared memory. The code complexity in the hypervisor >> should be minimal, it

Hi, I'm trying to manage LXC instances through OpenStack, which use libvirt as a virtualization driver layer. After launching LXC instance, I simply could not attach to the console. virsh # list Id Name State ---------------------------------- 14366 instance-00000078 running virsh # console 14366 Connected to domain instance-00000078 Escape character is ^] And it keeps

[Adding Tomas Golembiovsky] On Wed, Sep 26, 2018 at 12:11 PM Richard W.M. Jones <rjones@redhat.com> wrote: > > Rather than jumping to a solution, can you explain what the problem > is that you're trying to solve? > > You need to do <X>, you tried virt-v2v, it doesn't do <X>, etc. > Well, that's mainly IMS related challenges. We're working on

Hi, I am running OpenStack Cluster and use libvirt + cgroup to limit vm’s performance https://wiki.openstack.org/InstanceResourceQuota What I am confusing is.. 1. After running a vm instance with some croup limit applied, I can’t find any related cgroup settings. 2. Can I change limit value after instance is running? like change disk_read_iops_sec from 10 to 20. One of the xml file like below.

On Fri, Oct 28, 2016 at 01:28:19PM +0200, Henning Schild wrote: > Hey, > > i am running an unusual setup where i assign pci devices behind the > back of libvirt. I have two options to do that: > 1. a wrapper script for qemu that takes care of suid-root and appends > arguments for pci-assign > 2. virsh qemu-monitor-command ... 'device_add pci-assign...' > > I

Hi everyone, I use KVM on Openstack Cloud. And KVM migrated successfull, but not ping. *Source Host SIDE: *"/var/log/libvirt/libvirtd.log" 2014-06-16 05:15:50.599+0000: 2096: warning : qemuMigrationCancelDriveMirror:1383 : Unable to stop block job on drive-virtio-disk0 2014-06-16 05:15:50.601+0000: 2096: *warning : qemuMigrationCancelDriveMirror:1383 : Unable to stop block job on

Hi, We have upgraded the libvirt version from libvirt-1.0.5 to libvirt-1.0.6-1 on our linux machine. After this upgrade "virsh cpu-stats <domain>" command is not working on our HardWare. *virsh # cpu-stats test error: Failed to retrieve CPU statistics for domain 'test' error: internal error error accessing cgroup cpuacct for vcpu* ** *# cat /proc/cgroups #subsys_name