virt

virt@lists.centos.org

2 participants
1612 discussions

New Tutorial - RHCS + DRBD + KVM; 2-Node HA on EL6
by Digimer 19 Jun '12

19 Jun '12

Hi all, I'm happy to announce a new tutorial! https://alteeve.com/w/2-Node_Red_Hat_KVM_Cluster_Tutorial This tutorial walks a user through the entire process of building a 2-Node cluster for making KVM virtual machines highly available. It uses Red Hat Cluster services v3 and DRBD 8.3.12. It is written such that you can use entirely free or fully Red Hat supported environments. Highlights; * Full network and power redundancy; no single-points of failure. * All off-the-shelf hardware; Storage via DRBD. * Starts with base OS install, no clustering experience required. * All software components explained. * Includes all testing steps covered. * Configuration is used in production environments! This tutorial is totally free (no ads, no registration) and released under the Creative Common 3.0 Share-Alike Non-Commercial license. Feedback is always appreciated! -- Digimer E-Mail: digimer(a)alteeve.com Freenode handle: digimer Papers and Projects: http://alteeve.com Node Assassin: http://nodeassassin.org "omg my singularity battery is dead again. stupid hawking radiation." - epitron

8 13

Re: [CentOS-virt] Failing to start or create VM, cannot connect to hypervisor host
by Jeff Boyce 18 Jun '12

18 Jun '12

Responding to the daily digest again. Well, I finally pinpointed the problem and fixed it. But to answer you curiosity question, the host is running a hardware raid 5 (Dell T610 with a PERC H700). My problem was a result of a change made to my network configuration almost 2 weeks ago. When I brought the network backup, I just ifup'ed the em1 and br0 interfaces and everything was working. At least everything that was obvious at the time. In reality, I didn't have a loopback interface working, and I hadn't needed to look any any of my guests through VirtManager since then to notice the problem. As soon as I issued a service network restart to the host system, everything came back normal and I was able to connect to a console on my guest systems. It took hours of tracking down false leads from the log files, and learning how to interpret others before I got this pinpointed. I am now very thankful for keeping fairly detailed notes on all the changes to my system, as cross checking the logs against my notes helped my pinpoint the problem. Jeff > ------------------------------ > > Message: 2 > Date: Sun, 17 Jun 2012 11:19:41 -0700 > From: aurfalien <aurfalien(a)gmail.com> > Subject: Re: [CentOS-virt] Failing to start or create VM, cannot > connect to hypervisor host > To: Discussion about the virtualization on CentOS > <centos-virt(a)centos.org> > Message-ID: <B7DCC3C3-C847-4E18-B016-4FBA20F12815(a)gmail.com> > Content-Type: text/plain; charset=us-ascii > > Curious, is this system (the host) on a software raid? > > - aurf > On Jun 17, 2012, at 10:35 AM, jboyce(a)meridianenv.com wrote: > >> Sorry for the mess on the message threading; responding from the daily >> digest. >> >> Thanks for the suggestion. I'll research any option that may provide a >> lead to a solution right now. I have not tried to touch >> /etc/qemu/krb5.tab. After a little research on what this file is for, I >> don't see that it would help me since I have never set up the system to >> use kerberos. I don't even have an /etc/qemu directory on my host. I >> would suspect that part of the error is a side effect of something else >> that is the main cause. Please keep coming with the suggestions though. >> I am working on a plan B to make the data files available to the staff on >> Monday morning. >> >> Jeff >> >> >> >>> Message: 1 >>> Date: Sat, 16 Jun 2012 14:14:04 -0700 (PDT) >>> From: jboyce(a)meridianenv.com >>> Subject: [CentOS-virt] Failing to start or create VM, cannot connect >>> to hypervisor host To: centos-virt(a)centos.org >>> Message-ID: >>> <21752.184.157.241.237.1339881244.squirrel(a)www.meridianenv.com> >>> Content-Type: text/plain;charset=iso-8859-1 >>> >>> >>> Greetings - >>> >>> >>> I shutdown one of my Centos 6.2 VMs for some offline maintenance and am >>> now unable to get it to restart. I am also unable to create and start a >>> new VM. The host system is Centos 6.2, fully up to date. I have been >>> searching Google for two days and have not been successful in getting a >>> VM >>> to start. I have restarted libvirtd, but did not want to shutdown my >>> other >>> two running VMs and reboot my host system, unless I felt confident that >>> it >>> would solve the problem. The other two VMs on the box are still running >>> fine, but I am also unable to connect to a console in VirtManger with >>> them. I was able to connect to all these VM consoles from the host >>> system >>> just a week or so ago. The only changes that I had recently made to the >>> host system was to add some restrictions in my /etc/hosts.allow and >>> hosts.deny files and installed Fail2ban. I have reversed all of the >>> changes to my hosts.allow/deny files and have stopped the Fail2ban >>> service. Still unable to start or create a VM. I am at the end of my >>> rope here and am hoping someone will be able to direct me with where I >>> should be looking next. My error and log messages are listed below. >>> Thanks. >>> >>> >>> Jeff >>> >>> >>> >>> >>> >>> Trying to start the VM using VirtManager at the console of the host >>> results in the following error. >>> >>> error: Failed to start domain SequoiaVM >>> error: internal error process exited while connecting to monitor: char >>> device redirected to /dev/pts/7 inet_listen_opts: bind(ipv4, 127.0.0.1, >>> 5902) : Cannot assign requested >>> address inet_listen_opts: FAILED >>> >>> >>> >>> Each attempt at a restart results in the following set of messages in >>> /var/log/messages >>> >>> >>> Jun 16 13:45:04 earth kernel: device vnet2 entered promiscuous mode >>> Jun 16 13:45:04 earth kernel: br0: port 4(vnet2) entering learning state >>> Jun 16 13:45:04 earth qemu-kvm: Could not find keytab file: >>> /etc/qemu/krb5.tab: No such file or directory >>> Jun 16 13:45:04 earth kernel: br0: port 4(vnet2) entering disabled state >>> Jun 16 13:45:04 earth kernel: device vnet2 left promiscuous mode >>> Jun 16 13:45:04 earth kernel: br0: port 4(vnet2) entering disabled state >>> Jun 16 13:45:04 earth kernel: libfcoe_device_notification: >>> NETDEV_UNREGISTER vnet2 >>> >>> >>> >>> Log messages in /var/log/libvirt/libvirtd.log are similar to the console >>> >>> >>> 2012-06-16 19:56:39.807+0000: 32175: error : virNetSocketReadWire:911 : >>> End of file while reading data: Input/output error >>> 2012-06-16 20:15:23.672+0000: 32176: error : qemuMonitorOpenUnix:290 : >>> failed to connect to monitor socket: No such process 2012-06-16 >>> 20:15:23.672+0000: 32176: error : >>> qemuProcessWaitForMonitor:1289 : internal error process exited while >>> connecting to monitor: char device redirected to /dev/pts/7 >>> inet_listen_opts: bind(ipv4,127.0.0.1,5902): Cannot assign requested >>> address inet_listen_opts: FAILED >>> >>> >>> >>> Log messages in /var/log/libvirt/qemu/SequoiaVM.log are similar >>> >>> >>> 2012-06-16 13:45:04.572: starting up >>> LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none >>> /usr/libexec/qemu-kvm -S -M rhel6.2.0 -enable-kvm -m 2048 -smp >>> 4,sockets=4,cores=1,threads=1 -name SequoiaVM -uuid >>> 1ca3a14b-cd4b-f371-b3fe-1cd518480c09 -nodefconfig -nodefaults -chardev >>> socket,id=charmonitor,path=/var/lib/libvirt/qemu/SequoiaVM.monitor,server, >>> nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc >>> -no-shutdown -boot order=dc,menu=on -drive >>> file=/dev/vg_mei/lv_sequoiaroot,if=none,id=drive-virtio-disk0,format=raw,c >>> ache=none,aio=native -device >>> virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=vir >>> tio-disk0 -drive >>> file=/dev/vg_mei/lv_sequoiaswap,if=none,id=drive-virtio-disk1,format=raw,c >>> ache=none,aio=native -device >>> virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk1,id=vir >>> tio-disk1 -drive >>> file=/dev/vg_mei/lv_sequoiavar,if=none,id=drive-virtio-disk2,format=raw,ca >>> che=none,aio=native -device >>> virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk2,id=vir >>> tio-disk2 -drive >>> file=/dev/vg_mei/lv_sequoiahome,if=none,id=drive-virtio-disk3,format=raw,c >>> ache=none,aio=native -device >>> virtio-blk-pci,scsi=off,bus=pci.0,addr=0x8,drive=drive-virtio-disk3,id=vir >>> tio-disk3 -drive >>> file=/dev/vg_mei/lv_sequoiaecosystem,if=none,id=drive-virtio-disk4,format= >>> raw,cache=none,aio=native -device >>> virtio-blk-pci,scsi=off,bus=pci.0,addr=0x9,drive=drive-virtio-disk4,id=vir >>> tio-disk4 -drive >>> file=/dev/sr0,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw >>> -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 >>> -netdev tap,fd=28,id=hostnet0,vhost=on,vhostfd=29 -device >>> virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:9d:b2:49,bus=pci.0,add >>> r=0x3 -chardev pty,id=charserial0 -device >>> isa-serial,chardev=charserial0,id=serial0 -usb -device >>> usb-tablet,id=input0 >>> -vnc 127.0.0.1:2 -vga cirrus -device >>> intel-hda,id=sound0,bus=pci.0,addr=0x4 -device >>> hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device >>> virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0xa char device redirected >>> to /dev/pts/7 inet_listen_opts: bind(ipv4,127.0.0.1,5902): Cannot assign >>> requested address inet_listen_opts: FAILED >>> 2012-06-16 13:45:04.872: shutting down >>> >>> >>> >>> I attempted to create a new VM (TempSequoiaVM) via VirtManager which >>> also >>> failed to be created and started. These are the messages in >>> /var/log/libvirt/qemu/TempSequoiaVM.log >>> >>> >>> 2012-06-16 13:15:23.168: starting up >>> LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none >>> /usr/libexec/qemu-kvm -S -M rhel6.2.0 -enable-kvm -m 2048 -smp >>> 2,sockets=2,cores=1,threads=1 -name TempSequoiaVM -uuid >>> ef6c99c7-7fea-e24d-447c-cf98d6ffbec3 -nodefconfig -nodefaults -chardev >>> socket,id=charmonitor,path=/var/lib/libvirt/qemu/TempSequoiaVM.monitor,se >>> rver,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc >>> base=utc >>> -no-reboot >>> -no-shutdown -drive >>> file=/dev/vg_mei/lv_TempSequoia,if=none,id=drive-virtio-disk0,format=raw,c >>> ache=none,aio=native -device >>> virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=vir >>> tio-disk0,bootindex=2 -drive >>> file=/dev/sr0,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw >>> -device >>> ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1 >>> -netdev tap,fd=25,id=hostnet0,vhost=on,vhostfd=26 -device >>> virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:48:59:9e,bus=pci.0,add >>> r=0x3 -chardev pty,id=charserial0 -device >>> isa-serial,chardev=charserial0,id=serial0 -usb -device >>> usb-tablet,id=input0 >>> -vnc 127.0.0.1:2 -vga cirrus -device >>> intel-hda,id=sound0,bus=pci.0,addr=0x4 -device >>> hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device >>> virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 char device redirected >>> to /dev/pts/7 inet_listen_opts: bind(ipv4,127.0.0.1,5902): Cannot assign >>> requested address inet_listen_opts: FAILED >>> 2012-06-16 13:15:23.673: shutting down >>>

1 0

Re: [CentOS-virt] Failing to start or create VM, cannot connect to hypervisor host
by jboyce＠meridianenv.com 17 Jun '12

17 Jun '12

Sorry for the mess on the message threading; responding from the daily digest. Thanks for the suggestion. I'll research any option that may provide a lead to a solution right now. I have not tried to touch /etc/qemu/krb5.tab. After a little research on what this file is for, I don't see that it would help me since I have never set up the system to use kerberos. I don't even have an /etc/qemu directory on my host. I would suspect that part of the error is a side effect of something else that is the main cause. Please keep coming with the suggestions though. I am working on a plan B to make the data files available to the staff on Monday morning. Jeff > Message: 1 > Date: Sat, 16 Jun 2012 14:14:04 -0700 (PDT) > From: jboyce(a)meridianenv.com > Subject: [CentOS-virt] Failing to start or create VM, cannot connect > to hypervisor host To: centos-virt(a)centos.org > Message-ID: > <21752.184.157.241.237.1339881244.squirrel(a)www.meridianenv.com> > Content-Type: text/plain;charset=iso-8859-1 > > > Greetings - > > > I shutdown one of my Centos 6.2 VMs for some offline maintenance and am > now unable to get it to restart. I am also unable to create and start a > new VM. The host system is Centos 6.2, fully up to date. I have been > searching Google for two days and have not been successful in getting a > VM > to start. I have restarted libvirtd, but did not want to shutdown my other > two running VMs and reboot my host system, unless I felt confident that it > would solve the problem. The other two VMs on the box are still running > fine, but I am also unable to connect to a console in VirtManger with > them. I was able to connect to all these VM consoles from the host system > just a week or so ago. The only changes that I had recently made to the > host system was to add some restrictions in my /etc/hosts.allow and > hosts.deny files and installed Fail2ban. I have reversed all of the > changes to my hosts.allow/deny files and have stopped the Fail2ban > service. Still unable to start or create a VM. I am at the end of my > rope here and am hoping someone will be able to direct me with where I > should be looking next. My error and log messages are listed below. > Thanks. > > > Jeff > > > > > > Trying to start the VM using VirtManager at the console of the host > results in the following error. > > error: Failed to start domain SequoiaVM > error: internal error process exited while connecting to monitor: char > device redirected to /dev/pts/7 inet_listen_opts: bind(ipv4, 127.0.0.1, > 5902) : Cannot assign requested > address inet_listen_opts: FAILED > > > > Each attempt at a restart results in the following set of messages in > /var/log/messages > > > Jun 16 13:45:04 earth kernel: device vnet2 entered promiscuous mode > Jun 16 13:45:04 earth kernel: br0: port 4(vnet2) entering learning state > Jun 16 13:45:04 earth qemu-kvm: Could not find keytab file: > /etc/qemu/krb5.tab: No such file or directory > Jun 16 13:45:04 earth kernel: br0: port 4(vnet2) entering disabled state > Jun 16 13:45:04 earth kernel: device vnet2 left promiscuous mode > Jun 16 13:45:04 earth kernel: br0: port 4(vnet2) entering disabled state > Jun 16 13:45:04 earth kernel: libfcoe_device_notification: > NETDEV_UNREGISTER vnet2 > > > > Log messages in /var/log/libvirt/libvirtd.log are similar to the console > > > 2012-06-16 19:56:39.807+0000: 32175: error : virNetSocketReadWire:911 : > End of file while reading data: Input/output error > 2012-06-16 20:15:23.672+0000: 32176: error : qemuMonitorOpenUnix:290 : > failed to connect to monitor socket: No such process 2012-06-16 > 20:15:23.672+0000: 32176: error : > qemuProcessWaitForMonitor:1289 : internal error process exited while > connecting to monitor: char device redirected to /dev/pts/7 > inet_listen_opts: bind(ipv4,127.0.0.1,5902): Cannot assign requested > address inet_listen_opts: FAILED > > > > Log messages in /var/log/libvirt/qemu/SequoiaVM.log are similar > > > 2012-06-16 13:45:04.572: starting up > LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none > /usr/libexec/qemu-kvm -S -M rhel6.2.0 -enable-kvm -m 2048 -smp > 4,sockets=4,cores=1,threads=1 -name SequoiaVM -uuid > 1ca3a14b-cd4b-f371-b3fe-1cd518480c09 -nodefconfig -nodefaults -chardev > socket,id=charmonitor,path=/var/lib/libvirt/qemu/SequoiaVM.monitor,server, > nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc > -no-shutdown -boot order=dc,menu=on -drive > file=/dev/vg_mei/lv_sequoiaroot,if=none,id=drive-virtio-disk0,format=raw,c > ache=none,aio=native -device > virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=vir > tio-disk0 -drive > file=/dev/vg_mei/lv_sequoiaswap,if=none,id=drive-virtio-disk1,format=raw,c > ache=none,aio=native -device > virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk1,id=vir > tio-disk1 -drive > file=/dev/vg_mei/lv_sequoiavar,if=none,id=drive-virtio-disk2,format=raw,ca > che=none,aio=native -device > virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk2,id=vir > tio-disk2 -drive > file=/dev/vg_mei/lv_sequoiahome,if=none,id=drive-virtio-disk3,format=raw,c > ache=none,aio=native -device > virtio-blk-pci,scsi=off,bus=pci.0,addr=0x8,drive=drive-virtio-disk3,id=vir > tio-disk3 -drive > file=/dev/vg_mei/lv_sequoiaecosystem,if=none,id=drive-virtio-disk4,format= > raw,cache=none,aio=native -device > virtio-blk-pci,scsi=off,bus=pci.0,addr=0x9,drive=drive-virtio-disk4,id=vir > tio-disk4 -drive > file=/dev/sr0,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw > -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 > -netdev tap,fd=28,id=hostnet0,vhost=on,vhostfd=29 -device > virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:9d:b2:49,bus=pci.0,add > r=0x3 -chardev pty,id=charserial0 -device > isa-serial,chardev=charserial0,id=serial0 -usb -device usb-tablet,id=input0 > -vnc 127.0.0.1:2 -vga cirrus -device > intel-hda,id=sound0,bus=pci.0,addr=0x4 -device > hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device > virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0xa char device redirected > to /dev/pts/7 inet_listen_opts: bind(ipv4,127.0.0.1,5902): Cannot assign > requested address inet_listen_opts: FAILED > 2012-06-16 13:45:04.872: shutting down > > > > I attempted to create a new VM (TempSequoiaVM) via VirtManager which also > failed to be created and started. These are the messages in > /var/log/libvirt/qemu/TempSequoiaVM.log > > > 2012-06-16 13:15:23.168: starting up > LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none > /usr/libexec/qemu-kvm -S -M rhel6.2.0 -enable-kvm -m 2048 -smp > 2,sockets=2,cores=1,threads=1 -name TempSequoiaVM -uuid > ef6c99c7-7fea-e24d-447c-cf98d6ffbec3 -nodefconfig -nodefaults -chardev > socket,id=charmonitor,path=/var/lib/libvirt/qemu/TempSequoiaVM.monitor,se > rver,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc > -no-reboot > -no-shutdown -drive > file=/dev/vg_mei/lv_TempSequoia,if=none,id=drive-virtio-disk0,format=raw,c > ache=none,aio=native -device > virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=vir > tio-disk0,bootindex=2 -drive > file=/dev/sr0,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw > -device > ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1 > -netdev tap,fd=25,id=hostnet0,vhost=on,vhostfd=26 -device > virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:48:59:9e,bus=pci.0,add > r=0x3 -chardev pty,id=charserial0 -device > isa-serial,chardev=charserial0,id=serial0 -usb -device usb-tablet,id=input0 > -vnc 127.0.0.1:2 -vga cirrus -device > intel-hda,id=sound0,bus=pci.0,addr=0x4 -device > hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device > virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 char device redirected > to /dev/pts/7 inet_listen_opts: bind(ipv4,127.0.0.1,5902): Cannot assign > requested address inet_listen_opts: FAILED > 2012-06-16 13:15:23.673: shutting down > > > > > > > ------------------------------ > > > Message: 2 > Date: Sat, 16 Jun 2012 18:01:52 -0400 > From: Travis <corasian(a)gmail.com> > Subject: Re: [CentOS-virt] Failing to start or create VM, cannot > connect to hypervisor host To: Discussion about the virtualization on > CentOS > <centos-virt(a)centos.org> > Message-ID: > <CAKbLq_KcmO=72Qq3x=sDpMC21717tS=eumgqL_-LOoMP8-HC7A(a)mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > > A) Could be a perm issue for the krb5.tab file for the qemu system user. > > > B) Have you tried 'touch /etc/qemu/krb5.tab' if the file doesn't truly > exist?

2 1

Failing to start or create VM, cannot connect to hypervisor host
by jboyce＠meridianenv.com 17 Jun '12

17 Jun '12

Greetings - I shutdown one of my Centos 6.2 VMs for some offline maintenance and am now unable to get it to restart. I am also unable to create and start a new VM. The host system is Centos 6.2, fully up to date. I have been searching Google for two days and have not been successful in getting a VM to start. I have restarted libvirtd, but did not want to shutdown my other two running VMs and reboot my host system, unless I felt confident that it would solve the problem. The other two VMs on the box are still running fine, but I am also unable to connect to a console in VirtManger with them. I was able to connect to all these VM consoles from the host system just a week or so ago. The only changes that I had recently made to the host system was to add some restrictions in my /etc/hosts.allow and hosts.deny files and installed Fail2ban. I have reversed all of the changes to my hosts.allow/deny files and have stopped the Fail2ban service. Still unable to start or create a VM. I am at the end of my rope here and am hoping someone will be able to direct me with where I should be looking next. My error and log messages are listed below. Thanks. Jeff Trying to start the VM using VirtManager at the console of the host results in the following error. error: Failed to start domain SequoiaVM error: internal error process exited while connecting to monitor: char device redirected to /dev/pts/7 inet_listen_opts: bind(ipv4, 127.0.0.1, 5902) : Cannot assign requested address inet_listen_opts: FAILED Each attempt at a restart results in the following set of messages in /var/log/messages Jun 16 13:45:04 earth kernel: device vnet2 entered promiscuous mode Jun 16 13:45:04 earth kernel: br0: port 4(vnet2) entering learning state Jun 16 13:45:04 earth qemu-kvm: Could not find keytab file: /etc/qemu/krb5.tab: No such file or directory Jun 16 13:45:04 earth kernel: br0: port 4(vnet2) entering disabled state Jun 16 13:45:04 earth kernel: device vnet2 left promiscuous mode Jun 16 13:45:04 earth kernel: br0: port 4(vnet2) entering disabled state Jun 16 13:45:04 earth kernel: libfcoe_device_notification: NETDEV_UNREGISTER vnet2 Log messages in /var/log/libvirt/libvirtd.log are similar to the console 2012-06-16 19:56:39.807+0000: 32175: error : virNetSocketReadWire:911 : End of file while reading data: Input/output error 2012-06-16 20:15:23.672+0000: 32176: error : qemuMonitorOpenUnix:290 : failed to connect to monitor socket: No such process 2012-06-16 20:15:23.672+0000: 32176: error : qemuProcessWaitForMonitor:1289 : internal error process exited while connecting to monitor: char device redirected to /dev/pts/7 inet_listen_opts: bind(ipv4,127.0.0.1,5902): Cannot assign requested address inet_listen_opts: FAILED Log messages in /var/log/libvirt/qemu/SequoiaVM.log are similar 2012-06-16 13:45:04.572: starting up LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -S -M rhel6.2.0 -enable-kvm -m 2048 -smp 4,sockets=4,cores=1,threads=1 -name SequoiaVM -uuid 1ca3a14b-cd4b-f371-b3fe-1cd518480c09 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/SequoiaVM.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot order=dc,menu=on -drive file=/dev/vg_mei/lv_sequoiaroot,if=none,id=drive-virtio-disk0,format=raw,cache=none,aio=native -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0 -drive file=/dev/vg_mei/lv_sequoiaswap,if=none,id=drive-virtio-disk1,format=raw,cache=none,aio=native -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk1,id=virtio-disk1 -drive file=/dev/vg_mei/lv_sequoiavar,if=none,id=drive-virtio-disk2,format=raw,cache=none,aio=native -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk2,id=virtio-disk2 -drive file=/dev/vg_mei/lv_sequoiahome,if=none,id=drive-virtio-disk3,format=raw,cache=none,aio=native -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x8,drive=drive-virtio-disk3,id=virtio-disk3 -drive file=/dev/vg_mei/lv_sequoiaecosystem,if=none,id=drive-virtio-disk4,format=raw,cache=none,aio=native -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x9,drive=drive-virtio-disk4,id=virtio-disk4 -drive file=/dev/sr0,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=28,id=hostnet0,vhost=on,vhostfd=29 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:9d:b2:49,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -usb -device usb-tablet,id=input0 -vnc 127.0.0.1:2 -vga cirrus -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0xa char device redirected to /dev/pts/7 inet_listen_opts: bind(ipv4,127.0.0.1,5902): Cannot assign requested address inet_listen_opts: FAILED 2012-06-16 13:45:04.872: shutting down I attempted to create a new VM (TempSequoiaVM) via VirtManager which also failed to be created and started. These are the messages in /var/log/libvirt/qemu/TempSequoiaVM.log 2012-06-16 13:15:23.168: starting up LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -S -M rhel6.2.0 -enable-kvm -m 2048 -smp 2,sockets=2,cores=1,threads=1 -name TempSequoiaVM -uuid ef6c99c7-7fea-e24d-447c-cf98d6ffbec3 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/TempSequoiaVM.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-reboot -no-shutdown -drive file=/dev/vg_mei/lv_TempSequoia,if=none,id=drive-virtio-disk0,format=raw,cache=none,aio=native -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=2 -drive file=/dev/sr0,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1 -netdev tap,fd=25,id=hostnet0,vhost=on,vhostfd=26 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:48:59:9e,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -usb -device usb-tablet,id=input0 -vnc 127.0.0.1:2 -vga cirrus -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 char device redirected to /dev/pts/7 inet_listen_opts: bind(ipv4,127.0.0.1,5902): Cannot assign requested address inet_listen_opts: FAILED 2012-06-16 13:15:23.673: shutting down

3 2

Meaning of "vlan=" and "name=" in Linux KVM
by Arun Khan 12 Jun '12

12 Jun '12

Greetings KVM gurus, I am trying to understand a "use case" scenario for the "vlan=n" option and "name=name" for the "-net nic" and "-net tap" directives. I have done some search but I have not come up with anything that sheds any light on the above. <quote from kvm man> Network options: -net nic[,vlan=n][,macaddr=mac][,model=type] [,name=name][,addr=addr][,vectors=v] Create a new Network Interface Card and connect it to VLAN n (n = 0 is the default). The NIC is an e1000 by default on the PC target. Optionally, the MAC address can be changed to mac, the device address set to addr (PCI cards only), and a name can be assigned for use in monitor commands. Optionally, for PCI cards, you can specify the number v of MSI-X vectors that the card should have; this option currently only affects virtio cards; set v = 0 to disable MSI-X. If no -net option is specified, a single NIC is created. Qemu can emulate several different models of network card. Valid values for type are "virtio", "i82551", "i82557b", "i82559er", "ne2k_pci", "ne2k_isa", "pcnet", "rtl8139", "e1000", "smc91c111", "lance" and "mcf_fec". Not all devices are supported on all targets. -net tap[,vlan=n][,name=name][,fd=h][,ifname=name] [,script=file][,downscript=dfile] Connect the host TAP network interface name to VLAN n, use the network script file to configure it and the network script dfile to deconfigure it. If name is not provided, the OS automatically provides one. fd=h can be used to specify the handle of an already opened host TAP interface. The default network configure script is /etc/qemu-ifup and the default network deconfigure script is /etc/qemu-ifdown. Use script=no or downscript=no to disable script execution. </quote from kvm man> My objective is to create a small "virtual" network using bridges/tap interfaces on the Host OS and running the Guest OSs (the network segment separated by vlan=somenumber) My hypothesis is that with "vlan=X" and "name=somename" the VMs can be separated into different segments i.e. a set of tap interfaces on vlan=10 and another set of tap interfaces on vlan=20 connected to the same bridge br0. I have two VMs started with "kvm -net tap,vlan=10" and "kvm -net tap,vlan=20" respectively but with IP numbers in the same subnet 172.16.0.0/24; they are able to ping each other with different "vlan" numbers. I would appreciate any clarification on the "vlan=" and "name=" options. Sample script for my KVM VMs <script> #!/bin/bash kvm \ -vga std \ -m 1024 \ -cpu core2duo \ -smp 2,cores=2 \ -drive file=/home/kvmusr/KVM/vdisks/centos62.img,index=0 \ -net nic,vlan=1,model=e1000,macaddr=${nic_mac_addr0} \ -net tap,vlan=1,ifname=tap0,script=no,downscript=no \ </script> Thanks, -- Arun Khan

1 0

100% load on core after physically removing USB storage from host
by Emmanuel Noobadmin 12 Jun '12

12 Jun '12

I encountered a problem after removing a USB flash drive using virtual machine manager, I notice that the core assigned to the VM guest goes up to 100% load. Within the guest itself, there is no significant activity. This also prompted me to look at the other physical machine from which I used the USB flash drive to transfer files. And it was also exhibiting the same problem. Installed versions are qemu-kvm-0.12.1.2-2.209.el6_2.5.x86_64 on CentOS 6.2, 2.6.32-220.17.1.el6.x86_64 (Intel C204 PCH) There are no error messages in the log files and things seem to be working except for the fully loaded core. After some testing, the only steps needed are 1. VMM add physical host usb device -> select storage to guest 2. VMM remove hardware 3. Physically remove the USB storage from the host, thread/core assigned to guest goes 100% Repeating the same steps without restarting the guest causes cpu utilization to drop back to normal for about a second or so before going back up again. Problem goes away if I restart the guest. There don't seem to be anything related on RHEL bugtrack except one related to hotplug/unplugging a USB controller more than 1000 times. Is this is a bug or there is actually something else I am supposed to do before removing a physical device from a guest? Also is there anyway I get the core/thread back to normal without restarting the guest?

1 0

SR-IOV with Broadcom NIC??
by David Knierim 06 Jun '12

06 Jun '12

Hi, We recently purchased some HP Gen8 servers with Broadcom BCM57810 NIC controllers. I am running CentOS 6.2 on these servers configured as KVM hosts. Has anyone gotten the Broadcom chips to run with SR-IOV on CentOS 6.2? Any clues on how to get it working? I see from the Broadcom glossy marketing docs that this chip supports SR-IOV, but I cannot find a procedure for configuring it. The Red Hat docs show how to configure the Intel chips and the Emulex web site includes a procedure to configure SR-IOV with their chips. In both procedures, there are vendor-specific steps. It is also pretty obvious that appropriate drivers and firmware are required, which I do not know if I have. Any input would be most welcome. Thanks, David

1 0

Where should CentOS users get /usr/share/virtio-win/drivers for virt-v2v?
by Philip Durbin 04 Jun '12

04 Jun '12

I need to migrate a number of virtual machines from VMware ESX to CentOS 6 KVM hypervisors. Ultimately, I wrote an RPM spec file that solved my problem at https://github.com/fasrc/virtio-win/blob/master/virtio-win.spec but I'm not sure if there's another RPM in base CentOS or EPEL (something standard) I should be using instead. Originally, I was getting this "No root device found in this operating system image" error when attemting to migrate a Window 2008 VM. . . [root@kvm01b ~]# virt-v2v -ic 'esx://my-vmware-hypervisor.example.com/' \ -os transferimages --network default my-vm virt-v2v: No root device found in this operating system image. . . . but I solved this with a simply `yum install libguestfs-winsupport` since [the docs][v2v-guide] say: > If you attempt to convert a virtual machine using NTFS without the > libguestfs-winsupport package installed, the conversion will fail. Next I got an error about missing drivers for Windows 2008. . . [root@kvm01b ~]# virt-v2v -ic 'esx://my-vmware-hypervisor.example.com/' \ -os transferimages --network default my-vm my-vm_my-vm: 100% [====================================]D virt-v2v: Installation failed because the following files referenced in the configuration file are required, but missing: /usr/share/virtio-win/drivers/amd64/Win2008 . . . and I resolved this by grabbing an iso from Fedora at http://alt.fedoraproject.org/pub/alt/virtio-win/latest/ as recommended by http://www.linux-kvm.org/page/WindowsGuestDrivers/Download_Drivers and building an RPM from it with this spec file: https://github.com/fasrc/virtio-win/blob/master/virtio-win.spec Now, virt-v2v exits without error: [root@kvm01b ~]# virt-v2v -ic 'esx://my-vmware-hypervisor.example.com/' \ -os transferimages --network default my-vm my-vm_my-vm: 100% [====================================]D virt-v2v: my-vm configured with virtio drivers. [root@kvm01b ~]# Now, my question is, rather that the [virtio-win RPM from the spec file I wrote](https://github.com/fasrc/virtio-win/blob/master/virtio-win.spec), is there some other more standard RPM in base CentOS or EPEL that will resolve the error above? Here's a bit more detail about my setup: [root@kvm01b ~]# cat /etc/redhat-release CentOS release 6.2 (Final) [root@kvm01b ~]# rpm -q virt-v2v virt-v2v-0.8.3-5.el6.x86_64 See also [Bug 605334 – VirtIO driver for windows does not show specific OS: Windows 7, Windows 2003](https://bugzilla.redhat.com/show_bug.cgi?id=605334) [v2v-guide]: http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/V2V_Guide… Thanks, Phil p.s. I also posted this on Server Fault. If you prefer to answer there, I would be happy to summarize the answers and report back to the list: http://serverfault.com/questions/395347/where-should-centos-users-get-usr-s…

1 0

shut down a Centos 6 guest / libvirt / ACPI
by Michael Kress 03 Jun '12

03 Jun '12

Hi, shutting down a Centos6 kvm guest does not work from outside doing a 'virsh shutdown vmguest', I've installed the CentOS-6.2-x86_64-minimal.iso inside the kvm guest I reckon this is related to acpi ... # dmesg | grep ACPI ACPI Error: A valid RSDP was not found (20090903/tbxfroot-219) ACPI: Interpreter disabled. pnp: PnP ACPI: disabled acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 /proc/acpi/event does not exist # /usr/sbin/acpid acpid: can't open /proc/acpi/event: No such file or directory # grep ACPI /boot/config-`uname -r` CONFIG_X86_64_ACPI_NUMA=y # Power management and ACPI options CONFIG_ACPI=y CONFIG_ACPI_SLEEP=y CONFIG_ACPI_PROCFS=y CONFIG_ACPI_PROCFS_POWER=y CONFIG_ACPI_POWER_METER=m CONFIG_ACPI_SYSFS_POWER=y CONFIG_ACPI_PROC_EVENT=y CONFIG_ACPI_AC=y CONFIG_ACPI_BATTERY=y CONFIG_ACPI_BUTTON=y CONFIG_ACPI_VIDEO=m CONFIG_ACPI_FAN=y CONFIG_ACPI_DOCK=y CONFIG_ACPI_PROCESSOR=y CONFIG_ACPI_HOTPLUG_CPU=y CONFIG_ACPI_PROCESSOR_AGGREGATOR=m CONFIG_ACPI_THERMAL=y CONFIG_ACPI_NUMA=y # CONFIG_ACPI_CUSTOM_DSDT is not set CONFIG_ACPI_BLACKLIST_YEAR=0 # CONFIG_ACPI_DEBUG is not set CONFIG_ACPI_PCI_SLOT=y CONFIG_ACPI_CONTAINER=y CONFIG_ACPI_HOTPLUG_MEMORY=y CONFIG_ACPI_HOTPLUG_MEMORY_AUTO_ONLINE=y CONFIG_ACPI_SBS=m CONFIG_ACPI_HED=y CONFIG_ACPI_APEI=y CONFIG_ACPI_APEI_GHES=y CONFIG_ACPI_APEI_PCIEAER=y CONFIG_ACPI_APEI_EINJ=m CONFIG_ACPI_APEI_ERST_DEBUG=m CONFIG_X86_ACPI_CPUFREQ=m CONFIG_HOTPLUG_PCI_ACPI=y CONFIG_HOTPLUG_PCI_ACPI_IBM=m CONFIG_PNPACPI=y CONFIG_ATA_ACPI=y CONFIG_PATA_ACPI=m # ACPI drivers # ACPI drivers CONFIG_THINKPAD_ACPI=m # CONFIG_THINKPAD_ACPI_DEBUGFACILITIES is not set # CONFIG_THINKPAD_ACPI_DEBUG is not set # CONFIG_THINKPAD_ACPI_UNSAFE_LEDS is not set CONFIG_THINKPAD_ACPI_VIDEO=y CONFIG_THINKPAD_ACPI_HOTKEY_POLL=y CONFIG_ACPI_WMI=m # CONFIG_ACPI_ASUS is not set CONFIG_ACPI_TOSHIBA=m Any suggestions? Thanks in advance Regards Michael -- Michael Kress, kress(a)hal.saar.de http://www.michael-kress.de / http://kress.net P E N G U I N S A R E C O O L

3 5

Eucalyptus 2.0.3 on CentOS - VM auto fail-over?
by Rafał Radecki 16 May '12

16 May '12

Hi all. I am currently testing Eucalyptus. I have two servers, one of them has CLC, Walrus, CC and NC, the second only NC. When I make a new Xen VM (from kernel, initrd, filesystem image) then it is placed on one of the nodes with NC. I would like to test VM fail-over. When on one node the VM is not running good it should be transferred to the second node as I think. Do I need EBS for that? How should eucalyptus be configured? Any howtos? I have found only basic ones with installation and starting of VM instances. Best regards, Rafal Radecki.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt