similar to: Bug#744157: (no subject)

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,vncdisplay=6369,vncpasswd=x'] Working xl version: vnclisten="0.0.0.0:6369"

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. The domain keeps running during the save operation, doesn't get paused for any

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. Relevant snippet: # default vif script #vifscript="vif-bridge"

Package: xen-utils-4.3 Version: 4.3.0-3+b1 Severity: normal When I try to create an HVW withDevian/xen, I run into trouble. It used to work, maybe with xen 4.1, but it has never worked since. Bug 688311 was filed, with the same exact problem. That bug was somehow closed and no resolution or explanation was provided. I have seen posts mentioning "traditional" and "upstream"

Package: xen-hypervisor-4.3-amd64 Version: 4.3.0-3+b1 Severity: critical File: xen-hypervisor-4.3-amd Justification: breaks the whole system Dear Maintainer, Installation is a minimal system designed only to get dom0 working. The following are the uncommented GRUB commands GRUB_DEFAULT=0 GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`

Dear Xen-Team, after an debian-update (jessie) the hvm do not start: I'm not sure it's a bug or a support-question? If it's a bug I don't know which packet is affected. <http://www.dict.cc/englisch-deutsch/affected.html> I get now response on mailing lists so it look looks like bug fore me. The hvm works fine until I did 'apt-get upgrade' ( I think on Aug 9).

Package: xen-hypervisor-4.3-amd64 Version: 4.3.0-3+b1 Severity: normal Dear Maintainer, After booting into kernel 3.13 dom0, the keyboard no longer works. All other aspects work, ssh is needed to login to the system to start working with the domU's. They keyboard works at the grub menu just fine, and works normal when booting into the non xen kernel. -- System Information: Debian Release:

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're the relevant package versions: ii libxen-4.3 4.3.0-3+b1

Hi, I am having great difficulties in getting pci passthrough with VTd to work, surely I am doing something stupid but I cannot see what. "tangram" (https://www.blogger.com/profile/06588030231546523539) has been a huge help, but despite his efforts I am still stuck. Hardware: Intel S3200SHV motherboard BIOS : S3200X38.86B.00.00.0052 CPU : Intel Core 2

Hi Johannes: Thank you very much. Rkward now works. The only drawback is that I had to install it "by hand": sudo dpkg -i rkward_0.6.5-1~stretchcran.0_amd64.deb rkward-data_0.6.5-1~stretchcran.0_all.deb By default, apt-get installed the Debian repository version (rkward 0.6.5-1+b1 0.6.5-1+b1). Thanks for your contributions to the R-Debian project! Regards. Griera. On Mon, 25

When using the 4.3.0-3/4.3.0-3+b1 xen packages from the Debian archive, things work fine. However, when we compile the xen=4.3.0-3 source package ourselves, we run into an issue launching an HVM. As soon as the HVM bios is loaded, VCPU0 gets a triple fault and the HVM is destroyed (this is with "loglvl=all guest_loglvl=all hvm_debug=3" boot options). (XEN) HVM1: Multiprocessor

L.P.H. van Belle via samba writes: > Is samba-dsdb-modules installed ? Yes, I checked again, and all packages are installed, all of them with the proper version, and no leftovers. This server works fine for a half a day, and then these errors happen, so I think it's unlikely that it's related to the install itself. I have already made a backup of all tdb files with tdbbackup and

Package: xen-utils-common Version: 4.3.0-3 Severity: normal Dear Maintainer, I've just set up a fresh Jessie system using the installer dated 2014-03-05, then installed and enabled Xen 4.3. I've done this quite a few times before using Wheezy and 4.1. I set up xenbr0, then created a test domU using xen-create-image, which completed without issue. However I was unable to start the new

Read the data using scan(): # # a1 a2 a3 a4 # ------------- ------------- ------------- ------------- # b1 b2 b3 b1 b2 b3 b1 b2 b3 b1 b2 b3 # --- --- --- --- --- --- --- --- --- --- --- --- # # c1: # 4.1 4.6 3.7 4.9 5.2 4.7 5.0 6.1 5.5 3.9 4.4 3.7 # 4.3 4.9

Forgive me if this questions has been dealt with recently as I have been on a vacation/holiday and have not kept current with list activity. While building a VM with "setup-samba430-Jessie.sh" I notice that Debian 'experimental' is now (pulling) samba-4.3.1+dfsg-1 version. The script is not running correctly as (obviously) the patches are for samba-4.3.0+dfsg packages.

On Wed, 2014-01-01 at 09:52 -0600, Marc F. Clemente wrote: > I have seen posts mentioning "traditional" and "upstream" qemu-dm. > But it is not clear to me what the difference is between "traditional" > and "upstream", or how to select either one. This is explained in the xl.cfg(5) man page. http://xenbits.xen.org/docs/unstable/man/xl.cfg.5.html

On 01/02/2014 11:56 AM, Ian Campbell wrote: > You can select a non-default model use by using the > "device_model_version" directive in your config. From what I gather, for now, you MUST select a non-default model, using something like: device_model_version="qemu-xen" device_model_override="/usr/bin/qemu-system-x86_64" > In the context of Debian the

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

Dear mailing list, How do I make Tinc auto start on Debian 8 Jessie? I’ve compiled and installed the latest stable release tinc-1.0.33 and I’ve tried this: nano /usr/local/etc/tinc/nets.boot Added the netname of my vpn sudo service tinc start Should work according to: https://www.digitalocean.com/community/tutorials/how-to-install-tinc-and-set-up-a-basic-vpn-on-ubuntu-14-04

Hi list, for future reference: we haven't been able to fix it. Upgrading to 4.9.18 didn't help, so in the end we decided to downgrade to our previous version (4.5.12) which doesn't have this problem. Hooray for tdbbackup! Thanks Louis for thinking with us. Best regards, Roel And for Google: smbd[16461]: ldb: Failure during ltdb_lock_read(): Locking error ? Busy smbd[16461]: