similar to: Bug#675266: Please try to reproduce with Xen 4.1 from Wheezy.

There's a couple of patches in 4.1 which might plausibly be the fix for this. changeset: 23246:8f927378135a user: Jan Beulich <jbeulich at suse.com> date: Wed Mar 07 08:35:58 2012 +0000 files: xen/arch/ia64/xen/domain.c xen/arch/x86/domain.c xen/arch/x86/domctl.c description: passthrough: release assigned PCI devices

Hi Eric, I see that this happened with 3.1 kernel. Wheezy now has 3.2 which it will be releasing with, can you try that please? I'm afraid that because your kernel command line contained the "quiet" option there isn't much to go on in your video. If you can reproduce then even if you can't do serial console please do remove the quiet option. Ian.

On Feb 18, 2015, at 7:56 PM, Gene Heskett <gheskett at wdtv.com> wrote: > Even though I installed nut-doc, there are no man pages so I am running in > the dark again. They seem to be in the file list: https://packages.debian.org/wheezy/amd64/nut-client/filelist Is $MANPATH set to something strange? > > Where is the initial config and startup procedure to be found? ISTR it

Control: tag -1 +moreinfo Hi Marco, Thanks for your report. Unfortunately the logs you've provided are from a system booted without Xen, and due to the nature of the bug it is unlikely that any relevant logs made it onto the disk in order to survive the resulting reboot. Please could you try setting up a serial console and collect the full boot log.

On 18 February 2013 16:32, Ian Campbell <ijc at hellion.org.uk> wrote: > On Mon, 2013-02-18 at 13:51 +0000, Gavin wrote: > > > <stumped! /> > > If the kernel hasn't changed and you are 100% sure the network > configuration before and after the reboot is the same then so am I. > > All I can suggest is to reinstall the previous version of Xen. > Thanks

Ian Campbell <ijc at hellion.org.uk> writes: #Was that with the Jessie or Wheezy dom0 kernel? Actually tried both kernels. 3.13 on Jessie and 3.2 on Wheezy. The keyboard failed on any xen 4.3 boot. If it was nonxen, or xen 4.1 on any kernel the keyboard worked normal. Thanks for your help troubleshooting. Cheers, Mike -------------- next part -------------- An HTML attachment was

Greetings Charles; I eventually gave up making it work on ubuntu-10.04.4 LTS, and that drive is slowly curling up its toes, so I am running wheezy on a fresher drive now. I have installed all the nut stuffs from the repo, and now have two more scripts in /etc/init.d called nut-client and nut-server. dmesg |grep Belkin - : root at coyote:/etc/nut# dmesg|grep Belkin [ 4.242066] usb 2-3:

Control: tags -1 + moreinfo On Sat, 2016-05-14 at 19:10 +0200, Daniel Pocock wrote: > If somebody is still running wheezy for their dom0 (host) environment > and they are using jessie or other systems with grub2 in their VMs, they > can't boot their VM. > > A rather trivial 1-line fix in the dom0 (host) system fixes the problem. > > Please advise if the release team

Im setting up scripted samba4 installs to make things more uniform installations. It saves time, and errors, and it will be easier to trace bugs. ? This is the first one and more are comming. ? This is Update1: new link:? https://secure.bazuin.nl/scripts/? files are now clickable, we want easy ;-) ? How does it work and what do you need and what do you get in the end. ? What you get. Debian

Small update, i saw some errors in the webserver, i fixed the links below. All working now. ( sorry for that ) --------------- Im setting up scripted samba4 installs to make things more uniform installations. It saves time, and errors, and it will be easier to trace bugs. ? This is the first one and more are comming. ? This is Update1: new link:? https://secure.bazuin.nl/scripts files are

On 14/05/16 19:35, Adam D. Barratt wrote: > Control: tags -1 + moreinfo > > On Sat, 2016-05-14 at 19:10 +0200, Daniel Pocock wrote: >> If somebody is still running wheezy for their dom0 (host) environment >> and they are using jessie or other systems with grub2 in their VMs, they >> can't boot their VM. >> >> A rather trivial 1-line fix in the dom0

Package: src:xen Severity: important Version: 4.1.3~rc1+hg-20120614.a9c0a89c08f2-2 I recently upgrade from Squeeze to Wheezy on a system which had the xen-linux-system-686-pae metapackage (one of two which Provides: xen-linux-system). After dist-upgrade I had the new xen-utils-common and xenstore-utils (and a few others) but not the xen-utils-4.1 or xen-hypervisor-4.1-i386 or xen-hypervisor-amd64

Package: release.debian.org Severity: normal Tags: wheezy User: release.debian.org at packages.debian.org Usertags: pu X-Debbugs-CC: pkg-xen-devel at lists.alioth.debian.org If somebody is still running wheezy for their dom0 (host) environment and they are using jessie or other systems with grub2 in their VMs, they can't boot their VM. A rather trivial 1-line fix in the dom0 (host) system

Hai, ? Im setting up scripted samba4 installs to make things more uniform installations. It saves time, and errors, and it will be easier to trace bugs. ? This is the first one and more are comming. ? ? How does it work and what do you need and what do you get in the end. ? What you get. Debian wheezy, with sernet samba4.1 - server setup as AD-DC? ( the first server with samba4 )

Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-3+deb7u1 Severity: important Dear Maintainer, We are having a problem on several Supermicro servers (I'll include more details on the configuration later) : when booting Linux 3.2 linux-image-3.2.0-4-amd64 (Wheezy) as a DOM0 on Xen 4.1 (xen-hypervisor-4.1-amd64 from Wheezy), the system hangs after : [ 3.716174] scsi1 : ata_piix [

Apologies if this is posted on the wrong list, but when I try to get pci passthrough to work on a Wheezy Xen box I get NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out and then not much else works at all. The same hardware works just fine with Xen and Squeeze. It seemed to me that the problem I am seeing is very similar to

On Thu, 2014-05-15 at 12:44 -0700, Mike Egglestone wrote: > FWIW, > I also tried a fresh wheezy install. > Dist-upgraded to Jessie, and installed the xen-hypervisor package. > Then rebooted into the XEN 3.2 kernel that comes with wheezy. > Keyboard still doesn't work. Was that with the Jessie or Wheezy dom0 kernel? Ian.

Hi, "Ian Campbell" <ijc at hellion.org.uk> ?rta 2013-10-22 11:17-kor: > On Tue, 2013-10-22 at 11:52 +0200, PASZTOR Gyorgy wrote: > > When you use xl toolstack, you can't reboot domUs. > > When you switch back to xm toolstack, than reboot works again. > > I think the problem with the debian packaged version is the same as in > > this thread: > >

Package: xen-utils-4.4 Version: 4.4.1-9+deb8u8 Severity: normal Under Xen 4.1 in Debian 7 (wheezy), the following works when included in a DomU configuration in "/etc/xen/cfg/" -- bootloader = '/usr/lib/xen-default/bin/pygrub' After upgrading to Xen 4.4 as part of an upgrade to Debian 8 (jessie), the DomU silently fails to start. Examination of the log files shows that the

Hai,   Fist.. i start with a BIG THANK YOU to Achim Gottinger for making these samba wheezy packages and sharing them.   Achim created the samba 4.6.2 packages and i did a rebuild and checkup of these. I have uploaded the packages in my apt repo and to the download location.   Achim already applied the following to bug fixed: https://bugzilla.samba.org/show_bug.cgi?id=12685  net ads keytab