- Users - libvirt List Archives

[libvirt-users] libvirt-bin MOSTLY fails to create default virtual network
by m m 12 Jun '11

12 Jun '11

I have observed 3 scenarios after I reboot the host with 2 guests (which are supposed to autostart after boot/reboot of the host): 1. Default network is created but I can not ping guests. Gests don't have assigned IP address or they both have IP address 192.168.122.100. 2. Default network is not created. 3. Default netork is properly created and everything works fine. In each case guests are started and they work properly. Cases 1. and 2. happen a lot more often then case 3. My solutions: - When I restart libvirt-bin then everything is fine. - When I set 'sleep 40' in 'pre-start' section of /etc/init/libvirt-bin.conf and modify 'start on' section in the following way: start on (runlevel [2345] and net-device-up IFACE=br0) then everything works fine. However, none of the above solutions indeed solves the problem. Please, let me know if there is solution to this problem or what are your suggestions regarding this issue. **** HOST$ uname -a Linux ras 2.6.32-32-server #62-Ubuntu SMP Wed Apr 20 22:07:43 UTC 2011 x86_64 GNU/Linux GUEST1 and GUEST2 $ uname -a Linux server1-desktop 2.6.32-32-generic #62-Ubuntu SMP Wed Apr 20 21:54:21 UTC 2011 i686 GNU/Linux HOST$ libvirtd --version libvirtd (libvirt) 0.7.5 My idea was that some kernel modules sometimes are loaded before libvirt-bin starts, and sometimes libvirt-bin starts earlier, or in the middle of loading of these modules, that is why 3 scenarios can be observed. That is why I have added: cp /proc/modules /home/wsadmin2/modules1 cp /proc/modules /home/wsadmin2/modules2 to 'pre-start' and 'post-start' parts respectively of /etc/init/libvirt-bin.conf. Of course, beween execution of - pre-start part - exec /usr/sbin/libvirtd -d - post-start part other kernel modules can be loaded, so we can not be sure which additional modules in file 'modules2' were indeed loaded before libvirtd was actually started. Here are my observations: Scenatio 1. 33 (fixed) modules were logged - call them BASE MODULES. Scenatio 2. Beside BASE MODULES + the following modules were loaded: > iptable_filter 1841 0 - Live 0xffffffffa007c000 > ip_tables 18201 1 iptable_filter, Live 0xffffffffa0172000 > x_tables 22361 1 ip_tables, Live 0xffffffffa0164000 Scenatio 3. Beside BASE MODULES + the following modules were loaded: $ diff modules1 modules2 1c1,6 < iptable_filter 1841 0 - Live 0xffffffffa008b000 --- > xt_state 1490 14 - Live 0xffffffffa01ab000 > xt_tcpudp 2667 12 - Live 0xffffffffa01a5000 > nf_conntrack_ipv4 12742 14 - Live 0xffffffffa019b000 > nf_conntrack 73326 2 xt_state,nf_conntrack_ipv4, Live 0xffffffffa017d000 > nf_defrag_ipv4 1481 1 nf_conntrack_ipv4, Live 0xffffffffa0177000 > iptable_filter 1841 1 - Live 0xffffffffa008b000 3c8 < x_tables 22361 1 ip_tables, Live 0xffffffffa0162000 --- > x_tables 22361 3 xt_state,xt_tcpudp,ip_tables, Live 0xffffffffa0162000 Other observations: Scenatio 1. No errors in libvirtd.log Scenario 2. 10:06:06.980: error : networkAddIptablesRules:750 : failed to add iptables rule to allow DHCP requests from 'virbr0': Invalid argument (...) 10:06:08.630: error : qemudNetworkIfaceConnect:1445 : Failed to add tap interface to bridge 'virbr0': No such device 10:06:08.630: error : qemuAutostartDomain:584 : Failed to autostart VM 'cluster_server1': Failed to add tap interface to bridge 'virbr0': No such device 10:06:08.921: info : qemudDispatchSignalEvent:390 : Received unexpected signal 17 10:06:08.927: debug : virExecWithHook:617 : LC_ALL=C /usr/bin/kvm -help 10:06:08.938: info : qemudDispatchSignalEvent:390 : Received unexpected signal 17 10:06:09.000: error : qemudNetworkIfaceConnect:1445 : Failed to add tap interface to bridge 'virbr0': No such device 10:06:09.000: error : qemuAutostartDomain:584 : Failed to autostart VM 'cluster_server2': Failed to add tap interface to bridge 'virbr0': No such device (...) Scenatio 3. No errors in libvirtd.log I didn't see any valuable logs in /var/log/boot.log, /var/log/messages, /var/log/syslog. Please let me know if you want to see them anyway or have any suggestions right away.

2 1

[libvirt-users] e: How to disconnect the ISO image using virsh
by Jeff 10 Jun '11

10 Jun '11

I am trying to detach an ISO from a KVM machine and I've tried both attach-disk using " " in the file path as well as the update-device option but am getting this error error: Failed to update device from /var/run/libvirt/qemu/kvmtest1.xml error: XML description for unknown device type is not well formed or invalid. I tried doing a virsh edit on the xml file to remove the source file path to the ISO, as I assume is the correct method, and then running the virsh update-device but it's not working. Can anyone advise the correct steps to detach a device from a running and/or offline domain? Additionally - anyone have any guidance on how to attach a CD device to a domain that is currently shutdown, for example, if I wanted to boot the domain to a rescue CD image? Thanks Jeff 于 2011年03月31日 15:17, Masanari Iida 写道: Somebody sent me a tips. Following command do what I wanted to do. Thanks. attach-disk guest01 " " hdc --driver file --type cdrom --mode readonly Also using "update-device" with an xml which doesn't specify the source file path will work. On Thu, Mar 31, 2011 at 3:29 PM, Masanari Iida<standby24x7 gmail com> wrote: Hello, I can attach disc ISO image to cd-rom from virsh. And I can replace the ISO image from disc1 to disc2 using the 2nd example. (example) attach-disk guest01 /root/disc1.iso hdc --driver file --type cdrom --mode readonly attach-disk guest01 /root/disc2.iso hdc --driver file --type cdrom --mode readonly My question is, how can I disconnect the image from the cdrom drive using virsh. Because, if I try to detach-disk hdc, I got following errors. virsh # detach-disk guest01 hdc error: Failed to detach disk error: this function is not supported by the connection driver: This type of device cannot be hot unplugged What I can do is possible from virt-manager's "Disconnect" button, (next to source path: line) from Hardware's TAB, Disk hdc screen. I want to do this from virsh. OS: RHEL5.6 libvirt-0.8.2-15.el5_6.1 is used. Regards, Masanari Iida _______________________________________________ libvirt-users mailing list libvirt-users redhat com https://www.redhat.com/mailman/listinfo/libvirt-users

1 0

[libvirt-users] stuck after upgrade
by Julian Cerruti 10 Jun '11

10 Jun '11

Hi all, We're completely stuck helpless with our CentOS system which we've been using as a VM server. After an unanticipated system upgrade, we can't get virsh or virt-manager to connect to libvirt anymore. It gets completely stuck during startup, trying to connect. One of the suspicious things we've seen is the following: [root@ana libvirt]# netstat | grep /var/run/libvirt/libvirt-sock unix 3 [ ] STREAM CONNECTING 0 /var/run/libvirt/libvirt-sock unix 3 [ ] STREAM CONNECTING 0 /var/run/libvirt/libvirt-sock unix 3 [ ] STREAM CONNECTING 0 /var/run/libvirt/libvirt-sock unix 3 [ ] STREAM CONNECTING 0 /var/run/libvirt/libvirt-sock unix 3 [ ] STREAM CONNECTING 0 /var/run/libvirt/libvirt-sock .... I'm not adding more information here because there is so much we've tried that I wouldn't know where to start. I would be happy to provide any info that would be useful to solve this issue. Any hint or help would be greatly appreciated. Thanks! Julian

1 0

Re: [libvirt-users] libvirt-users Digest, Vol 18, Issue 11
by m m 10 Jun '11

10 Jun '11

I have attached all the logs (/var/log/dmesg, /var/log/libvirtd.log, /var/log/messages, /var/log/syslog, /var/log/boot.log and info about loaded modules /proc/modules) regarding scenatios1,2,3 (please see the README file for simple explanation what is there). By the way, I have installed only dnsmasq-bin (and not dnsmasq). Have a nice day 2011/6/8 <libvirt-users-request(a)redhat.com> > Send libvirt-users mailing list submissions to > libvirt-users(a)redhat.com > > To subscribe or unsubscribe via the World Wide Web, visit > https://www.redhat.com/mailman/listinfo/libvirt-users > or, via email, send a message with subject or body 'help' to > libvirt-users-request(a)redhat.com > > You can reach the person managing the list at > libvirt-users-owner(a)redhat.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of libvirt-users digest..." > > > Today's Topics: > > 1. Re: libvirt-users Digest, Vol 18, Issue 7(libvirt-bin MOSTLY > fails to create default virtual network) (m m) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 8 Jun 2011 08:28:19 -0500 > From: m m <bk.praca(a)gmail.com> > To: libvirt-users(a)redhat.com > Subject: Re: [libvirt-users] libvirt-users Digest, Vol 18, Issue > 7(libvirt-bin MOSTLY fails to create default virtual network) > Message-ID: <BANLkTikt49i78OJfzBgufoesv3C-Pjrdjw(a)mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > I have attached all the logs (/var/log/dmesg, /var/log/libvirtd.log, > /var/log/messages, /var/log/syslog, /var/log/boot.log and info about loaded > modules /proc/modules) regarding scenatios1,2,3 (please see the README file > for simple explanation what is there). By the way, I have installed only > dnsmasq-bin (and not dnsmasq). > Have a nice day > > 2011/6/6 <libvirt-users-request(a)redhat.com> > > > Send libvirt-users mailing list submissions to > > libvirt-users(a)redhat.com > > > > To subscribe or unsubscribe via the World Wide Web, visit > > https://www.redhat.com/mailman/listinfo/libvirt-users > > or, via email, send a message with subject or body 'help' to > > libvirt-users-request(a)redhat.com > > > > You can reach the person managing the list at > > libvirt-users-owner(a)redhat.com > > > > When replying, please edit your Subject line so it is more specific > > than "Re: Contents of libvirt-users digest..." > > > > > > Today's Topics: > > > > 1. libvirt-bin MOSTLY fails to create default virtual network (m > > m) > > > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Mon, 6 Jun 2011 14:24:04 -0500 > > From: m m <bk.praca(a)gmail.com> > > To: libvirt-users(a)redhat.com > > Subject: [libvirt-users] libvirt-bin MOSTLY fails to create default > > virtual network > > Message-ID: <BANLkTinrE80HURSwJUUv28_v9HB9mRxNNw(a)mail.gmail.com> > > Content-Type: text/plain; charset="iso-8859-1" > > > > I have observed 3 scenarios after I reboot the host with 2 guests (which > > are > > supposed to autostart after boot/reboot of the host): > > 1. Default network is created but I can not ping guests. Gests don't have > > assigned IP address or they both have IP address 192.168.122.100. > > 2. Default network is not created. > > 3. Default netork is properly created and everything works fine. > > In each case guests are started and they work properly. Cases 1. and 2. > > happen a lot more often then case 3. > > > > My solutions: > > - When I restart libvirt-bin then everything is fine. > > - When I set 'sleep 40' in 'pre-start' section of > > /etc/init/libvirt-bin.conf > > and modify 'start on' section in the following way: > > > > start on (runlevel [2345] and net-device-up IFACE=br0) > > > > then everything works fine. > > > > > > However, none of the above solutions indeed solves the problem. Please, > let > > me know if there is solution to this problem or what are your suggestions > > regarding this issue. > > > > **** > > HOST$ uname -a > > Linux ras 2.6.32-32-server #62-Ubuntu SMP Wed Apr 20 22:07:43 UTC 2011 > > x86_64 GNU/Linux > > > > GUEST1 and GUEST2 > > $ uname -a > > Linux server1-desktop 2.6.32-32-generic #62-Ubuntu SMP Wed Apr 20 > 21:54:21 > > UTC 2011 i686 GNU/Linux > > > > HOST$ libvirtd --version > > libvirtd (libvirt) 0.7.5 > > > > My idea was that some kernel modules sometimes are loaded before > > libvirt-bin > > starts, and sometimes libvirt-bin starts earlier, or in the middle of > > loading of these modules, that is why 3 scenarios can be observed. > > That is why I have added: > > cp /proc/modules /home/wsadmin2/modules1 > > cp /proc/modules /home/wsadmin2/modules2 > > to 'pre-start' and 'post-start' parts respectively of > > /etc/init/libvirt-bin.conf. > > > > Of course, beween execution of > > - pre-start part > > - exec /usr/sbin/libvirtd -d > > - post-start part > > other kernel modules can be loaded, so we can not be sure which > additional > > modules in file 'modules2' were indeed loaded before libvirtd was > actually > > started. > > > > Here are my observations: > > Scenatio 1. > > 33 (fixed) modules were logged - call them BASE MODULES. > > > > Scenatio 2. > > Beside BASE MODULES + the following modules were loaded: > > > > > iptable_filter 1841 0 - Live 0xffffffffa007c000 > > > ip_tables 18201 1 iptable_filter, Live 0xffffffffa0172000 > > > x_tables 22361 1 ip_tables, Live 0xffffffffa0164000 > > > > Scenatio 3. > > Beside BASE MODULES + the following modules were loaded: > > > > $ diff modules1 modules2 > > 1c1,6 > > < iptable_filter 1841 0 - Live 0xffffffffa008b000 > > --- > > > xt_state 1490 14 - Live 0xffffffffa01ab000 > > > xt_tcpudp 2667 12 - Live 0xffffffffa01a5000 > > > nf_conntrack_ipv4 12742 14 - Live 0xffffffffa019b000 > > > nf_conntrack 73326 2 xt_state,nf_conntrack_ipv4, Live > 0xffffffffa017d000 > > > nf_defrag_ipv4 1481 1 nf_conntrack_ipv4, Live 0xffffffffa0177000 > > > iptable_filter 1841 1 - Live 0xffffffffa008b000 > > 3c8 > > < x_tables 22361 1 ip_tables, Live 0xffffffffa0162000 > > --- > > > x_tables 22361 3 xt_state,xt_tcpudp,ip_tables, Live 0xffffffffa0162000 > > > > Other observations: > > Scenatio 1. > > No errors in libvirtd.log > > Scenario 2. > > > > 10:06:06.980: error : networkAddIptablesRules:750 : failed to add > iptables > > rule to allow DHCP requests from 'virbr0': Invalid argument > > (...) > > 10:06:08.630: error : qemudNetworkIfaceConnect:1445 : Failed to add tap > > interface to bridge 'virbr0': No such device > > 10:06:08.630: error : qemuAutostartDomain:584 : Failed to autostart VM > > 'cluster_server1': Failed to add tap interface to bridge 'virbr0': No > such > > device > > > > 10:06:08.921: info : qemudDispatchSignalEvent:390 : Received unexpected > > signal 17 > > 10:06:08.927: debug : virExecWithHook:617 : LC_ALL=C /usr/bin/kvm -help > > 10:06:08.938: info : qemudDispatchSignalEvent:390 : Received unexpected > > signal 17 > > 10:06:09.000: error : qemudNetworkIfaceConnect:1445 : Failed to add tap > > interface to bridge 'virbr0': No such device > > 10:06:09.000: error : qemuAutostartDomain:584 : Failed to autostart VM > > 'cluster_server2': Failed to add tap interface to bridge 'virbr0': No > such > > device > > (...) > > Scenatio 3. > > No errors in libvirtd.log > > > > > > I didn't see any valuable logs in /var/log/boot.log, /var/log/messages, > > /var/log/syslog. Please let me know if you want to see them anyway or > have > > any suggestions right away. > > -------------- next part -------------- > > An HTML attachment was scrubbed... > > URL: < > > > https://www.redhat.com/archives/libvirt-users/attachments/20110606/54a07ab3… > > > > > -------------- next part -------------- > > A non-text attachment was scrubbed... > > Name: scenario1 > > Type: application/octet-stream > > Size: 19317 bytes > > Desc: not available > > URL: < > > > https://www.redhat.com/archives/libvirt-users/attachments/20110606/54a07ab3… > > > > > -------------- next part -------------- > > A non-text attachment was scrubbed... > > Name: scenario2 > > Type: application/octet-stream > > Size: 8294 bytes > > Desc: not available > > URL: < > > > https://www.redhat.com/archives/libvirt-users/attachments/20110606/54a07ab3… > > > > > -------------- next part -------------- > > A non-text attachment was scrubbed... > > Name: scenario3 > > Type: application/octet-stream > > Size: 2366 bytes > > Desc: not available > > URL: < > > > https://www.redhat.com/archives/libvirt-users/attachments/20110606/54a07ab3… > > > > > -------------- next part -------------- > > A non-text attachment was scrubbed... > > Name: libvirt-bin.conf > > Type: application/octet-stream > > Size: 924 bytes > > Desc: not available > > URL: < > > > https://www.redhat.com/archives/libvirt-users/attachments/20110606/54a07ab3… > > > > > > > ------------------------------ > > > > _______________________________________________ > > libvirt-users mailing list > > libvirt-users(a)redhat.com > > https://www.redhat.com/mailman/listinfo/libvirt-users > > > > End of libvirt-users Digest, Vol 18, Issue 7 > > ******************************************** > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > https://www.redhat.com/archives/libvirt-users/attachments/20110608/625b332f… > > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: LucidClusterStack.rar > Type: application/rar > Size: 4473008 bytes > Desc: not available > URL: < > https://www.redhat.com/archives/libvirt-users/attachments/20110608/625b332f… > > > > ------------------------------ > > _______________________________________________ > libvirt-users mailing list > libvirt-users(a)redhat.com > https://www.redhat.com/mailman/listinfo/libvirt-users > > End of libvirt-users Digest, Vol 18, Issue 11 > ********************************************* >

2 1

Re: [libvirt-users] Resizing ext4 fedora qemu guest
by Richard W.M. Jones 10 Jun '11

10 Jun '11

Original message: https://www.redhat.com/archives/libvirt-users/2011-June/msg00017.html Best to post libguestfs and virt-tools questions on one of these two mailing lists: http://www.redhat.com/mailman/listinfo/libguestfs https://www.redhat.com/mailman/listinfo/virt-tools-list The answer is: yes, virt-resize understands ext4. I can't really say more since you don't say what virt-resize command line you are actually using. But if I were a gambling man, I'd say it's because you've forgotten: --lv-expand /dev/vg_custserv/lv_home (or whichever filesystem you want to resize). If that's not the problem, please post a full description of what you're trying to do, including the virt-resize command, the full output of the command, and the output of 'virt-filesystems --all --long' before and after the resize. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://et.redhat.com/~rjones/virt-df/

1 0

[libvirt-users] Shared Folders
by Guilherme Santos 09 Jun '11

09 Jun '11

Good afternoon. I am having trouble trying to set up shared folders in the guest VM using VirtualBox hypervisor. No matter what configuration is defined in my XML, it never works, I mean, no shared folder is added/specifyed, then, inside the guest, when I try to mount the folder, I always get a protocol error. If I use VirtualBoxManage, I can add/specify shared folders easily and mount it with no problem. I need to use libvirt in order to deal, in a generalized way, with the process of creating shared folders in all hypervisors supported by libvirt, otherwise my problem would be solved already. I must not use specific commands of a certain hypervisor (such as VirtualBoxManage's). How does libvirt allow me to set up shared folders? Does it use VirtualBoxManage for VBox hypervisors? If so, how do I use it? I've read the documentation and followed it in defining my XMLs. Thanks anyway! -- Guilherme Santos G. Baptista Undergraduate in Computer Science at UFCG LSD - Distributed Systems Laboratory

2 5

[libvirt-users] old, deleted LUN still showing up after a virsh pool-refresh
by Tom Georgoulias 09 Jun '11

09 Jun '11

Today I upgraded one of our KVM physical host servers to Centos 5.6. The other server remains on Centos 5.5. I've configured a storage pool in libvirt to use LUNs from an iscsi storage system as the volumes for each VM. After the upgrade, I decommisioned one of the VMs and removed the LUN from the storage system. Normally after this kind of operation, I simply need to run this command and the server will see that the LUN no longer exists and remove the volume. # virsh pool-refresh --pool=dev-kvm-storage Pool dev-kvm-storage refreshed This works fine on the centos 5.5 host, but the centos 5.6 still lists the old lun in the vol-list and displays zeros for the capacity. # virsh vol-info 7.0.0.26 --pool=dev-kvm-storage Name: 7.0.0.26 Type: block Capacity: 0.00 Allocation: 0.00 Do I need to do something different now for the newer version of libvirt that is included with centos 5.6? Here are the kernel and libvirt versions I'm using: Centos 5.6: kernel-2.6.18-238.9.1.el5 libvirt-0.8.2-15.el5_6.4 Centos 5.5: kernel-2.6.18-194.26.1.el5 libvirt-0.6.3-33.el5_5.3 Any help is greatly appreciated.

1 0

[libvirt-users] ANNOUNCE: oz 0.4.0 release
by Chris Lalancette 08 Jun '11

08 Jun '11

All, I'm pleased to announce release 0.4.0 of Oz. Oz is a program for doing automated installation of guest operating systems with limited input from the user. Release 0.4.0 is a bugfix and feature release for Oz. Some of the highlights between Oz 0.3.0 and 0.4.0 are: - Automatic detection/use of cached JEOS images (the previous method required the user of the oz libraries to detect whether the image was cached or not) - Fixes to make Debian installs work for both x86_64 and i386 - Honor user-provided automatic installation files better, by not doing modifications - Use pyparted to generate partitions on newly created disks (if necessary) - Add support for Fedora 15 - Add the ability to supply an initial root/Administrator password to the diskimage - Abort installs after 5 minutes of disk inactivity - Use M2Crypto to generate SSH keys (if necessary) - Some pydoc documentation (more of this to come in the future) - Support for Ubuntu 11.04 - Support for RHEL-6.1 More documentation on Oz (including links on how to obtain it) is available here: http://aeolusproject.org/oz.html For this release, Fedora 14 and RHEL-6 packages are available. Note that I have stopped providing Fedora 13 packages, since that distribution is (or will be) out of support. Also note that to install the RHEL-6 packages, you must be running RHEL-6.1 or later. If you have any questions or comments about Oz, please feel free to contact aeolus-devel(a)lists.fedorahosted.org or me (clalance(a)redhat.com) directly. Thanks, -- Chris Lalancette

1 0

Re: [libvirt-users] libvirt-users Digest, Vol 18, Issue 7(libvirt-bin MOSTLY fails to create default virtual network)
by m m 08 Jun '11

08 Jun '11

I have attached all the logs (/var/log/dmesg, /var/log/libvirtd.log, /var/log/messages, /var/log/syslog, /var/log/boot.log and info about loaded modules /proc/modules) regarding scenatios1,2,3 (please see the README file for simple explanation what is there). By the way, I have installed only dnsmasq-bin (and not dnsmasq). Have a nice day 2011/6/6 <libvirt-users-request(a)redhat.com> > Send libvirt-users mailing list submissions to > libvirt-users(a)redhat.com > > To subscribe or unsubscribe via the World Wide Web, visit > https://www.redhat.com/mailman/listinfo/libvirt-users > or, via email, send a message with subject or body 'help' to > libvirt-users-request(a)redhat.com > > You can reach the person managing the list at > libvirt-users-owner(a)redhat.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of libvirt-users digest..." > > > Today's Topics: > > 1. libvirt-bin MOSTLY fails to create default virtual network (m > m) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 6 Jun 2011 14:24:04 -0500 > From: m m <bk.praca(a)gmail.com> > To: libvirt-users(a)redhat.com > Subject: [libvirt-users] libvirt-bin MOSTLY fails to create default > virtual network > Message-ID: <BANLkTinrE80HURSwJUUv28_v9HB9mRxNNw(a)mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > I have observed 3 scenarios after I reboot the host with 2 guests (which > are > supposed to autostart after boot/reboot of the host): > 1. Default network is created but I can not ping guests. Gests don't have > assigned IP address or they both have IP address 192.168.122.100. > 2. Default network is not created. > 3. Default netork is properly created and everything works fine. > In each case guests are started and they work properly. Cases 1. and 2. > happen a lot more often then case 3. > > My solutions: > - When I restart libvirt-bin then everything is fine. > - When I set 'sleep 40' in 'pre-start' section of > /etc/init/libvirt-bin.conf > and modify 'start on' section in the following way: > > start on (runlevel [2345] and net-device-up IFACE=br0) > > then everything works fine. > > > However, none of the above solutions indeed solves the problem. Please, let > me know if there is solution to this problem or what are your suggestions > regarding this issue. > > **** > HOST$ uname -a > Linux ras 2.6.32-32-server #62-Ubuntu SMP Wed Apr 20 22:07:43 UTC 2011 > x86_64 GNU/Linux > > GUEST1 and GUEST2 > $ uname -a > Linux server1-desktop 2.6.32-32-generic #62-Ubuntu SMP Wed Apr 20 21:54:21 > UTC 2011 i686 GNU/Linux > > HOST$ libvirtd --version > libvirtd (libvirt) 0.7.5 > > My idea was that some kernel modules sometimes are loaded before > libvirt-bin > starts, and sometimes libvirt-bin starts earlier, or in the middle of > loading of these modules, that is why 3 scenarios can be observed. > That is why I have added: > cp /proc/modules /home/wsadmin2/modules1 > cp /proc/modules /home/wsadmin2/modules2 > to 'pre-start' and 'post-start' parts respectively of > /etc/init/libvirt-bin.conf. > > Of course, beween execution of > - pre-start part > - exec /usr/sbin/libvirtd -d > - post-start part > other kernel modules can be loaded, so we can not be sure which additional > modules in file 'modules2' were indeed loaded before libvirtd was actually > started. > > Here are my observations: > Scenatio 1. > 33 (fixed) modules were logged - call them BASE MODULES. > > Scenatio 2. > Beside BASE MODULES + the following modules were loaded: > > > iptable_filter 1841 0 - Live 0xffffffffa007c000 > > ip_tables 18201 1 iptable_filter, Live 0xffffffffa0172000 > > x_tables 22361 1 ip_tables, Live 0xffffffffa0164000 > > Scenatio 3. > Beside BASE MODULES + the following modules were loaded: > > $ diff modules1 modules2 > 1c1,6 > < iptable_filter 1841 0 - Live 0xffffffffa008b000 > --- > > xt_state 1490 14 - Live 0xffffffffa01ab000 > > xt_tcpudp 2667 12 - Live 0xffffffffa01a5000 > > nf_conntrack_ipv4 12742 14 - Live 0xffffffffa019b000 > > nf_conntrack 73326 2 xt_state,nf_conntrack_ipv4, Live 0xffffffffa017d000 > > nf_defrag_ipv4 1481 1 nf_conntrack_ipv4, Live 0xffffffffa0177000 > > iptable_filter 1841 1 - Live 0xffffffffa008b000 > 3c8 > < x_tables 22361 1 ip_tables, Live 0xffffffffa0162000 > --- > > x_tables 22361 3 xt_state,xt_tcpudp,ip_tables, Live 0xffffffffa0162000 > > Other observations: > Scenatio 1. > No errors in libvirtd.log > Scenario 2. > > 10:06:06.980: error : networkAddIptablesRules:750 : failed to add iptables > rule to allow DHCP requests from 'virbr0': Invalid argument > (...) > 10:06:08.630: error : qemudNetworkIfaceConnect:1445 : Failed to add tap > interface to bridge 'virbr0': No such device > 10:06:08.630: error : qemuAutostartDomain:584 : Failed to autostart VM > 'cluster_server1': Failed to add tap interface to bridge 'virbr0': No such > device > > 10:06:08.921: info : qemudDispatchSignalEvent:390 : Received unexpected > signal 17 > 10:06:08.927: debug : virExecWithHook:617 : LC_ALL=C /usr/bin/kvm -help > 10:06:08.938: info : qemudDispatchSignalEvent:390 : Received unexpected > signal 17 > 10:06:09.000: error : qemudNetworkIfaceConnect:1445 : Failed to add tap > interface to bridge 'virbr0': No such device > 10:06:09.000: error : qemuAutostartDomain:584 : Failed to autostart VM > 'cluster_server2': Failed to add tap interface to bridge 'virbr0': No such > device > (...) > Scenatio 3. > No errors in libvirtd.log > > > I didn't see any valuable logs in /var/log/boot.log, /var/log/messages, > /var/log/syslog. Please let me know if you want to see them anyway or have > any suggestions right away. > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > https://www.redhat.com/archives/libvirt-users/attachments/20110606/54a07ab3… > > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: scenario1 > Type: application/octet-stream > Size: 19317 bytes > Desc: not available > URL: < > https://www.redhat.com/archives/libvirt-users/attachments/20110606/54a07ab3… > > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: scenario2 > Type: application/octet-stream > Size: 8294 bytes > Desc: not available > URL: < > https://www.redhat.com/archives/libvirt-users/attachments/20110606/54a07ab3… > > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: scenario3 > Type: application/octet-stream > Size: 2366 bytes > Desc: not available > URL: < > https://www.redhat.com/archives/libvirt-users/attachments/20110606/54a07ab3… > > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: libvirt-bin.conf > Type: application/octet-stream > Size: 924 bytes > Desc: not available > URL: < > https://www.redhat.com/archives/libvirt-users/attachments/20110606/54a07ab3… > > > > ------------------------------ > > _______________________________________________ > libvirt-users mailing list > libvirt-users(a)redhat.com > https://www.redhat.com/mailman/listinfo/libvirt-users > > End of libvirt-users Digest, Vol 18, Issue 7 > ******************************************** >

1 0

[libvirt-users] Resizing ext4 fedora qemu guest
by Alex 08 Jun '11

08 Jun '11

Hi, I have a fedora14 host with a fedora15 guest and I'm trying to resize the /home partition from 200GB to 240GB. I'm relatively new to the virsh/guestfish commands, as well as LVM, although I think I have a reasonable understanding. I have followed the virt-resize directions (http://libguestfs.org/virt-resize.1.html) but it still shows 200GB: # fdisk -l /dev/mapper/vg_custserv-lv_home Disk /dev/mapper/vg_custserv-lv_home: 197.2 GB, 197165842432 bytes 255 heads, 63 sectors/track, 23970 cylinders, total 385089536 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Outside of the guest, I see this: # virt-filesystems --long --parts --lvs -h -a newdisk.img Name Type Size Parent /dev/vg_custserv/lv_home lv 184G /dev/vg_custserv /dev/vg_custserv/lv_root lv 50G /dev/vg_custserv /dev/vg_custserv/lv_swap lv 5.9G /dev/vg_custserv /dev/sda1 partition 500M /dev/sda /dev/sda2 partition 240G /dev/sda The partition is the correct size, but it appears the volume group(?) is not the correct size. fdisk from within the guest also shows the correct size for the device. I've tried resize2fs from within the guest. Does virt-resize understand the ext4 filesystem and how to properly resize it? Is that my problem? I've also tried using guestfish with lvresize-free without success: <fs> lvresize-free /dev/mapper/vg_custserv-lv_home 100 libguestfs: error: lvresize_free: New size (5876 extents) matches existing size (5876 extents) Run `lvresize --help' for more information. I'm really not sure what to do next. Any ideas greatly appreciated. Thanks, Alex

1 0