Bug#753258: LIO crash

2014-06-29 Thread Matyas Koszik
Package: linux-image-3.2.0-4-amd64 Version: 3.2.57-3+deb7u2 Severity: important I'm running a redundant storage server pair with DRBD and LIO. On the secondary node I had some RAID card resets, which triggered DRBD to disconnect the node - but before that, requests were held for several seconds

Bug#744930: Failed migration from 4.3 to 4.1 crashes VM on sender

2014-04-16 Thread Matyas Koszik
Package: xen Version: 4.3.0-3+b1 When trying to migrate from a 4.3 host to a 4.1 host (which should fail of course, but gracefully), the PV guest on the sending host crashes. To be honest, I have no idea which component to file this bug against. The sending host has been upgraded to jessie. Here

Bug#744157: (no subject)

2014-04-16 Thread Matyas Koszik
I'm afraid this still doesn't work even after upgrading to jessie (xen-utils-4.3 4.3.0-3+b1). Should I open a new bug against xen-utils-4.3 or can this bug somehow be applied to that package as well? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "uns

Bug#744927: No VIF information in xentop with xl

2014-04-16 Thread Matyas Koszik
Package: xen-utils-4.3 Version: 4.3.0-3+b1 Using the xl toolstack there's no information about the networks of the domUs in xentop. I have a PV and a HVM domU and both are shown as having 0 network interfaces, while in fact they have functioning interfaces. Here's one of the interfaces that shou

Bug#744163: xenstore problems

2014-04-10 Thread Matyas Koszik
Package: xen-utils-4.1 Version: 4.1.4-3+deb7u1 Severity: important When starting (or migrating in) a domain, sometimes I get the following exception: [2014-04-01 10:58:08 4821] ERROR (XendDomainInfo:2927) XendDomainInfo.initDomain: exception occurred Traceback (most recent call last): File "

Bug#744160: xl.conf ambiguity

2014-04-10 Thread Matyas Koszik
Package: xen-utils-common Version: 4.1.4-3+deb7u1 Severity: minor In the file /etc/xen/xl.conf there's a suggestion that vif scripts should be named relative to the /etc/xen/scripts directory, which is not the case, since absolute paths have to be used. The manual page xl.conf(5) is also missing.

Bug#744159: HVM guest can't be saved/migrated with xl

2014-04-10 Thread Matyas Koszik
Package: xen-utils-4.1 Version: 4.1.4-3+deb7u1 Severity: normal It seems to be impossible to save or migrate HVM guest using the xl toolstack. Trying to do so hangs the process initiating the action, and the domU can't be shut down with the 'xl shutdown' command after this. 'xl destroy' works. Th

Bug#744157: VNC parameters can be set only globally using xl

2014-04-10 Thread Matyas Koszik
Package: xen-utils-4.1 Version: 4.1.4-3+deb7u1 Switching to the xl toolstack I expected my configuration to work unmodified, but it doesn't, and I couldn't find any documentation regarding this, since xl.cfg(5) is missing. Original version, used with xm: vfb = ['type=vnc,vnclisten=0.0.0.0:6369,

Bug#613676: installation-reports: Keyboard does not work in Gnome/X after upgrade to squeeze

2011-02-21 Thread Matyas
I gave up on finding the bug. I will not be able to provide further system diagnostic and other information. Take care. -Matyas - Every hardware eventually breaks. Every software eventually works. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of

Bug#613676: installation-reports: Keyboard does not work in Gnome/X after upgrade to squeeze

2011-02-17 Thread Matyas
ned a window (where the keyboard still did not work). - I have no login set for the default user (this is a mythfrontend machine). - I configured to have lirc, irxevent, irexec, mythfrontend to run on startup of Gnome. ps shows that mythfrontend is running, but there is no GUI visible. The mythfrontend log indicates no errors. This latter makes me suspect that X/Gnome somehow fails to react and it is not the keyboard at fault. Thanks again. -Matyas - Every hardware eventually breaks. Every software eventually works. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#613676: installation-reports: Keyboard does not work in Gnome/X after upgrade to squeeze

2011-02-17 Thread Matyas
lso there, after a reboot I picked it: Nos? # uname -r 2.6.32-5-amd64 The keyboard problem is still there. Thanks! -Matyas - Every hardware eventually breaks. Every software eventually works. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubsc

Bug#613676: installation-reports: Keyboard does not work in Gnome/X after upgrade to squeeze

2011-02-17 Thread Matyas
4, the one pulled in by squeeze. -Matyas - Every hardware eventually breaks. Every software eventually works. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#613676: installation-reports: Keyboard does not work in Gnome/X after upgrade to squeeze

2011-02-16 Thread Matyas
stable') Architecture: i386 (x86_64) Kernel: Linux 2.6.35-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xorg depends on: ii gnome-terminal [x-terminal-em 2.30.2-1 The GNOME terminal

Bug#613676: installation-reports: Keyboard does not work in Gnome/X after upgrade to squeeze

2011-02-16 Thread Matyas A. Sustik
Package: installation-reports Severity: critical Justification: breaks unrelated software (First bug report; please be kind...) After doing apt-get dist-upgrade to squeeze I lost keyboard functionality under X/Gnome. Keyboard works during boot (setup, grub menu). If I stop gdm then keyboard w

Bug#588622: "nofatal" in openlog causes messages to be printed to stdout

2010-07-10 Thread Matyas Koszik
Package: perl Version: 5.10.0-19lenny2 Severity: normal The following code should not print anything to stdout, but it will: use Sys::Syslog; openlog "x", "nofatal", "local0"; syslog "err", "test"; There's no symbol named LOG_NOFATAL, so xlate in /usr/lib/perl/5.10.0/Sys/Syslog.pm will retu

Bug#560388: mount.nfs4: 'bg' option is not implemented; 'fg' doesn't work as expected

2009-12-10 Thread Matyas Koszik
er0m0.000s sys 0m0.000s # And there's one more, related to the same paragraph of the man page: # mount x:/ /nonexistent -o bg mount.nfs: mount point /nonexistent does not exist # "If the local mount point directory is missing, the mount(8) command acts as if the mount request timed