It appreciate if you could test bullseye as well. Thanks!
Have updated a server with Buster (on which I've tested Varnish
v6.1.1-1+deb10u3 before) to Bullseye and upgraded Varnish to
6.5.1-1+deb11u2.
The results are pretty much the same as with Buster.
The hosted pages work correctly with
Hello Salvatore!
Unofficial and amd64 only builds (including the source in case you
want to built it on your own) are at:
https://people.debian.org/~carnil/tmp/varnish/
I've installed v6.1.1 packages on several of our Buster servers.
Apparently all the websites and portals hosted there are
Hello Salvatore!
Those updates were already prepared by Florian Weimer, but we need
someone using it to actually test the updates as it includes other CVE
fixes (namely CVE-2021-36740). If you are interested to test (yet
unofficial) debs, let us know, this might speed up a bit the DSA
release
I know we (or most of us) are volunteers working on Debian. But I have
to admit I'm a bit worried that we haven't patched this critical
cache-poisoning vulnerability in Varnish for one month (except in Debian
Stretch LTS).
Attached patches containing the fixes for CVE-2022-23959.
For Debian
CVE-2022-23959 has meanwhile been rated as critical:
https://nvd.nist.gov/vuln/detail/CVE-2022-23959
Apparently it is rather easy to exploit:
http://cwe.mitre.org/data/definitions/444.html
Any ETA when a security-upgrade could become available?
Fixes for the vulnerability seem to be rather
Package: varnish
Severity: normal
Hello!
There is a new vendor-announcement regarding a request smuggling attack
- this time affects HTTP/1 connections. It's apparently affecting all
versions >= Stretch.
https://varnish-cache.org/security/VSV8.html
Package: src:linux
Version: 4.9.6-3
Severity: normal
Hello,
Since kernel 4.9.0 replaced 4.8.0 in stretch, my notebook was unable
to resume from hibernation. Hardware is a Lenovo Thinkpad X1 Carbon
Gen4. The issue first came up with 4.9.2, but is still present in the
4.9.6 version of
Package: linux-image-3.2.0-4-686-pae
Version: 3.2.68-1+deb7u2
Severity: normal
Dear Maintainer,
Using keepalived for IPVS, sometimes during bootup an kernel oops gets
triggered.
It seems to be a race condition when keepalived is accessing IPVS while later
isn't fully initialized yet.
Jul 30
Package: monitoring-plugins
Version: 2.1.1-1proxybpo70+1
Severity: normal
Dear Maintainer,
I'm having a problem with check_procs on several Wheezy systems.
There is apache running on these systems and I'm checking for its procsses with
check_procs.
First of all, the processes are actually
Package: enhanceio
Version: 0+git20130620-1
Severity: normal
Dear Maintainer,
I noticed that the EnhanceIO kernel module permanently logs the following
messages to the ring buffer:
[277586.126651] enhanceio: eio_handle_ssd_message: SSD_ADD event called for
ACTIVE cache ssdcache,
clean-up interval (minutes) : This option allows you to specify an
interval between each clean-up process.
TIME_BASED_CLEAN_INTERVAL=1
#!/bin/bash
#
# Written by Andreas Unterkircher u...@netshadow.at.
### BEGIN INIT INFO
# Provides: enhanceio
# Required-Start:$remote_fs $syslog
And finally 2.10.0 is available upstream too.
http://www.flightgear.org/news/flightgear-v2-10-released/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: ndoutils-common
Version: 1.4b9-1.1
Severity: normal
Hello,
New upstream major 1.5 contains several improvements regarding performance.
It would be great if we could get 1.5.2 [1] into unstable.
Cheers,
Andreas
[1] http://sourceforge.net/projects/nagios/files/ndoutils-1.x/
-- System
Package: openswan
Version: 1:2.6.28+dfsg-5+squeeze1
Severity: normal
Tags: upstream
If OpenSWAN (pluto) manages multiple interfaces and those can get up and down
regularly (DSL with PPPoE and automatic 24h disconnect from ISP etc) those
devices need to be attached and detached from pluto.
In
Hi Alexander,
Do any of you guys still experience the problem today? If so, does
upgrading pulseaudio to version 2.0-3 (currently in testing) or 2.0-4
(currently in unstable; fixes #673847) help?
From my side I have no more troubles with this bug.
Problem disappeared some-when years ago in
Package: flightgear
Version: 2.4.0-1.2
Severity: normal
On an up2date wheezy installation with
ii flightgear 2.4.0-1.2
ii subversion 1.6.17dfsg-4
terrasync reports the following when invoked
unki@kuecken:/tmp$ terrasync
Airports/K ... terrasync: Version mismatch
Package: remmina
Version: 1.0.0-4
Severity: minor
Enabling Hide-toolbar-in-tabbed-interfaces in Edit - Preferences
causes the remote OS window to be drawn at a wrong offset. The
rest of the remmina window becomes filled black.
This problem has also been reported by Ubuntu users at [1] and [2].
Package: keepalived
Version: 1:1.2.2-2
Severity: normal
In keepalived.conf.SYNOPSIS.gz the example code shows how to enter the
recipient email address like this:
notification_email {# Email to send alertes to
EMAIL ADDRESS # Standard email address
The parser is not very robust. It is quite difficult to fix without
replacing it. The manpage could be fixed but it is unlikely we can fix
(as downstream) the parser. Use -d -D -l to check if keepalived has
understood correctly your configuration file.
Yep, I agree. It's enough when it is
I have rebuilt the packages on squeeze (i386, amd64) with the attached
patch found at [1]. The previously logged message no longer appears.
Cheers
[1] https://launchpadlibrarian.net/82139424/0003-init-gcrypt.patch
From bbd500b9e0fb3b6df0f15fc0b1a35619d61a76f5 Mon Sep 17 00:00:00 2001
From:
Package: libpam-ccreds
Version: 10-5
Severity: normal
When using pam_ccreds.so on Squeeze it logs the following message to
/var/log/syslog on a user logon:
Oct 13 18:43:52 srv sshd[12920]: Libgcrypt warning: missing initialization -
please fix the application
A bug with a fix has been logged
Just for the records - this problem appears when you call lvremove
within the /target chroot environment by in-target.
If you remove in-target from your late_command and by this invoke
lvremove within d-i's rootfs, it works.
Andreas
--
To UNSUBSCRIBE, email to
Package: python-couchdb
Version: 0.6-1
Severity: minor
Tags: upstream
In /usr/share/pyshared/couchdb/json.py line 125 it seems a debug message has
been left.
'Using stdlib json' gets printed everytime when using this library.
A quick fix is:
--- json.py.orig 2009-07-02 16:02:57.0
Hi,
We are hitting this too now after years using lvremove in
late_command. Also while Squeeze was testing we were using this
without any problem.
Anyway problem seems to be that the late_command is invoked chrooted
in /target.
While calling lvremove from the debian-installer rootfs
Is someone actually monitoring these couchdb bugs? Even pkg-erlang-dev
seems quiet orphaned.
Right now it is quiet serious to come around this compaction problem of
a growing CouchDB with restarting the instance to avoid the disk getting
filled up.
Andreas
--
To UNSUBSCRIBE, email to
Package: libimobiledevice1
Version: 1.0.2-1
Severity: normal
All libimobiledevice-utils are failing to attach to an iPad with iOS 4.2.1.
For example idevicesyslog fails with:
me@host:~$ idevicesyslog GNUTLS ERROR: A TLS fatal alert has been received.
usbmuxd_send: Error -1 when sending:
duplicate to #608708
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Looks like this problem only occurs on compacting a database itself.
When compacting a view this issue does not show up and the original view
file gets deleted and is not leaving marks.
Andreas
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
This seems to be a known bug and is only occurring when using views -
it's fixed in newer upstream versions as indicated here [1].
It would be great if we can have this newer version packed - restarting
CouchDB to get around this problem is a pain when used together with
replication that
Phil Whineray announced a working IPv6 firehol version on the firehol
mailing list [1].
I have tested it already and it looks good.
[1] http://sourceforge.net/mailarchive/message.php?msg_id=27014139
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
We are quiet happy with it, as it is easy to configure and powerful -
apart from being a bash moloch :-)
At least getting it capable of IPv6 would be nice.
Is there a repository against I can format a patch for this?
Andreas
Zitat von Alexander Wirt formo...@debian.org:
Andreas Unterkircher
Package: couchdb
Version: 0.11.0-2.3
Severity: normal
When I invoke the following command to trigger a database compaction:
curl -H Content-Type: application/json -X POST
http://localhost:5984/db/_compact
CouchDB will rebuild its database file and clean up old revisions and so on.
This
Package: usbip
Version: 0.1.7-3
Severity: normal
A set of USB devices is exported via a usbip server. The usbip client can list
the exported devices from the remote server successfully:
u...@srv:~$ sudo usbip -l usbip₋server 21 | grep Dallas
5-7.1: Dallas Semiconductor : DS1490F 2-in-1 Fob,
Package: puppet
Version: 2.6.0-2
Severity: normal
I hit this bug too. And not only class'es are affected. defines
are also not more working when they contain a dash in their name.
Andreas
-- System Information:
Debian Release: squeeze/sid
APT prefers stable
APT policy: (990, 'stable'),
Package: bacula
Severity: wishlist
5.0.3 is upstream available containing fixes for some 5.0.x bugs that we hit.
0001599: Started using TLS and Accurate backups, the Director started crashing
at random times
0001568: SD sig11 crash when OpenSSL recieved a timeout signal
(well, they stat in
Hope it fixes it...
It works! The newest patch (addconn-new.patch) resolves it.
It's throwing a warning
ignoring invalid defaultnexthop: illegal (non-DNS-name) character in name
but anyway it up's the connection.
Cheers,
Andreas
--
To UNSUBSCRIBE, email to
I have seen that somebody yesterday replied to my upstream ticket and
added a patch for that problem. I will give it a try.
https://gsoc.xelerance.com/issues/1082
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Hi,
could you please test if version 2.6.26 solves your problem and if
not contact me?
Just tried it with 2.6.26 - the issue is the same
invalid default route: illegal (non-DNS-name) character in name
when trying to --add the route.
By clearing the variable defaultroutenexthop in
Tags: Patch, moreinfo
Version: 0.8.2-2
just updated the patch a bit to fit 0.8.2-2 where this problem still exists.
--- SwitcherDocklet.cs.orig 2009-06-26 07:50:20.0 +0200
+++ SwitcherDocklet.cs 2010-05-21 05:45:17.0 +0200
@@ -113,6 +113,12 @@
int
I don't think so. A config file is a file that you can edit with
either a text editor or some specialized configuration tool but a jar
file does not fall into that category.
I tend to set the wontfix tag because i think that dpkg-divert is the
right tool.
I support the wontfix. A compressed
I'm supporting this. The policy files should be preserved in /etc.
We had a (late) upgrade from Etch to Lenny. On Etch we were already
using a backport.org version of Java6. So for us it was just a minor
version upgrade to Lenny.
Developers replaced the policy files at some time in the past
Hello,
5.0.0 is already here too [1]. Would be great to pack that one instead
of the latest 3.0.x release. There some further necessary bugfixes in
it.
Regards,
Andreas
[1] http://www.bacula.org/en/?page=news
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a
upstream ticket
https://gsoc.xelerance.com/issues/1082
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: openswan
Version: 1:2.6.23+dfsg-2
Severity: normal
I hit a problem on a DSL Internet connection using pppd for PPPoE
dialin. If I try to add a new connection to OpenSWAN 2.6.23 it
fails with
invalid default route: illegal (non-DNS-name) character in name
I dig further and found
Just want to confirm the same - disabling SwitchProxy Tool (1.4.1) and
Firefox becomes stable here too.
Andreas
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Tags: patch
Just a quick'n'dirty fix which avoids gnome-do crash and successfully
wraps over from the first to the last workspace.
--- SwitcherDocklet.cs.orig 2009-06-26 07:50:20.0 +0200
+++ gnome-do-docklets-0.8.2/SwitcherDocklet/src/SwitcherDocklet.cs
2009-12-02
Package: gnome-do
Version: 0.8.2+dfsg-1
Severity: normal
I use four workspaces and have enabled the switcher docklet in docky.
When I'm in the first workspace, move the mouse pointer over the switcher
docklet and then move the mouse wheel up, gnome-do crashes and throws the
exception shown
Package: pulseaudio
Version: 0.9.19-2
Severity: normal
Everytime I start up my system, the volume control of pulseaudio is set to 0 -
to the lowest possible level, the 'Mute' option isn't active.
It's almost the same problem like noted here [1]. I tried [2], then the volume
starts up with
Package: pulseaudio
Version: 0.9.19-2
Severity: minor
In /usr/share/doc/pulseaudio/README.Debian it is stated:
priviledges in this way. It is highly recommended that all users that will
be running pulseaudio should be add to the pulse-rt group to prevent
skipping and dropouts in audio
merge 548363
this is a dup to #548363
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: openswan
Version: 1:2.6.22+dfsg-1.1
Severity: normal
It seems I hit a known bug on pre 2.6.23 versions which causing also
VPN tunnels to die after some amount of uptime.
Openswan user list suggested to upgrade to 2.6.23 where those things
should have been fixed.
Just for the records if someone else hit this problem.
As I can not get the routing information excluded via -I -var_route,
I adapted snmpd.conf to exclude OIDs out of the view. In this way
snmpd is not going to handle the routing information and does not hang
up.
I adapted the standard
Hello,
I have the same problems here on machines having a fullfeed
of Internet routes (~290k).
But the suggest -I parameter seems not to work with 5.2.3-7etch4.
I tried
/usr/sbin/snmpd -f -Lsd -Lf /dev/null \
-u snmp -I -var_route -p /var/run/snmpd.pid
as well as
/usr/sbin/snmpd -f -Lsd
I have backported now the Lenny version 5.4.1~dfsg-12 of net-snmp to
my etch machine. But also with it snmpd locks up with and without
providing -I var_route.
Cheers,
Andreas
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble?
u...@srv-mfm-vm01:~$ ls -l /etc/adjtime
lrwxrwxrwx 1 root root 9 2009-03-31 18:30 /etc/adjtime - /dev/null
It's a selfmade problem. Because we have some systems using a compact
flash as disk where just the /var filesystem is a RAM-based fs, we
wanted to avoid filesystem changes in /etc which
Package: base-files
Version: 5lenny3
Severity: normal
I'm trying to track down a nasty problem which I encounter from
to time on some of my Lenny machines. Sometimes, when I applied
updates via apt or cron-apt, I noticed afterwards, that the
permissions on /dev/null suddenly set to 644 instead
Hi,
Let's try to debug it even more: Does it also happen if you do this by
hand, as opposed to using dpkg-reconfigure?
/var/lib/dpkg/info/base-files.postinst configure 5lenny3
I can reproduce this with it:
u...@srv-mfm-vm01:~$ ls -l /dev/null
crw-rw-rw- 1 root root 1, 3 2009-06-09 10:40
Package: ifupdown
Version: 0.6.8
Severity: normal
Manpage says:
The wvdial Method
This method uses wvdial to configure a PPP interface. See that
command for more details.
Options
provider name
Use name as the provider (from /etc/ppp/peers).
Hi,
Could you check if the attached patch fixes your problem, it's the
upstream patch backported to 0.400.3?
I have applied it to 0.400.3 and rebuilt the package - it works! I can
create a guest even if the default route is pointing to dev brlan.
Just to note as I have not mentioned it
Package: virtinst
Version: 0.400.2
Severity: normal
Output from virt-manager --no-fork --debug:
2009-06-18 15:45:14,430 (create:711): Guest type set to os_type=hvm,
arch=x86_64, dom_type=kvm
2009-06-18 15:45:14,457 (create:466): Generating macaddr failed: invalid
literal for int() with base
so the issue is hal not listing these devices for you. This hal
0.5.12~git20090406.46dc48-2 which works. Could you check with this
version? I'm reassigning to hal but don't hesitte to keep me cc'ed.
I upgraded from 0.5.11-8 to 0.5.12~git20090406.46dc48-2, restarted
libvirtd and can confirm -
Almost the same, just that my bridge was also type manual as I do not
configure a IP address for it. And both devices link status was set to up.
iface vlan2 inet manual
vlan-raw-device eth0
iface br0 inet static
address 192.168.1.2
network 192.168.1.0
and how does your /sys/class/net directory looks like when it's working
in your virt-manager?
mine now contains:
u...@kuecken:~$ ls -l /sys/class/net/
total 0
drwxr-xr-x 6 root root 0 2009-06-11 05:43 br0
drwxr-xr-x 6 root root 0 2009-06-11 08:17 br1
drwxr-xr-x 5 root root 0 2009-06-11 05:43
Hello,
Just want to confirm that the fix works fine over months.
So either the kernel modules should be loaded elsewhere first,
or the init script of firehol should take care about.
Cheers,
Andreas
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
Package: libvirt0
Version: 0.6.3-4
Severity: normal
The following setup:
* eth0 is a physical interface
* eth1 is a physical interface
* vlan152 is a VLAN interface on eth0 with ID 152
* br0 is a bridge containing eth0
* br1 is a bridge containing eth1
* br2 is a bridge containing
The node listing is basically what hal exports. Are you seeing it from
within hal (lshal)?
You are right, neither vlan152 nor br2 show up. But also not br0 and
br1, that ones which show up in virt-manager.
lshal just lists the physical interfaces eth0 and eth1, not vlan152.
u...@vmtest:~$
Running virt-manager with --no-fork --debug should provide more
information on what's going on with that VLAN.
That brings up the following:
u...@vmtest:~$ sudo virt-manager --no-fork --debug
2009-06-04 12:22:37,621 (virt-manager:144): Application startup
2009-06-04 12:22:37,702 (keyring:31):
Package: cadaver
Version: 0.23.2-1
Severity: normal
It seems cadaver has problems handling files larger then 2GB. Trying to upload
a local file via WebDAV results in an error:
Could not open file: File too large
Downloading a file via WebDAV which is larger then 2GB results in a locally
Package: clamfs
Version: 1.0.0-1
Severity: normal
In a clamfs protect filesystem I have a file bigger then 2GB:
-rw-r-xr-- 1 www-data www-data 2663258112 2009-05-20 08:12 cdimage.iso
When I'm trying to read-access the file, I'm not allowed too:
u...@srv-vie-ftp01:...$ head cdimage.iso
head:
What is the example code supposed to do? I have no problem executing it
here:
$ ./group
buffer size from sysconf: 1024
gid: 124
It discovers what buffer size is necessary to successfully resolve
the group id on two amd64 systems I'm using here.
If you look at [1], I encounter problems with a
What is the example code supposed to do? I have no problem executing it
here:
$ ./group
buffer size from sysconf: 1024
gid: 124
It discovers what buffer size is necessary to successfully resolve
the group id on two amd64 systems I'm using here.
If you look at [1], I encounter problems with a
Package: virt-manager
Version: 0.7.0-1
Severity: normal
On an initial start of libvirtd, and the first connect of virt-manager to it,
libvirtd complains for a while (minutes) in the logs:
libvirtd: 08:14:16.141: error : this function is not supported by the
hypervisor: 'info blockstats' not
Is this reproduceable with virsh as well?
virsh domblkstat foo hdc
Yes, the same messages appear in the logs when I invoke this comamnd.
Also virsh returns and failure message then:
virsh # domblkstat srv-mfm-prod hda
error: Failed to get block stats srv-mfm-prod hda
error: this
Package: libvirt0
Version: 0.6.2-1
Severity: normal
I have several users here, each running virt-manager in their X
sessions to monitor a KVM host managed with libvirt. virt-manager
is configured to obtain all possible statistics from libvirt for
CPU- and RAM-usage as well as network- and
Package: virt-manager
Version: 0.7.0-1
Severity: normal
Re-creating a previously deleted guest basically succeeds but
shows up an error message. It is reproducable by following:
1. Create a guest called 'test'
2. Delete guest 'test' (regardless if or not keeping the diskfile)
3. Create again a
I've requested this upstream some time ago but they want to keep the
wizard simple. I wouldn't object to a Debian specific patch though, the
virtinst api has all that's needed.
Attached is a first try - an additional drop down box is
displayed in the Advanced options trough which the Device
I tried again.
lsusb shows up the newly plugged in device
(Aladdin Knowledge Systems HASP v0.06):
u...@srv-mfm-vm02:~$ sudo lsusb
Bus 006 Device 003: ID 03f0:1327 Hewlett-Packard
Bus 006 Device 002: ID 03f0:1027 Hewlett-Packard
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus
Package: virt-manager
Version: 0.7.0-1
Severity: normal
Not really sure if that problems more belong to virt-manager or libvirt0.
If I attach a USB device (crypto dongle, data stick, ...) it does not
shine up in
Details
- Add Hardware
- Physical Host Device
- USB Device
- The device
Package: smartmontools
Version: 5.38-2
Severity: normal
To get support for 64bit KVM guests I switch from the i686 kernel
(linux-image-2.6.26-1-686) to amd64 (linux-image-2.6.26-1-amd64).
The machine has a 3ware controller which smartmontools is capable
of checking its attached disks. After I
Usage of virtio is determined by the selected ostype. Using
generic/generic should disable virio and therefore find a PXE rom.
Sure, but with that kind of error message it is quiet difficult to
figure out, what's wrong. And choosing generic/generic when I know
exactly what operating system I
Package: virtinst
Version: 0.400.3-1
Severity: normal
When I try to create a new guest with virt-install and the following options:
sudo virt-install -n pbuild-vie-lenny -r 512 --arch=i686
--os-variant='debianlenny' -v --pxe -f /srv/guests/pbuild-vie-lenny_hda.img -b
br0 --vnc
I get back a
Package: libvirt0
Version: 0.6.1-1
Severity: normal
Trying to create a guest either with virt-manager or with virt-install results
in an error:
libvirtError: internal error unable to start guest: No valid PXE rom found for
network device
But the usual PXE rom's of KVM are in place:
Package: libvirt-bin
Version: 0.6.1-1
Severity: normal
Hi,
On some machines (at least reproduceable on them) when I installed
libvirt I get the following error when libvirt gets started:
u...@srv-mfm-vm02:~$ grep libvirt /var/log/syslog
Mar 22 14:56:31 srv-mfm-vm02 libvirtd: 14:56:31.347:
Looks more like a problem with nss on your machine. Are you running
nscd?
Luckily not, no nscd, no ldap - just local passwd/group:
u...@srv-mfm-vm02:/etc/xen$ grep -E passwd\|group\|shadow /etc/nsswitch.conf
passwd: compat
group: compat
shadow: compat
--
To
Package: virt-manager
Version: 0.6.1-5~mm.1
Severity: normal
I noticed that the menu entry Send Key - Ctrl+Alt+Delete is no longer
working. Indeed if you now select Send Key - Ctrl+Alt+Backspace it
submits a Ctrl+Alt+Delete to the guest. Easily noticable that it is no
longer working with a
Sure, do you want the full strace output? Below I just copied the lines
after it read libvirtd.conf till it exits:
getuid()= 0
getuid()= 0
getuid()= 0
open(/etc/libvirt/libvirtd.conf, O_RDONLY) = 10
Package: virt-manager
Version: 0.6.1-5~mm.1
Severity: normal
While I can migrate a guest between two Xen hosts with libvirt/virsh
(migrate --live domU xen+tls://...,), virt-manager fails to do so.
When I do a right-click on the guest - Migrate - the other node,
virt-manager just prints
Package: xen-hypervisor-3.2-1-amd64
Version: 3.2.1-2
Severity: normal
Hi,
Is the e1000 network card within domU no longer available?
With model=e1000 a Xen domain refuses to start while with
etch this was possible.
There are some Windows guests on which I can not install
gplpv, so with lenny
Thanks for checking! Looks like upstream commit
2b96b6676e5a4b464cdfc9d816d8828a4a5d3c0d
fixes this. So this should be fixed on 0.6.1 in testing.
I can confirm - I backported libvirt 0.6.1-1 from squeeze to lenny.
The VNC console immediately works with virt-manager 0.6.0-6 after
passing
So you added the interface, when the domain was shut down?
Exactly
Do you have a chance to test libvirt 0.6.1 from unstable/testing?
I backported libvirt 0.6.1-1 from squeeze to lenny. If I now add
an additional network adapter via virt-manager, it gets correctly
displayed in
Package: virt-manager
Version: 0.6.0-6
Severity: normal
I created a new guest via virt-manager. When the wizard asks for, I
configured a shared physical device for the initial network adapter.
Then I added another network adapter, this time one for a virtual
network. When I finished this
Ups, I missed one network adapter from the xen domain. To reproduce
it I already added a third network adapter too.
So as you can see, the bridge virbr0 has the same MAC as the
adapter in the XML dump
(device
(vif
(bridge br0)
(mac 00:16:36:4a:4d:9a)
Good to know! Does virsh domrain vncdisplay list the right port? If
not we have to look for the problem in libvirt, not virt-manager.
You seem to be right - vncdisplay for a machine with an automatically
allocated port simply returns nothing (here the first app-vmtest-02).
While the other
Could you try to reproduce this behaviour with virsh instead of
virt-manager? You can add new interfaces with attach-interface. This
might be a bug in libvirt not in virt-manager itself.
I tried that now by adding an interface with virsh and powered the
domain up:
virsh # attach-interface
Package: virt-manager
Version: 0.6.0-6
Severity: important
When I create a new guest via Virtual Machine Manager, the initial display is
set to VNC with the VNC port automatically allocated. When I now power up the
guest and switch to the console tab, I just see a message:
Console is not yet
Please attach the domains xml.
-- Guido
Sure, XML dump is below. When I start this guest, VNC is indeed
listening on port 5900 and I can connect to it per hand.
xenhost:~# netstat -avpn | grep qemu-dm
tcp0 0 127.0.0.1:5900 0.0.0.0:*
LISTEN 2146/qemu-dm
unix 3
Package: kvm
Version: 72+dfsg-4
Severity: normal
Referencing the former bug #487224 opened by Holger Fischer -
is it possible to backport the fix for PXE boot with an
e1000 network card also into the current Lenny version of KVM?
-- Package-specific info:
/proc/cpuinfo:
processor : 0
Package: xen-utils-common
Version: 3.2.0-2
Severity: normal
When I was trying to migrate (xm migrate) a guest from one host to another,
it simply fails. On the source host the virtual machine gets destroyed
without any warning message - on the destination host I see the following
error message
Package: debian-installer
Version: 20090123
Severity: normal
for etch I was using the following preseed lines to setup my systems
partition with LVM:
d-i partman-auto/purge_lvm_from_device boolean true
d-i partman/confirm_write_new_label boolean true
d-i partman/confirm boolean true
d-i
Package: debian-installer
Version: 20090123
Severity: normal
With etch's debian-installer we used the preseed lines below to
automatically setup our partitions. /boot and / as primary
partitions, all others as logical volumes.
d-i partman-auto/init_automatically_partition \
select Guided -
1 - 100 of 140 matches
Mail list logo
