- Users - libvirt List Archives

[libvirt-users] using shared storage with libvirt/KVM?
by David Ehle 04 May '10

04 May '10

I apologize if this is a duplicate. I submitted it before I was a list member and it looks like it went into limbo. Dear Moderator, please discard the original if it is sitll in a moderation queue. Hello, I've spent a few days googling and reading documentation, but I'm looking for clarification and advise on setting up KVM/libvirt with shared storage. I have 2 (for now) Ubuntu Karmic systems with KVM/virsh/virt-manager set up and running. I have a storage server that can do NFS/iSCSI/samba/ etc. I am trying to figure out the best way to set things up so that I can run several (eventually) production linux guests (mostly debian stable) on the 2 KVM host systems and be able to migrate them when maintenance is required on their hosts. Performance is of medium importance, stability/availibilty is pretty high priority. A common opinion seems to be that using LVs to hold disk images gives possibly the best IO performance, followed by raw, then qcow2. Would you agree or disagree with this? What evidence can you provide? I am also rather confused about using shared storage, and what options can be combined with this. I have succesfully made an iscsi device available to libvirt/virsh/virt-manager via an XML file + pool-define + pool-start. However the documentation states that while you can create pools through libvirt, volumes have to be pre-allocated: http://libvirt.org/storage.html "Volumes must be pre-allocated on the iSCSI server, and cannot be created via the libvirt APIs." I'm very unclear on what this means in general, and specifically how you preallocate the the Volumes. When I make a iscsi pool available via something like this: <pool type="iscsi"> <name>virtimages</name> <source> <host name="iscsi.example.com"/> <device path="demo-target"/> </source> <target> <path>/dev/disk/by-path</path> </target> </pool> In virt-manger I can see it as a pool, but when I try to select it for where to create an image, it uses the pool AS A Volume (I think). That brings me to my next question/misunderstanding... If you are using shared storage (via NFS or iSCSI) does that also mean you MUST use a file based image rather than an LVM LV? NFS makes directories available, not devices. You can make an unformated "raw" LV available via iSCSI, but its not seen on the far side as a LV but instead as a scsi disk which you need to partition. You can make a PV>VG>LV out of that and then make your new LV available to libvirt/KVM but then your stacking a heck of a lot of LVM/LVs/partion tables up which seems pretty dubious. I'm also not sure that the stack would be visable/available to the second system using that iSCSI device. (I'm pretty new to using iSCSI as well.) Redhat provides pretty good documentation on doing shared storage/live migration for NFS: http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.4/html/Virtuali… But unfortunately the section on Shared Storage with iSCSI is a bit lacking: "9.1. Using iSCSI for storing guests This section covers using iSCSI-based devices to store virtualized guests." and thats it. For maybe 6-10 guests, should I simply just be using NFS? Is its performance that much worse than iSCSI for this task? So since KVM/libvirt is getting used quite often in production now - but some simple things are not making any sense to me - I'm guessing that I have some really basic misunderstandings of how to do shared storage / Pools/ Volumes for migration. Would one of the kind readers of this least be willing to correct me? Please CC to my original email address as well as I am not yet a regular subscriber. Thanks again! David.

2 2

[libvirt-users] Issues after migrating from Xen to KVM
by Ralf Hornik Mailings 04 May '10

04 May '10

Dear list, I have moved my HVMs from xen to kvm and it worked well except some problems using virsh. First, one OpenSolaris HVM does boot with warnings: WARNING: /pci@0,0/pci1af4,1100@1,2 (uhci1): No SOF interrupts have been received, this USB UHCI host controller is unusable* *The corresponding process: /usr/bin/qemu-system-x86_64 -S -M pc-0.12 -enable-kvm -m 1024 -smp 1,sockets=1,cores=1,threads=1 \ -name server01 -uuid e382c360-23bd-b400-0b89-9a1e69613ec4 -nographic \ -nodefaults -chardev socket,id=monitor,path=/usr/local/libvirt/var/lib/libvirt/qemu/server01.monitor,server,nowait \ -mon chardev=monitor,mode=readline -rtc base=utc -boot c -drive file=/dev/xen_vol/xen_opensol,if=none,id=drive-ide0-0-0,boot=on \ -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -drive file=/dev/hde,if=none,id=drive-ide0-0-1 \ -device ide-drive,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1 -device rtl8139,vlan=0,id=net0,mac=00:16:3e:28:85:7a,bus=pci.0,addr=0x4 \ -net tap,ifname=tap0,vlan=0,name=hostnet0 -chardev pty,id=serial0 -device isa-serial,chardev=serial0 -usb -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3 This does not happen when I boot with plain qemu-bin: /usr/local/kvm/bin/qemu-system-x86_64 -hda /dev/xen_vol/xen_opensol \ -hdb /dev/hde -net nic,macaddr=00:16:3e:28:85:7a \ -net tap,ifname=tap0 -nographic \ -m 1024 -daemonize Second is one Centos 5.2 HVM that does not boot at all. However when I boot manually and omitt "-S" and "-nodefaults" then it comes up. I looked for the -S option and I wonder why it is being used by default. Can anybody help me? I cannot see any further documentation about the "-nodefault" option and how to disable "-S" Best regards Ralf

2 2

Re: [libvirt-users] Windows Vista Client Fails to Connect to Ubuntu libvirtd
by Matthias Bolte 03 May '10

03 May '10

2010/4/30 Tim McLeod <tim.mcleod(a)simulamen.eu>: > Requesting urgent assistance if I may? > > Attempting to connect to an Ubuntu machine using an MinMG compiled virsh on > a Windows Vista machine. Using insecure TCP simply to prove a concept to a > client. However, cannot connect; situation as follows: > > Edited /etc/libvirt/libvirt.conf as follows: > listen_tcp = 1 > auth_tcp = "none" > > Edited /etc/default//libvirt-bin as follows: > libvirt-opts="-d -l" Did you restart libvirtd after the changes and checked that it's started successfully? listen_tls defaults to 1 in /etc/libvirt/libvirt.conf, in combination with the -l flag (short for --listen) libvirtd requires properly configured SSL certificates. If libvirtd can't find the certificates or fails to validate them then it won't start up. You can disable TLS in /etc/libvirt/libvirt.conf by setting listen_tls = 0 and restart libvirtd. > Running virsh on Vista client fails as follows: > $ virsh -c qemu+tcp://192.168.1.101/system > error: unable to connect to libvirtd at '192.168.1.101': errno=10061 > error: failed to connect to the hypervisor > > Running virsh on Ubuntu server fails as follows: > $ virsh -c qemu+tcp:///system > Connecting to uri: qemu+tcp:///system > error: unable to connect to libvirtd at 'localhost': Connection refused > error: failed to connect to the hypervisor Once libvirtd is running and configured properly for TCP transport then remote and local TCP access to libvirtd works for me. > Indeed, with libvirt-opts="-d -l" in etc/default//libvirt-bin the 'default' > command also fails: > $ virsh -c qemu:///system > Connecting to uri: qemu:///system > error: unable to connect to 'var/run/libvirt/libvirt-sock': Connection > refused > error: failed to connect to the hypervisor > Local access to libvirtd using qemu:///system requires properly configured polkit, or running virsh as root. This is independent from the -d and -l flags. Matthias

2 1

[libvirt-users] Windows Vista Client Fails to Connect to Ubuntu libvirtd
by Development 01 May '10

01 May '10

Requesting urgent assistance if I may? Attempting to connect to an Ubuntu machine using an MinMG compiled virsh on a Windows Vista machine. Using insecure TCP simply to prove a concept to a client. However, cannot connect; situation as follows: Edited /etc/libvirt/libvirt.conf as follows: listen_tcp = 1 auth_tcp = "none" Edited /etc/default//libvirt-bin as follows: libvirt-opts="-d -l" Running virsh on Vista client fails as follows: $ virsh -c qemu+tcp://192.168.1.101/system error: unable to connect to libvirtd at '192.168.1.101': errno=10061 error: failed to connect to the hypervisor Running virsh on Ubuntu server fails as follows: $ virsh -c qemu+tcp:///system Connecting to uri: qemu+tcp:///system error: unable to connect to libvirtd at 'localhost': Connection refused error: failed to connect to the hypervisor Indeed, with libvirt-opts="-d -l" in etc/default//libvirt-bin the 'default' command also fails: $ virsh -c qemu:///system Connecting to uri: qemu:///system error: unable to connect to 'var/run/libvirt/libvirt-sock': Connection refused error: failed to connect to the hypervisor Suggestions very welcome... Tim McLeod

2 1

[libvirt-users] Windows Vista Client Fails to Connect to Ubuntu libvirtd
by Tim McLeod 01 May '10

01 May '10

Requesting urgent assistance if I may? Attempting to connect to an Ubuntu machine using an MinMG compiled virsh on a Windows Vista machine. Using insecure TCP simply to prove a concept to a client. However, cannot connect; situation as follows: Edited /etc/libvirt/libvirt.conf as follows: listen_tcp = 1 auth_tcp = "none" Edited /etc/default//libvirt-bin as follows: libvirt-opts="-d -l" Running virsh on Vista client fails as follows: $ virsh -c qemu+tcp://192.168.1.101/system error: unable to connect to libvirtd at '192.168.1.101': errno=10061 error: failed to connect to the hypervisor Running virsh on Ubuntu server fails as follows: $ virsh -c qemu+tcp:///system Connecting to uri: qemu+tcp:///system error: unable to connect to libvirtd at 'localhost': Connection refused error: failed to connect to the hypervisor Indeed, with libvirt-opts="-d -l" in etc/default//libvirt-bin the 'default' command also fails: $ virsh -c qemu:///system Connecting to uri: qemu:///system error: unable to connect to 'var/run/libvirt/libvirt-sock': Connection refused error: failed to connect to the hypervisor Suggestions very welcome... Tim McLeod

1 0

[libvirt-users] using shared storage with libvirt/KVM?
by David Ehle 01 May '10

01 May '10

Hello, I've spent a few days googling and reading documentation, but I'm looking for clarification and advise on setting up KVM/libvirt with shared storage. I have 2 (for now) Ubuntu Karmic systems with KVM/virsh/virt-manager set up and running. I have a storage server that can do NFS/iSCSI/samba/ etc. I am trying to figure out the best way to set things up so that I can run several (eventually) production linux guests (mostly debian stable) on the 2 KVM host systems and be able to migrate them when maintenance is required on their hosts. Performance is of medium importance, stability/availibilty is pretty high priority. A common opinion seems to be that using LVs to hold disk images gives possibly the best IO performance, followed by raw, then qcow2. Would you agree or disagree with this? What evidence can you provide? I am also rather confused about using shared storage, and what options can be combined with this. I have succesfully made an iscsi device available to libvirt/virsh/virt-manager via an XML file + pool-define + pool-start. However the documentation states that while you can create pools through libvirt, volumes have to be pre-allocated: http://libvirt.org/storage.html "Volumes must be pre-allocated on the iSCSI server, and cannot be created via the libvirt APIs." I'm very unclear on what this means in general, and specifically how you preallocate the the Volumes. When I make a iscsi pool available via something like this: <pool type="iscsi"> <name>virtimages</name> <source> <host name="iscsi.example.com"/> <device path="demo-target"/> </source> <target> <path>/dev/disk/by-path</path> </target> </pool> In virt-manger I can see it as a pool, but when I try to select it for where to create an image, it uses the pool AS A Volume (I think). That brings me to my next question/misunderstanding... If you are using shared storage (via NFS or iSCSI) does that also mean you MUST use a file based image rather than an LVM LV? NFS makes directories available, not devices. You can make an unformated "raw" LV available via iSCSI, but its not seen on the far side as a LV but instead as a scsi disk which you need to partition. You can make a PV>VG>LV out of that and then make your new LV available to libvirt/KVM but then your stacking a heck of a lot of LVM/LVs/partion tables up which seems pretty dubious. I'm also not sure that the stack would be visable/available to the second system using that iSCSI device. (I'm pretty new to using iSCSI as well.) Redhat provides pretty good documentation on doing shared storage/live migration for NFS: http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.4/html/Virtuali… But unfortunately the section on Shared Storage with iSCSI is a bit lacking: "9.1. Using iSCSI for storing guests This section covers using iSCSI-based devices to store virtualized guests." and thats it. For maybe 6-10 guests, should I simply just be using NFS? Is its performance that much worse than iSCSI for this task? So since KVM/libvirt is getting used quite often in production now - but some simple things are not making any sense to me - I'm guessing that I have some really basic misunderstandings of how to do shared storage / Pools/ Volumes for migration. Would one of the kind readers of this least be willing to correct me? Please CC to my original email address as well as I am not yet a regular subscriber. Thanks again! David.

1 0

[libvirt-users] attach-device broken?
by steven765＠yahoo.com 30 Apr '10

30 Apr '10

Hi, Just installed a new FC12 box with all new updates. Figured out to delete the CDROM so the images actually boot now. However, after the upgrade, I can no longer attach my network interfaces to running images? Was this capability removed? Is there some new setting that has to be configured? It's a very simple configuration that hasn't changed and still works on the pre-update box. <interface type='network'> <mac address='52:54:00:58:9c:00'/> <source network='mynetwork'/> yes it's defined and active </interface> Thanks in advance, Steve

1 0

[libvirt-users] Ignoring invalid update watch -1
by jeremy avnet 30 Apr '10

30 Apr '10

Hello, I've started to get these in my logs every now and then: libvirtd: 18:50:29.792: warning : virEventUpdateHandleImpl:149 : Ignoring invalid update watch -1 What does it mean? Thanks! .:. jeremy

1 0

[libvirt-users] libvirt client certificate location
by Vadym Chepkov 30 Apr '10

30 Apr '10

Hi, I was really surprised to find that location of client certificate, key and CA is hardcoded into libvirt. What if I need to manage servers with certificates issued by different CA? Or why do everybody has to use the same private key? Doesn't make it much of a private. It seems so strange I wonder if I am mistaken and it is possible to provide alternative location for the CA, key and certificate? Thank you, Vadym Chepkov

1 0

Re: [libvirt-users] Windows Client
by Matthias Bolte 30 Apr '10

30 Apr '10

2010/4/28 Tim McLeod <tim.mcleod(a)simulamen.eu>: > Having newly compiled a Libvirt on a Windows Vista machine (many thanks to > Matthias Bolte) Nine :) > I have attempted to connect to a remote Ubuntu machine using > virsh.exe. However, the connection fails as follows: > > > > $ virsh -c qemu+tcp:///system You need to specify the server in this URI using a hostname or IP address: qemu+tcp://ubuntu-server.com/system > error: unable to connect to libvirtd at 'localhost': errno=10061 > > error: failed to connect to the hypervisor > > > > 1. I have modified /etc/libvirt/libvirt.conf to set listen_tcp=1. You also need to change this #auth_tcp = "sasl" to auth_tcp = "none" to disable SASL authentication/encryption for TCP connections, because your libvirt on Windows is compiled without SASL support. If you need the libvirt connections to be encrypted you can switch from TCP to TLS connections using: qemu+tls://ubuntu-server.com/system > 2. I cannot find /etc/sysconfig/libvirtd so I am unable to set > LIBVIRTD_ARGS="--listen". > For Ubuntu packaged libvirt see /etc/default/libvirt-bin and change libvirtd_opts="-d" to libvirtd_opts="-d -l" as the comment suggest and restart libvirtd using /etc/init.d/libvirt-bin restart Now you should be able to connect to the libvirtd on your Ubuntu server. Matthias

2 2

[libvirt-users] Cloning very slow?
by Tom Hughes 30 Apr '10

30 Apr '10

Yesterday I cloned one of my VMs and, somewhat implausibly, it took virt-clone something like 8-9 hours to clone the 8Gb disk image... Copying it from the command line took a mere 6.5 minutes. I assume this is a bug, and it's not expected to take this long ;-) This was using virt-clone from python-virtinst-0.500.2-1.fc12.noarch in the virt-preview repository. Tom -- Tom Hughes (tom(a)compton.nu) http://compton.nu/

2 2

[libvirt-users] ruby-libvirt equiv of virsh list --all
by Mick Pollard 29 Apr '10

29 Apr '10

Hi all, I have a working KVM system managed with virsh and virt-install. I am currently playing with ruby-libvirt-0.1.0. I am wanting to build a simple sinatra/ruby app to show the VE's on a node and their state. I have ruby 1.8.5 on CentOS 5.4. I have the basics of it worked out but am a little stuck. Is there a way of retrieving a list of all VM's on a host using ruby-libvirt. ie: virsh list --all ? @conn.list_defined_domains only shows VE's not started (lists VE names) @conn.list_domains only shows VE's running (lists VE id's) What I ultimately would like is to retrieve a full list of the uuid's of all defined VE's(running or not). -- Regards Mick Pollard ( lunix ) ------------------------------------------------ BOFH Excuse of the day: Extraneous Configuration Invalidation

2 2

[libvirt-users] Windows Client
by Tim McLeod 29 Apr '10

29 Apr '10

Having newly compiled a Libvirt on a Windows Vista machine (many thanks to Matthias Bolte) I have attempted to connect to a remote Ubuntu machine using virsh.exe. However, the connection fails as follows: $ virsh -c qemu+tcp:///system error: unable to connect to libvirtd at 'localhost': errno=10061 error: failed to connect to the hypervisor 1. I have modified /etc/libvirt/libvirt.conf to set listen_tcp=1. 2. I cannot find /etc/sysconfig/libvirtd so I am unable to set LIBVIRTD_ARGS="--listen". As stated on a previous post, my background is Windows rather than Linux, so I am at a loss as to know where to look next. I would very much appreciate some guidance. Many thanks in anticipation... Tim McLeod

2 1

Re: [libvirt-users] Libvirt Compilation on MS Vista
by Matthias Bolte 29 Apr '10

29 Apr '10

Ah, sorry. I've the scripts at hand. I just forgot to post them. I attached the scripts and added a readme file. I tested this on Windows XP, but it should work without problem on Windows Vista too. The scripts could still be improved, for example gathering all relevant files for a libvirt Windows SDK into a separate directory would be nice. If you have any problems or questions with/about this scripts please report/ask them. PS: You'll need to rename setup_msys.bat_ to setup_msys.bat. Matthias 2010/4/26 Tim McLeod <tim.mcleod(a)simulamen.eu>: > Matthias, > > Polite enquiry on the progress of tidying up scripts to automate the MinGW/MSYS setup and libvirt compilation on Windows, if I may? Not meaning to appear impatient, but I would like to give my client some indication of when I can meet my deliverables. Many thanks... > > Tim > > -----Original Message----- > From: Matthias Bolte [mailto:matthias.bolte@googlemail.com] > Sent: 21 April 2010 08:14 > To: tim.mcleod(a)simulamen.eu > Cc: libvirt-users(a)redhat.com > Subject: Re: [libvirt-users] Libvirt Compilation on MS Vista > > [Let's keep the list involved] > > 2010/4/20 Tim McLeod <tim.mcleod(a)simulamen.eu>: >> Matthias, >> >> Thank you for the swift response. Now, the current state is the result of following the instructions found a la Web in the attached 'print to PDF' file. Situation as follows: >> >> 1. MinGW. MinGW-5.1.4.exe installed without error; no issues. >> 2. MSYS. Failed to locate the executable MSYS-1.0.11-2004.04.30-1.exe, but MSYS-1.0.11.exe did install without error. >> 3. msysDTK. msysDTK-1.0.1.exe installed without error; no issues. >> 4. GTK. gtk-dev-2.12.9-win32-2.exe installed without error; no issues. >> 5. M4. Failed to locate compressed file m4-1.4.7-MSYS.tar.bz2, used m4-1.4.13-1-msys-1.0.11-bin.tar.lzma instead. Did not understand instruction to extract to the 'root' folder but instead replaced the original M4.exe found in C:\MSYS\1.0\bin with the M4.exe found in the lzma file. >> 6. Autoconf. Failed to 'make' source found in autoconf-2.62.tar.gz due to a '[m4sugar.m4f] Error 1' error, but following a reference found on the Web to this error not occurring in autoconf-2.52.tar.gz, successfully 'made' and installed this version. When moving on to step 7, Automake, compilation failed since autoconf 2.6 or newer was required. However, autoconf-2.60.tar.gz failed with the 'm4sugar.m4f' error in the same way as v2.62. >> >> Brick wall; sore head! As I'm sure you have guessed my background is MS Windows rather than Linux so I am finding these. Probably minor issues to you, extremely daunting and frustrating to me. I am encouraged that you have successfully compiled a Windows Libvirt client, hope you can point me in the right direction. Many thanks... >> >> Tim >> > > Okay, so the problem is setting up a working MinGW/MSYS environment. > You used the instructions posted here: > https://www.redhat.com/archives/libvir-list/2008-June/msg00145.html > > I didn't try that, but I wrote a set of scripts to automate the > MinGW/MSYS setup and libvirt compliation on Windows. I'll clean them > up a bit and post them, so you can try to use them. > > Probably we should also improve http://libvirt.org/windows.html with > more details. > > Matthias > >

2 1

[libvirt-users] Using the host's LVM to manage virtual disks
by scar 27 Apr '10

27 Apr '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 i am envisioning a scenario that a fellow sysadmin is employing using xen, where the host is configured with LVM. basically, one volume group spans the physical disk. then, various logical volumes are created for the host and (Linux) guest OSes. this makes it easy to resize logical volumes should it be needed. is a setup like this possible with libvirt? the best i can think up, so far, is to create a new logical disk, vm1, and pass that as an argument to the -f option of virt-install. then, during the installation i can setup LVM within the guest. not sure if this would even work if i need to expand the volume size. first i would expand the size of vm1. then, within the vm1 OS i would expand the size of the root partition. i would like to not have to use this second layer of LVM. for example, on the host OS, i would create two logical volumes: vm1-root and vm1-swap, and these are what vm1 would use for root and swap. then, if needed, i can just increase the size of vm1-root, etc. thanks -----BEGIN PGP SIGNATURE----- iEYEAREIAAYFAkvSJ08ACgkQXhfCJNu98qDAoQCfbdN84rlxmFJCwHnsaHXdv0l4 juUAmwfE2Te+l07VfkuJYUI2/us83F5e =AmQ+ -----END PGP SIGNATURE-----

2 2

[libvirt-users] Unable to switch ISO with virsh/kvm
by Don Morrison 27 Apr '10

27 Apr '10

I'd created a VM with "virsh create" that has a CD-ROM attached <disk type='file' device='cdrom'> <source file='/images/myiso_1.2.iso'/> <target dev='sdb' bus='scsi'/> <readonly/> <alias name='scsi0-0-1'/> <address type='drive' controller='0' bus='0' unit='1'/> </disk> Now I'd like to swap that iso out and mount a new one without taking down the guest. But it fails as follows: virsh detach-disk sles-11 sdb error: Failed to detach disk error: this function is not supported by the hypervisor: This type of device cannot be hot unplugged Attaching a new iso also fails. virsh attach-disk sles-11 /images/myiso_1.3,iso sdc --type cdrom --mode readonly error: Failed to attach disk error: internal error No device with bus 'scsi' and target 'sdc' I've tried all of the variations I can think of (including attach-device detach-device, ide vs scsi, block vs file, mounting an empty CDROM device, etc) and I can't get this to work. It does work when the VM is powered down, but I need to do the iso switch when the VM is up, which seems like pretty basic functionality if trying to install an OS that covers multiple ISOs. Is this expected to work? If so, any tips on what I'm doing wrong? Thanks. I'm running SLES 11 SP1 (beta) damkvm:/tmp # virsh --version 0.7.6 damkvm:/tmp # libvirtd --version libvirtd (libvirt) 0.7.6 damkvm:/tmp # virsh version Compiled against library: libvir 0.7.6 Using library: libvir 0.7.6 Using API: QEMU 0.7.6 Running hypervisor: QEMU 0.12.3 Don Morrison

1 0

Re: [libvirt-users] Libvirt Compilation on MS Vista
by Matthias Bolte 27 Apr '10

27 Apr '10

[Let's keep the list involved] 2010/4/20 Tim McLeod <tim.mcleod(a)simulamen.eu>: > Matthias, > > Thank you for the swift response. Now, the current state is the result of following the instructions found a la Web in the attached 'print to PDF' file. Situation as follows: > > 1. MinGW. MinGW-5.1.4.exe installed without error; no issues. > 2. MSYS. Failed to locate the executable MSYS-1.0.11-2004.04.30-1.exe, but MSYS-1.0.11.exe did install without error. > 3. msysDTK. msysDTK-1.0.1.exe installed without error; no issues. > 4. GTK. gtk-dev-2.12.9-win32-2.exe installed without error; no issues. > 5. M4. Failed to locate compressed file m4-1.4.7-MSYS.tar.bz2, used m4-1.4.13-1-msys-1.0.11-bin.tar.lzma instead. Did not understand instruction to extract to the 'root' folder but instead replaced the original M4.exe found in C:\MSYS\1.0\bin with the M4.exe found in the lzma file. > 6. Autoconf. Failed to 'make' source found in autoconf-2.62.tar.gz due to a '[m4sugar.m4f] Error 1' error, but following a reference found on the Web to this error not occurring in autoconf-2.52.tar.gz, successfully 'made' and installed this version. When moving on to step 7, Automake, compilation failed since autoconf 2.6 or newer was required. However, autoconf-2.60.tar.gz failed with the 'm4sugar.m4f' error in the same way as v2.62. > > Brick wall; sore head! As I'm sure you have guessed my background is MS Windows rather than Linux so I am finding these. Probably minor issues to you, extremely daunting and frustrating to me. I am encouraged that you have successfully compiled a Windows Libvirt client, hope you can point me in the right direction. Many thanks... > > Tim > Okay, so the problem is setting up a working MinGW/MSYS environment. You used the instructions posted here: https://www.redhat.com/archives/libvir-list/2008-June/msg00145.html I didn't try that, but I wrote a set of scripts to automate the MinGW/MSYS setup and libvirt compliation on Windows. I'll clean them up a bit and post them, so you can try to use them. Probably we should also improve http://libvirt.org/windows.html with more details. Matthias

2 1

[libvirt-users] Problems moving qemu machine to libvirt
by Erik de Castro Lopo 26 Apr '10

26 Apr '10

Hi all, I have a qemu-system-arm machine that I am currently starting using: qemu-system-arm -M versatilepb -nographic \ -hda img.qcow2 \ -net vde,vlan=0,sock=/var/run/qemu-vde.ctl \ -net nic,vlan=0,macaddr=52:54:00:12:34:22 \ -kernel vmlinuz-2.6.18-6-versatile \ -initrd initrd.img-2.6.18-6-versatile \ -append "root=/dev/sda1 console=ttyAMA0,115200n8" I converted the above to a virsh XML file using: virsh domxml-from-native qemu-argv run.argc > arm32.xml which resulted in this (minor modifications to provide full paths): <domain type='qemu'> <name>arm32</name> <uuid>e433002b-107f-5b16-415b-7afb3e3a4d84</uuid> <memory>262144</memory> <currentMemory>262144</currentMemory> <vcpu>1</vcpu> <os> <type arch='arm' machine='versatilepb'>hvm</type> <kernel>/kvm/arm32/vmlinuz-2.6.18-6-versatile</kernel> <initrd>/kvm/arm32/initrd.img-2.6.18-6-versatile</initrd> </os> <features> <acpi/> </features> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/kvm/arm32/arm32.sh</emulator> <disk type='file' device='disk'> <source file='/kvm/arm32/img.qcow2'/> <target dev='hda' bus='ide'/> <address type='drive' controller='0' bus='0' unit='0'/> </disk> <controller type='ide' index='0'/> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target port='0'/> </console> </devices> </domain> Since libvirt doesn't support VDE networking I use a wrapper around qemu-system-arm (/kvm/arm32/arm32.sh) containing: #!/bin/bash exec /usr/bin/qemu-system-arm $@ \ -net nic,vlan=0,macaddr=52:54:00:12:34:22 \ -net vde,vlan=0,group=vde2-net,mode=0770,sock=/var/run/qemu-vde.ctl \ -append "root=/dev/sda1 console=ttyAMA0,115200n8" However, doing this I get the following error when I attempt to start the VM: error: Failed to start domain arm32 error: internal error Process exited while reading console log output: char device redirected to /dev/pts/10 qemu: could not open disk image console=ttyAMA0,115200n8\"": No such file or directory The first problem (console log output) is probably due to the second, where it seems that this: <cmdline>root=/dev/sda1 console=ttyAMA0,115200n8</cmdline> is not being passed to qemu correctly. I have tried quoting the command line but that doesn't help. Anyone have any clues? Cheers, Erik -- ---------------------------------------------------------------------- Erik de Castro Lopo http://www.mega-nerd.com/

2 1

[libvirt-users] QEmu 0.12.3 Libvirt-0.8.0 and serials ports
by Jorge Alejandro Rodríguez 26 Apr '10

26 Apr '10

I have a problem with libvirt and serial ports. When I run a xml with serial tag over libvirt0.8.0 and qemu 0.11 this is the line that libvirt execute LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-0.11 -cpu qemu32 -enable-kvm -m 0 -smp 1 -name uml2 -uuid 431cb9f4-fdba-c4e8-a35f-23b52f91120a -monitor unix:/var/lib/libvirt/qemu/uml2.monitor,server,nowait -boot cd -drive file=/root/.vnuml/simulations/tutorial-r1_xp/vms/uml2/fs/root_cow_fs,if=ide,bus=0,unit=0,boot=on -drive file=/root/.vnuml/simulations/tutorial-r1_xp/vms/uml2/fs/opt_fs.iso,if=ide,media=cdrom,bus=0,unit=1 -net nic,macaddr=fe:fd:00:00:02:01,vlan=0,name=net0 -net tap,fd=19,vlan=0,name=hostnet0* -serial unix:/root/.vnuml/simulations/tutorial-r1_xp/vms/uml2/uml2_socket,server,nowait * -parallel none -usb -vnc :1001 -vga cirrus -balloon virtio and the virtual machine created have a serial port but when I run the same xml in a machine with qemu 0.12.3 this is the line that libvirt execute LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-0.12 -cpu qemu32 -enable-kvm -m 0 -smp 1,sockets=1,cores=1,threads=1 -name uml2 -uuid 3e3a4836-94b4-869c-4180-724c970c1909 -nodefaults -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/uml2.monitor,server,nowait -mon chardev=monitor,mode=readline -rtc base=utc -boot cd -drive file=/root/.vnuml/simulations/tutorial-r1_xp/vms/uml2/fs/root_cow_fs,if=none,id=drive-ide0-0-0,boot=on -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -drive file=/root/.vnuml/simulations/tutorial-r1_xp/vms/uml2/fs/opt_fs.iso,if=none,media=cdrom,id=drive-ide0-0-1,readonly=on -device ide-drive,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1 -device rtl8139,vlan=0,id=net0,mac=fe:fd:00:00:02:01,bus=pci.0,addr=0x4 -net tap,fd=18,vlan=0,name=hostnet0 -chardev socket,id=serial0,path=/root/.vnuml/simulations/tutorial-r1_xp/vms/uml2/uml2_socket,server,nowait -device isa-serial,chardev=serial0 -usb -vnc :1001 -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3 the virtual machine don't have any serial port. If you execute the line: /usr/bin/kvm -M pc-0.11 -cpu qemu32 -enable-kvm -m 0 -smp 1 -name uml2 -uuid 431cb9f4-fdba-c4e8-a35f-23b52f91120a -monitor unix:/var/lib/libvirt/qemu/uml2.monitor,server,nowait -boot cd -drive file=/root/.vnuml/simulations/tutorial-r1_xp/vms/uml2/fs/root_cow_fs,if=ide,bus=0,unit=0,boot=on -drive file=/root/.vnuml/simulations/tutorial-r1_xp/vms/uml2/fs/opt_fs.iso,if=ide,media=cdrom,bus=0,unit=1 -net nic,macaddr=fe:fd:00:00:02:01,vlan=0,name=net0 -net tap,fd=19,vlan=0,name=hostnet0* -serial unix:/root/.vnuml/simulations/tutorial-r1_xp/vms/uml2/uml2_socket,server,nowait * -parallel none -usb -vnc :1001 -vga cirrus -balloon virtio (the same line before) over qemu 0.12.3 the viertual machine have serial port. Any ideas?

2 2

[libvirt-users] Failed to insert a cd in a virtual machine running
by Jorge Alejandro Rodríguez 23 Apr '10

23 Apr '10

I can't attach a cd when a vm is running with qemu 0.12.3 (ubuntu 10.04), the problem is not with qemu because when I start the vm with kvm command (without libvirt) I can change the cd with qemu-monitor without any problem and eject it too (libvirt say me that it isn't supported by hypervisor). the versions of libvirt that I have tried are 0.7.7 and 0.8.0. Any ideas? Thanks. Jorge

1 1

[libvirt-users] Allowing incoming traffic to a virtual network
by Mathias Tausig 22 Apr '10

22 Apr '10

Hello! I have some virtual networks defined on a virtualization host (using libvirt 0.7.7 and kvm 0.12.3) with some virtual bridges (virbr1, virbr2) which are all plugged into a phisical bridge br0. Now I would like to allow external hosts to connect to guest machines, but the automatically created iptables rules forbid it. I have found this rather old post on the mailing list http://www.redhat.com/archives/libvir-list/2007-January/msg00048.html which suggests a "forwarding" element for the network configuration, but this seem to be unimplemented. cheers Mathias

1 0

Re: [libvirt-users] New VM Snapshot API Not working
by Tej Parkash, ERS, HCLTech 22 Apr '10

22 Apr '10

All, Ok, I got it working..... Problem was that I didnt include xen option for configure step. But looks like Xen Hypervisor does not have support of Snapshot. :( I guess I have to fall back to save and restore method... Sorry for the noise. Thanks Tej ________________________________________ From: Tej Parkash, ERS, HCLTech Sent: Wednesday, April 21, 2010 2:31 PM To: libvir-list(a)redhat.com Subject: New VM Snapshot API Not working All, I have compiled new libvirt library 0.8.0. Compilation and installation went really fine except "make check" which has show some test got failed. Here is what make check said. Failed Test: ---------------snip----------- PASS: statstest TEST: qparamtest ................................ 32 OK PASS: qparamtest TEST: capabilityschematest !!!!!!!!!!!! 12 FAILED FAIL: capabilityschematest TEST: interfaceschematest !!!!!!!!!!!!!!!!!! 18 FAILED FAIL: interfaceschematest TEST: networkschematest !!!!!!!!!!! 11 FAILED FAIL: networkschematest TEST: storagepoolschematest !!!!!!!!!!!!!!!!!!!! 20 FAILED FAIL: storagepoolschematest TEST: storagevolschematest !!!!!!!!!!!! 12 FAILED FAIL: storagevolschematest TEST: domainschematest !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 40 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 80 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 120 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 160 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 200 !! 202 FAILED FAIL: domainschematest TEST: nodedevschematest !!!!!!!!!!!!!! 14 FAILED FAIL: nodedevschematest TEST: nwfilterschematest !!!!!!!!!!!!!!!!!!!!!!!!!!! 27 FAILED FAIL: nwfilterschematest TEST: test_conf.sh .. 2 OK ---------------- snip --------------------------- ==================== 9 of 40 tests failed ==================== make[3]: *** [check-TESTS] Error 1 make[3]: Leaving directory `/tmp/libvirt-0.8.0/tests' make[2]: *** [check-am] Error 2 make[2]: Leaving directory `/tmp/libvirt-0.8.0/tests' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/tmp/libvirt-0.8.0/tests' make: *** [check-recursive] Error 1 ------------------------------------------------------------------------- However installation went fine. After I started create some snapshot, I am getting some remote error: root@hcl:~# xm li Name ID Mem VCPUs State Time(s) Domain-0 0 622 2 r----- 1755.3 Test 3 256 1 -b---- 4.4 root@hcl:~# virsh snapshot-create 3 error: unmarshalling remote_error root@hcl:~# virsh snapshot-create 3 test.xml error: unmarshalling remote_error I have even written a C code with API's but same problem. Here is livirt version n all root@hcl:/tmp/libvirt-0.8.0# libvirtd --version libvirtd (libvirt) 0.8.0 root@hcl:/tmp/libvirt-0.8.0# virsh -v 0.8.0 root@hcl:/tmp/libvirt-0.8.0# Any Idea???????????????? Any suggestion???????/ Thanks Tej DISCLAIMER: ----------------------------------------------------------------------------------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any mail and attachments please check them for viruses and defect. -----------------------------------------------------------------------------------------------------------------------

2 1

Re: [libvirt-users] Libvirt Compilation on MS Vista
by Matthias Bolte 21 Apr '10

21 Apr '10

2010/4/19 Tim McLeod <tim.mcleod(a)simulamen.eu>: > Does a comprehensive set of instructions on how to compile Libvirt on a > Microsoft Vista platform exist? Has this ever been accomplished? I would > very much appreciate input from persons who can give me confidence that a > Windows client application can be developed on top of Libviet that connects > to a QEMU system on an Ubuntu server. The Libvirt Windows Support page > (http://libvirt.org/windows.html) implies the exercise is trivial. Over the > last three weeks of failure I have come to find this assertion extremely > amusing. > Compiling libvirt for Windows in not very well documented. You can use the mingw32 cross-compile toolchain provided by Fedora. I think several people build libvirt for Windows this way. Another option is to use MinGW and MSYS on Windows to compile libvirt for Windows. I did that successfully. So before I start to describe the setup/compilation process and so on... could you describe what your current setup looks like and what problems you're facing? Matthias

2 1

[libvirt-users] Question about libvirt general storage driver/framework
by Povilas 21 Apr '10

21 Apr '10

Hello, I have setup consisting of few nodes dedicated to virtualisation and shared storage application. For running virtual machines we are using KVM, and libvirt to manage them. Also, I am trying to setup some tools for managing storage volumes. I know about libvirt storage pools and existing storage volumes support, but what I would like to see in libvirt is generic storage driver (ideally it could depend on external application or script), or some framework for managing storage. Now we are testing NBD setup, and for some reasons I don't want to use kvm-nbd. We would like to use custom nbd client and manage block device creation/deletion for ourselves. Maybe in future we will use iSCSI instead of NBD, so platform/transport agnostic framework or driver would be very helpful. I've searched and read both mailing lists (libvir-list and libvirt-users), and have found that some libvirt users were asking for similar or same feature. E.g : https://www.redhat.com/archives/libvir-list/2009-August/msg00348.html So, the main question is: maybe there is some progress already done or someone is thinking about working on it ? -- Regards, Povilas

1 0

[libvirt-users] New Snapshot API Not working
by Tej Parkash, ERS, HCLTech 21 Apr '10

21 Apr '10

All, I have compiled new libvirt library 0.8.0. Compilation and installation went really fine except "make check" which has show some test got failed. Here is what make check said. Failed Test: ---------------snip----------- PASS: statstest TEST: qparamtest ................................ 32 OK PASS: qparamtest TEST: capabilityschematest !!!!!!!!!!!! 12 FAILED FAIL: capabilityschematest TEST: interfaceschematest !!!!!!!!!!!!!!!!!! 18 FAILED FAIL: interfaceschematest TEST: networkschematest !!!!!!!!!!! 11 FAILED FAIL: networkschematest TEST: storagepoolschematest !!!!!!!!!!!!!!!!!!!! 20 FAILED FAIL: storagepoolschematest TEST: storagevolschematest !!!!!!!!!!!! 12 FAILED FAIL: storagevolschematest TEST: domainschematest !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 40 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 80 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 120 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 160 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 200 !! 202 FAILED FAIL: domainschematest TEST: nodedevschematest !!!!!!!!!!!!!! 14 FAILED FAIL: nodedevschematest TEST: nwfilterschematest !!!!!!!!!!!!!!!!!!!!!!!!!!! 27 FAILED FAIL: nwfilterschematest TEST: test_conf.sh .. 2 OK ---------------- snip --------------------------- ==================== 9 of 40 tests failed ==================== make[3]: *** [check-TESTS] Error 1 make[3]: Leaving directory `/tmp/libvirt-0.8.0/tests' make[2]: *** [check-am] Error 2 make[2]: Leaving directory `/tmp/libvirt-0.8.0/tests' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/tmp/libvirt-0.8.0/tests' make: *** [check-recursive] Error 1 ------------------------------------------------------------------------- However installation went fine. After I started create some snapshot, I am getting some remote error: root@hcl:~# xm li Name ID Mem VCPUs State Time(s) Domain-0 0 622 2 r----- 1755.3 Test 3 256 1 -b---- 4.4 root@hcl:~# virsh snapshot-create 3 error: unmarshalling remote_error root@hcl:~# virsh snapshot-create 3 test.xml error: unmarshalling remote_error I have even written a C code with API's but same problem. Here is livirt version n all root@hcl:/tmp/libvirt-0.8.0# libvirtd --version libvirtd (libvirt) 0.8.0 root@hcl:/tmp/libvirt-0.8.0# virsh -v 0.8.0 root@hcl:/tmp/libvirt-0.8.0# Any Idea???????????????? Any suggestion???????/ Thanks Tej DISCLAIMER: ----------------------------------------------------------------------------------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any mail and attachments please check them for viruses and defect. -----------------------------------------------------------------------------------------------------------------------

1 0