- Users - libvirt List Archives

[libvirt-users] live migration to localhost with lvm based storage
by Vasiliy Tolstov 11 Oct '14

11 Oct '14

I have lvm based (thin pool) storage on local disks. I need to move vps from one vg on one disk to another. Does it possible to migrate to localhost with blockcopy migration to another vg? I'm understand that i can move lv from one vg to another, but i don't need that. -- Vasiliy Tolstov, e-mail: v.tolstov(a)selfip.ru jabber: vase(a)selfip.ru

2 1

[libvirt-users] How to assign multiple IP addresses to a container
by WANG Cheng D 10 Oct '14

10 Oct '14

Dear all, I want to assign multiple IP address to a container, does anybody know how to achieve that? Thanks in advance. Cheng

1 0

[libvirt-users] is memoryBacking support 'share' and 'mem-path' parameter
by Linhaifeng 09 Oct '14

09 Oct '14

Hi, I want to use this qemu command '-object memory-backend-file,id=mem,size=2048M,mem-path=/mnt/huge,share=on' with libvirt but i can't find the 'mem-path' and 'share' in the documentation. because the vhost-user backend based on 'share=on' parameter and libvirt support vhostuser i guess there maybe another way to support this parameter? this is my xml: <cpu> <numa> <cell id='0' cpus='0' memory='1048576' memAccess='shared'/> <cell id='1' cpus='1' memory='1048576' memAccess='shared'/> </numa> </cpu> <memoryBacking> <hugepages> <page size="2" unit="M" nodeset="0,1"/> </hugepages>   </memoryBacking> <interface type='vhostuser'> <mac address='52:54:00:3b:83:1a'/> <source type='unix' path='/path/port1' mode='client'/> <model type='virtio'/> </interface> <interface type='vhostuser'> <mac address='52:54:00:3b:83:1b'/> <source type='unix' path='/path/port2' mode='client'/> <model type='virtio'/> </interface> when i create the VM the qemu command is like this without 'share=on' parameter: -object memory-backend-file,prealloc=yes,mem-path=/dev/hugepages/libvirt/qemu,size=1024M,id=ram-node0 -numa node,nodeid=0,cpus=0,memdev=ram-node0 -object memory-backend-file,prealloc=yes,mem-path=/dev/hugepages/libvirt/qemu,size=1024M,id=ram-node1 -numa node,nodeid=1,cpus=1,memdev=ram-node1

2 3

[libvirt-users] Question about vnc connection password set to empty
by Wei Zhang 09 Oct '14

09 Oct '14

Hello, everybody here I have a question about graphical buffers for rhel7. Thanks so much in advance who can give me some suggestions about that. When I try to do regression for bug859317(https://bugzilla.redhat.com/show_bug.cgi?id=859317) on RHEL7， I found that guest could be connected success with virt-viewer when set/update the graphics passwd to empty. But according to comment 2 in this bug, libvirt will blocks all access to the VNC server when set a password to empty. So could you please help us check is it acceptable on RHEL7? Below is my test steps on RHEL7: Version-Release number of selected component (if applicable): libvirt-1.2.8-3.el7.x86_64 qemu-kvm-rhev-2.1.0-5.el7.x86_64 kernel-3.10.0-150.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. Define guest with a graphics device like: ......................................... <graphics type='vnc' port='-1' autoport='yes' passwd=""/> ......................................... 2. Connecting with vncviewer or virt-viewer . # virsh start dom2 # virsh dumpxml dom2 --security-info |grep graphics <graphics type='vnc' port='5900' autoport='yes' listen='127.0.0.1' passwd=''> </graphics> # virt-viewer dom2 connect the guest success with empty password 3. The problem can be reproduced when changed the graphics passwd from an non-empty to an empty # virsh dumpxml dom2 --security-info |grep graphics <graphics type='vnc' port='5900' autoport='yes' listen='127.0.0.1' passwd='123'> </graphics> # cat change-passwd.xml <graphics type='vnc' port='-1' autoport='yes' listen='127.0.0.1' passwd=''/> # virsh update-device dom2 change-passwd.xml # virsh dumpxml dom2 --security-info |grep graphics <graphics type='vnc' port='5900' autoport='yes' listen='127.0.0.1' passwd=''> </graphics> login the guest with virt-viewer command # virt-viewer testks also can connect the guest dom2 success with empty password 4. I produce the same steps on RHEL6.6 libvirt-0.10.2-46.el6.x86_64, the guest can not be connected when set graphics vnc password to empty, the same result with bug 859317. Actual results: we can login the guest when set the graphics passwd empty Expected results: I am not sure what is the right behaviour for RHEL7? thank

1 0

[libvirt-users] virsh net-start default fails
by David Roundy 08 Oct '14

08 Oct '14

Hi all, I'm getting an error, and have failed to succeed in googling for help with it. I have an old VM that I created a while back (at least one reboot ago, possibly a kernel upgrade ago), and am now finding that it won't start due to a lack of the 'default' network. When I look for how to fix this, everyone seems to agree on the command: # virsh net-start default error: failed to get network 'default' error: An error occurred, but the cause is unknown But this fails. A natural next check would be to use net-list: # virsh net-list --all Name State Autostart ----------------------------------------- Which demonstrates that the 'default' network is unknown. I'm certain that it used to exist, and the file /var/lib/libvirt/network/default.xml does exist, claims to be autogenerated and looks reasonable. I am at a loss as to how to debug this further. Any suggestions? -- David Roundy

4 3

[libvirt-users] sr-vio on intel while virsh chooses rtl8139 for model type
by lejeczek 08 Oct '14

08 Oct '14

hi everybody I'd presume virsh makes the best possible choice, right? It is that just seems bit... odd having realtek in guest and Intel's VF on host, no? regards

2 5

[libvirt-users] win2k8 guest and (strange) number of cpus task manager sees
by lejeczek 08 Oct '14

08 Oct '14

hi everybody a qemu-kvm guest gets 16 cpus and Windows in "Device Manager" sees all sixteeen but "Task Manager" shows only 4, the same "System" properties say "(4 processors)" I'd like to learn a bit about this - is it some sort of "resources management" on the libvirt/qemu causing this? And what does it do to a guest performance-wise side? it's on Scientific L 7, qemu-kvm-1.5.3-60.el7_0.7.x86_64 libvirt-1.1.1-29.el7_0.1.x86_64 regards P.

2 2

[libvirt-users] what is the xml fomat about memory-backend-file
by Linhaifeng 08 Oct '14

08 Oct '14

Hi, I want to use virsh to create a VM with the qemu parameter '-object memory-backend-file,id=mem,size=2048M,mem-path=/mnt/huge,share=on -numa node,memdev=mem'. How to write the XML file?

3 4

[libvirt-users] libvirt-sandbox on Fedora 21
by Gene Czarcinski 07 Oct '14

07 Oct '14

It sure would be nice if someone who knows what they are doing took a look at this problem: https://bugzilla.redhat.com/show_bug.cgi?id=1135762 The current situation on Fedora 21 is that virt-sandbox and virt-sandbox-service simply do not work if a network is defined (e.g., -N address-192.168.1.1/34). I would give dhcp as an example but to work, that needs to patch I submitted in another BZ report. Since both virt-sandbox -c lxc:/// -N <network>,source=default and doing systemctl start <sandbox> result in the same error and since I am running the fedora-virt-preview rpms and the failure *does not* occur on Fedora 20 but *does* occur on Fedora 21, I have to assume that the problem is not directly in libvirt. However, determining what/where the problem really is, is stretching my abilities a bit too far ... help!! Gene

2 3

[libvirt-users] Virtual gaming/workstation desktops using KVM VGA passthrough?
by Alex G.S. 07 Oct '14

07 Oct '14

Dear List, Recently I read an article [1] about how to use KVM and VGA passthrough to create multiple GPU accelerated VM's for use in gaming or as virtual workstations: [1] http://www.pugetsystems.com/labs/articles/Multiheaded-NVIDIA-Gaming-using-U… I'm planning on building a KVM workstation to do this using CentOS 7 or Ubuntu 14.04 LTS as the base virtualization host and then an Intel Xeon CPU and two Nvidia GeForce GTX 750's as GPU's for the virtual machines. I'm really new to this sort of GPU passthrough on KVM and am wondering if anyone has any advice or has done this before? Thank you!

3 4