similar to: Unable to remove an lvm on CentOS-6

At the beginning of January I encountered a problem where several vm guests on a single host somehow managed to see the the virtual disks assigned to other guests on the same hosts. I was unable to resolve this situation and shutdown the affected guests after creating new guest instances and moving the services and data off the corrupted guests. I have since removed these guests via virt-manager

At the beginning of January I encountered a problem where several vm guests on a single host somehow managed to see the the virtual disks assigned to other guests on the same hosts. I was unable to resolve this situation and shutdown the affected guests after creating new guest instances and moving the services and data off the corrupted guests. I have since removed these guests via virt-manager

CentOS-6.2 I created a new VirtIO disk for one of my virtual machines. Previous experience has taught me that I need to partition it before attempting to add the new storage to the physical volume set of the intended guest. Up to now I have simply accepted the defaults given by fdisk after telling it that I want a new partition. The defaults always exclude the first 2048 sectors. Disk

On Mon, January 16, 2012 17:01, Dennis Jacobfeuerborn wrote: > On 01/16/2012 10:16 PM, James B. Byrne wrote: > > ... >> The xmldump for this guest instance contains this: > ... > > Please post the xmldumps of the original guest and cloned > guest right after > cloning and without any modifications. > > Regards, > Dennis Prototype dumpxml virsh # dumpxml

I have a KVM vm running CentOS-6.8 on a host also running CentOS-6.8. This instance is used for occasional development projects which require segregation. Thus it is seldom accessed. At some point in the recent past this guest developed an issue with starting. Specifically these messages were found in the system log files: /var/log/messages-20170312:Mar 10 16:31:06 vhost04 kernel: dracut:

I am investigating the procedure to follow when moving a KVM guest instance from one host to another where the guest uses LVM as its storage. As a preliminary cut I have cobbled the following together from various sources located through Google searches: 1. Log in to vmhost_old 2. Shutdown guest 3. Create an LVM snapshot of the guest volume 3.a. lvcreate -s -L 300m -n LVM_guest_snapshot

How, exactly, does CentOS-6.3 with udev recognize an USB modem when it is plugged in. How is it indicated? What other configuration is required? I can find the modem in /sys/class/tty and I can get the attributes using udevadm but I do not see anything in ps that refers to the modem device. -- *** E-Mail is NOT a SECURE channel *** James B. Byrne

CentOS-6.0 I created an lv (120 Gb) to hold the image of a KVM guest instance. I mounted this at /var/lib/libvirt/images/lv_guest01. When I do a df I see the lv is mounted at the desired location. When I run the virtual machine manager from the desktop I am given the option to install the image into the root directory tree or to browse for an alternative location. When I browse to the mount

On Wed, June 24, 2015 16:11, Chuck Campbell wrote: > > Is there an easy to follow "howto" for normal LVM administration > tasks. I get tired of googling every-time I have to do something > I don't remember how to do regarding LVM, so I usually just > don't bother with it at all. > > I believe it has some benefit for my use cases, but I've been >

I was creating some directories (mkdir xxxx) while cd'ed to a mounted LV. The first couple of directories were created but subsequent attempts give the following error: #mkdir: cannot create directory `xxxxx': Input/output error The contents of /var/log/messages shows this: Aug 5 10:48:57 inet05 kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } Aug 5 10:48:57

I am performing some configuration testing on a kvm host. When installing a guest operating system is it advisable to place each instance in a separate lv or better to accept the default and store them on the root file system? Respecting lvm, does one configure lvs in a virtual server to take space from the main vg or does one allocate lv space from inside that allocated to the virtual instance?

We are in the process of migrating several stand-alone server hosts onto a CentOS-6 kvm virtual host. We also use Webmin to administer our hosts. All of the guests, without exception, have been cloned brom a prototype guest using virt-manager. All of the additional VirtIO disks assigned to some of the guests have been added through virt-manager as well. Recently I have encountered a situation

We are in the process of migrating several stand-alone server hosts onto a CentOS-6 kvm virtual host. We also use Webmin to administer our hosts. All of the guests, without exception, have been cloned brom a prototype guest using virt-manager. All of the additional VirtIO disks assigned to some of the guests have been added through virt-manager as well. Recently I have encountered a situation

I changed the entries in smb4.conf (smb.conf) to this: [global] . . . dns update command = /usr/local/sbin/samba_dnsupdate nsupdate command = /usr/local/bin/samba-nsupdate -d -g And this is what results when I run: samba_dnsupdate --verbose -d8 --all-names . . . update(nsupdate): SRV _ldap._tcp.Default-First-Site-Name._sites.ForestDnsZones.brockley.harte-lyne.ca

I am testing DC administration using samba-4.10.15 on FreeBSD-12.1p6 and have run across this: [root at smb4-2 ~ (master)]# samba-tool domain join BROCKLEY.HARTE-LYNE.CA DC -U"BROCKLEY\administrator" INFO 2020-06-25 14:26:10,692 pid:47306 /usr/local/lib/python3.7/site-packages/samba/join.py #104: Finding a writeable DC for domain 'BROCKLEY.HARTE-LYNE.CA' INFO 2020-06-25

This is all the diagnostic information I can think of at the moment: [root at smb4-1 ~ (master)]# klist Credentials cache: FILE:/tmp/krb5cc_0 Principal: administrator at BROCKLEY.HARTE-LYNE.CA Issued Expires Principal Jul 2 10:35:11 2020 Jul 2 20:35:11 2020 krbtgt/BROCKLEY.HARTE-LYNE.CA at BROCKLEY.HARTE-LYNE.CA [root at smb4-1 ~ (master)]# grep nsup

> Could be because you added the wrong line to your smb4.conf (why does > freebsd call it smb4.conf ?), Why does freebsd put these things in /usr/local/etc/? Some questions have answers that are not worth the effort to know. > try: > nsupdate command = /usr/local/sbin/nsupdate -g I did catch that error earlier. But it makes no difference. samba_dnsupdate does not give any

Thank you for your patience. On Tue, June 30, 2020 16:48, Rowland penny wrote: > > From 'man smb.conf': > > nsupdate command (G) > > This option sets the path to the nsupdate command which is used for > GSS-TSIG dynamic DNS updates. > > Default: nsupdate command = /usr/bin/nsupdate -g > > dns update command (G) > > This

I have introduced some error in my dns resolution and I would like some help fixing it as I cannot seem to detect what I have done wrong. Briefly the setup is this: name servers: DNS01 - 216.185.71.33 DNS02 - 209.47.176.33 DNS03 - 216.185.71.34 DNS04 - 209.47.176.34 - offline DNS01 is a master DNS02-04 are slaves of 216.185.71.33 All are listed as authoritative for the zone test.com The

On 07/07/2020 20:00, James B. Byrne via samba wrote: > I have this on the DC smb4-1.brockley.harte-lyne.ca: > > samba-tool dns query localhost brockley.harte-lyne.ca brockley.harte-lyne.ca > ALL -U administrator > Password for [BROCKLEY\administrator]: > Name=, Records=6, Children=0 > SOA: serial=7, refresh=900, retry=600, expire=86400, minttl=3600, >