similar to: Still trying to run hvm (Invalid mode)

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: grave I tried to start an HVM guest to setup Windows 2003 64 bits entreprise R2, and I spent a long time figuring out that there is no /usr/lib/xen folder by default, and this is where Xen is searching for it's file when using HVM, VNC and all. Doing a simple symlink with ln -s /usr/lib/xen-3.2.1 /usr/lib/xen made it working, if it's not

Package: xen-utils-common Version: 4.1.0~rc6-1 Recently I had troubles with creating more than one network bridge for my domU. For example, I have 2 domU running with xenbr0 bridge for both with peth0 and two vif#.0 interfaces in it. Everything is fine. Now I need to run another one domU with a different bridge attached to a different interface. I'm trying to bring up a new bridge manually

Hello, I asked Aurelien Jarno from the Debian glibc team about our /lib/tls problem. It gave me a little help: # ldd /bin/echo libc.so.6 => /lib/tls/libc.so.6 (0x40021000) # touch /etc/ld.so.hwnocap # ldd /bin/echo libc.so.6 => /lib/libc.so.6 (0x40021000) I think this could help us. -- Julien Danjou .''`. Debian Developer : :' :

Package: xen-hypervisor-3.2-1-i386 Version: 3.2-1 Severity: critical Tags: security Justification: DoS of entire system regardless of privilege When running the exploit listed in bug 464953 [1], Xen's memory state becomes corrupted and the hypervisor eventually crashes, taking all of the domU's with it. As such, this breaks operational behaviour, so I have marked this as critical. [1]

Hi folks I tried to find a solution for the update problem. Currently I have 3 kernels, 2.6.16-16, 2.6.16-17 and 2.6.17-6 and each of them needs another hypervisor. As it is the goal of Debian to not break on updates completely, I propose the following change: * Introduce xen-common source which provides xen-utils-common binary packages. This package provides a dispatcher for the installed

Hi, I'm having difficulty applying and rebuilding the patch for the version of Xen included in Debian's Etch release. After applying the patch and updating the changelog I receive this error: steve at dev:~/xen-3.0-3.0.3-0$ debuild -sa fakeroot debian/rules clean if [ -f debian/control ] && [ -f debian/control.md5sum ] && [ -f debian/rules.gen ]; then \

Package: xen-utils-4.1 Version: 4.1.3-2 Severity: important Dear Maintainer, Creating a new HVM domU fails with the following error: map shared IO page returned error 22 I've narrowed it down to qemu-dm which fails to start: # /usr/lib/xen-4.1/bin/qemu-dm [...] qemu_map_cache_init nr_buckets = 10000 size 4194304 errno0 = 2 domid = -1 shared page at pfn 0 errno1 = 3 errno2 = 22 map shared IO

Package: xcp-xapi Version: 1.3.2-9 Severity: normal Function wait_for_xapi in /etc/init.d/xcp-xapi does not work as intented. Symptoms: (on slave) /etc/init.d/xcp-xapi restart [....] Restarting The XenAPI server: xapiThe host toolstack is still initialising. Please wait. Cause: Line 'xe pif-scan host-uuid=${INSTALLATION_UUID}' called before xapi is fully synced with master.

Hi folks With the lack of responses to my restructuring the last weeks, it looks like pkg-xen is dead. Now, what to do? My favorite is to merge it into the kernel repository where I have my infrastructure (archive and autobuilders for snapshots for example) to properly work on it. Bastian -- No one wants war. -- Kirk, "Errand of Mercy", stardate 3201.7 -------------- next part

I''m going to set up a PVM on xen-3.3.1 debian-amd64. I need advices about the best methods to install a fresh debian on it (i.e. how to choose the kernel for pvm) . I''ve installed xen from sources and only have one xen kernel in /boot which I''m using for dom0; should I use the same kernel for domUs? There is any problem on use vcpus=2; the other vm is an hvm running

I''m still having some issues with cloud provisioner. I have a fresh install of provisioner, .60rc1, puppet 2.7.3, and dashboard 1.2.0. Everything has a very default install as described in the documentation. I was unable to get bootstrap to work, so I did things in a linear fashion (create, install, classify). Classify is failing and theres not really any good debug info, I just get

Hi folks I propose the following changes for 3.1: - Rename source to xen-3. Upstream stripped one part of the version, so the next should be 3.2. - pygrub as extra package. - Rename i386 to i386-nonpae - Rename i386-pae to i386. PAE is upstream default now and pae images works with a 64bit hypervisor. We should think about supporting libvirt. It provides an AFAIK stable interface on the

Hi folks XenSource published a trademark policy[1]. I don't think we will be able to follow it if we want to support installation of different versions at the same time. Bastian [1]: http://www.xensource.com/company/legal.html -- There are some things worth dying for. -- Kirk, "Errand of Mercy", stardate 3201.7 -------------- next part -------------- A non-text attachment was

[message cross posted to the pkg-xen and xen-devel list] Dear everyone, Bastian Blank - which is the person (among others, but mainly him) that is packaging Xen in Debian -, has decided last summer that he doesn't want to deal with the qemu-dm of Xen, thus removing Xen Qemu and support for HVM in Debian. Here is what he wrote:

[message cross posted to the pkg-xen and xen-devel list] Dear everyone, Bastian Blank - which is the person (among others, but mainly him) that is packaging Xen in Debian -, has decided last summer that he doesn't want to deal with the qemu-dm of Xen, thus removing Xen Qemu and support for HVM in Debian. Here is what he wrote:

I''m setting Xen3.0.4 with CentOS5.2 I don''t know what exactly needs to add. So I make ramdisk with following command. : mkinitrd -v -f --with libata --with sd_mod --with sg --with ext3 --with scsi_mod --with jbd --with ahci --with dm_mod --with dm_multipath --with dm_snapshot --with dm_zero --with dm_mirror --with pcspkr --with mii --with 8139too --with 8139cp --with i2c_piix4

I have a problem. In my application I have a few Grid objects in a Notebook. The Grid objects are populated via GridTableBase. Certain Grid cells need to have a choice interface (I''m artificially enforcing foreign key constraints). All this works to the point where you try to edit the value for that cell. The choice box renders (i.e. the drop down arrow appears) then the application

Package: xen-utils-3.4 Version: 3.4.0-1 Severity: important The current version of the package does not contain the IOEMU tools. This makes HVM domains, and PV domains with emulated features like VFB impossible to run. There might be good reasons for this, but then at least the package description should contain a warning that makes this obvious, so that users know that they can not simply

Package: xen-utils-common Version: 4.1.4-3+deb7u1 Severity: normal Dear Maintainer, i changed toolkit to xl, after that i observe that my domU started as HVM domains. I found same problem here: http://mail-index.netbsd.org/port-xen/2012/04/11/msg007216.html When i manualy setup loop devices and specify it as disks in my VM conf file, domU started as PV. -- System Information: Debian Release: 7.1

R-developers, I have a binary R package built using R 2.14.1 that I would like to run on R 3.0.0. Unfortunately, the original source code is unavailable, so I cannot rebuild the package as R 3.0.0 requires. Is there a straight forward way of converting the package (.rdb, .rdx and .rds files) in the binary package from a 2.14.1 version to a 3.0.0 version without the source code (perhaps