similar to: pvhvm on debian

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

Hi developers, I met some domU issues and the log suggests missing interrupt. Details from here: http://www.gossamer-threads.com/lists/xen/users/263938#263938 In summary, this is the suspicious log: (XEN) vmsi.c:122:d32767 Unsupported delivery mode 3 I''ve checked the code in question and found that mode 3 is an ''reserved_1'' mode. I want to trace down the source of this

Hey folks, I'd like to get a .deb of the unmodified_drivers put together. I just filed ITP, and I would love to have your help with it. http://wp.colliertech.org/cj/?p=653 I've never built a kernel package before, nor have I used DKMS, so it's going to be a bumpy ride for me. Do any of you have experience with these tools? Have you built the unmodified_drivers modules recently?

Processing commands for control at bugs.debian.org: > reopen 678923 Bug #678923 {Done: George Shuklin <george.shuklin at gmail.com>} [xcp-xapi] xcp-xapi: host-disable and host-reboot make host disable forever Bug reopened Ignoring request to alter fixed versions of bug #678923 to the same values previously set > End of message, stopping processing here. Please contact me if you need

Rowland, you are correct. I remember now. When we started using XenServer, Wheezy would not work under it. This is a Squeeze installation, not Wheezy. Will Samba no longer work with Squeeze? If so it may be an excuse to upgrade the domain after all these years. On 06/05/2015 11:23 AM, Rowland Penny wrote: > On 05/06/15 16:07, Ryan Ashley wrote: >> I noticed something different on the

Ok, so if i understand right, your sysvol is on a shared folder which is a debian squeeze server. i think you problem is that the needed acl cant be set on the queeze server. and why not systemd, since gentoo also does systemd https://wiki.gentoo.org/wiki/Systemd and if you really want, just run your install with preseed/late_command="in-target apt-get install -y sysvinit-core"

Hey Roger, I am seeing this weird behavior when using #linux-next + stable/for-jens-3.8 tree. Basically I can do ''pvscan'' on xvd* disk and quite often I get checksum errors: # pvscan /dev/xvdf PV /dev/xvdf2 VG VolGroup00 lvm2 [18.88 GiB / 0 free] PV /dev/dm-14 VG vg_x86_64-pvhvm lvm2 [4.00 GiB / 68.00 MiB free] PV /dev/dm-12 VG vg_i386-pvhvm lvm2

Well, here is my plan of action. I will migrate the VMs on the secondary server to the primary one. Then I will zero the RAID10 array, install the latest XenServer, and load a Gentoo VM to build the needed binary packages. I can then create a new DC, promote it to the primary server, move the Windows VMs back to the secondary server, and then wipe and reload the primary box. This way I have an

Louis, 4.2.2 (git clone method for 4-2-stable branch) is what I am running. I will NOT be using Debian 8 due to systemd. If I have to do this, we're going to plan a down-time for the client, zero everything, do a fresh XenServer install and install Gentoo 64bit under XS. If that is what must be done, so be it. I can do that. I'll simply have one VM on each physical server which builds the

Package: xen-hypervisor-4.1-amd64 Version: 4.1.2-2 When installing xen-linux-system on a new Dell R810 server, Wheezy, Squeeze and Ubuntu server 11.10 all boot fine when booted directly into the standard kernel, but when booting through Xen (after installing the package xen-linux-system) the boot process hangs as soon as Xen passes control to the Dom0 kernel: "Gave up waiting for root

Hello, I just discovered a strange bug with serial passthrough in xen 4.1 on Debian Wheezy. The Dom0 has a GSM modem connected to serial port. The serial port is passed through to a DomU with options 'irq = [ 4 ]' and 'ioports = [ '3f8-3ff ]'. This worked as expected on Debian Squeeze with Xen 4.0 and Linux kernel 2.6.32 (both for Dom0 and DomU). On Debian Wheezy with Xen

Hello, I just discovered a strange bug with serial passthrough in xen 4.1 on Debian Wheezy. The Dom0 has a GSM modem connected to serial port. The serial port is passed through to a DomU with options 'irq = [ 4 ]' and 'ioports = [ '3f8-3ff ]'. This worked as expected on Debian Squeeze with Xen 4.0 and Linux kernel 2.6.32 (both for Dom0 and DomU). On Debian Wheezy with Xen

Subject: xen-utils-4.1: /usr/lib/xen-default missing Package: xen-utils-4.1 Version: 4.1.3-1 Severity: important Dear Maintainer, when using paravirtualization with xen and libvirt the path for pygrub is: /usr/lib/xen-default/bin/pygrub But this path is not provided with xen-utils-4.1 and will brake upgrades to wheezy. With xen-utils-4.0 and debian squeeze this path is provided with

Package: xen-hypervisor-4.1-amd64 Version: 4.1.3-3 Severity: normal Forwarded: http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1789 Dear Debian Xen Team, after an upgrade from Squeeze to Wheezy I see about ten of these per second filling my system log (about 8 MB/h): Nov 23 00:15:37 acromantula kernel: [ 462.544193] powernow-k8: fid trans failed, fid 0x2, curr 0x0 Nov 23 00:15:37 acromantula

Hi, can anyone provide any pointers as to how to avoid this issue? A CentOS 5.3 domU on snv_111 dom0 is crashing on bott unless I remove /lib/modules/2.6.18-128.1.6.el5/kernel/drivers/xenpv_hvm dom0: haggis:~$ uname -a SunOS haggis 5.11 snv_111 i86pc i386 i86xpv Name: SUNWxvm Summary: Hypervisor Header Files Category: System/Virtualization State: Installed

There are basically three issues we''re waiting to sort out (see below for more info): * XSA-55 * cpu hotplug in qemu-upsream * The MMIO hole issue Unfortuantely, there is considerable uncertainty about how long it will take for each of those to complete. We''re hoping to be able to release maybe on the 19th, This information will be mirrored on the Xen 4.3 Roadmap wiki page:

On 30/06/15 17:18, Ryan Ashley wrote: > I hate to revive this, but before I push my client through an upgrade, I > have to be sure my issue is with ACLs not being supported, as suggested. > Squeeze does have ACL support. > > root at dc01:/samba/var/locks# getfacl sysvol > # file: sysvol > # owner: root > # group: 3000000 > user::rwx > user:root:rwx >

Hi, I'm attempting to install the 3.3 beta3 on Debian. The files are located in a directory that looks like they were built for Debian Lenny, here: http://download.gluster.org/pub/gluster/glusterfs/qa-releases/3.3.0beta3/Debian/5.0.3/ Note the 5.0.3 at the end of the path.. However, when attempting to install the .deb file, it gives an error about package libssl1.0.0 being missing. That

Hi. On the release version of Debian Wheezy, I am missing symbols for left and right brackets in plotmath. Anybody see similar trouble while reviewing demo(plotmath)? This is a completely clean, fresh install. I've not installed any peculiar libraries or packages, except R, the installation of which still puzzles me. I configured a CRAN mirror for packages using squeeze-cran3 folder, and

I want to try to get VGA passthrough working in a Windows 7 x64 domU. I''m running debian squeeze/testing/unstable with Jeremy''s 2.6.32.x kernel. The best I got to work is the device showing up under Windows 7, with all resources and whatnot. I''ve applied the vga-loadbios patch and vBAR-pBAR patch to xen, and the vBAR-pBAR patch to qemu-dm. This behaviour