[libvirt-users] cpuacct and emulator/cpuacct
by Jean-Pierre Ribeauville
Hello,
Does it exist some documentation concerning following topic ?
What's difference between following perf counters :
/cgroup/cpuacct/libvirt/qemu/test/cpuacct.usage
and
/cgroup/cpuacct/libvirt/qemu/test/emulator/cpuacct.usage
Thx .
Regards,
J.P. Ribeauville
P: +33.(0).1.47.17.27.78
Puteaux 3 Etage 5 Bureau 4
jpribeauville(a)axway.com<mailto:jpribeauville@axway.com>
http://www.axway.com<http://www.axway.com/>
P Pensez à l'environnement avant d'imprimer.
10 years
[libvirt-users] adding devices and chardev in .xml configuration file ...
by Jean-Pierre Ribeauville
Hi,
As I want to start qemu by adding following parameters :
-device virtio-serial
-chardev socket,path=/tmp/foo,server,nowait,id=test
-device virtserialport,chardev=test,name=port.0
Is it possible to add them in the .xml configuration file of the guest , so they will be automatically added when the guest is started ?
If yes , any doc describing the syntax ?
Thx.
Regards,
J.P. Ribeauville
P: +33.(0).1.47.17.27.78
Puteaux 3 Etage 5 Bureau 4
jpribeauville(a)axway.com<mailto:jpribeauville@axway.com>
http://www.axway.com<http://www.axway.com/>
P Pensez à l'environnement avant d'imprimer.
10 years
[libvirt-users] Migrate Win2k3 to KVM
by Ruzsinszky Attila
Hi,
I made a disk image with CloneZilla from the original physical machine.
That image was restored on an iSCSI volume.
It isn't booting. I got BSOD.
I tried IDE, SATA, SCSI disk type without any success.
I tried to using virtio driver and if I use my image+W2k3 install CD+virtio
VFD the Windows repair console see the disk and I can use the repair
console with my image but the windows not start
(or not booting because the system disk can't be seen by original
"registry").
The drivers from virtio VFD image were copied to Windows' Driver directory
manually.
I tried to use virt-win-reg:
rattila@amd1:~$ virt-win-reg SJ-SIMISPC
/dev/disk/by-path/<iSCSI-path>:simispc-lun-2: Engedély megtagadva at
/usr/bin/virt-win-reg line 260.
(it means: Permission denied.)
What can I do changing the original driver to virtio (or IDE/SATA/SCSI in
KVM)?
I can't do anything with the physical machine so the only option is playing
with the disk image.
TIA,
Ruzsi
10 years
[libvirt-users] Access to virtualization on a multi-user system
by sbaugh＠catern.com
Hi libvirt-users,
I find myself wanting to do something that seems like it must have some
obvious solution: I have multiple users (let's just assume local Unix
accounts) on a Linux system, and I want them all to have access to
KVM-accelerated virtualization. But, I don't want them to be able to
meddle with each other's virtual machines. Is there a solution to this
problem?
Methods of attack that have occured to me:
- Use PolicyKit to only allow a user to access qemu:///system VMs that
are somehow marked as owned by that user
- Run multiple libvirt qemu:///system daemons and restrict access to
each on a per-user basis
- Allow qemu:///session VMs to actually be KVM-accelerated (this seems
like the best way to do it, but I have no idea if that's even
possible)
Again, the third seems like the best way, but I'm not sure of how to
allow such VMs to be KVM-accelerated, and not sure if it's possible for
them to use anything other than usermode networking.
Hopefully I'm missing some obvious way to do it!
Thanks for any assistance!
10 years
[libvirt-users] Error attaching tape drive device to KVM guest
by Jake Kugel
Hello,
i'm trying to configure a host SCSI device (tape drive) so that it is
available in a KVM guest VM, but am receiving an error when attempting to
attach the device. My guest xml has the following scsi controller
defined:
<controller type='scsi' index='0' model='virtio-scsi'>
<alias name='scsi0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x04'
function='0x0'/>
</controller>
I created tapedrive.xml with following contents:
<disk type='block' device='lun' sgio='unfiltered'>
<driver name='qemu' type='raw' cache='none'/>
<source dev='/dev/st0'/>
<target dev='st0' bus='scsi'/>
<address type='drive' controller='0' bus='0' target='0' unit='0'/>
</disk>
I then attempt to attach using following command, and receive this error:
# virsh attach-device instance-0000002d tapedrive.xml --config
error: Failed to attach device from tapedrive.xml
error: internal error: Invalid harddisk device name: st0
Does anyone know cause of the error? In <address> section of tape drive
definition I am using type='drive', I tried type='tape' also but same
error. is there a different property value I should use here, or general
advice for attaching tape drive to KVM guest? Thanks, Jake
10 years
[libvirt-users] Slow network performance issues
by Alex Regan
Hi,
I have a fedora21 system that's been running fine under normal network
activity, but trying to perform a full backup of the 300GB filesystem is
taking forever because the network speed appears to be very slow.
Using rsync, the transfer speeds reach a max of like 180kB/s. Using
rsync to copy files on the local filesystem is greater than 55MB/s, so I
don't think it's a disk issue.
What kind of network speed can I expect copying data across the network
from the guest to another host on the same gigabit network?
I'm using the virtio driver:
# lsmod|grep virtio
virtio_console 28672 0
virtio_balloon 16384 0
virtio_net 32768 0
virtio_blk 20480 4
virtio_pci 24576 0
virtio_ring 20480 5
virtio_blk,virtio_net,virtio_pci,virtio_balloon,virtio_console
virtio 16384 5
virtio_blk,virtio_net,virtio_pci,virtio_balloon,virtio_console
ethtool on the vnet0 interface shows the speed at only 10Mb/s. Is that
normal? Or even changable?
I've included the qemu command-line below.
# ps ax|grep propguest
1582 ? Sl 25433:37 /usr/bin/qemu-system-x86_64 -machine
accel=kvm -name propguest -S -machine pc-1.2,accel=kvm,usb=off -m 16384
-realtime mlock=off -smp 4,sockets=4,cores=1,threads=1 -uuid
b67e10fe-7ef0-a1ca-cecf-3f3506d54e1a -no-user-config -nodefaults
-chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/propguest.monitor,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc
-no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2
-device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -drive
file=/var/lib/libvirt/iso-images/Fedora-18-x86_64-DVD.iso,if=none,id=drive-ide0-1-0,readonly=on,format=raw
-device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive
file=/var/lib/libvirt/images/propguest.img,if=none,id=drive-virtio-disk0,format=qcow2
-device
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
-drive
file=/var/lib/libvirt/images/propguest-2.img,if=none,id=drive-virtio-disk2,format=raw
-device
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x9,drive=drive-virtio-disk2,id=virtio-disk2
-netdev tap,fd=23,id=hostnet0,vhost=on,vhostfd=24 -device
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:11:66:5a:51,bus=pci.0,addr=0x3
-chardev pty,id=charserial0 -device
isa-serial,chardev=charserial0,id=serial0 -chardev
spicevmc,id=charchannel0,name=vdagent -device
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0
-device usb-tablet,id=input0 -spice
port=5900,addr=127.0.0.1,disable-ticketing,seamless-migration=on -device
qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,bus=pci.0,addr=0x2 -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=0x8
Any ideas greatly appreciated.
Thanks,
Alex
10 years
