[libvirt-users] Cannot create qcow2 images with libvirt 0.8.1
by Guido Winkelmann
Hi,
After upgrading to libvirt 0.8.1, I can no longer create empty volumes with no
backing store and an explicit format of qcow2.
This XML volume definition:
<volume>
<name>testserverb-data2.img</name>
<allocation>0</allocation>
<capacity units='G'>20</capacity>
<target>
<format type='qcow2'/>
<permissions>
<owner>107</owner>
<group>107</group>
<mode>0744</mode>
</permissions>
</target>
</volume>
yields the error "Cannot run /usr/bin/qemu-img to create /data/testserverb-
data.img: Invalid argument"
In /var/log/messages on the qemu host I can find the following snippet after
that:
error : virRunWithHook:933 : internal error '/usr/bin/qemu-img create -f qcow2
/data/testserverb-data.img 0K' exited with non-zero status 1 and signal 0:
qemu-img: Image creation needs a size parameter#012
error : virStorageBackendCreateExecCommand:537 : Cannot run /usr/bin/qemu-img
to create /data/testserverb-data.img: Invalid argument
error : qemudClientReadBuf:1653 : gnutls_record_recv: A TLS packet with
unexpected length was received.
If I leave out the <format> element and/or specify a <backingStore> element
for the volume, it works again. (I suppose the backing store makes it work
because in that case qemu-img does not need a size parameter...)
The host system is a vanilla Fedora Core 12 system (aside from the upgraded
libvirt).
Regards,
Guido Winkelmann
14 years, 6 months
[libvirt-users] Hot-add interface crashes libvirt
by steven765＠yahoo.com
Hi Everyone,
After upgrading FC12 and now FC13 whenever I try to attach a network device using attach-device it promptly crashes libvirtd. Is there an option that changed in the network interface xml spec I missed?
I really need this feature or at least the ability to connect and disconnect interfaces if that's possible?
I've tried defining my network card in several ways:
First the one that worked previously:
<interface type="network">
<mac address="52:54:00:5c:fe:a8"/>
<source network="fedora"/>
</interface>
Second copying what appeared in the xml after using the add hardware through the VMM:
<interface type='network'>
<mac address='52:54:00:5c:fe:a8'/>
<source network='fedora'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
</interface>
Both ways fail now. Please help.
Thanks,
Steve
14 years, 7 months
[libvirt-users] NAT-based network 2x-4x faster than routed network?
by Kenni Lund
Hi
Is it expected behaviour that a libvirt NAT-based network is faster
than a libvirt routed network?
I would guess that the routed network would be the fastest one in all
cases, but I'm seeing the opposite in my setup. On a 100mbit internet
connection, the routed network tops at 4mbyte/sec, while the nat-based
network goes all the way to 10mbyte/sec. I've spend the last 6 hours
on trying to figure out the cause of this, changing settings,
reinstalling the system, but the problem persists and I can't find the
cause of it.
It is a clean and fairly simple setup:
- Clean installation of CentOS 5.5
- Installation of kvm+libvirt+virt-manager+xorg
- iptables service disabled
- 1 public IP for the host (xxx.yyy.zzz.215) on a /32 subnet with
xxx.yyy.zzz.193 as gateway
- 3 public IP for the routed network (xxx.yyy.zzz.251-253) on a /26
subnet with the same gateway as the host
- 1 virtual machine with either the NAT or the routed libvirt network assigned
I have no networking connection errors or similar, it works perfectly
with both the NAT and the routed network, but the routed network is
just 2-4 times slower than the NAT one.
Do you have any suggestions of what the problem might be? When I look
at the iptables rules generated by libvirt, and the routing table,
everything looks fine AFAICT. Traceroute from guest doesn't reveal
anything either. Ping times from the two networks are similar, so the
main issue seems to be throughput.
Any help or pointers to what I should look at, is highly appreciated... :)
I've copy pasted some of my relevant system configuration into pastebin:
http://pastebin.com/jtTrHLqA
Thank you,
Kenni
14 years, 7 months
[libvirt-users] ctrl+alt+2 disabled?
by Ralf Hornik Mailings
Dear list,
I need to attach pci devices using qemu command interface but when I
use the vnc connection started using virsh, the key combination (or
qemu interface) seems to be disabled.
How can I (re)enable it?
Thanks and best regards
Ralf
14 years, 7 months
[libvirt-users] virsh domxml-from-native not working
by Ralf Hornik Mailings
Dear list,
when I try to convert the (working) command
/usr/bin/qemu-system-x86_64 \
-drive file=/dev/xen_vol/xen_ca,cache=none,if=virtio,boot=on \
-net nic,model=virtio,macaddr=00:16:3E:04:F5:6D \
-net tap,ifname=tap1 -m 256 -name ca \
-vnc 10.0.0.100:4 -daemonize -k de
into an xml file:
<domain type='qemu'>
<name>ca</name>
<uuid>dfef3884-d7a9-f6cf-5204-1615963cc0e8</uuid>
<memory>262144</memory>
<currentMemory>262144</currentMemory>
<vcpu>1</vcpu>
<os>
<type arch='x86_64'>hvm</type>
</os>
<features>
<acpi/>
</features>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>destroy</on_crash>
<devices>
<emulator>/usr/bin/qemu-system-x86_64</emulator>
<disk type='block' device='disk'>
<driver cache='none'/>
<source dev='/dev/xen_vol/xen_ca'/>
<target dev='vda' bus='virtio'/>
</disk>
<interface type='ethernet'>
<mac address='00:16:3e:04:f5:6d'/>
<target dev='tap1'/>
<model type='virtio'/>
</interface>
<input type='mouse' bus='ps2'/>
<graphics type='vnc' port='5904' autoport='no' listen='10.0.0.100'/>
<video>
<model type='cirrus' vram='9216' heads='1'/>
</video>
</devices>
</domain>
Then it stops to boot while haning on "Loading Grub Stage 2".
Additionally, the keyboard encoding "de" is missing.
The corresponding process is:
/usr/bin/qemu-system-x86_64 -S -M pc-0.12 -no-kvm -m 256 \
-smp 1,sockets=1,cores=1,threads=1 \
-name ca -uuid dfef3884-d7a9-f6cf-5204-1615963cc0e8 \
-nodefaults \
-chardev
socket,id=monitor,path=/usr/local/libvirt/var/lib/libvirt/qemu/ca.monitor,server,nowait
\
-mon chardev=monitor,mode=readline -rtc base=utc -boot c \
-drive
file=/dev/xen_vol/xen_ca,if=none,id=drive-virtio-disk0,boot=on,cache=none
\
-device
virtio-blk-pci,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0
\
-device
virtio-net-pci,vlan=0,id=net0,mac=00:16:3e:04:f5:6d,bus=pci.0,addr=0x5 \
-net tap,ifname=tap1,vlan=0,name=hostnet0 -usb -vnc 10.0.0.100:4 \
-vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3
Any Ideas, hats going wrong?
Thank yout and best regards
Ralf Hornik
14 years, 7 months
[libvirt-users] Sharing same storage on two diffrent KVM hosts
by shy Perets
Hello ,
I whould like your suggestion regarding the following problem :
I got 2 host which are running under RHEL5.4 hypervizor . both of the hosts
disks is a logical volume .( Each for each ) under the same VG .
I want to add storage ( another logical volume ) which will be availble for
both of the host as local disk . ( Share storage )
Thanks .
14 years, 7 months
