similar to: CentOS-6 cannot get kvm guest to start - network error

I have been looking at this problem on and off for a considerable period. Given my lack of knowledge I have been unable to resolve this quickly and in consequence it has been constantly shoved to the background as other issues arise. Here is the situation: I have two dual-homed kvm hosts both running CentOS-6.7 and identically configured. These are connected to the same LAN segment via

Does anyone recognize this sort of message or have any idea what might cause it? May 28 11:00:06 inet09 setroubleshoot: [avc.ERROR] Plugin Exception catchall #012Traceback (most recent call last):#012 File "/usr/lib64/python2.6/site-packages/setroubleshoot/analyze.py", line 191, in analyze_avc#012 report = plugin.analyze(avc)#012 File

I did a yum update to my desktop machine as root this morning and now my regular logon account sees this whenever I press the enter key: etc/audisp/audispd.conf: Permission denied etc/audisp/plugins.d/af_unix.conf: Permission denied etc/audisp/plugins.d/syslog.conf: Permission denied etc/audit/audit.rules: Permission denied etc/audit/auditd.conf: Permission deniedetc/dhcp/dhclient.d/ntp.sh:

CentOS-6.2 We moved a cron job from a CentOS-5.7 host to a CentOS-6.2 host. The MAILTO variable is set to support at harte-lyne.ca in both instances. On the CentOS-6 host instead of receiving the mail with the output we see this in /var/log/cron instead: Mar 12 14:49:01 inet09 CROND[6639]: (cron theheart) UNSAFE (support at harte-lyne.ca ) The CentOS-5 host uses Sendmail as the MTA, the

I am experimenting with routing tables to obtain a little understanding of how things work. I have a kvm hypervisor host (KVM1) with two physical Ethernet nics configured as bridges (br0 and br1). KVM1 br0 is configured with a public ipv4 address [x.y.z.42/24] and br1 is configured with a private ipv4 address [192.168.216.42/24]. A second kvm hypervisor, KVM2, is similarly configured albeit with

I read this on the RHN commentary respecting cve-2014-3566: https://securityblog.redhat.com/2014/10/15/poodle-a-ssl3-vulnerability-cve-2014-3566/: . . . The first aspect of POODLE, the SSL 3.0 protocol vulnerability, has already been fixed through iterative protocol improvements, leading to the current TLS version, 1.2. It is simply not possible to address this in the context of the SSL 3.0

I am in the middle of a rather confusing situation. At the moment I am unable to shutdown a KVM guest machine. Nor am I presently able to open a virt-manager session on the host. I am not exactly sure what has happened but the problem with the vm guest is that issuing a "virsh shutdown 1" from the root console has no effect. # virsh list Id Name State

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

The vm host shows this: # setserial -g /dev/ttyS* /dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4 /dev/ttyS1, UART: 16950/954, Port: 0xd040, IRQ: 17 /dev/ttyS2, UART: 16950/954, Port: 0xd048, IRQ: 17 /dev/ttyS3, UART: 16950/954, Port: 0xd050, IRQ: 17 # # ll /dev/ttyS* crw-rw----. 1 root dialout 4, 64 Nov 10 12:18 /dev/ttyS0 crw-rw----. 1 root dialout 4, 65 Nov 10 12:18 /dev/ttyS1 crw-rw----. 1

Is it possible to use this exploit against a kvm guest to read memory used by the host? In other words: if an exploitable service, say httpd with mod_ssl, is running in guest system 'vm1' hosted on system 'virthost' then what implications does that have with respect to guests vm2 and vm3 and to virthost itself? -- *** E-Mail is NOT a SECURE channel *** James

Is it possible to use this exploit against a kvm guest to read memory used by the host? In other words: if an exploitable service, say httpd with mod_ssl, is running in guest system 'vm1' hosted on system 'virthost' then what implications does that have with respect to guests vm2 and vm3 and to virthost itself? -- *** E-Mail is NOT a SECURE channel *** James

On Mon, June 23, 2014 00:29, Arun Khan wrote: > On Thu, Feb 20, 2014 at 3:36 AM, Dusty Mabe <dustymabe at gmail.com> wrote: >> >> On 02/19/2014 04:01 PM, James B. Byrne wrote: The root cause of the original problem was a change in the behaviour of libvirt (and the GUI of virt-manager) when creating new vms. The host system was already bridged and had other vms previously

i86_64 CentOS-6.5 I have installed a Windows instance as a kvm guest on a host running CentOS-6.5. I can access the desktop through the virt-manager console and everythign seems to work, although the mouse cursor seems to get lost from time to time. The virt-manager console display supports various resolutions but when I re-size the desktop display remains essentially a square inside a letter

I am working with a cloned vm. In the process of (re-)adding an additional virtio disk I received a notice that the change could not be made to a running instance. Which was curious because I had shut that v down. Now I cannot get it to start from virt-manager, the run selection is greyed out. If I try and pause it from the graphical vm details interface then I get a message that the vm is not

On Tue, March 17, 2015 18:13, Dennis Jacobfeuerborn wrote: > > Have you tried restarting the libvirtd service? > > Regards, > Dennis > What does that do to the other running guest vm instances? -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB at Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca

I installed a new CentOS-6.3 kvm guest on a recently provisioned kvm host also running CentOS-6.3. This guest will not connect to the network and the host cannot connect to it via its public IP address. I had previously installed a guest system on thst same kvm host using the same ISO and that system connects to the network without problem. I next created a third guest isntance and this too does

I installed a new CentOS-6.3 kvm guest on a recently provisioned kvm host also running CentOS-6.3. This guest will not connect to the network and the host cannot connect to it via its public IP address. I had previously installed a guest system on thst same kvm host using the same ISO and that system connects to the network without problem. I next created a third guest isntance and this too does

I have a CentOS-6 guest VM configured on a CentOS-6 host. If I run virt-manager then I can start the guest VM but once it is running I cannot get a shutdown command to have effect. To shutdown the running guest I either must select Force Off from the Shut Down menu or open the guest console and issue shutdown from the command line. Is there some setting that is required to have Shut Down have

CentOS-6.5 i86_64 qemu-kvm-0.12.1.2-2.415.el6_5.4 MS-Windows v7proSP1 We have installed a MicroSoft Win7 system as a guest and have joined it to our MS AD domain. The system runs and has internet access. However, the IPv4 address it obtains and the gateway it is assigned are both sourced from the virtual machine host system and not from our AD DC DHCP server. To clarify, the virbr0 IP address

These are the messages that I get when trying to attach a virtio disk to or perform a shutdown of the problem vm guest. Add hardware This device could not be attached to the running machine. Would you like to make the device available after the next guest shutdown? Requested operation is not valid: cannot do live update a device on inactive domain Traceback (most recent call last): File