Displaying 20 results from an estimated 5000 matches similar to: "[PATCH] appliance: Disable ipv6 in the appliance because qemu usernet is ipv4 only"
2014 Jan 24
0
Re: [PATCH] appliance: Disable ipv6 in the appliance because qemu usernet is ipv4 only
On Thu, Jan 23, 2014 at 11:44:52PM +0100, Olaf Hering wrote:
> Signed-off-by: Olaf Hering <olaf@aepfle.de>
> ---
>
> Untested in this environment.
>
> appliance/init | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/appliance/init b/appliance/init
> index b25ea26..cc8c978 100755
> --- a/appliance/init
> +++ b/appliance/init
> @@ -71,6
2014 Jan 24
1
Re: [PATCH] appliance: Disable ipv6 in the appliance because qemu usernet is ipv4 only
On Thu, Jan 23, 2014 at 11:46:33PM +0100, Olaf Hering wrote:
> On Thu, Jan 23, Olaf Hering wrote:
>
> > +++ b/appliance/init
> > # Update the system clock.
> > hwclock -u -s
>
> Why is that needed? Just wondering...
I suspect it's not needed at all.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-top is
2014 Jan 24
2
Re: [PATCH] appliance: Disable ipv6 in the appliance because qemu usernet is ipv4 only
On Fri, Jan 24, Richard W.M. Jones wrote:
> However I don't understand why disabling IPv6 should be necessary. If
> sites resolve to AAAA+A records, then presumably it's going to choose
> the A (IPv4) route since no IPv6 route exists. If a site resolves to
> only an AAAA record, then it's not reachable whatever we do.
For me the code tries to reach the ipv6 address,
2014 Jan 23
0
Re: [PATCH] appliance: Disable ipv6 in the appliance because qemu usernet is ipv4 only
On Thu, Jan 23, Olaf Hering wrote:
> +++ b/appliance/init
> # Update the system clock.
> hwclock -u -s
Why is that needed? Just wondering...
Olaf
2014 Jan 24
0
Re: [PATCH] appliance: Disable ipv6 in the appliance because qemu usernet is ipv4 only
On Fri, Jan 24, 2014 at 11:55:26AM +0100, Olaf Hering wrote:
> On Fri, Jan 24, Richard W.M. Jones wrote:
>
> > However I don't understand why disabling IPv6 should be necessary. If
> > sites resolve to AAAA+A records, then presumably it's going to choose
> > the A (IPv4) route since no IPv6 route exists. If a site resolves to
> > only an AAAA record, then
2014 Feb 05
2
[PATCH] appliance/init: provide a symlink /var/lock
Provide /var/lock as symlink to /run/lock, as it might be used by
applications.
---
appliance/init | 1 +
1 file changed, 1 insertion(+)
diff --git a/appliance/init b/appliance/init
index b25ea26..aac3f5a 100755
--- a/appliance/init
+++ b/appliance/init
@@ -32,6 +32,7 @@ mount -t sysfs /sys /sys
mkdir -p /run
mount -t tmpfs -o "nosuid,size=20%,mode=0755" tmpfs /run
mkdir -p
2014 Oct 02
5
Re: [PATCH v2 1/4] appliance: Use dhclient instead of hard-coding IP address of appliance.
On Thu, Oct 02, Richard W.M. Jones wrote:
> The script won't fail, but the network won't work. What's the
> alternative on SuSE?
I think that would be dhcpcd, which is also used by NetworkManager.
Olaf
2013 Jun 11
2
[PATCH] Mask some package names if appliance is build for SUSE
Signed-off-by: Olaf Hering <olaf@aepfle.de>
---
Not compile-tested!
appliance/packagelist.in | 13 ++++++++-----
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/appliance/packagelist.in b/appliance/packagelist.in
index 8a4a5ea..a00a7ad 100644
--- a/appliance/packagelist.in
+++ b/appliance/packagelist.in
@@ -126,11 +126,9 @@ dosfstools
file
findutils
gawk
-gdisk
grep
2013 Jun 11
3
Re: [PATCH] Mask some package names if appliance is build for SUSE
On Tue, Jun 11, Richard W.M. Jones wrote:
> But supermin is supposed to ignore packages that don't exist in the
> distro. This is a bug in supermin or the zypp plugin for supermin.
It looks like zypper has no "ignore unknown packages/provides" flag.
zypper .. install $pkg is called with an unknown package then zypper
will just abort because it expects valid input.
Maybe
2012 Oct 08
1
[PATCH][RFC] launch: appliance is optional
# virt-filesystems -v -d 6326ad4e-5805-2ab4-1338-d1dad8c76162 --all
libguestfs: libvirt version = 10002
libguestfs: [00000ms] connect to libvirt
libguestfs: [00001ms] get libvirt capabilities
libguestfs: [00234ms] build appliance
libguestfs: [00234ms] create libvirt XML
libguestfs: error: error constructing libvirt XML at "xmlTextWriterWriteAttribute (xo, BAD_CAST "file", BAD_CAST
2013 Aug 22
2
--disable-appliance creates supermin.d files
Why does the toplevel Makefile process appliance/, and creates
supermin.d during make install, whith configure --disable-appliance? I
have to double check what actually happens, it seems it causes startup
failures if the resulting binary packages are started on a host that
happens to have supermin installed.
Olaf
2014 Oct 02
2
Re: [PATCH v2 1/4] appliance: Use dhclient instead of hard-coding IP address of appliance.
On Thu, Oct 02, Richard W.M. Jones wrote:
> +if grep -sq guestfs_network=1 /proc/cmdline; then
> + dhclient
> +fi
dhclient will be missing at least in openSUSE. Not an issue now, does
the script fail if the command fails to execute due to ENOENT?
Olaf
2014 Oct 02
2
Re: [PATCH v2 1/4] appliance: Use dhclient instead of hard-coding IP address of appliance.
On Thu, Oct 02, Richard W.M. Jones wrote:
> It seems as if it would, from reading the dhcpcd man page ..
Looks like the syntax is 'dhcpcd <interface>'.
Olaf
2014 Oct 02
6
[PATCH v2 0/4] launch: libvirt: Use qemu-bridge-helper to implement a full network (RHBZ#1148012).
v2:
- Make virbr0 configurable.
- Fix the tests.
2013 Aug 22
1
Re: --disable-appliance creates supermin.d files
On Thu, Aug 22, Richard W.M. Jones wrote:
> On Thu, Aug 22, 2013 at 09:28:36AM +0200, Olaf Hering wrote:
> > Why does the toplevel Makefile process appliance/, and creates
> > supermin.d during make install, whith configure --disable-appliance? I
> > have to double check what actually happens, it seems it causes startup
> > failures if the resulting binary packages are
2013 Aug 24
12
[Bug 2143] New: X11 forwarding for ipv4 is broken when ipv6 is disabled on the loopback interface
https://bugzilla.mindrot.org/show_bug.cgi?id=2143
Bug ID: 2143
Summary: X11 forwarding for ipv4 is broken when ipv6 is
disabled on the loopback interface
Product: Portable OpenSSH
Version: 5.3p1
Hardware: All
OS: Linux
Status: NEW
Severity: minor
Priority: P5
2012 Mar 16
7
[PATCH] tools: specify datadir for qemu-xen build to fix firmware loading
# HG changeset patch
# User Olaf Hering <olaf@aepfle.de>
# Date 1331924173 -3600
# Node ID bf1d5778ffd10858b402068b9473e410791ebd07
# Parent 72e6530b29463f0913af365f5d085d94ff75627c
tools: specify datadir for qemu-xen build to fix firmware loading
qemu-xen does currently not find the firmware files, such as
vgabios-cirrus.bin. The reason is that qemu-xen uses the default prefix
/usr/local.
2012 Jul 10
9
[PATCH] stubdom: fix errors in newlib
# HG changeset patch
# User Olaf Hering <olaf@aepfle.de>
# Date 1341839122 -7200
# Node ID 2dd50c201ca0d3542f3589942ae9e51d33ec7509
# Parent 42f76d536b116d2ebad1b6705ae51ecd171d2581
stubdom: fix errors in newlib
rpmlint found a few code bugs in newlib, and marks them as errors after
rpm build. Add another newlib patch and apply it during stubdom build.
I: A function uses a
2013 Jan 31
7
[PATCH] libxl: pass debug flag down to libxl_domain_suspend
# HG changeset patch
# User Olaf Hering <olaf@aepfle.de>
# Date 1359648298 -3600
# Node ID 256d59b2bc8a413876559dc8daf4c52ba46677de
# Parent 12455da211d4e841692b2374086356a87eb74ff7
libxl: pass debug flag down to libxl_domain_suspend
libxl_domain_suspend is already prepared to handle LIBXL_SUSPEND_DEBUG,
and xl migrate handles the -d switch as well. Pass this flag down to
2012 Dec 05
3
[PATCH] qemu-traditional: update configure check for -lrt changes in glibc 2.17
configure uses clock_gettime to check whether -lrt is needed - and don''t
check other functions. With glibc 2.17 clock_gettime is part of libc, so
use timer_gettime instead, which is in -lrt in old and new versions of
glibc.
Signed-off-by: Olaf Hering <olaf@aepfle.de>
---
configure | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure b/configure
index