Per this thread:
http://thread.gmane.org/gmane.comp.emulators.libvirt/19672
here's a patch that solves both problems:
From 1b330b3070f904dfc1c380151afa3aaf2a121cd3 Mon Sep 17 00:00:00 2001
From: Jim Meyering j...@meyering.net
Date: Thu, 7 Jan 2010 21:07:42 +0100
Subject: [PATCH] let configure
Diego Elio “Flameeyes” Pettenò wrote:
Il giorno gio, 07/01/2010 alle 23.03 +0100, Jim Meyering ha scritto:
So your change forced all other users of --disable-shared
to also configure with --without-python, but did not inform them
of the new constraint. BTW, it also rendered build
Hi,
attached patch looks for the DMI information in /sys/class since older
kernels (e.g. 2.6.26) have it there.
Cheers,
-- Guido
From: =?UTF-8?q?Guido=20G=C3=BCnther?= a...@sigxcpu.org
Date: Thu, 7 Jan 2010 10:13:51 +0100
Subject: [PATCH] Also look for dmi information in /sys/class
older kernels
Manao ahoana, Hello, Bonjour,
My server has 3 public IPs: IP1, IP2, IP3.
I intend to create 3 bridges: virbr1, virbr2, virbr3.
Each bridge will NAT from 3 to 5 KVM guests.
About IP1:
I would like incoming connexion on IP1 to:
- IP1:80 to be DNAT'd to one virbr1 VM, specialized on HTTP
On Fri, Jan 08, 2010 at 01:45:12AM +0100, Matthias Bolte wrote:
---
HACKING |6 +++---
docs/FAQ.html.in|2 +-
docs/bugs.html.in |6 +++---
docs/contact.html.in|4 ++--
docs/deployment.html.in |4 ++--
docs/hacking.html.in|6
On Fri, Jan 08, 2010 at 09:05:25AM +0100, Jim Meyering wrote:
Per this thread:
http://thread.gmane.org/gmane.comp.emulators.libvirt/19672
here's a patch that solves both problems:
From 1b330b3070f904dfc1c380151afa3aaf2a121cd3 Mon Sep 17 00:00:00 2001
From: Jim Meyering
On Fri, Jan 08, 2010 at 09:35:36AM +0100, Guido Günther wrote:
Hi,
attached patch looks for the DMI information in /sys/class since older
kernels (e.g. 2.6.26) have it there.
Cheers,
-- Guido
From: =?UTF-8?q?Guido=20G=C3=BCnther?= a...@sigxcpu.org
Date: Thu, 7 Jan 2010 10:13:51 +0100
Il giorno ven, 08/01/2010 alle 09.05 +0100, Jim Meyering ha scritto:
* python/Makefile.am (libvirtmod_la_LDFLAGS): Do not use -shared.
This reverts 8838ee39ab1c2bb7fffe93bfda220692664e8be6.
Not really necessary at this point.
--
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/
Patch concept by Jim Meyering j...@meyering.net, moved before the Python
testing, and changed the message a bit to explain the problem.
---
configure.in |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/configure.in b/configure.in
index 3f2f8ff..5275412 100644
---
On Thu, Jan 07, 2010 at 04:50:03PM -0800, Chris Wright wrote:
* Fischer, Anna (anna.fisc...@hp.com) wrote:
So, when setting a breakpoint for the exit() call I'm getting a bit closer
to figuring where it kills my guest.
Thanks, this helps clarify what is happening.
Breakpoint 1, exit
Daniel Veillard wrote:
...
* configure.ac: Make --disable-shared imply --without-python and
configure.in actually
Thanks. will adjust.
--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
Daniel Veillard wrote:
...
However, the point is still valid, so I'll wait for confirmation.
This is still about defensive coding, i.e., ensuring that
maintenance doesn't violate invariants in harder-to-diagnose ways.
If you get a bug report, which would you rather hear?
libvirt sometimes
On Thu, Jan 07, 2010 at 10:23:28PM +0100, Daniel Veillard wrote:
On Thu, Jan 07, 2010 at 08:36:25PM +, Daniel P. Berrange wrote:
On Thu, Jan 07, 2010 at 09:19:17PM +0100, Diego Elio ???Flameeyes???
Petten? wrote:
Il giorno gio, 07/01/2010 alle 21.14 +0100, Jim Meyering ha scritto:
On Thu, Jan 07, 2010 at 05:31:59PM +, Daniel P. Berrange wrote:
On Thu, Jan 07, 2010 at 02:53:20PM +0100, Daniel Veillard wrote:
The -mem-prealloc flag should be used when using large pages
This ensures qemu tries to allocate all required memory immediately,
rather than when first used.
Il giorno ven, 08/01/2010 alle 12.12 +0100, Jim Meyering ha scritto:
Using -shared in python/ would now be a little misleading,
since it's useful only when building with --disable-shared,
and python/ is no longer built with --disable-shared.
Not at all. It was needed to avoid building the
Il giorno ven, 08/01/2010 alle 11.16 +, Daniel P. Berrange ha
scritto:
What problems do shared libraries cause with GDB - I've never had any
trouble with it at all - it 'just works' perfectly picking up any
debuginfo
packages from things we link against too. The only GDB issues I see
Diego Elio “Flameeyes” Pettenò wrote:
Il giorno ven, 08/01/2010 alle 12.12 +0100, Jim Meyering ha scritto:
Using -shared in python/ would now be a little misleading,
since it's useful only when building with --disable-shared,
and python/ is no longer built with --disable-shared.
Not at all.
Il giorno ven, 08/01/2010 alle 12.44 +0100, Jim Meyering ha scritto:
Oh, I see what you mean, finally.
I had read only the first description of -shared in libtool
documentation, and hadn't realized that was only for *compile mode*.
There's a slightly different description following that,
On Fri, Jan 08, 2010 at 12:21:44PM +0100, Diego Elio ???Flameeyes??? Petten?
wrote:
Il giorno ven, 08/01/2010 alle 11.16 +, Daniel P. Berrange ha
scritto:
What problems do shared libraries cause with GDB - I've never had any
trouble with it at all - it 'just works' perfectly
Daniel P. Berrange wrote:
On Thu, Jan 07, 2010 at 11:03:23AM +0100, Daniel Veillard wrote:
On Thu, Jan 07, 2010 at 09:37:57AM +0100, Jim Meyering wrote:
However, the point is still valid, so I'll wait for confirmation.
This is still about defensive coding, i.e., ensuring that
Diego Elio Pettenò wrote:
Patch concept by Jim Meyering j...@meyering.net, moved before the Python
testing, and changed the message a bit to explain the problem.
---
configure.in |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/configure.in b/configure.in
index
Daniel Veillard wrote:
...
Sure, ACK :-)
Thanks. Diego proposed an improvement, so I expect to push this instead:
http://thread.gmane.org/gmane.comp.emulators.libvirt/19696/focus=19710
--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
On Fri, Jan 08, 2010 at 12:13:24PM +0100, Jim Meyering wrote:
Daniel Veillard wrote:
...
However, the point is still valid, so I'll wait for confirmation.
This is still about defensive coding, i.e., ensuring that
maintenance doesn't violate invariants in harder-to-diagnose ways.
If you
On 01/07/2010 11:53 PM, Dustin Xiong wrote:
Date: Thu, 7 Jan 2010 09:15:32 -0500
From: crobi...@redhat.com
To: x_k_...@hotmail.com
CC: berra...@redhat.com; libvirt-l...@redhat.com
Subject: Re: [libvirt] [virt-tools-list] Questions about virt-manager
running on Arch of Itanium 64
On
Hi Folks,
We've been brainstorming ways to improve/broaden the libvirt community
and one (of many) ideas is to create a separate libvirt users mailing
list. The rationale is that this list is 95% patch submission from
developers, often very high traffic and thus it may not be appealing for
Il 08/01/10 15.56, Daniel P. Berrange ha scritto:
- Development of libvirt itself (libvirtd, hypervisor drivers, etc)
- Development of libvirt language bindings (perl, python, java, etc)
- Patch submission for libvirt language bindings
I would like to add “Inter-distribution
Daniel P. Berrange a écrit :
Hi Folks,
Hello
[...]
Thus we're considering creating a new list
libvirt-us...@redhat.com
[...]
Excellent idea. I was thinking to unsubscribe from the actual list
because of the hudge dev traffic. If such a list is started, I will switch.
Regards
2010/1/8 Daniel Veillard veill...@redhat.com:
On Fri, Jan 08, 2010 at 01:45:12AM +0100, Matthias Bolte wrote:
---
HACKING | 6 +++---
docs/FAQ.html.in | 2 +-
docs/bugs.html.in | 6 +++---
docs/contact.html.in | 4 ++--
docs/deployment.html.in |
On Tue, Jan 05, 2010 at 03:00:06AM +0100, Matthias Bolte wrote:
---
src/esx/esx_driver.c | 38 +++---
1 files changed, 27 insertions(+), 11 deletions(-)
diff --git a/src/esx/esx_driver.c b/src/esx/esx_driver.c
index f86654a..ddda66e 100644
---
On Fri, Jan 08, 2010 at 04:06:49PM +0100, Diego E. “Flameeyes” Pettenò wrote:
Il 08/01/10 15.56, Daniel P. Berrange ha scritto:
- Development of libvirt itself (libvirtd, hypervisor drivers, etc)
- Development of libvirt language bindings (perl, python, java, etc)
- Patch submission for
This series is a merge of two previous series I posted
http://www.redhat.com/archives/libvir-list/2009-December/msg00232.html
http://www.redhat.com/archives/libvir-list/2009-December/msg00392.html
It accomplishes quite a lot of things, having major impact on the QEMU
driver, hopefully all in
Add the virDomainDeviceAddress information to the sound, video
and watchdog devices. This means all of them gain the new XML
element
address /
This brings them upto par with disk/net/hostdev devices which
already have address info
* src/conf/domain_conf.h: Add virDomainDeviceAddress to
From: Wolfgang Mauerer wolfgang.maue...@siemens.com
This augments virDomainDevice with a controller element
that is used to represent disk controllers (e.g., scsi
controllers). The XML format is given by
controller type=scsi index=num
address type=pci domain=0xNUM bus=0xNUM slot=0xNUM/
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
--- a/src/qemu/qemu_monitor_text.c
+++ b/src/qemu/qemu_monitor_text.c
@@ -1678,14
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 _virDomainDevicePCIAddress {
unsigned int domain;
unsigned int bus;
unsigned
Existing applications using libvirt are not aware of the disk
controller concept. Thus, after parsing the disk definitions
in the XML, it is neccessary to create controller elements
to satisfy all requested disks, as per their defined drive
addresses
* src/conf/domain_conf.c,
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
* src/conf/domain_conf.h, src/conf/domain_conf.c,
---
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/qemu/qemu_conf.c
+++ b/src/qemu/qemu_conf.c
@@ -2268,6 +2268,28 @@ error:
}
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 controller/bus/unit addressing
* src/qemu/qemu_conf.c, src/qemu/qemu_conf.h:
Introduce a new structure
struct _virDomainDeviceDriveAddress {
unsigned int controller;
unsigned int bus;
unsigned int unit;
};
and plug that into virDomainDeviceAddress and generates XML that
looks like
address type='drive' controller='1' bus='0'
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 -device, assign disk names based on QEMU's
historical naming scheme.
*
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
* src/qemu/qemu_conf.c: Convert Virtio ballon to -device and
give it an explicit PCI address
*
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
40
... 75 OK
PASS: statstest
On Tue, Jan 05, 2010 at 03:01:06AM +0100, Matthias Bolte wrote:
Currently only the faultcode and faultstring are deserialized, the
detail part is ignored. The implementation of many new SOAP types
would be necessary to deserialize the detail part correctly. As an
intermediate solution the raw
From: Wolfgang Mauerer wolfgang.maue...@siemens.com
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
hotplug of controllers though, enables the
When parsing the disk element specification, if no address
is provided for the disk, then automatically assign one based on
the target dev='sdXX'/ device name. This provides for backwards
compatability with existing applications using libvirt, while also
allowing new apps to have complete fine
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 then correlating the vendor/product IDs
with the devices we booted with.
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
* src/qemu/qemu_driver.c, src/qemu/qemu_monitor.c,
src/qemu/qemu_monitor.h,
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 file,id=serial0,path=/tmp/serial.log -device
isa-serial,chardev=serial0
This patch
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=PCI SLOT
NB, pcspk still uses the old -soundhw syntax
---
src/qemu/qemu_conf.c | 97
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 filled before a new one is added.
If the user specifies an high drive index
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 simplified pair of args
-netdev user,id=user.0
-device
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,id=drive-virtio-0,format=qcow2
-device
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. This change switches over to make
libvirt explicitly calculate the
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: Remove hack which deleted duplicated
sound device models.
*
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=1
-device usb-storage,drive=usb-1
Again, the index= arg is wrong here, and
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 to support this concept.
The QEMU driver sets them whenever using the
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_conf.c, src/conf/domain_conf.h: Add hooks for
parsing / formatting device info
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 changes in graphics default
* src/qemu/qemu_conf.c, src/qemu/qemu_conf.h:
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 configured
* tests/qemuargv2xmltest.c, tests/qemuxml2argvtest.c: Test for
handling
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 later patch
NB, the PIIX3 (IDE, FDC, ISA-Bridge) will always have slot 1 and
The current syntax for watchdogs is
-watchdog i6300esb
The new syntax will now be
-device i6300esb,id=watchdogNN,addr=PCI-SLOT
---
src/qemu/qemu_conf.c | 91 ++--
.../qemuxml2argv-watchdog-device.args |1 +
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=DEV
---
src/qemu/qemu_conf.c | 32 ++-
The old syntax is
-pcidevice host=BUS:SLOT:FUNCTION
The new syntax is
-device pci-assign,host=BUS:SLOT:FUNCTION,addr=PCI SLOT,id=host0
---
src/qemu/qemu_conf.c | 51 +++-
.../qemuxml2argv-hostdev-pci-address-device.args |1 +
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/qemu_conf.c | 11 ++-
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 flag will help avoid unwelcome surprises from future
QEMU releases
*
The original code. would only print the warning message if using
/dev/random failed, but would still go ahead and call
virUUIDGeneratePseudoRandomBytes in all cases anyway.
---
src/util/uuid.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/util/uuid.c
On Fri, Jan 08, 2010 at 05:22:56PM +, Daniel P. Berrange wrote:
This series is a merge of two previous series I posted
http://www.redhat.com/archives/libvir-list/2009-December/msg00232.html
http://www.redhat.com/archives/libvir-list/2009-December/msg00392.html
It accomplishes quite
Daniel Huhardeaux t...@tootai.net :
Excellent idea. I was thinking to unsubscribe from the actual list
because of the hudge dev traffic
You were not abble to filter and split the destination folder?
Are you serious?
--
Architecte Informatique chez Blueline/Gulfsat:
Administration
2010/1/8 Daniel Veillard veill...@redhat.com:
On Tue, Jan 05, 2010 at 03:00:06AM +0100, Matthias Bolte wrote:
---
src/esx/esx_driver.c | 38 +++---
1 files changed, 27 insertions(+), 11 deletions(-)
diff --git a/src/esx/esx_driver.c b/src/esx/esx_driver.c
On 12/31/2009 07:42 PM, Philip Jameson wrote:
I was starting to use libvirt on a project, and realized that there was
nothing in the API for snapshots. As I need to be able to take snapshots
without taking down the machine (that and KVM's restore function didn't seem
to be working terribly
71 matches
Mail list logo
