IIRC, this was a problem with older versions of QEmu that was fixed later.
Are you on a recent version? You should be able to run a single VCPU,
Windows XP instance *without* ACPI and have low CPU usage. I've done it.
Note, this problem still exists for multi-VCPU XP instances.
.:. jeremy
On Mon,
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 : Unexp
On Mon, Aug 9, 2010 at 1:13 PM, jeremy avnet
> wrote:
> 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.
Interestingly, if I restrict the host machine to only ever
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
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 libvirt
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.cr
On Wed, Jun 9, 2010 at 1:38 AM, Daniel P. Berrange wrote:
> I guess you restarted libvirtd - there was a bug that causes it to
> forget the interface name if you restart it.
Is there a way of reminding it? :-/
Thanks for your response.
.:. jeremy
___
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:
Compared to the others which have:
This is problematic as I wanted to use domifstat o
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
___
libvirt-users mailing list
libvirt-users@redhat
On Tue, Apr 20, 2010 at 11:01 AM, Wang David wrote:
> Apr 19 17:27:36 virtualserver3 kernel: [14202.411373] type=1503
> audit(1271723256.513:75): operation="open" pid=3147 parent=1
> profile="libvirt-20030353-cdee-109a-1abb-dc4971d036c2" requested_mask="r::"
> denied_mask="r::" fsuid=0 ouid=0
> n
On Mon, Apr 19, 2010 at 5:31 PM, Wang David wrote:
> -
>
> +
>
Why are you changing this? Unless you've gone through extra steps to
configure your guest OS to use this different driver and location of the
boot disk, it's going to fail to boot. Perhaps try leaving this line
unchanged
On Mon, Apr 19, 2010 at 6:02 AM, Chris Lalancette wrote:
> Unfortunately, that is the expected behavior. If you do:
>
> # brctl show
> # /etc/init.d/networking restart
> # brctl show
I also have this problem when I net-destroy/net-start the libvirt network in
order to load a new network definit
You should try connecting to the VM via VNC and see what's happening on that
side. The XML you pasted was for a VM not running, when it's running, you'll
see a port defined in .
Did you enter those MAC addresses or did you let libvirt generate them for
you?
.:. jeremy
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 connecti
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 connecti
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 s
log/2010/01/compiling-libvirt-and-ruby-libvirt-on-mac-os-x/
For reference, I'm on Snow Leopard and use MacPorts. I've successfully used
virsh on OS X to connect to a remote libvirtd server.
.:. jeremy avnet / brainsik
libvirt-0.7.6_OSX.patch
Description: Binary data
libvirt-0.7.6_OSX.READM
17 matches
Mail list logo
