similar to: virsh edit has no impact on domain

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 :

I also ran "virsh capabilities". It looks like the machine "pc-i440fx-4.0" is available there. Does it mean anything to this case? I am guessing "4.0" means Qemu version, which is the version I am trying to install from source. https://gist.github.com/proywm/433de1f410c5e7d68cff5833e03fb5dc On Sat, Jul 20, 2019 at 2:36 PM Probir Roy <proy@email.wm.edu> wrote:

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):

Hi, I am trying to preload two shared libraries while running Qemu using libvirt. To preload the shared libraries I have added an environment variable in the $domain.xml file with the following command: ``` virt-xml generic --edit --confirm --qemu-commandline

On Wed, Jul 17, 2019 at 13:33:08 -0500, Probir Roy wrote: > Hi, > > I am trying to preload two shared libraries while running Qemu using > libvirt. To preload the shared libraries I have added an environment > variable in the $domain.xml file with the following command: > > ``` > virt-xml generic --edit --confirm --qemu-commandline >

Your setup is in consistant. > 127.0.0.1 localhost.localdomain localhost > 127.0.0.1 localhost I suggest run my debugscript, make sure the servers there base setup is the same. + set both DC's there /etc/resolv.conf search msi.mydomain.com mydomain.com # IF THIS IS DC1 nameserver 172.23.93.26 nameserver 172.23.93.25 nameserver 172.23.93.3 # and for DC0

On Wed, Oct 31, 2018 at 09:32:30AM +0100, Andrea Bolognani wrote: >On Wed, 2018-10-31 at 10:56 +0900, Minjun Hong wrote: >> Hi. >> >> Thanks to help of this mailing list (especially Jim Fehlig), I have finished setup of libvirt. >> However, there is something weird. It is that I installed libvirt on 5 servers but >> the default connection of one of them is

Hi. Thanks to help of this mailing list (especially Jim Fehlig), I have finished setup of libvirt. However, there is something weird. It is that I installed libvirt on 5 servers but the default connection of one of them is 'qemu:///' even if those of the others are all 'xen:///'. I searched how to change it but, I only found a bypass adding "

On Ubuntu 20.04 I have provisioned a AD DC using samba-4.12 from Louis' Repo and his instructions: https://github.com/thctlo/samba4/blob/master/full-howto-Ubuntu18.04-samba-AD_DC.txt In the output of: samba-tool domain provision --use-rfc2307 --realm=XXX.XXX --domain=XXX --dns-backend=BIND9_DLZ --adminpass=XXXxxx I see this: WARNING /usr/lib/python3/dist-packages/samba/provision/sambadns.py

On Thu, 2019-04-18 at 15:29 +0100, Daniel P. Berrangé wrote: > On Thu, Apr 18, 2019 at 04:23:05PM +0200, Andrea Bolognani wrote: > > qemuDomainAssignAddresses() is supposed to make sure that any address > > configured explicitly by the user (or previously by libvirt) is > > preserved, and it's doing that correctly when it's called from inside > >

On Thu, 2018-11-01 at 16:40 +0100, Erik Skultety wrote: > On Wed, Oct 31, 2018 at 05:33:09PM +0100, Martin Kletzander wrote: > > On Wed, Oct 31, 2018 at 09:32:30AM +0100, Andrea Bolognani wrote: > > > On Wed, 2018-10-31 at 10:56 +0900, Minjun Hong wrote: > > > > I searched how to change it but, I only found a bypass adding " LIBVIRT_DEFAULT_URI='xen:///'

Moving to libvirt-users where it belongs. On Thu, 2019-04-18 at 06:47 +0000, Tal Attaly wrote: > Hi, > I have bridge type interface defined with slot 3 - > <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> > but after running virsh domxml-to-native qemu-argv I get slot 2- > -netdev tap,fd=21,id=hostnet0 -device

Hi ! I wonder, that i got a login shell, if i start the gnome-terminal on my Gnome-Desktop, recognizing the sourcing of all files in /etc/profile.d/ .. Can somebody give me an hint, where it's system-wide configured or it's a bug and it isn't configurable ? (it's not configured as login-shell in Preferences and the checkbox ;-) ) For Ubuntu18.04 it's not the default,

I followed this url to set up Samba AD DC. https://github.com/thctlo/samba4/blob/master/full-howto-Ubuntu18.04-samba-AD_DC.txt I do have it working. I am testing with a Windows 10 VM as a member of the domain. The machine joins the domain. Also, as administrator, I can create and enforce Group Policies. from this Windows machine. I have a Fedora 29 server which serves DHCP and DNS (and

Hi Andrea Thanks for the reply. Below is some more information regarding the same.. uname -a Linux t1040rdb 3.12.37-rt51-QorIQ-SDK-V1.8+gf488de6 #2 SMP Mon Jul 20 14:43:02 IST 2015 ppc GNU/Linux libvirtd --version libvirtd (libvirt) 1.2.13 cat /usr/share/libvirt/cpu_map.xml </arch> <arch name='ppc64'> <model name='POWERPC_e5500'> <vendor

No XML containing guest information is formed.I'm getting error prior to guest XML formation. On Jul 22, 2015 3:00 PM, "Andrea Bolognani" <abologna@redhat.com> wrote: > On Wed, 2015-07-22 at 14:09 +0530, abhishek jain wrote: > > Hi Andrea > > > > Thanks for the reply. > > Below is some more information regarding the same.. > > > > uname

> > I followed this url to set up Samba AD DC. > > https://github.com/thctlo/samba4/blob/master/full-howto-Ubuntu18. > 04-samba-AD_DC.txt > > > > I do have it working. I am testing with a Windows 10 VM as a member > > of the domain. > > The machine joins the domain. Also, as administrator, I can create > > and enforce > > Group Policies. from

Hello R-devel, Currently on Unix-like systems, Sys.which incorporates the absolute path to the `which` executable, obtained at the configure stage: > ## hopefully configure found [/usr]/bin/which > which <- "@WHICH@" > if (!nzchar(which)) { > warning("'which' was not found on this platform") This poses a problem for the Spack package

I have 2 Ububtu DCs. One acting as a secondary/failover. At one point the users were replicated from primary to secondary. But now they are not replicating. The output from samba-tool drs showrepl is attached. What else may I provide to aid diagnostics? I know Samba does not replicate sysvol 'yet', so rsync is needed, but that does not seem to contain the users. Thank you,

Hi , We have an DC (Ubuntu18.04) which also acts as a file server. The server was recently classic upgraded to AD. Before that all the home drives were in /home. When we migrated to change we added the following in smb.conf to give users access to their existing home folders. The problem now is that when we create a user either using samba-tool create user username or smbpasswd or even via RSAT,