similar to: qemu:///session vs qemu:///system

Hi, I try to connect from virsh -c qemu:///session and it shows the VMs created by by that particular user (testuser). But when i try from root virsh -c qemu:///system i don't see the vms created by testuser. How do i make it appear in the root's virsh ie the vms created by testuser ? I need this because i need information for global VM statistics created by all users. Can someone

On 10/10/2015 10:53 AM, Spencer Baugh wrote: > > Dear libvirt-users, > > Suppose my home directory is network mounted on to several different > machines. And suppose I defined some VMs in qemu:///session. The > configuration files and disk images for qemu:///session are stored in my > home directory. > > Now suppose I log in to some machine and use virsh. The

Cole Robinson <crobinso@redhat.com> writes: > The proper way to make sure shared VMs aren't started across multiple machines > is libvirt's locking support: https://libvirt.org/locking.html > > It requires running a separate daemon though so isn't trivial, and I have no > idea if it can be made to work with qemu:///session. Hmm, but what do you mean by shared VMs

Dear libvirt-users, Suppose my home directory is network mounted on to several different machines. And suppose I defined some VMs in qemu:///session. The configuration files and disk images for qemu:///session are stored in my home directory. Now suppose I log in to some machine and use virsh. The qemu:///session VMs that are marked autostart are started. Now if I log into another machine and

Then you should definitely submit a bug with redhat about this, seems like a serious one. -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ----- Original Message ----- > From: "Gena Makhomed" <gmm at csdoc.com> > To: centos-virt at centos.org > Sent: Wednesday, 29 July, 2015 23:09:14 > Subject: [CentOS-virt] CentOS 7.1 + qemu-kvm-ev + SLIC

On Thu, Jul 30, 2015 at 9:04 PM, Gena Makhomed <gmm at csdoc.com> wrote: > On 30.07.2015 10:49, Nux! wrote: > > Then you should definitely submit a bug with redhat about this, seems like >> a serious one. >> > > Ok, done: > > https://bugzilla.redhat.com/show_bug.cgi?id=1248758 > > P.S. > > As I can see - bugzilla.redhat.com for oVirt Product >

On 10/16/20 10:23 AM, Eric Blake wrote: > A rather trivial decoding; we may enhance it further if qemu extends > things to give an integer depth alongside its tri-state encoding. > --- > > I'll wait to push this to libnbd until the counterpart qemu patches > land upstream, although it looks like I've got positive review. Whoops, I accidentally pushed this before qemu

Hello, we are using several centos servers under Vmware. We are having more and more requests for server space for each business application (let assume that these business requests are for different type of services: databases, web apps, application servers etc. I wonder which solution is better: 1. new CentOS under vmware (having several CentOS servers under Vmware) or 2. new CentOS under KVM

On 04/10/2018 09:07 AM, Nir Soffer wrote: > On Tue, Apr 10, 2018 at 4:48 PM Kevin Wolf <kwolf@redhat.com> wrote: > >> Am 10.04.2018 um 15:03 hat Nir Soffer geschrieben: >>> On Tue, Apr 10, 2018 at 1:44 PM Richard W.M. Jones <rjones@redhat.com> >>> wrote: >>> >>>> We now have true zeroing support in oVirt imageio, thanks for that.

hi! what is the difference between wine and a virtualisation like virtualbox? what are advantages and disadvantages compared to each other? peter

Thanks for letting me know I'm not making myself clear, let me try again with a few more specifics, These are Windows VMs with three disk images for C:, D: and L:. To simplify I'll focus on the image for C: which had grown to 77G physical size on the hypervisor's ssd (I just double-checked that with 'ls -al' because qemu-img below says 70G, this image had two snapshots at one

On Sunday 01 February 2009 05:25:40 Ramón García wrote: > This is not a quite fair comparison. Other virtual machines must be > doing garbage collection, while LLVM, as it is using C code, it is > taking advantage of memory allocation by hand. That is an insignificant advantage in this particular case (SciMark2) because the memory for each test is preallocated and not part of the

On 30.07.2015 10:49, Nux! wrote: > Then you should definitely submit a bug with redhat about this, seems like a serious one. Ok, done: https://bugzilla.redhat.com/show_bug.cgi?id=1248758 P.S. As I can see - bugzilla.redhat.com for oVirt Product does not contain qemu-kvm-ev Component at all - looks like this is yet another bug - in the bugzilla settings. But I can't find how to report

On Mon, Aug 03, 2020 at 01:45:45PM +0000, Kim-Norman Sahm wrote: > hi, > > i’m running Debian 10 on POWER9 and would like to spawn x86_64 emulated VMs. > The virtual machine is configured to run with 8 vpus but it’s very slow. > On the host you can see that the qemu-system-x86_64 process is using just one core! > > Ppc64le guests are using multi cores, so its looks like an

On 29.07.2015 21:34, Nux! wrote: > Yes, you can. > In fact you can use the binaries from the ovirt repo itself, no need to rebuild. Thank you! In fact - I can't use raw binaries from the ovirt repo itself, because these qemu-kvm binaries contains one bug, which is already fixed in Debian: If you want to migrate Windows from hardware node to VM using CentOS 7.1 on hardware node and

On Tue, Nov 18, 2014 at 11:37:31AM +0530, Niranjan wrote: > libvirt: XML-RPC error : Cannot recv data: Connection reset by peer > virt-builder: error: libguestfs error: could not connect to libvirt (URI = > qemu:///session): Cannot recv data: Connection reset by peer [code=38 > domain=7] This is a libvirt bug. Possibly: https://bugzilla.redhat.com/show_bug.cgi?id=1164773 or:

A rather trivial decoding; we may enhance it further if qemu extends things to give an integer depth alongside its tri-state encoding. --- I'll wait to push this to libnbd until the counterpart qemu patches land upstream, although it looks like I've got positive review. info/nbdinfo.c | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/info/nbdinfo.c b/info/nbdinfo.c index

Greetings I am trying to create quick fedora20 vm's and using virt-builder for it. Currently when i run virt-builder on Fedora 21 it fails with below errors: <snip> [juno@dhcp207-208 ~]$ virt-builder fedora-20 --cache ~/.cache/virt-builder [ 1.0] Downloading: http://libguestfs.org/download/builder/fedora-20.xz [ 1.0] Planning how to build this image [ 1.0] Uncompressing [ 9.0]

Hi all, following the discussion on about documentation, I was wondering whether we need to look at a standard way in which we recommend how to provision images for VMs. Am starting this with a Xen hat, but the discussion should not be specific to this. There are a number of options, but all have some trade-offs == #1 virt-install == Advantages: similar to KVM Disadvantages: may cause

Dear all, while playing around with openssh-4.1p1 (trying to add AFS token forwarding in SSH-2), I noticed that agressive rekeying (as e.g. employed by regress/rekey.sh, rekeying every 16bytes) seems to disturb the various forwardings (X11, agent) set up at the beginning of the session. These do not trigger regression test errors, since the client does not ask for confirmation from the server for