search for: kannenberg

Hello, I've been consistently attempting to make the setup mentioned in the subject work on the following hardware: Xeon E3 1275 (v1, Sandy Bridge) Asus P8B WS (Firmware: 0904 and 2009) 16 GB RAM Sapphire Radeon HD 7950 OC (Firmware: 015.013.000.010.000705) Linux 3.4.1 dom0, x86-64, pvops. Xen 4.1.2 (+ security patch) and 4.1.3-rc1. Old qemu-dm setup. (not new mainline qemu) Windows 7 64-bit

hi all, i just wonder, after searching the online resources, if there is any paper describing howto uninstall completelly xen: - xen, - tools and - stubdom from a debian box. maybe also a brief description how to update, for example, a xem 4.1.2 to 4.2 in a future step? i use: - debian 6.0.5 amd64 - xen 4.1.2 - kernel 3.4.4 thanks a lot for your answers walter.

Hi, everyone. I''m Guilherme Suzuki (brazillian, by the way) and really interested in xen-vga-passthru. Lately, I bought a brand new Saphire HD 7950 (OC Boost) because I saw in a wiki somewhere that users have been able to passthru these VGA devices to domU (win7, win-xp and so on). But, after I installed it, I executed *lspci -vv* to check if FLR in DevCap was present (which

Hi, unfortunatly your latest change "AMD,IOMMU: Clean up old entries in remapping tables when creating new one" (Changeset 26517 in xen-unstable and 25975 in xen-4.2-testing) is causing a CPU0 Panic at boot for me. When i tried to boot latest versions of xen unstable or xen-testing, my dom0 gives me the message: (XEN) ************************************* (XEN) Panic on CPU 0: (XEN)

Hi All, We have a xen server and using 8 core processor. I can see that there is 99% iowait on only core 0. 02:28:49 AM CPU %user %nice %sys %iowait %irq %soft %steal %idle intr/s 02:28:54 AM all 0.00 0.00 0.00 12.65 0.00 0.02 2.24 85.08 1359.88 02:28:54 AM 0 0.00 0.00 0.00 96.21 0.00 0.20 3.19 0.40 847.11 02:28:54 AM

Hi everyone since I''m currently migrating from xm to xl and now are also a victim of the said error, I started researching on it and found that many people had the issue but not many found solution and behind this BSOD (=Bluescreen of Death), there are actually multiple errors in hiding. What I would like to do is gather as much info as possible in this thread to form a kind of

Hi, sure I can give you some info, but unfortunately as explained here (http://lists.xen.org/archives/html/xen-users/2012-06/msg00392.html), dual vga is broken for me currently, too. But i guess this is only a matter of finding the currupted changeset. In general, I was never aware that this is even a problem. I used to simply hide both graphic cards from the dom0 at boot time via the

Good evening everyone, I am attempting to compile Xen 4.2.1 from source on Ubuntu 12.10 and cannot for the life of me figure out what I am doing wrong. This is the script I wrote that I am running on a brand new install from ubuntu-12.10-server-amd64.iso apt-get update apt-get -y upgrade apt-get -y dist-upgrade reboot (uname -r returns back 3.5.0-23-generic) apt-get install -y build-essential

Hi everyone, I would like to ask what the current status of FLR, or better of FLR emulation is in latest Xen and if we can expect better support in the future. I''m asking because with xl (latest build and traditional qemu, not upstream), I always had problems with rebooting domUs which have vga cards passed through to them, because appearently they don''t get reinitialized and

Hi everybody, I''m currently a little confused about the status of the different qemu trees for xen unstable.. from what I''ve gathered so far, there are 3 different trees: 1) Qemu-Xen-Unstable (Repo: http://xenbits.xen.org/gitweb/?p=staging/qemu-xen-unstable.git;a=shortlog;h=refs/heads/master ) This is the default repository which is download while xen-unstable is build 2)

Hi, I''m currently switching from toolstacks from xm to xl. Because I have a rather complex network setup with my domUs, I use xen''s nat capabilities. But what works fine with xm behaves slightly strange in xl: I use something like the following to establish a domU interface within my vif part: ''type=vif, mac=00:16:3E:06:DA:B2, ip=192.168.2.1, vifname=fw11,