search for: avnet

Regardless of the filesystem (i''ve used reiserfs, xfs, ext3), whenever I mount a fresh DRBD partition I get some nasty kernel messages. This is under Debian Sarge, Xen kernel 2.6.11.12-xen0 (dom0) using DRBD v0.7.11 (pulled from Debian "testing"). This is what I did to create the partition. On both nodes I created a new LVM storage device and started DRBD: # lvcreate

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

I have over 20 guests running on a particular host and the three longest running ones are missing the network device information in their XML description: <interface type='network'> <mac address='54:52:10::f2:c5'/> <source network='local'/> </interface> Compared to the others which have: <interface

Hello, I'm receiving a lot of these since a couple of days ago: libvirtd: 16:30:10.960: error : qemudDispatchServer:1282 : Too many active clients (20), dropping connection I'm trying to figure out where all these active clients are coming from. I have a daemon running the interacts with libvirtd, but it only creates two long-lived connections (I'm very sure). What constitutes an

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.

Sorry to spam the list, but wondering if anyone has any interest : Due to political motivations, my current employer has decided to stop utilizing ZFS based storage systems. This has left us with some Stec ZeusRAM devices that we now have no use for. Purchased brand new from Avnet in August of 2011, put into service in September, used for approx. 1 year. We have 6x disks available - part number Z4RZF3D-8UC. If anyone is interested, please email me off-list. -Matt Breitbach

Debian Sarge Xen 2.0.7 / Linux 2.6.11.12-xen0 bridged networking I started receiving these: Nov 17 16:03:41 host kernel: Dead loop on virtual device xen-br0, fix it urgently! Currently, I am running LVS on dom0. It is serving packets to a domU on the same physical machine and to a domU on a different machine. The messages started happening when we started hosting files for download and

I've seen this error a couple of times over the past month, but it's starting to happen more regularly now (perhaps since VM usage is increasing). The last few times I've seen it when trying to start a VM (virsh start domain): $ virsh start goat Connecting to uri: qemu:///system error: Failed to start domain goat error: internal error cannot parse QEMU version number in ' PC

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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/libvirt-users/attachments/20100429/30b2bd60/attachment.htm>

Hello. I just upgraded from libvirt 0.7.0 to 0.7.5 in Ubuntu Lucid and now my application will get into a hung state. I have to kill it at which point I get the following error from the Python bindings: Traceback (most recent call last): File "/usr/local/app/vm.py", line 246, in launch vm.create() File "/usr/lib/python2.6/dist-packages/libvirt.py", line 300, in create

Hello, I recently upgraded to libvirt 0.8.3 and qemu 0.12.5 and I'm seeing these messages in syslog: libvirtd: 09:52:34.591: warning : virStorageBackendQEMUImgBackingFormat:623 : Unexpected exit status '1', qemu probably failed libvirtd: 09:52:34.746: warning : qemudParsePCIDeviceStrs:1422 : Unexpected exit status '1', qemu probably failed I'm not having any problems, but