- Users - libvirt List Archives

[libvirt-users] libvirt -- add virtio-scsi disk with scsi-generic
by 韩诚 25 Jan '13

25 Jan '13

Hi, Paolo, All, I read "virtio-scsi support proposal v2"(http://permalink.gmane.org/gmane.comp.emulators.libvirt/50428) Try to add a virtio-scsi with scsi-generic like this: <hostdev type='scsi'> <source> <adapter name='scsi_host0'/> <address type='scsi' bus='0' target='0' unit='0'/> </source> <target> <address type='scsi' controller='0' bus='0' target='0' unit='2'/> </target> </hostdev> But It turn out to be wrong, showing: error: Failed to define domain from rhel63ga error: XML error: unknown host device source address type 'scsi_host' I'd like to know how shall to add a virtio-scsi disk with scsi-generic option. Thanks~ -- Best regards, Cheng

3 4

[libvirt-users] virtual machine id
by 春祥王 23 Jan '13

23 Jan '13

Below is my start.xml: <domain type='kvm' id='12'> <name>start-ubuntu</name> <memory>1048576</memory> <currentMemory>1048576</currentMemory> <vcpu>1</vcpu> <os> <type>hvm</type> <boot dev='hd'/> ...... I start the machine virsh create start.xml virsh list Id Name State ---------------------------------------------------- 20 start-ubuntu running I set id=12,but it is actually 20,I don't know why. Thanks.

2 1

Re: [libvirt-users] snapshot troubles
by Christian Schmidt 23 Jan '13

23 Jan '13

Hi Juergen, if you are using kvm/qemu with libvirt you can try to delete the snapshot with the qemu monitor commands. The general syntax is virsh qemu-monitor-command --hmp <domain> '<command> [...]' So you can try virsh qemu-monitor-command --hmp DOMINO1-prealloc 'info snapshots' and thne delete it with the provided snapshot ID virsh qemu-monitor-command --hmp DOMINO1-prealloc 'delvm <ID>' This will delete the snapshot from your diskimage. Christian. On Di, 2013-01-22 at 18:00, libvirt-users-request(a)redhat.com wrote: > Message: 3 > Date: Mon, 21 Jan 2013 23:43:57 +0100 > From: jurgen.depicker(a)let.be > To: libvirt-users <libvirt-users(a)redhat.com> > Subject: [libvirt-users] snapshot troubles > Message-ID: > <OF4AE792B7.46B8D599-ONC1257AFA.0073C652-C1257AFA.007D0C38(a)let.be> > Content-Type: text/plain; charset="us-ascii" > > Dear all, > I created some snapshots, a long time ago, using the xml description > option, so the snapshots have a name with a space in it... > Really a bad choice apparently, since it seems impossible to delete > them > now: I cannot find how to enter the snapshot name properly due to the > space. Quotes don't seem to help; escaping the space doesn't help > either. > Anybody knows how to solve this? > eg: > snapshot-delete DOMINO1-prealloc --snapshotname 'W2K3-virgin install' > error: Domain snapshot not found: no snapshot with matching name > ''W2K3-virgin' > (-> notive also the extra ' added ) > > root@VLET3:~# time virsh snapshot-delete DOMINO1-prealloc > "W2K3-virgin\ > install" > error: unexpected data 'install' > > Thanks, Juergen >

3 2

[libvirt-users] snapshot troubles
by jurgen.depicker＠let.be 23 Jan '13

23 Jan '13

Dear all, I created some snapshots, a long time ago, using the xml description option, so the snapshots have a name with a space in it... Really a bad choice apparently, since it seems impossible to delete them now: I cannot find how to enter the snapshot name properly due to the space. Quotes don't seem to help; escaping the space doesn't help either. Anybody knows how to solve this? eg: snapshot-delete DOMINO1-prealloc --snapshotname 'W2K3-virgin install' error: Domain snapshot not found: no snapshot with matching name ''W2K3-virgin' (-> notive also the extra ' added ) root@VLET3:~# time virsh snapshot-delete DOMINO1-prealloc "W2K3-virgin\ install" error: unexpected data 'install' Thanks, Juergen

2 4

[libvirt-users] Fwd: problem with libvirt
by rakshith h p 23 Jan '13

23 Jan '13

HI, i'm rakshith from bangalore. I'm using libvirt in one of my work. I have a problem in using it.So i would request your guidance. I have a controller which uses libvirt to establish the connection to the managed nodes. After the connection is successful, if the network goes down, the control will indefinitely wait inside the libvirt mod functions. It will come out only after the network is back and required data is obtained. In this case i need to add time out and get the control back once the data is not available and throw an exception. Can u please tell if there is any way i can do it.Thanks in advance -- Thanks and regards Rakshith H P Mobile - +919844303929

1 0

[libvirt-users] Fwd problem with libvirt
by rakshith h p 23 Jan '13

23 Jan '13

---------- Forwarded message ---------- From: "rakshith h p" <hpr3929(a)gmail.com> Date: 22 Jan 2013 22:10 Subject: problem with libvirt To: <berrange(a)redhat.com> Cc: HI, i'm rakshith from bangalore. I'm using libvirt in one of my work. I have a problem in using it.So i would request your guidance. I have a controller which uses libvirt to establish the connection to the managed nodes. After the connection is successful, if the network goes down, the control will indefinitely wait inside the libvirt mod functions. It will come out only after the network is back and required data is obtained. In this case i need to add time out and get the control back once the data is not available and throw an exception. Can u please tell if there is any way i can do it.Thanks in advance -- Thanks and regards Rakshith H P Mobile - +919844303929

1 0

[libvirt-users] Question about blkiotune.device_weight
by hzguanqiang 22 Jan '13

22 Jan '13

Hi, Hu Tao I noticed that in your patch about blkiotune.device_weight, You set the device blkio weight value between 100 and 1000. But from the kernel document, I see that the blkio weight can be set from 10 to 1000. Why do you limit the weight minimum to 100 rather than 10 ? Looking forward your explanation, thanks! -------------- Best regards! GuanQiang 2013-01-18

3 2

[libvirt-users] error on startup
by Bryan D. Payne 22 Jan '13

22 Jan '13

I'm running libvirt 1.0.1 and qemu 1.3. I see the following error of libvirtd startup: 2013-01-19 04:51:06.183+0000: 1459: error : virCommandWait:2287 : internal error Child process (LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin HOME=/ /usr/bin/kvm -help) unexpected exit status 1 This is indeed what the return code seems to be for that command. This this just a version issue with libvirt and qemu or ?? root@host:~# kvm -help usage: qemu-x86_64 [options] program [arguments...] Linux CPU emulator (compiled for x86_64 emulation) Options and associated environment variables: Argument Env-variable Description -h print this help -g port QEMU_GDB wait gdb connection to 'port' -L path QEMU_LD_PREFIX set the elf interpreter prefix to 'path' -s size QEMU_STACK_SIZE set the stack size to 'size' bytes -cpu model QEMU_CPU select CPU (-cpu help for list) -E var=value QEMU_SET_ENV sets targets environment variable (see below) -U var QEMU_UNSET_ENV unsets targets environment variable (see below) -0 argv0 QEMU_ARGV0 forces target process argv[0] to be 'argv0' -r uname QEMU_UNAME set qemu uname release string to 'uname' -B address QEMU_GUEST_BASE set guest_base address to 'address' -R size QEMU_RESERVED_VA reserve 'size' bytes for guest virtual address space -d options QEMU_LOG activate log -D logfile QEMU_LOG_FILENAME override default logfile location -p pagesize QEMU_PAGESIZE set the host page size to 'pagesize' -singlestep QEMU_SINGLESTEP run in singlestep mode -strace QEMU_STRACE log system calls -version QEMU_VERSION display version information and exit Defaults: QEMU_LD_PREFIX = /usr/gnemul/qemu-x86_64 QEMU_STACK_SIZE = 8388608 byte QEMU_LOG = /tmp/qemu.log You can use -E and -U options or the QEMU_SET_ENV and QEMU_UNSET_ENV environment variables to set and unset environment variables for the target process. It is possible to provide several variables by separating them by commas in getsubopt(3) style. Additionally it is possible to provide the -E and -U options multiple times. The following lines are equivalent: -E var1=val2 -E var2=val2 -U LD_PRELOAD -U LD_DEBUG -E var1=val2,var2=val2 -U LD_PRELOAD,LD_DEBUG QEMU_SET_ENV=var1=val2,var2=val2 QEMU_UNSET_ENV=LD_PRELOAD,LD_DEBUG Note that if you provide several changes to a single variable the last change will stay in effect. root@host:~# echo $? 1 Thanks, -bryan

2 2

[libvirt-users] Cannot get eth0 to work on libvirt-lxc
by Marco Monteiro 19 Jan '13

19 Jan '13

I'm trying to get an Archlinux guest running on a Archlinux host. Everything works except ethernet. When I boot the host, --- # dmesg |tail [ 8.265493] Bridge firewalling registered [ 8.514547] IPv6: ADDRCONF(NETDEV_UP): virbr0: link is not ready [ 8.645303] ip6_tables: (C) 2000-2006 Netfilter Core Team --- Then I do --- # virsh -c lxc:/// start gitolite Domain gitolite started # dmesg |tail [ 348.793398] device veth0 entered promiscuous mode [ 348.793553] IPv6: ADDRCONF(NETDEV_UP): veth0: link is not ready [ 348.997973] IPv6: ADDRCONF(NETDEV_CHANGE): veth0: link becomes ready [ 348.997998] virbr0: topology change detected, propagating [ 348.998001] virbr0: port 1(veth0) entered forwarding state [ 348.998008] virbr0: port 1(veth0) entered forwarding state [ 348.998017] IPv6: ADDRCONF(NETDEV_CHANGE): virbr0: link becomes ready [ 349.784174] EXT4-fs (xvdg): re-mounted. Opts: (null) --- Then I enter the guest and do --- # ip link 5: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT qlen 1000 link/ether 02:00:00:00:00:17 brd ff:ff:ff:ff:ff:ff 7: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN mode DEFAULT link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 --- So, eth0 exists. Now, still in the guest: --- # systemctl start dhcpcd@eth0 A dependency job for dhcpcd(a)eth0.service failed. See 'journalctl -xn' for details. # journalctl -xn -- Logs begin at Sat 2013-01-19 10:50:45 UTC, end at Sat 2013-01-19 10:56:26 UTC Jan 19 10:54:48 gitolite sudo[38]: pam_unix(sudo:session): session opened for us Jan 19 10:54:48 gitolite systemd[1]: Expecting device sys-subsystem-net-devices- -- Subject: Unit sys-subsystem-net-devices-eth0.device has begun with start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/7d495 -- -- Unit sys-subsystem-net-devices-eth0.device has begun starting up. Jan 19 10:56:18 gitolite systemd[1]: Job sys-subsystem-net-devices-eth0.device/s Jan 19 10:56:18 gitolite systemd[1]: Timed out waiting for device sys-subsystem- -- Subject: Unit sys-subsystem-net-devices-eth0.device has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02c -- -- Unit sys-subsystem-net-devices-eth0.device has failed. -- -- The result is timeout. Jan 19 10:56:18 gitolite systemd[1]: Dependency failed for dhcpcd on eth0. -- Subject: Unit dhcpcd(a)eth0.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02c -- -- Unit dhcpcd(a)eth0.service has failed. -- -- The result is dependency. --- At this point, nothing new in dmesg. Even though ip link should a eth0 device, the sys-subsystem-net-devices-eth0.device has failed? I don't understand this. This is libvirt 1.0.1 in linux 2.6.11. I tried with both systemd 197 and (thinking that recent changes with device naming could be the problem) with 196. It didn't work on either. The domain configuration is: --- <domain type='lxc'> <name>gitolite</name> <uuid>3122bf1d-11bb-0dd8-be64-7e352b3f8694</uuid> <memory unit='KiB'>262144</memory> <currentMemory unit='KiB'>262144</currentMemory> <vcpu placement='static'>1</vcpu> <os> <type arch='x86_64'>exe</type> <init>/sbin/init</init> </os> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/lib/libvirt/libvirt_lxc</emulator> <filesystem type='mount' accessmode='passthrough'> <source dir='/mnt/gitolite'/> <target dir='/'/> </filesystem> <interface type='network'> <mac address='02:00:00:00:00:17'/> <source network='default'/> </interface> <console type='pty'> <target type='lxc' port='0'/> </console> </devices> </domain> --- I also tried using bridged networking configuration but I see the same problem. What could be causing this? Any ideas? Thanks, Marco

1 0

[libvirt-users] Problems with VM networking on Ubuntu Quantal
by Dale Amon 18 Jan '13

18 Jan '13

I have shifted some VM's to a new server running Quantal and have had a world of trouble. The first one was caused by issues with an apparently compiled in path in their apparmor version which forced VM pools to be in /srv or similar rather than where I wanted them. For now this was not a big issue, and thankfully the server where it would be a big time problem (there are individual drives per major customer or user) is Debian. But... I still have issues. The networking has changed considerably and although I can get my VM running, I cannot reach it. The new quantal machines give you something like this: br0 Link encap:Ethernet HWaddr **** inet addr:10.0.0.xx Bcast:10.0.0.255 Mask:255.255.255.0 inet6 addr: *****/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 p6p1 Link encap:Ethernet HWaddr **** UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 virbr0 Link encap:Ethernet HWaddr **** inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 vnet0 Link encap:Ethernet HWaddr fe:54:00:84:3c:4f inet6 addr: fe80::fc54:ff:fe84:3c4f/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 The VM machine has a static ip on the same network, ie 10.0.0.x. It worked fine on the old server but is not reachable (and cannot connect outward). Forwarding is turned on: cat /proc/sys/net/ipv4/ip_forward 1 The VM has eth0 Link encap:Ethernet HWaddr **** inet addr:10.0.0.xx Bcast:10.0.0.255 Mask:255.255.255.0 inet6 addr: *****/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 An attempt to ping from the VM to anything outside gives a "Destination host unreachable" message. It has been a long time since I set the old machine up, so I may well have forgotten some step.

2 2