similar to: Couple of libvirtd warnings

Hi I'm trying to hotplug an usb device into kvm but the device is not attached this is the definition: cat kingston.xml <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x1131' /> <product id='0x1001' /> </source> </hostdev> the attach and detach

Hello all, I'm using libvirt 0.8.3 on Debian Lenny (package provided in lenny-backports). After restarting libvirtd, I cannot start VM anymore. The daemon is restarted, but each time I try to start a domain, I get this message : virsh # start vm2 error: Failed to start domain vm2 error: internal error Process exited while reading console log output: When daemon is started with -v

I'm seeing this problem with both the virtio and e1000 driver with both linux and windows guests. About 5 - 10% of the VMs I launch have network problems. They seem to always get an IP from the DHCP server (dnsmasq), but afterwards either they can not make an outside network connection or they lose connectivity at a later time. Sometimes the connectivity comes back, sometimes it doesn't.

Hi, I want to migrate from vmware to KVM. Therefore I have installed debian stable (lenny) and create two virtual machines (KVM). Both (XP as well as Vista) running fine. After upgrading to debian testing (sqeeze) both XP-guest as well as Vista-guest didn't start anymore. Both are failing during preparation, probably because of a network-problem. I will give XP as an example: cat

Hi, squeeze host, winxp guest. guest fails to start: PCI: devfn 24 not available fpr virtio-net-pci, in use by virtio-blk-pci Error initializing virtio-net-pci xml-File: ======== <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/var/lib/winxp'/> <target dev='hda'

Hello everybody, i've defined a simple network, with no dhcp. I'd like to use dnsmasq only as a dns server. $ virsh net-dumpxml basicswitch <network> <name>basicswitch</name> <uuid>60f491d2-d6c4-6b57-8a50-081cace8dedc</uuid> <forward mode='nat'/> <bridge name='virbr1' stp='on' delay='0' /> <ip

I hope this is simple I have one kvm host that lists all my domains even after shut down. 'virsh list --all' shows machines in 'running' and 'shut off' states. If I copy those over to another machine and it only shows the virt machines in running state. vmhost2:~$ virsh list --all Id Name State ---------------------------------- 4 mybox4

It seems virsh 0.8.3 cannot connect to libvirtd 0.6.3. Machine 1: iibvirtd is 0.6.3 Machine 2: virsh 0.6.1 virsh -c xen+ssh://root at 192.168.1.78 list Connecting to uri: qemu:///session Id Name State ---------------------------------- 0 Domain-0 running 1 shanxi idle Machine 3: virsh 0.8.3 virsh -c xen+ssh://root at 192.168.1.78 list error:

Hi! Occasionally of late, I've seen a few cases where libvirtd cpu usage shoots up to 100% and stays there indefinitely. This seems to happen when a QEMU VM is starting up, although on one occasion I *think* I saw it happen after a QEMU VM was p2p-migrated. Doing strace -f -p <libvirtd pid> reveals a flood of poll() functions calls like these: [pid 1690] poll([{fd=3,

Hello everybody, I am a new user discovering libvirt with KVM software. During my first VM creation, I saw an issue with virsh that I can't understand. I wanted to emulate another CPU than the classical qemu32 using virsh. So I used the virsh capabilites command to detect how is detected my CPU host which is an Intel Xeon E5410 and my problem is that this CPU is detected only with the

Hi, Anybody know how to build libvirt on Mac OSX 10.6 ? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/libvirt-users/attachments/20100215/ee529872/attachment.htm>

Are there any recommendations as to how often a new connection should be made versus reused? Right now we create a new connection *every time* we hit libvirt for something. We can easily change this so that a single connection is made for a series of libvirt calls, or even so that a single connection is used for the lifetime of the running application. What are the issues to consider when making

Are there any recommendations as to how often a new connection should be made versus reused? Right now we create a new connection *every time* we hit libvirt for something. We can easily change this so that a single connection is made for a series of libvirt calls, or even so that a single connection is used for the lifetime of the running application. What are the issues to consider when making

Hi, in order to get hook scripts to work, I used a backported version of libvirtd on Ubuntu 10.04 LTS. Here are the details: Compiled against library: libvir 0.8.3 Using library: libvir 0.8.3 Using API: QEMU 0.8.3 Running hypervisor: QEMU 0.12.5 After adjusting the apparmor profile to accept the hook scripts under /etc/libvirt/hooks/, I am able to start and stop domains again, but only the

Hello, We are using libvirt 0.8.3 to build KVM guests (KVM version is qemu-kvm 0.12.5). I see kvm supports aio flag with either native or threads option. Where in libvirt XML should we define aio option? Thanks in advance Ranga -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hey All, I'm just wondering whether this is what caused my server to crash. Started last night in NZ land. Jun 20 19:22:11 elm dovecot: imap-login: Disconnected (tried to use disallowed plaintext auth): user=<>, rip=attackerip, lip=10.0.0.3, session=<0C8LzpDfZQDINsQC> occasionally get Jun 20 19:22:52 elm dovecot: imap-login: Disconnected (no auth attempts in 1 secs):

Hi, Is there a reasonable way to alternately use several versions of libvirtd on the same system? I ask because there are features of 0.9.X I want to experiment with, yet also need to use the systems where I'm doing that to connect via virt-manager and virsh to non-experimental systems running 0.8.8 and 0.8.3 on Ubuntu - which the compiled-from-tar 0.9.x has an incompatibility with. As far

Dear All, I have upgrade my hypervisors: qemu-kvm 0.12.5 => 1.1.2 libvirt-bin 0.8.3-5 => 0.9.12.3 (debian6 to debian7) After that upgrade, i noticed that live migration was most of the time failing (freeze) (not always) I also noticed that creating a machine with the updated hypervisor was always working. After some days of

Hi, I've updated my Debian lenny to Debian squeeze last week. So I have now: libvirt 0.8.3-5 qemu-kvm 0.12.5+dfsg-3 virt-manager 0.8.4-8 Today I try to start my Vista quest again. I am surprised because it won't starts. In "/var/log/libvirt/qemu/devel-vista.log" stands "Read failed". The Console stays as a black screen after a short SeaBIOS message. I tried

On Fri, Jul 04, 2014 at 11:04:53AM +0200, Benoit Rousselle wrote: > Dear All, > > I have upgrade my hypervisors: > qemu-kvm 0.12.5 => 1.1.2 > libvirt-bin 0.8.3-5 => 0.9.12.3 > (debian6 to debian7) > > After that upgrade, i noticed that live migration was most of the time > failing (freeze) (not always) >