Displaying 20 results from an estimated 5000 matches similar to: "libvirt restarting vms on restart?"
2010 Feb 11
1
libvirt attaching wrong usb device?
I'm trying to attach a USB device which is attached to my host to a
guest instance. The device definition in the XML looks like:
<hostdev mode='subsystem' type='usb' managed='yes'>
<source>
<vendor id='0x046d'/>
<product id='0xc111'/>
</source>
</hostdev>
and the device
2007 May 16
8
2.6.20-1-amd64 Xen with RHEL5 guest
Hi
I am having some problems installing a paravirt RHEL guest on a deb amd64 xen
machine
uname -a = Linux debxen 2.6.20-1-xen-amd64 #1 SMP Tue Apr 24 22:23:22 UTC 2007
x86_64 GNU/Linux ============== xm info ==============
host : debxen
release : 2.6.20-1-xen-amd64
version : #1 SMP Tue Apr 24 22:23:22 UTC 2007
machine : x86_64
2008 Feb 26
7
[PATCH]Add free memory size of every NUMA node in phsical info
Returns free memory size per node in "xm info". This info can help users
who want to bind their guest domain in one node of their NUMA machines
thought set CPU affinity. I also write IA64 part support which I would
send to XEN-IA64 mail-list. Thanks.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
2007 Dec 06
7
[PATCH] Fix ioemu compile
# HG changeset patch
# User john.levon@sun.com
# Date 1196969481 28800
# Node ID 2c28ac4db1f7542220b1472821e8631b79b6a23a
# Parent 4a98d4b6e4daccd610175e3c0f8cab49b056c649
Fix ioemu compile
serial.c was including another Linux-specific header.
Signed-off-by: John Levon <john.levon@sun.com>
diff --git a/tools/ioemu/hw/serial.c b/tools/ioemu/hw/serial.c
--- a/tools/ioemu/hw/serial.c
+++
2007 Jun 21
19
Writing a tool for Shared Persistent Windows Boot Image
Before, in my "Hard Problem" email I was trying to communicate a
design issue were trying to solve with Xen.
This is what we need to do:
1) Deploy 24 Windows XP VMs in parallel.
2) Boot them from a shared Windows XP C: drive.
3) Since this is a read-only shared image we obviously can''t have
multiple VM''s writing to it.
4) All writes to the boot image for logging,
2007 Jun 21
19
Writing a tool for Shared Persistent Windows Boot Image
Before, in my "Hard Problem" email I was trying to communicate a
design issue were trying to solve with Xen.
This is what we need to do:
1) Deploy 24 Windows XP VMs in parallel.
2) Boot them from a shared Windows XP C: drive.
3) Since this is a read-only shared image we obviously can''t have
multiple VM''s writing to it.
4) All writes to the boot image for logging,
2010 Mar 04
1
Regarding SPICE
Hi,
I have set up KVM on FC12.
I was wondering if its possible to Display the VM using spice + libvirt?
As in, if I can define my domain with graphics like:
<graphics type='spice' port='-1' autoport='yes' listen='0.0.0.0'/>
or
<graphics type='spice' port='5903' '
2007 May 22
6
xen version compatibility
If I have a linux kernel on dom0 from xen 3.0.2 and my xen binary is
version 3.1.0, can I expect things to work? What about if my dom0
kernel and xen binary are both 3.1.0 and I have a para virt domU with
xen 3.0.2 code in? What about if the tools are from a different
version of xen?
I''m asking because I''m running fedora 6 and I''d like to try out xen
3.1.0 or 3.0.4
2010 Jan 26
1
domain definition storage
Hi,
I defined several xen domains with libvirt. Can anybody tell me where
libvirt stores these definitions? E.g. what files would one need to back up?
Is it correct, that the xen domain definitions in /var/lib/xend/domains
are overwritten regularly by libvirt?
Many thanks,
Arik
2010 Mar 13
1
behaviour of "virsh shutdown domainName"
Hi all,
I am experiencing some problems with different versions of libvirt
(0.7.5 and 0.7.7), with a kvm (WinXP), host running Ubuntu 9.10, and i
would like to ask you two questions:
- In virsh, after running the command "shutdown domainName", what
should be the final state of the domain, if the shutdown finishes
correctly: "shutoff", "no-state",
2007 Feb 13
5
ATI fglrx patch, OpenGL is working
Hi all.
have fglrx driver working with xen, opengl runs fine for me.
see http://pastebin.ca/350588
it''s tested with kernel 2.6.19, driver version 8.33.6, xen version 3.0.3 and
3.0.4
thanks to Jacob Gorm Hansen for suggestions
testing, feedback (and bugreports - hope not) are welcome
Christian
--
"Without music to decorate it, time is just a bunch of boring production
2010 Jul 29
1
Too many active clients?
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
2008 Jul 19
11
HVM direct boot broken in xen-unstable
Hi!
On x86_64, changeset 18081, running/building on rhel5, trying to use the HVM direct boot causes the domain to reboot immediately and then the log says the domain is restarting too rapidly. No obvious hints as to where the problem is. If I build the in-tree ioemu code, things work. Any clues as to where to look or how to get some useful debugging output?
Thanks,
John Byrne
2009 May 28
1
[PATCH node] Temporarily disable security driver.
I've uploaded a new libvirtd based on the latest release into F12
but it requires a selinux config which we do not have on the node.
This is a temporary hack to make it work until we go to an F11 node.
Must remember to remove this for F11!!
Signed-off-by: Ian Main <imain at redhat.com>
---
scripts/ovirt-functions | 5 +++++
1 files changed, 5 insertions(+), 0 deletions(-)
diff
2007 May 16
6
Keyboard change
Hello,
it''s not the first time but ... Who know?
Well, I use xen in HVM. All works fine, my keyboard in Dom0 is AZERTY, but
this keyboard become QWERTY when i enter in VM, it''s not useful to type
password.
How can i keep my keyboard AZERTY in my VM and in Dom0?
--
Benjamin HENRION
Elève de 4eme année de l'' EXIA (Nancy)
Ecole supérieure d''informatique
Spé
2008 Mar 25
2
Re: [Fedora-xen] RHEL5 - Xend will not start after software upgrade
Hello,
Recently I ran yum update on a RHEL5 x86_64 machine and as part of the update, the following packages were installed:
Updated: xen-libs-3.0.3-41.el5.x86_64
Updated: xen-libs-3.0.3-41.el5.i386
Installed: kernel-xen-2.6.18-53.1.14.el5.x86_64
Updated: xen-3.0.3-41.el5.x86_64
After the update, I rebooted the machine. Now, I cannot get xend to start:
2010 May 05
1
libvirtd loses all of its data after restart
Hi,
I'm having a problem with libvirtd (backend being kvm) losing its if I restart
it with /etc/init.d/libvirtd restart.
What I did was:
Start libvirtd
Connect to it using virsh
Create a new storage pool with pool-create-as
Create some volumes with vol-create-as
Create some virtual machines with create
Restart libvirtd using /etc/init.d/libvirtd restart
Reconnect with virsh
After
2008 Aug 12
2
Announcing: Open OVF project source code availibility
Announcing the open-ovf project and source code availibility.
Hi folks, we are announcing the availibility of source code for the
open-ovf project.
OVF is a standard packaging format for virtual machines and software
appliances. The open-ovf project is seeking contributors and users to
help establish OVF as a transparent and platform-nuetral method for
packaing virtual machine images.
We
2010 Feb 03
1
[libvirt] [LXC] Tyring to locate livbvirt operations for LXC relocation
Hello,
I am searching for the libvirt operations for relocating LXC (system or
application) containers. LXC relocation mechanism is done by checkpoint /
restart. I went over libvirt API documentation and found the following
methods:
virDomainSave that receives a domain and path to state file. The method
saves domain's memory contents into a disk file.
virDomainRestore that receives a domain
2007 Jun 01
6
PATCH: Use name instead of pid in QEMU logs
The attached patch changes the logfile name generated by qemu-dm to use the
pattern qemu-dm-[NAME].log instead of qemu-dm-[PID].log. This makes it
easier for the adminsitrator to figure out which log corresponds to which
guest (particularly after a crash where you no long know what PID the
qemu-dm process for your guest had). It also prevents the number of log
files from growing unbounded.