- Users - libvirt List Archives

[libvirt-users] Usage serial device
by David Goulet 04 Oct '11

04 Oct '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I'm trying to connect the *same* serial device to two KVM Linux machines where one is running KGDB and the other uses the connected serial to interact with the target machine running under KGDB. However, I'm unable to do so. Using a pty port, I am able to use my kgdb setup with host/VM but unable to make it work with VM/VM since it's two different pty created on the two machines. Anyone on this list can help me with that kind of setup ? Unfortunately, I must use libvirtd 0.7.5 for now... I'm aware that it might be a version issue here but still... Thanks! David -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJOihLOAAoJEELoaioR9I02GawH/1Ux197Pj3F+Qf54LcI3yy+w Vhd8yOGIAreBES7FUIf/7dCFqUz2mXFbtRuo9KZi+M0qs02kEs/nbhgOJLmHdZFA iRdCprzCR4Ue1x8H/tVogfBElfGhlJDaPHx5KIsxDmXwPJYhrPBt8qhyzLSTVQZG /pibv03sQdGRM6ZIyIhbA3ZmZ7Yh0SToGl3Fodw5Yp6YjrxRtpTu/OkHuHweM+nq wxthsgVstAEjJSxwV5O1+GzQ8xVDzjvZTvSRXnU2mTKXTiW2CkbnPbDG7cYfAcdx jICcAOf4AHtuKt5ZTfXFMUT4qSPfEntoXKsjt1IpCOpYH70GNGxLkh96SKjS1+w= =AYT3 -----END PGP SIGNATURE-----

2 1

[libvirt-users] Second VM cannot get dhcp ip in NAT mode
by Magicloud Magiclouds 03 Oct '11

03 Oct '11

Hi, Yesterday I started to use libvirt with kvm under centos6. The first VM works great. Today I added another VM and start to initialize with virt-install. Well, it seems that, the second VM cannot get dhcp ip. I did not change the default libvirt network configuration. What should I do? -- 竹密岂妨流水过山高哪阻野云飞

2 3

[libvirt-users] qemu+ssh fails with "packet received from server too large"
by Trey Dockendorf 01 Oct '11

01 Oct '11

I'm attempting to connect to my KVM host from a remote system, but am unable to connect using virsh. I'm able to connect if I disable sasl on the KVM host... The KVM host is on CentOS 6 x86_64 with libvirt-0.8.1 Here's the command I'm using, --------- $ virsh -c qemu+ssh://kvmhost.tld/system error: packet received from server too large error: failed to connect to the hypervisor Here's the uncommented lines in my /etc/libvirt/libvirtd.conf ----------- listen_tls = 1 listen_tcp = 0 listen_addr = "...." (set to eth0) key_file = "/var/lib/puppet/ssl/private_keys/kvmhost.tld.pem" cert_file = "/var/lib/puppet/ssl/certs/kvmhost.tld.pem" ca_file = "/var/lib/puppet/ssl/certs/ca.pem" log_level = 1 log_filters="1:remote 1:event" log_outputs="1:syslog:libvirtd 1:file:/var/log/libvirt/libvirtd.log" There is no output in /var/log/libvirt/libvirtd.log while trying to connect remotely through virsh. The only logs that are generated are /var/log/secure, -------------- Sep 30 19:34:53 kvmhost sshd[20074]: Accepted publickey for foreman from 10.1.0.1 port 55269 ssh2 Sep 30 19:34:53 kvmhost sshd[20074]: pam_unix(sshd:session): session opened for user foreman by (uid=0) Sep 30 19:34:53 kvmhost sshd[20074]: pam_unix(sshd:session): session closed for user foreman I've also opened up the port through iptables, 1 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:16514 And I don't see anything being blocked by SELinux during these connection attempts. Is there possibly a log filter I could enable to shed more light on this? Any help is greatly appreciated. Thanks - Trey

1 0

[libvirt-users] Difficutlies with lp port
by Anselmo 30 Sep '11

30 Sep '11

Hello, I'm using libvirt on debian as host and Windows XP Home as guest. I would like to pass the /dev/parport0 to XP to attach a printer. I use virt-manager. When I add a parallel port as a "dev" type I got this conf file: .... <parallel type='dev'> <source path='/dev/parport0'/> <target port='0'/> </parallel> .... And this command line: .... -chardev tty,id=charparallel0,path=/dev/parport0 -device isa-parallel,chardev=charparallel0,id=parallel0 .... The first parameter is "tty".Should not it be "parport"? Anyway I never see any parallel port on the guest with these options. Even starting kvm from the command line. While is seems to work immediatly using the kvm option: "-parallel /dev/parport0" Where i've made a mistake? Or how can I just tell libvirt to use the "-parallel" option instead. Thank's for your help Anselmo Luginbühl

1 0

[libvirt-users] win7 instance just disappears
by Alex 30 Sep '11

30 Sep '11

Hi, I have a fedora15 box with a win7 kvm instance that has been running for some time, but lately it seems to just crash and disappear without any idea of what happened. It's never happened while I have been using it, only when the instance is idle. I usually start the instance using virt-manager, but also start it just using "virsh start mykvm" then access it using the spicec client. I can't find any logging information to indicate why this is happening or how to go about fixing it. I've tried accessing it using the normal virt-manager client as well as the spicec client an it doesn't make any difference. When it crashes, the whole process is gone. Is there something that could cause it to do this when the system is idle? I also installed the qxl video drivers (qxl-win-0.1010-20110308-d9eb3203bd) some time ago, so it could possibly be related to that. I thought it might be helpful to have a copy of the qemu XML file: <domain type='kvm'> <name>alex-win7</name> <uuid>f7decb31-88cf-d003-8716-66258550b996</uuid> <memory>3145728</memory> <currentMemory>3145728</currentMemory> <vcpu>1</vcpu> <os> <type arch='x86_64' machine='pc-0.14'>hvm</type> <boot dev='hd'/> </os> <features> <acpi/> <apic/> <pae/> </features> <cpu match='exact'> <model>Opteron_G3</model> <vendor>AMD</vendor> <feature policy='require' name='skinit'/> <feature policy='require' name='vme'/> <feature policy='require' name='mmxext'/> <feature policy='require' name='fxsr_opt'/> <feature policy='require' name='cr8legacy'/> <feature policy='require' name='ht'/> <feature policy='require' name='3dnowprefetch'/> <feature policy='require' name='3dnowext'/> <feature policy='require' name='wdt'/> <feature policy='require' name='extapic'/> <feature policy='require' name='pdpe1gb'/> <feature policy='require' name='osvw'/> <feature policy='require' name='cmp_legacy'/> <feature policy='require' name='3dnow'/> </cpu> <clock offset='localtime'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/qemu-kvm</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/home/libvirt-images/alex-win7.img'/> <target dev='hda' bus='ide'/> <address type='drive' controller='0' bus='0' unit='0'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/home/libvirt-images/alex-win7a-2.img'/> <target dev='vda' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </disk> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:6c:6c:47'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='spicevmc'> <target type='virtio' name='com.redhat.spice.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'/> <graphics type='spice' autoport='yes'/> <sound model='ich6'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </sound> <video> <model type='qxl' vram='9216' heads='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </memballoon> </devices> </domain> Thanks, Alex

1 0

[libvirt-users] ANNOUNCE: Perl binding release Sys-Virt version 0.9.5
by Daniel P. Berrange 30 Sep '11

30 Sep '11

I am pleased to announce a new release of the Perl binding, Sys::Virt version 0.9.5, is now available for download: http://search.cpan.org/CPAN/authors/id/D/DA/DANBERR/Sys-Virt-0.9.5.tar.gz Changes in this release - Add all new APIs in libvirt 0.9.5 - Add missing snapshot creation/lookup methods - Fix typo in method listing snapshots - Add missing snapshot constant - Add example for save/restore usage - Re-add abort job binding accidentally deleted All historical releases and online documentation are available from the CPAN page http://search.cpan.org/dist/Sys-Virt/ There is no planned update for libvirt 0.9.6, since that did not introduce any new APIs that require work in the Perl layer. Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|

1 0

[libvirt-users] virsh cannot list broken guest.
by Magicloud Magiclouds 29 Sep '11

29 Sep '11

Hi, I am starting to learn using libvirt with kvm on CentOS 6. Just used this command to start a guest: virt-install -ntest -r1024 --vcpus=1 -c/var/lib/libvirt/images/CentOS-6.0-x86_64-netinstall.iso --os-type=linux --os-variant=rhel6 --disk vol=kvmguests/test --vnc -v --virt-type=kvm --check-cpu --prompt --arch=x86_64 Then I found out that I misconfigured vnc. And I do not know how to gracefully stop qemu. So I killed it. Then with the command, I got: ERROR Guest name 'test' is already in use. What is the name of your virtual machine? But at this time, there is nothing listed in virsh: Welcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh # list Id Name State ---------------------------------- virsh # connect qemu:///system virsh # list Id Name State ---------------------------------- virsh # What should I do? -- 竹密岂妨流水过山高哪阻野云飞

1 2

[libvirt-users] Snapshot Error
by huachao yao 29 Sep '11

29 Sep '11

Hey When I want to take a snapshot for a Domain by using virDomainSnapshotCreateXML. The Error as below happen: libvir: QEMU error : Requested operation is not valid: Disk '/var/lib/libvirt/images/fedora-qcow.qcow2' does not support snapshotting The snapshot Configuration is : <domainsnapshot> <description>Snapshot of OS install and updates</description> <disks> <disk name='/var/lib'> <source file='/var/lib-snapshot'/> </disk> <disk name='vdb' snapshot='no'/> </disks> </domainsnapshot> And /var/lib/libvirt/images/fedora-qcow.qcow2 is the disk for the domain (use qemu-img to create). And I had tried another Disk format (*.img), but the error still happen. how can i deal with this error?? PS:qemu version is 0.14 & libvirt version is 0.9.4. Pls help. :-(

3 2

[libvirt-users] how to convert from xen .cfg files to libvirt xml?
by Mauro 28 Sep '11

28 Sep '11

I have a .cfg configuration file for a xen virtual machine. I need to convert it in xml format to use with libvirt. So I run virsh domxml-from-native xen-xm backupsrv.cfg but I have an error: error: Unknown failure. How can I investigate about the error?

2 7

[libvirt-users] virsh edit problems
by Robin Lee Powell 27 Sep '11

27 Sep '11

I've got a problem where I can't access my console (well, I can', but I can't type in a password), which I don't think is a libvirt issue but any help or commentary is certainly welcome http://thread.gmane.org/gmane.comp.emulators.kvm.devel/79561 , and I'm trying to debug it by trying out different console/serial options in my .xml file, and I can't change them. What I have now: <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> No matter what I change, whether I use "virsh edit" or edit the files directly, even with libvirt off, as soon as libvirt notices (i.e. when I turn it back on) my changes get blown away and it ends up looking just like the above. Even as simple a thing as changing the port number, or removing the console, or adding a second serial... all gone. Oh, wait, that's not quite true; adding a second serial *does* work. But nothing else I've tried does. What I'm actually trying to do is copy the docs http://libvirt.org/formatdomain.html#elementsConsole more closely and specify my own source paths; I'm worried that the serial and the console are somehow ending up in the same place and maybe that's causing my problem? What I've been trying to do is something like: <serial type='pty'> <source path='/dev/pts/3'/> <target port='0'/> </serial> <console type='pty'> <source path='/dev/pts/4'/> <target port='0'/> </console> And it just won't stick. Maybe that's not even my problem, but it's not showing any errors, and it's annoying me and I'd like to understand why. -Robin

2 2