similar to: Configuring default network/storage for qemu:///session

"Daniel P. Berrange" <berrange@redhat.com> writes: > There's nothing in libvirt which auto-creates such resources by default. > > IIRC, it is probably virt-manager and/or GNOME Boxes applications which > are creating them. Ah, in this case it's virt-install, quite right. My mistake. Still, then, what would be best way to have some initial configuration for

On Thu, Mar 03, 2016 at 10:20:41AM -0500, catern@catern.com wrote: > > Hi libvirt-user, > > If I run (as a normal user): > > virsh -c qemu:///session net-list --all > virsh -c qemu:///session pool-list --all > > I see a default network and a default pool. And indeed, these appear in > the persistent configuration. It seems these are created the first time >

Hi Daniel, thanks for the quick reply we did try to override SMBIOS host_uuid_source = "machine-id" and it didn't work even that nodes have different [root@modi01 kubevirt]# ./cluster-up/ssh.sh kind-1.17.0-worker root@kind-1:/# cat /etc/machine-id [root@modi01 kubevirt]# ./cluster-up/ssh.sh kind-1.17.0-control-plane root@kind-1:/# cat /etc/machine-id

Hi, I ran into some troubles while upgrading pigeonhole: crane dovecot: lda(petar): Error: sieve: Failed to access user storage (temporary failure) crane dovecot: lda(petar): Error: sieve: file storage: Could not find storage root directory; path was left unconfigured and autodetection failed After reading through the changelog, I noticed that there have been some changes in the script

On Mon, Jan 12, 2015 at 01:19:18PM +0100, Stephan Bosch wrote: > > Petar Bogdanovic schreef op 12-1-2015 om 13:05: > >Hi, > > > >I ran into some troubles while upgrading pigeonhole: > > > > crane dovecot: lda(petar): Error: sieve: Failed to access user storage (temporary failure) > > crane dovecot: lda(petar): Error: sieve: file storage: Could not

Greetings folks. I've setup libvirtd on my manjaro linux laptop. Got a couple of VM's running (Win10 and Debian10) through NAT without any issues. This is what the current network diagram looks like and it works fine: +-----------------------------------+ | +---------------------+ | | |

On Tue, Sep 30, 2014 at 04:44:05PM +0100, Richard W.M. Jones wrote: > When using the libvirt backend, don't use the SLIRP. Use > qemu-bridge-helper via libvirt to give us a full network connection. > One consequence of this is that 'ping' works in virt-builder > --run-command. > > Note unfortunately this does not fix virt-rescue (since it overrides > the default

Hi libvirt-users, I find myself wanting to do something that seems like it must have some obvious solution: I have multiple users (let's just assume local Unix accounts) on a Linux system, and I want them all to have access to KVM-accelerated virtualization. But, I don't want them to be able to meddle with each other's virtual machines. Is there a solution to this problem? Methods of

Is there a way to specify default files to use for new mailbox creations? For example, when a mailbox's directory structure is created, there is no greeting, unavailable, or busy messages, so the incoming calls get the message: "The person at extension XXXXXX is not available". I'd like to be able to specify default files to be used and copied into the voicemail structure,

Hi, I am trying to run Qemu-4.0 installed from source code. When I run virt-manager to create a VM, I get the following error: ``` Unable to complete install: 'internal error: process exited while connecting to monitor: 2019-07-19T17:06:35.954242Z qemu-system-x86_64: -enable-kvm: unsupported machine type Use -machine help to list supported machines' Traceback (most recent call last):

Hello.. I've asked this question before without getting any further help really.. When a new user is added using "adduser" on 5.x (havn't really checked if it's the same under 4.x or not), the default homedir permission is 755 (drwxr-xr-x) which to me, looks a bit insecure? It's of course pretty easy to solve it by a simple chmod, but yet, isn't there anyway to

The attached patch changes the logfile name generated by qemu-dm to use the pattern qemu-dm-[NAME].log instead of qemu-dm-[PID].log. This makes it easier for the adminsitrator to figure out which log corresponds to which guest (particularly after a crash where you no long know what PID the qemu-dm process for your guest had). It also prevents the number of log files from growing unbounded.

Hi, I'm using a heavily tweaked CentOS 5.4 for desktop installs (here's what it looks like: http://www.microlinux.fr/captures.html). For every app I install, I try to configure a sensible default configuration system-wide for all users. For example, once I found a nice configuration for XMMS (default skin, loads of plugins, orange On Screen Display in a nice font, etcetera), I put my

It is true that the machine contains 'pc-i440fx-4.0'. I am using Ubuntu18.04 and libvirt-4.0.0 This is probably a separate issue, but while updating the machine name neither "virsh define" or "virsh edit" updates the name to "pc". I was reading the FAQ of libvirt on updating the configuration at :

On Wed, Sep 12, 2018 at 6:59 AM, Martin Kletzander <mkletzan@redhat.com> wrote: > On Mon, Sep 10, 2018 at 02:38:48PM -0400, David Vossel wrote: > >> On Wed, Aug 29, 2018 at 4:55 AM, Daniel P. Berrangé <berrange@redhat.com> >> wrote: >> >> On Tue, Aug 28, 2018 at 05:07:18PM -0400, David Vossel wrote: >>> > Hey, >>> > >>>

On Thu, Jun 29, 2017 at 12:17:02PM +0100, Richard W.M. Jones wrote: > On Wed, Jun 28, 2017 at 10:33:48AM +0200, Pino Toscano wrote: > > On Tuesday, 27 June 2017 22:56:25 CEST Richard W.M. Jones wrote: > > > > > > Not that I'm opposed to this patch, but there's a bit of history here: > > > > > >

Hi togeteher, Config: Server: Samba 3.0.2a as PDC, no LDAP, no Kerberos Clients: WinXP Prof all working, dom-Logons are ok. When I add a new linux-user, there ist a default profile for the linux-user in the skel-directory. Does Samba provide a 'skel-profile' for new samba-users (=domain- users). If so, where do I have to put the default profile and do I have to set special owner /

Greetings, I am running a test automation service which makes use of QEMU/KVM. As the tests run for few minutes, the time spent booting the OS (Windows) is quite a waste of resources so I decided to play a bit around the idea of hot cloning running VMs. Following an old discussion I found, I proceeded with saving the VM state through virsh save, edit its XML file with virsh save-image-edit and

I am using PAM and pam_smbpass.so with Samba 2.999 (Debian sid package). If, in /etc/pam.d/samba, I set session required pam_smbpass.so then login fails, and the log says: [2002/08/04 15:43:26, 0] auth/pampass.c:smb_pam_error_handler(73) smb_pam_error_handler: PAM: session setup failed : Module is unknown [2002/08/04 15:43:26, 1] smbd/session.c:session_claim(103) pam_session

On Wed, Aug 29, 2018 at 4:55 AM, Daniel P. Berrangé <berrange@redhat.com> wrote: > On Tue, Aug 28, 2018 at 05:07:18PM -0400, David Vossel wrote: > > Hey, > > > > Over in KubeVirt we're investigating a use case where we'd like to > perform > > a live migration within a network namespace that does not provide > libvirtd > > with network access.