2010/1/15 Bryan Kearney :
> When using the java library, we are seeing libvirt error messages spit out..
> such as:
>
> libvir: Remote error : unable to connect to '/var/run/libvirt/libvirt-sock':
> No such file or directory
>
> Is there a means of supressing that logging via the api?
>
> -- bk
>
When using the java library, we are seeing libvirt error messages spit
out.. such as:
libvir: Remote error : unable to connect to
'/var/run/libvirt/libvirt-sock': No such file or directory
Is there a means of supressing that logging via the api?
-- bk
--
libvir-list mailing list
libvir-list
So the plan is still to start the feature freeze end of next friday
the 22 Jan and try to push 0.7.6 on the 29th.
This mean there is still one week to push features :-)
Daniel
--
Daniel Veillard | libxml Gnome XML XSLT toolkit http://xmlsoft.org/
dan...@veillard.com | Rpmfind RPM sea
On Fri, Jan 15, 2010 at 04:33:01PM +, Daniel P. Berrange wrote:
> On Fri, Jan 15, 2010 at 01:39:18PM +0100, Daniel Veillard wrote:
> > On Fri, Jan 08, 2010 at 05:22:58PM +, Daniel P. Berrange wrote:
> > > All guest devices now use a common device address structure
> > > summarized by:
> > >
On Fri, Jan 08, 2010 at 05:23:30PM +, Daniel P. Berrange wrote:
> Replace
>
>-balloon virtio
>
> With
>
>-device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3
>
> This allows it to get correct assigned PCI address as declared in
> previous patch
ACK,
Daniel
--
Daniel Veill
On Fri, Jan 08, 2010 at 05:23:29PM +, Daniel P. Berrange wrote:
> Instead of relying on QEMU to assign PCI addresses and then querying
> them with 'info pci', manually assign all PCI addresses before starting
> the guest. These addresses are not stable across reboots. That will
> come in a lat
On Fri, Jan 08, 2010 at 05:23:28PM +, Daniel P. Berrange wrote:
> QEMU always configures a VGA card. If no video card is included in
> the libvirt XML, it is neccessary to explicitly turn off the default
> using -vga none
>
> * src/qemu/qemu_conf.c: Pass -vga none if no video card is configure
On Fri, Jan 08, 2010 at 05:23:27PM +, Daniel P. Berrange wrote:
> Not all QEMU builds default to SDL graphics for their display.
> Newer QEMU now has an explicit -sdl flag, which we can use to
> explicitly request SDL intead of relying on the default. This
> protects libvirt against unexpected
On Fri, Jan 08, 2010 at 05:23:26PM +, Daniel P. Berrange wrote:
> The old syntax was
>
>-chardev SOMECONFIG
>-nic user,guestfwd=tcp:IP:PORT-chardev:CHARDEV
>
> The new syntax is
>
>-chardev SOMECONFIG
>-netdev user,guestfwd=tcp:IP:PORT,chardev=ID,id=user-ID
> ---
> src/qemu/
Seem there is no way to get host CPU usage in libvirt API? I can get
freeMemory by virNodeGetFreeMemory, but no cpu usage API.
How about add a new api for it? The host CPU usage is also important for VM
creation and migration decision, like the free memory.
Yes, I know, I can got it from "top"...:
On Fri, Jan 08, 2010 at 05:23:25PM +, Daniel P. Berrange wrote:
> The old syntax is
>
> -pcidevice host=BUS:SLOT:FUNCTION
>
> The new syntax is
>
> -device pci-assign,host=BUS:SLOT:FUNCTION,addr=,id=host0
> ---
> src/qemu/qemu_conf.c | 51
> +
On Fri, Jan 08, 2010 at 05:23:24PM +, Daniel P. Berrange wrote:
> ---
> src/qemu/qemu_conf.c | 34 --
> 1 files changed, 32 insertions(+), 2 deletions(-)
>
> diff --git a/src/qemu/qemu_conf.c b/src/qemu/qemu_conf.c
> index 1ea61a9..3b39a91 100644
> --- a/src/
On Fri, Jan 08, 2010 at 05:23:23PM +, Daniel P. Berrange wrote:
> The old syntax was
>
>-usbdevice host:PRODUCT:VENDOR
>
> Or
>
>-usbdevice host:BUS.DEV
>
> The new syntax is
>
>-device usb-host,product=PRODUCT,vendor=VENDOR
>
> Or
>
>-device usb-host,hostbus=BUS,hostaddr
On Fri, Jan 08, 2010 at 05:23:22PM +, Daniel P. Berrange wrote:
> The previous syntax was severely limited in its options
>
> -usbdevice disk:/home/berrange/output.img
>
> The new syntax is the same as for other disk types
>
> -drive file=/home/berrange/output.img,if=none,id=usb-1,index=
On Fri, Jan 15, 2010 at 05:45:27PM +0100, Marc Haber wrote:
> Took that patch, applied it to Debian's 0.7.5-4 source package, built
> the package, installed it, same error.
Looks to me like the issue is still present in git head.
git clone
./autogen
create debian/ to allow building the debian pac
FYI, I pushed this simple fix.
Matthias
---
docs/news.html.in |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/docs/news.html.in b/docs/news.html.in
index 7e06096..83b394f 100644
--- a/docs/news.html.in
+++ b/docs/news.html.in
@@ -26,7 +26,7 @@ and check the ChangeLog t
On Fri, Jan 15, 2010 at 11:11:08AM +0100, Jim Meyering wrote:
> Updating to newer gnulib also pulled in a new sytnax-check
> test that evoked new warnings. No big deal, but I addressed them.
> The only trick was to see that the warnings about @SCHEMADIR@
> and @SYSCONFDIR@ were false positives. T
Updating to newer gnulib also pulled in a new sytnax-check
test that evoked new warnings. No big deal, but I addressed them.
The only trick was to see that the warnings about @SCHEMADIR@
and @SYSCONFDIR@ were false positives. To allow them, I defined
the variable in cfg.mk. See below.
>From 6e7
On Wed, Jan 13, 2010 at 03:56:03PM +0100, Paolo Bonzini wrote:
> On 01/08/2010 06:23 PM, Daniel P. Berrange wrote:
> >diff --git a/src/qemu/qemu_conf.c b/src/qemu/qemu_conf.c
> >index 5dcd50f..eded887 100644
> >--- a/src/qemu/qemu_conf.c
> >+++ b/src/qemu/qemu_conf.c
> >@@ -1592,6 +1592,9 @@ static
On Fri, Jan 08, 2010 at 05:23:20PM +, Daniel P. Berrange wrote:
> The current preferred syntax for disk drives uses
>
> -drive file=/vms/plain.qcow,if=virtio,index=0,boot=on,format=qcow
>
> The new syntax splits this up into a pair of linked args
>
> -drive file=/vms/plain.qcow,if=none,i
On Fri, Jan 08, 2010 at 05:23:21PM +, Daniel P. Berrange wrote:
> The current syntax uses a pair of args
>
>-net nic,macaddr=52:54:00:56:6c:55,vlan=3,model=pcnet,name=pcnet.0
>-net user,vlan=3,name=user.0
>
> The new syntax does not need the vlan craziness anymore, and
> so has a sim
On Fri, Jan 08, 2010 at 05:23:19PM +, Daniel P. Berrange wrote:
> The current syntax for audio devices is a horrible multiplexed
> arg
>
> -soundhw sb16,pcspk,ac97
>
> The new syntax is
>
> -device sb16,id=sound0
>
> or
>
> -device AC97,id=sound1,addr=
>
> NB, pcspk still uses
On Fri, Jan 08, 2010 at 05:23:18PM +, Daniel P. Berrange wrote:
> The current syntax for watchdogs is
>
> -watchdog i6300esb
>
> The new syntax will now be
>
> -device i6300esb,id=watchdogNN,addr=
> ---
> src/qemu/qemu_conf.c | 91
> +
On Fri, Jan 08, 2010 at 05:23:17PM +, Daniel P. Berrange wrote:
> The current character device syntax uses either
>
> -serial tty,path=/dev/ttyS2
>
> Or
>
> -chardev tty,id=serial0,path=/dev/ttyS2 -serial chardev:serial0
>
> With the new -device support, we now prefer
>
> -chardev fi
On Fri, Jan 15, 2010 at 05:42:31PM +0100, Daniel Veillard wrote:
> On Fri, Jan 08, 2010 at 05:23:16PM +, Daniel P. Berrange wrote:
> > When starting a guest, give every device a unique alias. This will
> > be used for the 'id' parameter in -device args in later patches.
> > It can also be used
On Fri, Jan 15, 2010 at 02:29:09PM +, Daniel P. Berrange wrote:
> If I were a betting man, I'd bet on this changeset which was missed
> from the 0.7.5 release
>
> http://libvirt.org/git/?p=libvirt.git;a=commit;h=c0a9b6a5338e54b64a4a28415ffbdb6bcc2b38c5
Took that patch, applied it to Debian's
On Fri, Jan 08, 2010 at 05:23:16PM +, Daniel P. Berrange wrote:
> When starting a guest, give every device a unique alias. This will
> be used for the 'id' parameter in -device args in later patches.
> It can also be used to uniquely identify devices in the monitor
>
> For old QEMU without -de
On Fri, Jan 15, 2010 at 01:39:18PM +0100, Daniel Veillard wrote:
> On Fri, Jan 08, 2010 at 05:22:58PM +, Daniel P. Berrange wrote:
> > All guest devices now use a common device address structure
> > summarized by:
> >
> > enum virDomainDeviceAddressType {
> > VIR_DOMAIN_DEVICE_ADDRESS_TY
On Fri, Jan 08, 2010 at 05:23:15PM +, Daniel P. Berrange wrote:
> Probe for the new -device flag and if available set the -nodefaults
> flag, instead of using -net none, -serial none or -parallel none.
> Other device types will be converted to use -device in later patches.
> The -nodefaults fla
On 01/15/2010 10:30 AM, Jim Fehlig wrote:
Update the API Extensions doc to reflect new source directory layout.
---
docs/api_extension.html.in |8
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/docs/api_extension.html.in b/docs/api_extension.html.in
index 59d3414..
On Fri, Jan 08, 2010 at 05:23:14PM +, Daniel P. Berrange wrote:
> Although the serial, parallel, chanel, input & fs devices do
> not have PCI address info, they can all have device aliases.
> Thus it neccessary to associate the virDomainDeviceInfo data
> with them all.
>
> * src/conf/domain_co
On Fri, Jan 08, 2010 at 05:23:13PM +, Daniel P. Berrange wrote:
> This patch introduces the support for giving all devices a short,
> unique name, henceforth known as a 'device alias'. These aliases
> are not set by the end user, instead being assigned by the hypervisor
> if it decides it want
On Fri, Jan 08, 2010 at 05:23:12PM +, Daniel P. Berrange wrote:
> The PCI device addresses are only valid while the VM is running,
> since they are auto-assigned by QEMU. After shutdown they must
> all be cleared. Future QEMU driver enhancement will allow for
> persistent PCI address assignment
On Fri, Jan 15, 2010 at 05:12:52PM +0100, Daniel Veillard wrote:
> On Fri, Jan 08, 2010 at 05:23:12PM +, Daniel P. Berrange wrote:
> > The PCI device addresses are only valid while the VM is running,
> > since they are auto-assigned by QEMU. After shutdown they must
> > all be cleared. Future Q
Update the API Extensions doc to reflect new source directory layout.
---
docs/api_extension.html.in |8
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/docs/api_extension.html.in b/docs/api_extension.html.in
index 59d3414..de6eedc 100644
--- a/docs/api_extension.html.i
Current implementation of x86Decode() used for CPUID -> model+features
translation does not always select the closest CPU model. When walking
through all models from cpu_map.xml the function considers a new
candidate as a better choice than a previously selected candidate only
if the new one is a s
This stops libvirt from probing for a libvirtd on the ESX server and
sets the base for the implementation of the secondary drivers.
---
src/Makefile.am|5 ++
src/esx/esx_device_monitor.c | 93 +++
src/esx/esx_device_monitor.h | 29 ++
On Fri, Jan 08, 2010 at 05:23:11PM +, Daniel P. Berrange wrote:
> Existing applications using libvirt are not aware of the disk
> controller concept. Thus, after parsing the definitions
> in the XML, it is neccessary to create elements
> to satisfy all requested disks, as per their defined dr
On Fri, Jan 08, 2010 at 05:23:09PM +, Daniel P. Berrange wrote:
> It is perfectly acceptable to have multiple sound devices of
> same type in guest configuration. If the underlying hypervisor
> does not like this, it is its job to complain, not the XML
> parser's
>
> * src/conf/domain_conf.c:
On Fri, Jan 08, 2010 at 05:23:08PM +, Daniel P. Berrange wrote:
> Hotunplug of devices requires that we know their PCI address. Even
> hotplug of SCSI drives, required that we know the PCI address of
> the SCSI controller to attach the drive to. We can find this out
> by running 'info pci' and
On Fri, Jan 08, 2010 at 05:23:10PM +, Daniel P. Berrange wrote:
> Temp hack
> ---
> src/qemu/qemu_monitor_text.c |9 +++--
> 1 files changed, 3 insertions(+), 6 deletions(-)
>
> diff --git a/src/qemu/qemu_monitor_text.c b/src/qemu/qemu_monitor_text.c
> index 52cd97c..2b8c1e8 100644
>
On Fri, Jan 08, 2010 at 05:23:07PM +, Daniel P. Berrange wrote:
> The current SCSI hotplug support attaches a brand new SCSI controller
> for every disk. This is broken because the semantics differ from those
> used when starting the VM initially. In the latter case, each SCSI
> controller is f
On Fri, Jan 08, 2010 at 05:23:06PM +, Daniel P. Berrange wrote:
> From: Wolfgang Mauerer
>
> This patch allows for explicit hotplug/unplug of SCSI controllers.
> Ordinarily this is not required, since QEMU/libvirt will attach
> a new SCSI controller whenever one is required. Allowing explicit
On Fri, Jan 15, 2010 at 03:13:25PM +0100, Marc Haber wrote:
> Hi,
>
> On Fri, Jan 15, 2010 at 11:43:26AM +, Matthew Booth wrote:
> > Could you please post the full domain XML, and the QEMU command line it
> > generated? You can get the latter from
> > /var/log/libvirt/qemu/.log. Can you also p
Hi,
On Fri, Jan 15, 2010 at 11:43:26AM +, Matthew Booth wrote:
> Could you please post the full domain XML, and the QEMU command line it
> generated? You can get the latter from
> /var/log/libvirt/qemu/.log. Can you also post the versions of
> qemu and libvirt?
$ cat /etc/libvirt/qemu/grml-te
On Fri, Jan 15, 2010 at 02:08:54PM +0100, Daniel Veillard wrote:
> On Fri, Jan 08, 2010 at 05:23:02PM +, Daniel P. Berrange wrote:
> > From: Wolfgang Mauerer
> >
> > This augments virDomainDevice with a element
> > that is used to represent disk controllers (e.g., scsi
> > controllers). The
2010/1/15 Matthew Booth :
> On 15/01/10 10:37, Matthias Bolte wrote:
>> 2010/1/14 Matthew Booth :
>>> I'm trying to use the ESX driver to extract metadata from ESX in an easily
>>> digestible form for driving V2V. I've noticed the domain XML seems to be
>>> missing a few bits:
>>>
>>>
>>
>> This i
On Fri, Jan 15, 2010 at 02:34:21PM +0100, Daniel Veillard wrote:
> On Fri, Jan 08, 2010 at 05:23:05PM +, Daniel P. Berrange wrote:
> > The current code for using -drive simply sets the -drive 'index'
> > parameter. QEMU internally converts this to bus/unit depending
> > on the type of drive. Th
On 15/01/10 10:37, Matthias Bolte wrote:
> 2010/1/14 Matthew Booth :
>> I'm trying to use the ESX driver to extract metadata from ESX in an easily
>> digestible form for driving V2V. I've noticed the domain XML seems to be
>> missing a few bits:
>>
>>
>
> This is currently not implemented, but co
On Fri, Jan 08, 2010 at 05:23:05PM +, Daniel P. Berrange wrote:
> The current code for using -drive simply sets the -drive 'index'
> parameter. QEMU internally converts this to bus/unit depending
> on the type of drive. This does not give us precise control over
> the bus/unit assignment though
On Fri, Jan 08, 2010 at 05:23:04PM +, Daniel P. Berrange wrote:
> To enable it to be called from multiple locations, split out
> the code for building the -drive arg string. This will be needed
> by later patches which do drive hotplug, the conversion to use
> -device, and the conversion to con
On Fri, Jan 08, 2010 at 05:23:03PM +, Daniel P. Berrange wrote:
> Convert the QEMU monitor APIs over to use virDomainDeviceAddress
> structs for passing addresses in/out, instead of individual bits.
> This makes the number of parameters smaller & easier to deal with.
> No functional change
>
>
On Fri, Jan 08, 2010 at 05:23:02PM +, Daniel P. Berrange wrote:
> From: Wolfgang Mauerer
>
> This augments virDomainDevice with a element
> that is used to represent disk controllers (e.g., scsi
> controllers). The XML format is given by
>
>
>
>
Actually we also allow decimal
On Fri, Jan 08, 2010 at 05:23:01PM +, Daniel P. Berrange wrote:
> When parsing the element specification, if no
> is provided for the disk, then automatically assign one based on
> the device name. This provides for backwards
> compatability with existing applications using libvirt, while al
On Fri, Jan 08, 2010 at 05:23:00PM +, Daniel P. Berrange wrote:
> Add the virDomainDeviceAddress information to the sound, video
> and watchdog devices. This means all of them gain the new XML
> element
>
>
>
> This brings them upto par with disk/net/hostdev devices which
> already have ad
On Fri, Jan 08, 2010 at 05:22:59PM +, Daniel P. Berrange wrote:
> Introduce a new structure
>
> struct _virDomainDeviceDriveAddress {
> unsigned int controller;
> unsigned int bus;
> unsigned int unit;
> };
>
> and plug that into virDomainDeviceAddress and
On Fri, Jan 08, 2010 at 05:22:58PM +, Daniel P. Berrange wrote:
> All guest devices now use a common device address structure
> summarized by:
>
> enum virDomainDeviceAddressType {
> VIR_DOMAIN_DEVICE_ADDRESS_TYPE_NONE,
> VIR_DOMAIN_DEVICE_ADDRESS_TYPE_PCI,
> };
>
> struct _virD
QEMU's command line equivalent for the following domain XML fragment
2
...
is
-smp 2,sockets=1,cores=2,threads=1
This syntax was introduced in QEMU-0.12.
Version 2 changes:
- -smp argument build split into a separate function
- always add ",sockets=S,cores=C,t
On Fri, Jan 08, 2010 at 05:22:57PM +, Daniel P. Berrange wrote:
> Only print out '.' for each test case, full test output can be
> re-enabled with VIR_TEST_VERBOSE=1, or VIR_TEST_DEBUG=
>
> Sample output now looks like
>
> TEST: statstest
> ..
2010/1/15 Daniel P. Berrange :
> On Fri, Jan 15, 2010 at 12:04:50PM +0100, Matthias Bolte wrote:
>> 2010/1/15 Matthias Bolte :
>> > 2010/1/14 Matthew Booth :
>> >> I'm trying to use the ESX driver to extract metadata from ESX in an easily
>> >> digestible form for driving V2V. I've noticed the doma
On 15/01/10 09:18, Marc Haber wrote:
> [my apologies for this re-post. I stupidly managed to hide the first
> instance of this mail away in an unrelated patch-thread and am thus
> afraid that the people who could have answered didn't see it]
>
> Hi,
>
> I have one test host running Debian unstabl
On Fri, Jan 15, 2010 at 12:04:50PM +0100, Matthias Bolte wrote:
> 2010/1/15 Matthias Bolte :
> > 2010/1/14 Matthew Booth :
> >> I'm trying to use the ESX driver to extract metadata from ESX in an easily
> >> digestible form for driving V2V. I've noticed the domain XML seems to be
> >> missing a few
2010/1/15 Jim Meyering :
> Matthias Bolte wrote:
>> Commit 5073aa994af460e775cb3e548528e28d7660fcc8 added an additional
>> '}' to a case block that messed up the block structure of the get_files
>> function.
>> ---
>> src/security/virt-aa-helper.c | 1 -
>> 1 files changed, 0 insertions(+), 1 d
2010/1/15 Matthias Bolte :
> 2010/1/14 Matthew Booth :
>> I'm trying to use the ESX driver to extract metadata from ESX in an easily
>> digestible form for driving V2V. I've noticed the domain XML seems to be
>> missing a few bits:
>>
>>
>
> This is currently not implemented, but could be by parsi
2010/1/14 Matthew Booth :
> I'm trying to use the ESX driver to extract metadata from ESX in an easily
> digestible form for driving V2V. I've noticed the domain XML seems to be
> missing a few bits:
>
>
This is currently not implemented, but could be by parsing the CPUIDs.
This is on my todo lis
Daniel P. Berrange wrote:
> * docs/contact.html.in: Document new users mailing list
...
Sounds good.
> +
> + Both mailing lists require that you subscribe before posting
> to the list,
Since both lists are using listhelper,
http://savannah.gnu.org/maintenance/ListHelperAntiSpam
it i
On Fri, Jan 15, 2010 at 11:03:01AM +0100, Jim Meyering wrote:
> A week or two ago, upstream gnulib was fixed to be more namespace friendly
> in how it creates replacement headers. For some of its replacements
> (e.g., , used via gnulib/lib/stdio.h), it would unnecessarily
> include another header,
On Fri, Jan 15, 2010 at 10:41:49AM +0100, Jim Meyering wrote:
> FYI, pushed as obvious...
>
> >From 02765872876ba8a820a5047f664da8a7b870b7b9 Mon Sep 17 00:00:00 2001
> From: Jim Meyering
> Date: Fri, 15 Jan 2010 10:22:08 +0100
> Subject: [PATCH] xen: do not report a write-to-Xen-daemon failure as
Matthias Bolte wrote:
> Commit 5073aa994af460e775cb3e548528e28d7660fcc8 added an additional
> '}' to a case block that messed up the block structure of the get_files
> function.
> ---
> src/security/virt-aa-helper.c |1 -
> 1 files changed, 0 insertions(+), 1 deletions(-)
>
> diff --git a/src/
A week or two ago, upstream gnulib was fixed to be more namespace friendly
in how it creates replacement headers. For some of its replacements
(e.g., , used via gnulib/lib/stdio.h), it would unnecessarily
include another header, e.g., . That would make it so that
an application using gnulib's co
FYI, pushed as obvious...
>From 02765872876ba8a820a5047f664da8a7b870b7b9 Mon Sep 17 00:00:00 2001
From: Jim Meyering
Date: Fri, 15 Jan 2010 10:22:08 +0100
Subject: [PATCH] xen: do not report a write-to-Xen-daemon failure as a read
failure
* src/xen/xend_internal.c (wr_sync): Correct the diagnos
Le 14/01/2010 vers 01:09, dans le message intitulé "Re: [libvirt] [RFC]
Proposal for introduction of network trafficfiltering capabilities for
filtering of network traffic from and to VMs", Dimitrios
Pendarakis(Dimitrios
Pendarakis ) a écrit:
Hi,
> Note that this is the case for th
[my apologies for this re-post. I stupidly managed to hide the first
instance of this mail away in an unrelated patch-thread and am thus
afraid that the people who could have answered didn't see it]
Hi,
I have one test host running Debian unstable (kernel 2.6.32.3), and I
would like to virtualize
73 matches
Mail list logo
