similar to: KVM - restart of VMs after rejoin a node into cluster

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

This error is not 100% reproducible. However, kernel panic has been occurred many times for last two months. It usually happens when multi VMs (in our case, 14 VMs) are booting together. After we made three big changes to gain more availibility, it began to happen. Changes are : 1. Use *NAS* as vm storage for migration from local disk 2. Use *two bondings* for switch HA (with 4 nics) from

Installed Puppet Enterprise 3.0.0 on two Ubuntu 12.04 VMs created through Oracle VirtualBox. Networking is bridged mode through laptop''s ethernet adapter so VMs are on the same corporate subnet as the actual host. During the same run of the VMs as the install of puppet master and agent, was able to login to master https://puppetmaster and register the agent node. However a few

Recent versions of libvirt seem to have taken to starting new copies of my vms when they restart. Any vm marked to start when libvirt is started is started, even if it is already running, which leads to multiple running vms trying to use the same disk image. I think this probably started with the upgrade from 0.7.4 to 0.7.5 but I can't be entirely sure as I only realised yesterday that I

This is a problem I've had on and off under CentOS5 and CentOS6, with both xen and kvm. Currently, it happens consistently with kvm on 6.5, e.g. with every kernel update. I *think* it generally worked fine with the 6.4 kernels. There are 7 VMs running on a 6.5, x86_64, 8GB RAM host, each with 512MB RAM and using the e1000 NIC. I picked this specific NIC because the default does not allow

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Hi there, After updating a server from CentOS 5.3 to 5.4 my Xen pci-passthru setup has some troubles. The server has two NICs, one used by dom0 and the other assigned to a domU and one SCSI controler assigned to another domU. It has been working fine since CentOS 5.1, when I did the initial setup. After upgrading to 5.4, I get this error when starting the domU with one of the NICs assigned:

Good morning, I need to use pciback.hide to hide a pci card because I want to pci passthrough that card to a domU. My hardware neither supports Intel-Vt-d nor AMD's IOMMU. Unfortunately this doesn't seem to work in Centos 54 anymore. I guess it doesn't work because it is not compiled into the kernel, but as a module. I got the following error in dmesg and the pci device is still

Hi everyone Ok this is really strange. I''ve been messing around with Xen for the past few weeks on a 32bit test machine and CentOS 5.4 and it''s been working fine. Today I went into the office on a Sunday to install Xen on our server but I had a major problem. The server is a home-build with a Tyan s5211 motherboard with an Intel i3210w chipset CentOS 5.4 64bit installed and

Hi, I'm having a problem with libvirtd (backend being kvm) losing its if I restart it with /etc/init.d/libvirtd restart. What I did was: Start libvirtd Connect to it using virsh Create a new storage pool with pool-create-as Create some volumes with vol-create-as Create some virtual machines with create Restart libvirtd using /etc/init.d/libvirtd restart Reconnect with virsh After

Hi everyone Ok this is really strange. I''ve been messing around with Xen for the past few weeks on a 32bit test machine and CentOS 5.4 and it''s been working fine. At the weekend I went into the office to install Xen on our server but I had a major problem. The server is a home-build with a Tyan s5211 motherboard with an Intel i3210w chipset CentOS 5.4 64bit installed and

We recently replaced a failing PDC, and it seems to be working just fine: # net rpc testjoin Join to 'OURDOMAIN' is OK # net lookup dc OURDOMAIN 172.16.1.40 But the BDC now seems to be having problems. We cannot get new workstations (in the subnet with the BDC) to join the domain, and while logged into the BDC, we get: # net rpc testjoin Unable to find a suitable server Join to

I am currently running Version 2.0.7 of Samba on a Solaris 8 server. Every time that we need to reboot the server, we find that in order to get Samba up and running again we need to have our domain admin remove our server from the domain, add the server back into the domain, and then we need to join the domain using smbpasswd. This doesn't sound right to me. Has anybody else seen this

I've samba 3.0.2 joined to a NT 4.0 domain as a domain member server. # net rpc join -U -UAdministrator%password Windows clients access it using winbind. If I upgrade all NT 4.0 servers to W2K3 AD, # net ads join -U Administrator%password do I need to rejoin the samba servers to AD? Will winbind continue to work? I think W2K3 by default uses kerberos. Will all uid.gid mapping be lost?

Hi guys and girls, I'm running Samba-3.0.4 as a PDC for about 40 workstations. It's been running perfectly for about 6 months. Suddenly in the last week two PCs have required that they be 'rejoined' to the domain. This seems to be happening every couple days or so. I've looked through the logs but can't find any clues about missing computer accounts etc. Any ideas why ?

Hi Everybody, Here in my company we have migrated from nt4 to Debian Sarge with Samba 3.0.14a + OpenLdap 2.2.23 + db4. Well, it's working fine except for one problem. When I have to get back to a backup copy on my ldap slaves on my BDCs some, or sometimes all, Windows XP machines need to be rejoined to the domain. I manage a workaround stopping Samba every time I need to reset the ldap

On Tue, 6 Dec 2016, Rodriguez Alban via samba wrote: > Hello, > > Samba 4.4.7 AD member on Linux SLES 12 here ... > > We've been running flawlessly for weeks with version 4.4.5 until we > updated to 4.4.6 and experienced this bug: > https://bugzilla.samba.org/show_bug.cgi?id=12369 So we updated to 4.4.7 > in which this issue was fixed with an interim downgrade to

On 4/2/2018 1:47 PM, Krzysztof Paszkowski via samba wrote: > Hi all, > > After demoting one of AD DCs, I’m unable to join the domain again. > Demoting was fine. > > OS is Centos 6 > Samba 4.7.6 (with 4.7.4 doesn’t work either) built from sources. > > > klist > Ticket cache: FILE:/tmp/krb5cc_0 > Default principal: administrator at DOMAIN.NET.PL > > Valid

On Tue, 3 Apr 2018 15:13:58 +0200 Krzysztof Paszkowski via samba <samba at lists.samba.org> wrote: > I've cleared all DNS records (indeed, they were still there). > I'm not sure if that was the issue, cause I've discovered that the > real problem is related to insufficient Administrator rights. Funny, if I had thought of that, I would have written something like: At

On Tue, 3 Apr 2018 17:36:35 +0200 Krzysztof Paszkowski via samba <samba at lists.samba.org> wrote: > I'm sorry, you're absolutely right. I'm not sure why I didn't follow > your hint. My fault. > > Now, it seems I have exactly the same output as you: > > [root at dc private]# net rpc rights list accounts -U Administrator > > BUILTIN\Administrators