Block front and back connection

Block front and back connection

[Daniel Castro]

Hello,

I am trying to make my frontend block driver connect to xen block
backend. I have the ring and gref, yet I do not know where in xenstore
should I write the keys to tell the backend to connect to my frontend.

Thanks for the help.

Daniel

-- 
+-=====---------------------------+
| +---------------------------------+ | This space intentionally blank
for notetaking.
| |   | Daniel Castro,                |
| |   | Consultant/Programmer.|
| |   | U Andes                         |
+-------------------------------------+

Re: Block front and back connection

[Pasi Kärkkäinen]

On Mon, Aug 08, 2011 at 11:17:52PM +0900, Daniel Castro wrote:
> Hello,
> 
> I am trying to make my frontend block driver connect to xen block
> backend. I have the ring and gref, yet I do not know where in xenstore
> should I write the keys to tell the backend to connect to my frontend.
> 
> Thanks for the help.
> 

Did you check for example Linux kernel xen-blkfront and xen-blkback drivers? 
Upstream kernel.org Linux 3.0 has both included.

-- Pasi

Reporting some xen 4.1.2* and 4.0 issues like limitations to 4 VCPUs for debian squeeze HVMs etc

[Mark Schneider]

Thank you very much at Pasi (pasik) for his kindly help!

<pasik> ironm: well you might want to report those to xen-devel mailinglist
<pasik> ironm: with exact software versions, and exact step-by-step 
instructions how to reproduce
<ironm> pasik, yes .. it is easy to reproduce as I have prepared two xen 
live images you can put on an USB sticks and boot from them:
rsync -avP 
rsync://www.it-infrastrukturen.ch/ftp/xen411-wheezy-kernel3-amd64-live-gnome-binary-hybrid.iso 
.
rsync -avP 
rsync://www.it-infrastrukturen.ch/ftp/xen40-squeeze-amd64-live-gnome-binary-hybrid.iso 
.

More details how I was testing are at:
http://www.it-infrastrukturen.com/fileadmin/linux/debian-live-xen/README.xen-live

<ironm> pasik, only HMVs images are on raid
    ACTIVE            '/dev/vg_xen/squeeze' [32,00 GiB] inherit
    ACTIVE   Original '/dev/vg_xen/wheezy' [32,00 GiB] inherit


Issue 1: 4 VCPUs limitation for squeeze?
# ---
<ironm> pasik, my problem was/is that HVM images for squeeze and wheezy 
created on xen 4.0 for some reason didn't boot on xen 4.1.2* ..
<ironm> pasik, when I create HVM images on xen 4.1.2* they can boot 
correctly .. however with some limitations for squeeze (not more than 
4VCPUs )
<pasik> ironm: do the images made on 4.0 boot properly on 4.1.2 if you 
have only 1 vcpu and say, 1 GB of mem?
<ironm> pasik, I had to install again . and this squeeze images boots 
now with 8GB RAM / 4cores
<ironm> pasik, I made tests with 1 core / 1 GB, 2 cores / 2GB and 4 
cores / 8GB .. they worked
<ironm> 8cores / 4 or 8 GB didn't work for squeeze

The error looks like:
http://www.it-infrastrukturen.com/fileadmin/linux/paste/squeeze/squeeze-xen4.1.2-issue-install-menu-pic1.png
http://www.it-infrastrukturen.com/fileadmin/linux/paste/squeeze/squeeze-xen4.1.2-issue-error-pic2.png

Config files are like:
http://www.it-infrastrukturen.com/fileadmin/linux/paste/HVM/hvm-squeeze.born2b3.net.cfg
http://www.it-infrastrukturen.com/fileadmin/linux/paste/HVM/hvm-wheezy.born2b3.net.cfg

<ironm> pasik,  I will check if I can boot from HVM images (created on 
xen 4.1.2*) after rebooting xen 4.0

Issue 2: problem with too big install image size? (DVD images)
<ironm> maybe there is a problem when using DVD.iso images for 
installations .. (no problem with CD size )
<ironm> big size images (like DVD) or just the content (missing grub 
packages on them) causes install errors in HVMs

The error looks like:
http://www.it-infrastrukturen.com/fileadmin/linux/paste/wheezy/vxda-setting3-grub-error.png


Issues 3+: different errors in log files of xen 4.1.2*
http://www.it-infrastrukturen.com/fileadmin/linux/paste/wheezy/xen4.1.2-kernel3final/qemu-dm-squeezehvm.born2b3.net.log-xen412-k3.txt
http://www.it-infrastrukturen.com/fileadmin/linux/paste/wheezy/xen4.1.2-kernel3final/qemu-dm-wheezyhvm.born2b3.net.log-xen412-k3.tx
http://www.it-infrastrukturen.com/fileadmin/linux/paste/wheezy/xen4.1.2-kernel3final/xen-hotplug.log-xen412-k3.txt
http://www.it-infrastrukturen.com/fileadmin/linux/paste/wheezy/xen4.1.2-kernel3final/xend-debug.log-xen412-k3.txt
http://www.it-infrastrukturen.com/fileadmin/linux/paste/wheezy/xen4.1.2-kernel3final/xend.log-xen412-k3.txt
http://www.it-infrastrukturen.com/fileadmin/linux/paste/wheezy/xen4.1.2-kernel3final/xm_dmesg-xen412-k3.txt
http://www.it-infrastrukturen.com/fileadmin/linux/paste/wheezy/xen4.1.2-kernel3final/xm_info-xen412-k3.txt


Thank you / regards,
Mark

-- 
ms@it-infrastrukturen.org

Re: Reporting some xen 4.1.2* and 4.0 issues like limitations to 4 VCPUs for debian squeeze HVMs etc

[Pasi Kärkkäinen]

On Tue, Aug 09, 2011 at 01:26:44AM +0200, Mark Schneider wrote:
>
> Issue 1: 4 VCPUs limitation for squeeze?
> # ---
> <ironm> pasik, my problem was/is that HVM images for squeeze and wheezy  
> created on xen 4.0 for some reason didn't boot on xen 4.1.2* ..
> <ironm> pasik, when I create HVM images on xen 4.1.2* they can boot  
> correctly .. however with some limitations for squeeze (not more than  
> 4VCPUs )
> <pasik> ironm: do the images made on 4.0 boot properly on 4.1.2 if you  
> have only 1 vcpu and say, 1 GB of mem?
> <ironm> pasik, I had to install again . and this squeeze images boots  
> now with 8GB RAM / 4cores
> <ironm> pasik, I made tests with 1 core / 1 GB, 2 cores / 2GB and 4  
> cores / 8GB .. they worked
> <ironm> 8cores / 4 or 8 GB didn't work for squeeze
>
> The error looks like:
> http://www.it-infrastrukturen.com/fileadmin/linux/paste/squeeze/squeeze-xen4.1.2-issue-install-menu-pic1.png
> http://www.it-infrastrukturen.com/fileadmin/linux/paste/squeeze/squeeze-xen4.1.2-issue-error-pic2.png
>

So based on the "squeeze-xen4.1.2-issue-error-pic2.png" I recommend you to enable debugging options for the kernel, from the boot menu.

Add at least "nomodeset initcall_debug debug loglevel=10" 
Then paste/capture the output.

Some questions: 
	- That "BUG: soft lockup - CPU#0 stuck for 61s!" only happens when you have 8 vcpus, right?
	- What if you install with 1 vcpu, then after installation install the latest debian updates (new kernel),
	  and then try using 8 vcpus with the updated debian kernel?


> Config files are like:
> http://www.it-infrastrukturen.com/fileadmin/linux/paste/HVM/hvm-squeeze.born2b3.net.cfg

Looks OK.


> http://www.it-infrastrukturen.com/fileadmin/linux/paste/HVM/hvm-wheezy.born2b3.net.cfg
>

For what is this wheezy cfgfile? 


>
> Issue 2: problem with too big install image size? (DVD images)
> <ironm> maybe there is a problem when using DVD.iso images for  
> installations .. (no problem with CD size )
> <ironm> big size images (like DVD) or just the content (missing grub  
> packages on them) causes install errors in HVMs
>
> The error looks like:
> http://www.it-infrastrukturen.com/fileadmin/linux/paste/wheezy/vxda-setting3-grub-error.png
>

So are you saying you only get that GRUB error when installing from DVD.iso,
but if you install from CD.iso GRUB installs ok ? do other deb packages install OK? 

Is DVD/CD iso image the only difference? Are you sure the checksums of the iso images are OK?

>
> Issues 3+: different errors in log files of xen 4.1.2*
> http://www.it-infrastrukturen.com/fileadmin/linux/paste/wheezy/xen4.1.2-kernel3final/qemu-dm-squeezehvm.born2b3.net.log-xen412-k3.txt
> http://www.it-infrastrukturen.com/fileadmin/linux/paste/wheezy/xen4.1.2-kernel3final/qemu-dm-wheezyhvm.born2b3.net.log-xen412-k3.tx
> http://www.it-infrastrukturen.com/fileadmin/linux/paste/wheezy/xen4.1.2-kernel3final/xen-hotplug.log-xen412-k3.txt
> http://www.it-infrastrukturen.com/fileadmin/linux/paste/wheezy/xen4.1.2-kernel3final/xend-debug.log-xen412-k3.txt
> http://www.it-infrastrukturen.com/fileadmin/linux/paste/wheezy/xen4.1.2-kernel3final/xend.log-xen412-k3.txt
> http://www.it-infrastrukturen.com/fileadmin/linux/paste/wheezy/xen4.1.2-kernel3final/xm_dmesg-xen412-k3.txt
> http://www.it-infrastrukturen.com/fileadmin/linux/paste/wheezy/xen4.1.2-kernel3final/xm_info-xen412-k3.txt
>
>

What exactly is the issue here? What problem are you having? 

-- Pasi

Re: Block front and back connection

[Wei Liu]

On Mon, Aug 08, 2011 at 11:17:52PM +0900, Daniel Castro wrote:
> Hello,
> 
> I am trying to make my frontend block driver connect to xen block
> backend. I have the ring and gref, yet I do not know where in xenstore
> should I write the keys to tell the backend to connect to my frontend.
> 

You can find some clues in libxl_devices.c .

The frontend path is

/local/domain/FRONTEND_DOMID/device/DEVICE_KIND/DEVID

The backend path is

/local/domain/BACKEND_DOMID/backend/BACKEND_KIND/FRONTEND_DOMID/DEVID

Often the BACKEND_DOMID is 0.

And looking into Linux kernel's xen-{blkfront,blkback} helps you a
lot.

Then you can switch xenbus state after proper values are in place, so
that frontend and backend can connect to each other.

Wei.

Re: Block front and back connection

[Daniel Castro]

On Tue, Aug 9, 2011 at 11:27 AM, Wei Liu <liuw@liuw.name> wrote:
> On Mon, Aug 08, 2011 at 11:17:52PM +0900, Daniel Castro wrote:
>> Hello,
>>
>> I am trying to make my frontend block driver connect to xen block
>> backend. I have the ring and gref, yet I do not know where in xenstore
>> should I write the keys to tell the backend to connect to my frontend.
>>
>
> You can find some clues in libxl_devices.c .
>
> The frontend path is
>
> /local/domain/FRONTEND_DOMID/device/DEVICE_KIND/DEVID
>
> The backend path is
>
> /local/domain/BACKEND_DOMID/backend/BACKEND_KIND/FRONTEND_DOMID/DEVID
>
> Often the BACKEND_DOMID is 0.
>
> And looking into Linux kernel's xen-{blkfront,blkback} helps you a
> lot.
>
> Then you can switch xenbus state after proper values are in place, so
> that frontend and backend can connect to each other.
>
> Wei.
>

Thank, this is what I was looking for!

Daniel



-- 
+-=====---------------------------+
| +---------------------------------+ | This space intentionally blank
for notetaking.
| |   | Daniel Castro,                |
| |   | Consultant/Programmer.|
| |   | U Andes                         |
+-------------------------------------+

Re: Reporting some xen 4.1.2* and 4.0 issues like limitations to 4 VCPUs for debian squeeze HVMs etc

[Mark Schneider]

[-- Attachment #1: Type: text/plain, Size: 7363 bytes --]

Thanks a lot for your answer Pasi.

Am 09.08.2011 02:55, schrieb Pasi Kärkkäinen:
> On Tue, Aug 09, 2011 at 01:26:44AM +0200, Mark Schneider wrote:
>    
>> Issue 1: 4 VCPUs limitation for squeeze?
>> # ---
>> <ironm>  pasik, my problem was/is that HVM images for squeeze and wheezy
>> created on xen 4.0 for some reason didn't boot on xen 4.1.2* ..
>> <ironm>  pasik, when I create HVM images on xen 4.1.2* they can boot
>> correctly .. however with some limitations for squeeze (not more than
>> 4VCPUs )
>> <pasik>  ironm: do the images made on 4.0 boot properly on 4.1.2 if you
>> have only 1 vcpu and say, 1 GB of mem?
>> <ironm>  pasik, I had to install again . and this squeeze images boots
>> now with 8GB RAM / 4cores
>> <ironm>  pasik, I made tests with 1 core / 1 GB, 2 cores / 2GB and 4
>> cores / 8GB .. they worked
>> <ironm>  8cores / 4 or 8 GB didn't work for squeeze
>>
>> The error looks like:
>> http://www.it-infrastrukturen.com/fileadmin/linux/paste/squeeze/squeeze-xen4.1.2-issue-install-menu-pic1.png
>> http://www.it-infrastrukturen.com/fileadmin/linux/paste/squeeze/squeeze-xen4.1.2-issue-error-pic2.png
>>      
> So based on the "squeeze-xen4.1.2-issue-error-pic2.png" I recommend you to enable debugging options for the kernel, from the boot menu.
>
> Add at least "nomodeset initcall_debug debug loglevel=10"
> Then paste/capture the output.
>
> Some questions:
> 	- That "BUG: soft lockup - CPU#0 stuck for 61s!" only happens when you have 8 vcpus, right?
>    
It happens when I use 8 VCPUs. Please check the attached 
"BUG_soft_lockup-CPU_No_X.png"
There are more messages from CPU#0, 1, 5, 7. I have attached also the 
kernel 3.0.1 kernel config.

I will repeat this test on another DL385g7 server in case this one has 
hardware troubles.

> 	- What if you install with 1 vcpu, then after installation install the latest debian updates (new kernel),
> 	  and then try using 8 vcpus with the updated debian kernel?
>    
I have still to execute such test with 8 cores after updating kernel 
after installation (time issue yet). Until now the server booted 
correctly with 4 cores.


>> Config files are like:
>> http://www.it-infrastrukturen.com/fileadmin/linux/paste/HVM/hvm-squeeze.born2b3.net.cfg
>>      
> Looks OK.
>
>    
>> http://www.it-infrastrukturen.com/fileadmin/linux/paste/HVM/hvm-wheezy.born2b3.net.cfg
>>      
> For what is this wheezy cfgfile?
>    
Just only to check that this config is so far correct for wheezy tests.


>> Issue 2: problem with too big install image size? (DVD images)
>> <ironm>  maybe there is a problem when using DVD.iso images for
>> installations .. (no problem with CD size )
>> <ironm>  big size images (like DVD) or just the content (missing grub
>> packages on them) causes install errors in HVMs
>>
>> The error looks like:
>> http://www.it-infrastrukturen.com/fileadmin/linux/paste/wheezy/vxda-setting3-grub-error.png
>>      
> So are you saying you only get that GRUB error when installing from DVD.iso,
> but if you install from CD.iso GRUB installs ok ? do other deb packages install OK?
>
> Is DVD/CD iso image the only difference? Are you sure the checksums of the iso images are OK?
>    
md5sums of all .iso images are the same compare to ones on debian server:
root@xen411dom0:/ftp# md5sum -b debian-6.0.2.1-amd64-DVD-1.iso
b9b401989a84d751f5ec7e37cf2d825c *debian-6.0.2.1-amd64-DVD-1.iso

root@xen411dom0:/etc/xen# md5sum -b /ftp/debian-testing-amd64-DVD-1.iso
80473b659aae8269c81d4c50bdb63fe0 */ftp/debian-testing-amd64-DVD-1.iso

# md5sum from debian.org (below)
b9b401989a84d751f5ec7e37cf2d825c  debian-6.0.2.1-amd64-DVD-1.iso
80473b659aae8269c81d4c50bdb63fe0  debian-testing-amd64-DVD-1.iso

It looks like the wheezy testing DVD image misses the grub package (s. 
last lines in link  / below)
http://www.it-infrastrukturen.com/fileadmin/linux/paste/wheezy/syslog
# ---

Aug  6 19:23:58 in-target: E
Aug  6 19:23:58 in-target: : Paket grub-common kann nicht gefunden werden
Aug  6 19:23:58 grub-installer: info: Identified partition label for /dev/xvda1: msdos
Aug  6 19:23:59 grub-installer: dpkg: warning: ignoring request to remove grub which isn't installed.
Aug  6 19:23:59 grub-installer: dpkg: warning: ignoring request to remove grub-legacy which isn't installed.
Aug  6 19:24:00 in-target: Paketlisten werden gelesen...

Aug  6 19:24:00 in-target: Statusinformationen werden eingelesen...
Aug  6 19:24:00 in-target: E: Paket »grub-pc« hat keinen Installationskandidaten
Aug  6 19:24:00 grub-installer: info: Calling 'apt-install grub-pc' failed

# ---

>> Issues 3+: different errors in log files of xen 4.1.2*
>> http://www.it-infrastrukturen.com/fileadmin/linux/paste/wheezy/xen4.1.2-kernel3final/qemu-dm-squeezehvm.born2b3.net.log-xen412-k3.txt
>> http://www.it-infrastrukturen.com/fileadmin/linux/paste/wheezy/xen4.1.2-kernel3final/qemu-dm-wheezyhvm.born2b3.net.log-xen412-k3.tx
>> http://www.it-infrastrukturen.com/fileadmin/linux/paste/wheezy/xen4.1.2-kernel3final/xen-hotplug.log-xen412-k3.txt
>> http://www.it-infrastrukturen.com/fileadmin/linux/paste/wheezy/xen4.1.2-kernel3final/xend-debug.log-xen412-k3.txt
>> http://www.it-infrastrukturen.com/fileadmin/linux/paste/wheezy/xen4.1.2-kernel3final/xend.log-xen412-k3.txt
>> http://www.it-infrastrukturen.com/fileadmin/linux/paste/wheezy/xen4.1.2-kernel3final/xm_dmesg-xen412-k3.txt
>> http://www.it-infrastrukturen.com/fileadmin/linux/paste/wheezy/xen4.1.2-kernel3final/xm_info-xen412-k3.txt
>>      
> What exactly is the issue here? What problem are you having?
>    
Many entries in log files I am wondering about .. some examples:

# ---

cat: /sys/bus/scsi/devices/host0/vendor: No such file or directory
cat: /sys/bus/scsi/devices/host0/model: No such file or directory
cat: /sys/bus/scsi/devices/host0/type: No such file or directory
cat: /sys/bus/scsi/devices/host0/rev: No such file or directory
.
# ---

# ---

[2011-08-07 10:42:47 2902] WARNING (XendAPI:708) API call: VBD.set_device not found
[2011-08-07 10:42:47 2902] WARNING (XendAPI:708) API call: VBD.set_type not found
[2011-08-07 10:42:47 2902] WARNING (XendAPI:708) API call: session.get_all_records not found
[2011-08-07 10:42:47 2902] WARNING (XendAPI:708) API call: event.get_record not found
[2011-08-07 10:42:47 2902] WARNING (XendAPI:708) API call: event.get_all not found
[2011-08-07 10:42:47 2902] WARNING (XendAPI:708) API call: VIF.set_device not found
[2011-08-07 10:42:47 2902] WARNING (XendAPI:708) API call: VIF.set_MAC not found
[2011-08-07 10:42:47 2902] WARNING (XendAPI:708) API call: VIF.set_MTU not found
[2011-08-07 10:42:47 2902] WARNING (XendAPI:708) API call: debug.get_all not found

# ---

# ---

(XEN) traps.c:2430:d0 Domain attempted WRMSR 00000000c0010000 from 0x0000000000430076 to 0x0000000000530076.
(XEN) printk: 4028 messages suppressed.
(XEN) traps.c:2430:d0 Domain attempted WRMSR 00000000c0010000 from 0x0000000000430076 to 0x0000000000030076.

# ---

Thank you / regards, Mark

> -- Pasi
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>    


-- 
ms@it-infrastrukturen.org

+++ Free infrastructure software for all. +++


[-- Attachment #2: config-3.0.1.gz --]
[-- Type: application/gzip, Size: 31631 bytes --]

[-- Attachment #3: BUG_soft_lockup-CPU_No_X.png --]
[-- Type: image/png, Size: 138095 bytes --]

[-- Attachment #4: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: Reporting some xen 4.1.2* and 4.0 issues like limitations to 4 VCPUs for debian squeeze HVMs etc

[Pasi Kärkkäinen]

On Tue, Aug 09, 2011 at 11:05:14PM +0200, Mark Schneider wrote:
>>>
>>> The error looks like:
>>> http://www.it-infrastrukturen.com/fileadmin/linux/paste/squeeze/squeeze-xen4.1.2-issue-install-menu-pic1.png
>>> http://www.it-infrastrukturen.com/fileadmin/linux/paste/squeeze/squeeze-xen4.1.2-issue-error-pic2.png
>>>      
>> So based on the "squeeze-xen4.1.2-issue-error-pic2.png" I recommend you to enable debugging options for the kernel, from the boot menu.
>>
>> Add at least "nomodeset initcall_debug debug loglevel=10"
>> Then paste/capture the output.
>>

Please do this:

	- start the HVM Squeeze VM with 8 vcpus
	- Use kernel options: "console=tty1 console=ttyS0 nomodeset initcall_debug debug loglevel=10"
	- Paste the full console output to reply-email, as inline text

>
> I will repeat this test on another DL385g7 server in case this one has  
> hardware troubles.
>

Does it also happen on Intel? Or only on AMD ?

Thanks,

-- Pasi

Re: Reporting some xen 4.1.2* issues like limitations to 4 VCPUs for debian squeeze HVMs

[Mark Schneider]

[-- Attachment #1: Type: text/plain, Size: 21190 bytes --]

Am 13.08.2011 20:39, schrieb Pasi Kärkkäinen:
> On Tue, Aug 09, 2011 at 11:05:14PM +0200, Mark Schneider wrote:
>    
>>>> The error looks like:
>>>> http://www.it-infrastrukturen.com/fileadmin/linux/paste/squeeze/squeeze-xen4.1.2-issue-install-menu-pic1.png
>>>> http://www.it-infrastrukturen.com/fileadmin/linux/paste/squeeze/squeeze-xen4.1.2-issue-error-pic2.png
>>>>
>>>>          
>>> So based on the "squeeze-xen4.1.2-issue-error-pic2.png" I recommend you to enable debugging options for the kernel, from the boot menu.
>>>
>>> Add at least "nomodeset initcall_debug debug loglevel=10"
>>> Then paste/capture the output.
>>>
>>>        
> Please do this:
>
> 	- start the HVM Squeeze VM with 8 vcpus
> 	- Use kernel options: "console=tty1 console=ttyS0 nomodeset initcall_debug debug loglevel=10"
> 	- Paste the full console output to reply-email, as inline text
>    

Done. s. below the output

>> I will repeat this test on another DL385g7 server in case this one has
>> hardware troubles.
>>
>>      
> Does it also happen on Intel? Or only on AMD ?
>    
I can test only on AMD (HP DL385g7 with two Opteron 6180SE CPUs / 32GB RAM)

> Thanks,
>
> -- Pasi
>
>    


-- 
ms@it-infrastrukturen.org


not full file (as it is TOO long for my icedove client). Please see attachment boot.msgs.gz
# ---
root@xen411dom0:/ftp/HVM# xm console 11
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 2.6.32-5-amd64 (Debian 2.6.32-35) (dannf@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Tue Jun 14 09:42:28 UTC 2011
[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64 root=UUID=82dee80a-285a-440f-bedf-064c5790e2dc ro console=tty1 console=ttyS0 nomodeset initcall_debug debug loglevel=10
[    0.000000] KERNEL supported cpus:
[    0.000000]   Intel GenuineIntel
[    0.000000]   AMD AuthenticAMD
[    0.000000]   Centaur CentaurHauls
[    0.000000] BIOS-provided physical RAM map:
[    0.000000]  BIOS-e820: 0000000000000000 - 000000000009e000 (usable)
[    0.000000]  BIOS-e820: 000000000009e000 - 00000000000a0000 (reserved)
[    0.000000]  BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
[    0.000000]  BIOS-e820: 0000000000100000 - 00000000f0000000 (usable)
[    0.000000]  BIOS-e820: 00000000fc000000 - 0000000100000000 (reserved)
[    0.000000]  BIOS-e820: 0000000100000000 - 0000000210000000 (usable)
[    0.000000] DMI 2.4 present.
[    0.000000] last_pfn = 0x210000 max_arch_pfn = 0x400000000
[    0.000000] MTRR default type: write-back
[    0.000000] MTRR fixed ranges enabled:
[    0.000000]   00000-9FFFF write-back
[    0.000000]   A0000-BFFFF write-combining
[    0.000000]   C0000-FFFFF write-back
[    0.000000] MTRR variable ranges enabled:
[    0.000000]   0 base 0000F0000000 mask FFFFF8000000 uncachable
[    0.000000]   1 base 0000F8000000 mask FFFFFC000000 uncachable
[    0.000000]   2 disabled
[    0.000000]   3 disabled
[    0.000000]   4 disabled
[    0.000000]   5 disabled
[    0.000000]   6 disabled
[    0.000000]   7 disabled
[    0.000000] TOM2: 0000000840000000 aka 33792M
[    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[    0.000000] last_pfn = 0xf0000 max_arch_pfn = 0x400000000
[    0.000000] initial memory mapped : 0 - 20000000
[    0.000000] init_memory_mapping: 0000000000000000-00000000f0000000
[    0.000000]  0000000000 - 00f0000000 page 2M
[    0.000000] kernel direct mapping tables up to f0000000 @ 8000-d000
[    0.000000] init_memory_mapping: 0000000100000000-0000000210000000
[    0.000000]  0100000000 - 0210000000 page 2M
[    0.000000] kernel direct mapping tables up to 210000000 @ b000-15000
[    0.000000] RAMDISK: 37724000 - 37fef69d
[    0.000000] ACPI: RSDP 00000000000ea020 00024 (v02    Xen)
[    0.000000] ACPI: XSDT 00000000fc0134b0 00034 (v01    Xen      HVM 00000000 HVML 00000000)
[    0.000000] ACPI: FACP 00000000fc0132d0 000F4 (v04    Xen      HVM 00000000 HVML 00000000)
[    0.000000] ACPI: DSDT 00000000fc003440 0FE05 (v02    Xen      HVM 00000000 INTL 20100528)
[    0.000000] ACPI: FACS 00000000fc003400 00040
[    0.000000] ACPI: APIC 00000000fc0133d0 000D8 (v02    Xen      HVM 00000000 HVML 00000000)
[    0.000000] ACPI: Local APIC address 0xfee00000
[    0.000000] No NUMA configuration found
[    0.000000] Faking a node at 0000000000000000-0000000210000000
[    0.000000] Bootmem setup node 0 0000000000000000-0000000210000000
[    0.000000]   NODE_DATA [0000000000010000 - 0000000000017fff]
[    0.000000]   bootmap [0000000000018000 -  0000000000059fff] pages 42
[    0.000000] (8 early reservations) ==>  bootmem [0000000000 - 0210000000]
[    0.000000]   #0 [0000000000 - 0000001000]   BIOS data page ==>  [0000000000 - 0000001000]
[    0.000000]   #1 [0000006000 - 0000008000]       TRAMPOLINE ==>  [0000006000 - 0000008000]
[    0.000000]   #2 [0001000000 - 000168a454]    TEXT DATA BSS ==>  [0001000000 - 000168a454]
[    0.000000]   #3 [0037724000 - 0037fef69d]          RAMDISK ==>  [0037724000 - 0037fef69d]
[    0.000000]   #4 [000009e000 - 0000100000]    BIOS reserved ==>  [000009e000 - 0000100000]
[    0.000000]   #5 [000168b000 - 000168b0d0]              BRK ==>  [000168b000 - 000168b0d0]
[    0.000000]   #6 [0000008000 - 000000b000]          PGTABLE ==>  [0000008000 - 000000b000]
[    0.000000]   #7 [000000b000 - 0000010000]          PGTABLE ==>  [000000b000 - 0000010000]
[    0.000000] found SMP MP-table at [ffff8800000fbd00] fbd00
[    0.000000]  [ffffea0000000000-ffffea00073fffff] PMD ->  [ffff880001800000-ffff8800089fffff] on node 0
[    0.000000] Zone PFN ranges:
[    0.000000]   DMA      0x00000000 ->  0x00001000
[    0.000000]   DMA32    0x00001000 ->  0x00100000
[    0.000000]   Normal   0x00100000 ->  0x00210000
[    0.000000] Movable zone start PFN for each node
[    0.000000] early_node_map[3] active PFN ranges
[    0.000000]     0: 0x00000000 ->  0x0000009e
[    0.000000]     0: 0x00000100 ->  0x000f0000
[    0.000000]     0: 0x00100000 ->  0x00210000
[    0.000000] On node 0 totalpages: 2097054
[    0.000000]   DMA zone: 56 pages used for memmap
[    0.000000]   DMA zone: 109 pages reserved
[    0.000000]   DMA zone: 3833 pages, LIFO batch:0
[    0.000000]   DMA32 zone: 14280 pages used for memmap
[    0.000000]   DMA32 zone: 964664 pages, LIFO batch:31
[    0.000000]   Normal zone: 15232 pages used for memmap
[    0.000000]   Normal zone: 1098880 pages, LIFO batch:31
[    0.000000] ACPI: PM-Timer IO Port: 0xb008
[    0.000000] ACPI: Local APIC address 0xfee00000
[    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x02] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x04] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x06] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x08] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x0a] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x0c] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x0e] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x10] disabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x12] disabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x14] disabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x16] disabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x18] disabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x1a] disabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x1c] disabled)
[    0.000000] ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
[    0.000000] IOAPIC[0]: apic_id 1, version 17, address 0xfec00000, GSI 0-47
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 low level)
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 low level)
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 low level)
[    0.000000] ACPI: IRQ0 used by override.
[    0.000000] ACPI: IRQ2 used by override.
[    0.000000] ACPI: IRQ5 used by override.
[    0.000000] ACPI: IRQ9 used by override.
[    0.000000] ACPI: IRQ10 used by override.
[    0.000000] ACPI: IRQ11 used by override.
[    0.000000] Using ACPI (MADT) for SMP configuration information
[    0.000000] SMP: Allowing 15 CPUs, 7 hotplug CPUs
[    0.000000] nr_irqs_gsi: 48
[    0.000000] Xen version 4.1.
[    0.000000] Xen Platform PCI: I/O protocol version 1
[    0.000000] Netfront and the Xen platform PCI driver have been compiled for this kernel: unplug emulated NICs.
[    0.000000] Blkfront and the Xen platform PCI driver have been compiled for this kernel: unplug emulated disks.
[    0.000000] You might have to change the root device
[    0.000000] from /dev/hd[a-d] to /dev/xvd[a-d]
[    0.000000] in your root= kernel command line option
[    0.000000] HVMOP_pagetable_dying not supported
[    0.000000] PM: Registered nosave memory: 000000000009e000 - 00000000000a0000
[    0.000000] PM: Registered nosave memory: 00000000000a0000 - 00000000000e0000
[    0.000000] PM: Registered nosave memory: 00000000000e0000 - 0000000000100000
[    0.000000] PM: Registered nosave memory: 00000000f0000000 - 00000000fc000000
[    0.000000] PM: Registered nosave memory: 00000000fc000000 - 0000000100000000
[    0.000000] Allocating PCI resources starting at f0000000 (gap: f0000000:c000000)
[    0.000000] Booting paravirtualized kernel on Xen
[    0.000000] NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:15 nr_node_ids:1
[    0.000000] PERCPU: Embedded 30 pages/cpu @ffff880008c00000 s90328 r8192 d24360 u131072
[    0.000000] pcpu-alloc: s90328 r8192 d24360 u131072 alloc=1*2097152
[    0.000000] pcpu-alloc: [0] 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 --
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 2067377
[    0.000000] Policy zone: Normal
[    0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64 root=UUID=82dee80a-285a-440f-bedf-064c5790e2dc ro console=tty1 console=ttyS0 nomodeset initcall_debug debug loglevel=10
[    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[    0.000000] Initializing CPU#0
[    0.000000] Checking aperture...
[    0.000000] No AGP bridge found
[    0.000000] Calgary: detecting Calgary via BIOS EBDA area
[    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
[    0.000000] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[    0.000000] Placing 64MB software IO TLB between ffff880008dde000 - ffff88000cdde000
[    0.000000] software IO TLB at phys 0x8dde000 - 0xcdde000
[    0.000000] Memory: 8187556k/8650752k available (3081k kernel code, 262536k absent, 200660k reserved, 1890k data, 592k init)
[    0.000000] SLUB: Genslabs=14, HWalign=64, Order=0-3, MinObjects=0, CPUs=15, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000] NR_IRQS:4352 nr_irqs:936
[    0.000000] Xen HVM callback vector for event delivery is enabled
[    0.000000] Console: colour VGA+ 80x25
[    0.000000] console [tty1] enabled
[    0.000000] console [ttyS0] enabled
[    0.000000] Detected 2500.094 MHz processor.
[    0.024001] Calibrating delay loop (skipped), value calculated using timer frequency.. 5000.18 BogoMIPS (lpj=10000376)
[    0.060043] Security Framework initialized
[    0.076014] SELinux:  Disabled at boot.
[    0.092472] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
[    0.123203] Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
[    0.152781] Mount-cache hash table entries: 256
[    0.164217] Initializing cgroup subsys ns
[    0.184013] Initializing cgroup subsys cpuacct
[    0.200019] Initializing cgroup subsys devices
[    0.216012] Initializing cgroup subsys freezer
[    0.232012] Initializing cgroup subsys net_cls
[    0.256205] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
[    0.284014] CPU: L2 Cache: 512K (64 bytes/line)
[    0.300011] CPU 0/0x0 ->  Node 0
[    0.312027] tseg: 00bfe00000
[    0.324066] CPU: Physical Processor ID: 0
[    0.344010] CPU: Processor Core ID: 0
[    0.360017] mce: CPU supports 6 MCE banks
[    0.380067] using C1E aware idle routine
[    0.396010] Performance Events: AMD PMU driver.
[    0.416027] ... version:                0
[    0.432011] ... bit width:              48
[    0.448011] ... generic registers:      4
[    0.468010] ... value mask:             0000ffffffffffff
[    0.500011] ... max period:             00007fffffffffff
[    0.516011] ... fixed-purpose events:   0
[    0.536011] ... event mask:             000000000000000f
[    0.563496] ACPI: Core revision 20090903
[    0.601188] Not enabling x2apic, Intr-remapping init failed.
[    0.620011] Setting APIC routing to physical flat
[    0.643142] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=0 pin2=0
[    0.704667] CPU0: AMD Opteron(tm) Processor 6180 SE stepping 01
[    0.728029] Xen: using vcpuop timer interface
[    0.744015] installing Xen timer for CPU 0
[    0.744015]   alloc irq_desc for 16 on node 0
[    0.744015]   alloc kstat_irqs on node 0
[    0.744015] calling  migration_init+0x0/0x4f @ 1
[    0.744015] initcall migration_init+0x0/0x4f returned 0 after 0 usecs
[    0.744015] calling  spawn_ksoftirqd+0x0/0x4f @ 1
[    0.744015] initcall spawn_ksoftirqd+0x0/0x4f returned 0 after 0 usecs
[    0.744015] calling  init_call_single_data+0x0/0x7f @ 1
[    0.744015] initcall init_call_single_data+0x0/0x7f returned 0 after 0 usecs
[    0.744015] calling  spawn_softlockup_task+0x0/0x6b @ 1
[    0.744015] initcall spawn_softlockup_task+0x0/0x6b returned 0 after 0 usecs
[    0.744015] calling  relay_init+0x0/0x14 @ 1
[    0.744015] initcall relay_init+0x0/0x14 returned 0 after 0 usecs
[    0.744015] calling  tracer_alloc_buffers+0x0/0x199 @ 1
[    0.744015] initcall tracer_alloc_buffers+0x0/0x199 returned 0 after 0 usecs
[    0.744015] calling  init_trace_printk+0x0/0xc @ 1
[    0.744015] initcall init_trace_printk+0x0/0xc returned 0 after 0 usecs
[    0.744015] Booting processor 1 APIC 0x2 ip 0x6000
[    0.024001] Initializing CPU#1
[    0.744015] Stuck ??
[    0.744015] Booting processor 2 APIC 0x4 ip 0x6000
[    0.024001] Initializing CPU#2
[    0.024001] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
[    0.024001] CPU: L2 Cache: 512K (64 bytes/line)
[    0.024001] CPU 1/0x2 ->  Node 0
[    0.024001] CPU: Physical Processor ID: 0
[    0.024001] CPU: Processor Core ID: 2
[    0.024001] installing Xen timer for CPU 1
[    0.024001] BUG: unable to handle kernel NULL pointer dereference at 0000000000000018
[    0.024001] IP: [<ffffffff810e7f7a>] __kmalloc+0xc0/0x141
[    0.024001] PGD 0
[    0.024001] Oops: 0000 [#1] SMP
[    0.024001] last sysfs file:
[    0.024001] CPU 1
[    0.024001] Modules linked in:
[    0.024001] Pid: 0, comm: swapper Not tainted 2.6.32-5-amd64 #1 HVM domU
[    0.024001] RIP: 0010:[<ffffffff810e7f7a>]  [<ffffffff810e7f7a>] __kmalloc+0xc0/0x141
[    0.744015] Stuck ??
[    0.744015] Booting processor 3 APIC 0x6 ip 0x6000
[    0.024001] Initializing CPU#3
[    0.024001] RSP: 0018:ffff88020f0b5d88  EFLAGS: 00010046
[    0.024001] RAX: 0000000000000001 RBX: 00000000000000d0 RCX: 0000000200000010
[    0.024001] RDX: 0000000000000000 RSI: 00000000000000d0 RDI: ffffffff81196c8d
[    0.024001] RBP: 0000000000000246 R08: 000000000000000a R09: 0000000000000000
[    0.024001] R10: 0000000000000000 R11: 00000000000186a0 R12: ffffffff81453f10
[    0.024001] R13: 00000000000000d0 R14: 00000000000000d0 R15: 0000000000000007
[    0.024001] FS:  0000000000000000(0000) GS:ffff880008c20000(0000) knlGS:0000000000000000
[    0.024001] CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
[    0.024001] CR2: 0000000000000018 CR3: 0000000001001000 CR4: 00000000000006e0
[    0.024001] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[    0.024001] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[    0.024001] Process swapper (pid: 0, threadinfo ffff88020f0b4000, task ffff88020f093880)
[    0.024001] Stack:
[    0.024001]  ffffffffffffffff ffffffff81196c8d 0000003608c20000 00000000000000d0
[    0.024001]<0>  ffff88020f0b5e38 0000000000000007 ffffffff813a0fcd 0000000000000000
[    0.024001]<0>  0000000000000000 ffffffff81196c8d 0000000000000000 0000000000000000
[    0.024001] Call Trace:
[    0.024001]  [<ffffffff81196c8d>] ? kvasprintf+0x41/0x68
[    0.024001]  [<ffffffff81196c8d>] ? kvasprintf+0x41/0x68
[    0.024001]  [<ffffffff81196cfd>] ? kasprintf+0x49/0x54
[    0.024001]  [<ffffffff8119774b>] ? __bitmap_weight+0x3a/0x7e
[    0.024001]  [<ffffffff812f5a8f>] ? set_cpu_sibling_map+0x2f4/0x311
[    0.024001]  [<ffffffff8100dee4>] ? xen_setup_timer+0x2c/0xa2
[    0.024001]  [<ffffffff8100df71>] ? xen_hvm_setup_cpu_clockevents+0x17/0x1d
[    0.024001]  [<ffffffff812f5c6a>] ? start_secondary+0x17c/0x185
[    0.024001] Code: 10 74 05 e8 90 33 21 00 9c 58 66 66 90 66 90 48 89 c5 fa 66 66 90 66 66 90 65 8b 04 25 a8 e3 00 00 48 98 49 8b 94 c4 f0 02 00 00<8b>  4a 18 89 4c 24 14 48 8b 1a 48 85 db 74 0c 8b 42 14 48 8b 04
[    0.024001] RIP  [<ffffffff810e7f7a>] __kmalloc+0xc0/0x141
[    0.024001]  RSP<ffff88020f0b5d88>
[    0.024001] CR2: 0000000000000018
[    0.024001] ---[ end trace a7919e7f17c0a725 ]---
[    0.024001] Kernel panic - not syncing: Attempted to kill the idle task!
[    0.024001] Pid: 0, comm: swapper Tainted: G      D    2.6.32-5-amd64 #1
[    0.024001] Call Trace:
[    0.024001]  [<ffffffff812fa67a>] ? panic+0x86/0x143
[    0.024001]  [<ffffffff812fa785>] ? printk+0x4e/0x59
[    0.024001]  [<ffffffff81051125>] ? do_exit+0x72/0x6c6
[    0.024001]  [<ffffffff812fd3bd>] ? oops_end+0xaf/0xb4
[    0.024001]  [<ffffffff810323fc>] ? no_context+0x1e9/0x1f8
[    0.024001]  [<ffffffff810325b1>] ? __bad_area_nosemaphore+0x1a6/0x1ca
[    0.024001]  [<ffffffff811b7a41>] ? write_vga+0x17/0x4c
[    0.024001]  [<ffffffff811b8f83>] ? vgacon_scroll+0x164/0x181
[    0.024001]  [<ffffffff81193502>] ? number+0x132/0x22e
[    0.024001]  [<ffffffff812fc895>] ? page_fault+0x25/0x30
[    0.024001]  [<ffffffff81196c8d>] ? kvasprintf+0x41/0x68
[    0.024001]  [<ffffffff810e7f7a>] ? __kmalloc+0xc0/0x141
[    0.024001]  [<ffffffff81196c8d>] ? kvasprintf+0x41/0x68
[    0.024001]  [<ffffffff81196c8d>] ? kvasprintf+0x41/0x68
[    0.024001]  [<ffffffff81196cfd>] ? kasprintf+0x49/0x54
[    0.024001]  [<ffffffff8119774b>] ? __bitmap_weight+0x3a/0x7e
[    0.024001]  [<ffffffff812f5a8f>] ? set_cpu_sibling_map+0x2f4/0x311
[    0.024001]  [<ffffffff8100dee4>] ? xen_setup_timer+0x2c/0xa2
[    0.024001]  [<ffffffff8100df71>] ? xen_hvm_setup_cpu_clockevents+0x17/0x1d
[    0.024001]  [<ffffffff812f5c6a>] ? start_secondary+0x17c/0x185
[    0.024001] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
[    0.024001] CPU: L2 Cache: 512K (64 bytes/line)
[    0.024001] CPU 2/0x4 ->  Node 0
[    0.024001] CPU: Physical Processor ID: 0
[    0.024001] CPU: Processor Core ID: 4
[    0.024001] installing Xen timer for CPU 2
[    0.024001] BUG: unable to handle kernel NULL pointer dereference at 0000000000000018
[    0.024001] IP: [<ffffffff810e7f7a>] __kmalloc+0xc0/0x141
[    0.024001] PGD 0
[    0.024001] Oops: 0000 [#2] SMP
[    0.024001] last sysfs file:
[    0.024001] CPU 2
[    0.024001] Modules linked in:
[    0.024001] Pid: 0, comm: swapper Tainted: G      D    2.6.32-5-amd64 #1 HVM domU
[    0.024001] RIP: 0010:[<ffffffff810e7f7a>]  [<ffffffff810e7f7a>] __kmalloc+0xc0/0x141
[    0.024001] RSP: 0018:ffff88020f0c9d88  EFLAGS: 00010046
[    0.024001] RAX: 0000000000000002 RBX: 00000000000000d0 RCX: 0000000200000010
[    0.024001] RDX: 0000000000000000 RSI: 00000000000000d0 RDI: ffffffff81196c8d
[    0.024001] RBP: 0000000000000246 R08: 000000000000000a R09: 0000000000000000
[    0.024001] R10: 0000000000000000 R11: 00000000000186a0 R12: ffffffff81453f10
[    0.024001] R13: 00000000000000d0 R14: 00000000000000d0 R15: 0000000000000007
[    0.024001] FS:  0000000000000000(0000) GS:ffff880008c40000(0000) knlGS:0000000000000000
[    0.024001] CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
[    0.024001] CR2: 0000000000000018 CR3: 0000000001001000 CR4: 00000000000006e0
[    0.024001] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[    0.024001] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[    0.024001] Process swapper (pid: 0, threadinfo ffff88020f0c8000, task ffff88020f0954c0)
[    0.024001] Stack:
[    0.024001]  ffffffffffffffff ffffffff81196c8d 0000003608c40000 00000000000000d0
[    0.024001]<0>  ffff88020f0c9e38 0000000000000007 ffffffff813a0fcd 0000000000000000
[    0.024001]<0>  0000000000000000 ffffffff81196c8d 0000000000000000 0000000000000000
[    0.024001] Call Trace:
[    0.024001]  [<ffffffff81196c8d>] ? kvasprintf+0x41/0x68


[-- Attachment #2: boot.msgs.gz --]
[-- Type: application/gzip, Size: 5129 bytes --]

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: Reporting some xen 4.1.2* issues like limitations to 4 VCPUs for debian squeeze HVMs

[Pasi Kärkkäinen]

On Tue, Aug 23, 2011 at 06:57:05PM +0100, Stefano Stabellini wrote:
> On Sat, 13 Aug 2011, Mark Schneider wrote:
> > Am 13.08.2011 20:39, schrieb Pasi Kärkkäinen:
> > > On Tue, Aug 09, 2011 at 11:05:14PM +0200, Mark Schneider wrote:
> > >
> > >>>> The error looks like:
> > >>>> http://www.it-infrastrukturen.com/fileadmin/linux/paste/squeeze/squeeze-xen4.1.2-issue-install-menu-pic1.png
> > >>>> http://www.it-infrastrukturen.com/fileadmin/linux/paste/squeeze/squeeze-xen4.1.2-issue-error-pic2.png
> > >>>>
> > >>>>
> > >>> So based on the "squeeze-xen4.1.2-issue-error-pic2.png" I recommend you to enable debugging options for the kernel, from the boot menu.
> > >>>
> > >>> Add at least "nomodeset initcall_debug debug loglevel=10"
> > >>> Then paste/capture the output.
> > >>>
> > >>>
> > > Please do this:
> > >
> > >       - start the HVM Squeeze VM with 8 vcpus
> > >       - Use kernel options: "console=tty1 console=ttyS0 nomodeset initcall_debug debug loglevel=10"
> > >       - Paste the full console output to reply-email, as inline text
> > >
> > 
> > Done. s. below the output
> 
> Are you sure it is the default Squeeze kernel?
> If so I cannot reproduce the bug on my box (Intel, 4 cpus).
>

The crash only happens when you have more than 4 vcpus for the squeeze hvm guest..

-- Pasi

Re: Reporting some xen 4.1.2* issues like limitations to 4 VCPUs for debian squeeze HVMs

[Stefano Stabellini]

[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]

On Sat, 13 Aug 2011, Mark Schneider wrote:
> Am 13.08.2011 20:39, schrieb Pasi Kärkkäinen:
> > On Tue, Aug 09, 2011 at 11:05:14PM +0200, Mark Schneider wrote:
> >
> >>>> The error looks like:
> >>>> http://www.it-infrastrukturen.com/fileadmin/linux/paste/squeeze/squeeze-xen4.1.2-issue-install-menu-pic1.png
> >>>> http://www.it-infrastrukturen.com/fileadmin/linux/paste/squeeze/squeeze-xen4.1.2-issue-error-pic2.png
> >>>>
> >>>>
> >>> So based on the "squeeze-xen4.1.2-issue-error-pic2.png" I recommend you to enable debugging options for the kernel, from the boot menu.
> >>>
> >>> Add at least "nomodeset initcall_debug debug loglevel=10"
> >>> Then paste/capture the output.
> >>>
> >>>
> > Please do this:
> >
> >       - start the HVM Squeeze VM with 8 vcpus
> >       - Use kernel options: "console=tty1 console=ttyS0 nomodeset initcall_debug debug loglevel=10"
> >       - Paste the full console output to reply-email, as inline text
> >
> 
> Done. s. below the output

Are you sure it is the default Squeeze kernel?
If so I cannot reproduce the bug on my box (Intel, 4 cpus).

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: Reporting some xen 4.1.2* issues like limitations to 4 VCPUs for debian squeeze HVMs

[Stefano Stabellini]

[-- Attachment #1: Type: text/plain, Size: 1444 bytes --]

On Tue, 23 Aug 2011, Pasi Kärkkäinen wrote:
> On Tue, Aug 23, 2011 at 06:57:05PM +0100, Stefano Stabellini wrote:
> > On Sat, 13 Aug 2011, Mark Schneider wrote:
> > > Am 13.08.2011 20:39, schrieb Pasi Kärkkäinen:
> > > > On Tue, Aug 09, 2011 at 11:05:14PM +0200, Mark Schneider wrote:
> > > >
> > > >>>> The error looks like:
> > > >>>> http://www.it-infrastrukturen.com/fileadmin/linux/paste/squeeze/squeeze-xen4.1.2-issue-install-menu-pic1.png
> > > >>>> http://www.it-infrastrukturen.com/fileadmin/linux/paste/squeeze/squeeze-xen4.1.2-issue-error-pic2.png
> > > >>>>
> > > >>>>
> > > >>> So based on the "squeeze-xen4.1.2-issue-error-pic2.png" I recommend you to enable debugging options for the kernel, from the boot menu.
> > > >>>
> > > >>> Add at least "nomodeset initcall_debug debug loglevel=10"
> > > >>> Then paste/capture the output.
> > > >>>
> > > >>>
> > > > Please do this:
> > > >
> > > >       - start the HVM Squeeze VM with 8 vcpus
> > > >       - Use kernel options: "console=tty1 console=ttyS0 nomodeset initcall_debug debug loglevel=10"
> > > >       - Paste the full console output to reply-email, as inline text
> > > >
> > > 
> > > Done. s. below the output
> > 
> > Are you sure it is the default Squeeze kernel?
> > If so I cannot reproduce the bug on my box (Intel, 4 cpus).
> >
> 
> The crash only happens when you have more than 4 vcpus for the squeeze hvm guest..

I am testing with 8 vcpus but only 4 pcpus.

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: Reporting some xen 4.1.2* issues like limitations to 4 VCPUs for debian squeeze HVMs

[Pasi Kärkkäinen]

On Tue, Aug 23, 2011 at 07:10:44PM +0100, Stefano Stabellini wrote:
> On Tue, 23 Aug 2011, Pasi Kärkkäinen wrote:
> > On Tue, Aug 23, 2011 at 06:57:05PM +0100, Stefano Stabellini wrote:
> > > On Sat, 13 Aug 2011, Mark Schneider wrote:
> > > > Am 13.08.2011 20:39, schrieb Pasi Kärkkäinen:
> > > > > On Tue, Aug 09, 2011 at 11:05:14PM +0200, Mark Schneider wrote:
> > > > >
> > > > >>>> The error looks like:
> > > > >>>> http://www.it-infrastrukturen.com/fileadmin/linux/paste/squeeze/squeeze-xen4.1.2-issue-install-menu-pic1.png
> > > > >>>> http://www.it-infrastrukturen.com/fileadmin/linux/paste/squeeze/squeeze-xen4.1.2-issue-error-pic2.png
> > > > >>>>
> > > > >>>>
> > > > >>> So based on the "squeeze-xen4.1.2-issue-error-pic2.png" I recommend you to enable debugging options for the kernel, from the boot menu.
> > > > >>>
> > > > >>> Add at least "nomodeset initcall_debug debug loglevel=10"
> > > > >>> Then paste/capture the output.
> > > > >>>
> > > > >>>
> > > > > Please do this:
> > > > >
> > > > >       - start the HVM Squeeze VM with 8 vcpus
> > > > >       - Use kernel options: "console=tty1 console=ttyS0 nomodeset initcall_debug debug loglevel=10"
> > > > >       - Paste the full console output to reply-email, as inline text
> > > > >
> > > > 
> > > > Done. s. below the output
> > > 
> > > Are you sure it is the default Squeeze kernel?
> > > If so I cannot reproduce the bug on my box (Intel, 4 cpus).
> > >
> > 
> > The crash only happens when you have more than 4 vcpus for the squeeze hvm guest..
> 
> I am testing with 8 vcpus but only 4 pcpus.
>

Oh, ok. I think the user reporting the problem was using AMD boxes.. 
Did you try on Intel? 

-- Pasi

Re: Reporting some xen 4.1.2* issues like limitations to 4 VCPUs for debian squeeze HVMs

[Stefano Stabellini]

[-- Attachment #1: Type: text/plain, Size: 297 bytes --]

On Tue, 23 Aug 2011, Pasi Kärkkäinen wrote:
> > > The crash only happens when you have more than 4 vcpus for the squeeze hvm guest..
> > 
> > I am testing with 8 vcpus but only 4 pcpus.
> >
> 
> Oh, ok. I think the user reporting the problem was using AMD boxes.. 
> Did you try on Intel? 
 
Yes

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: Reporting some xen 4.1.2* issues like limitations to 4 VCPUs for debian squeeze HVMs

[Konrad Rzeszutek Wilk]

> [    0.024001] installing Xen timer for CPU 1
> [    0.024001] BUG: unable to handle kernel NULL pointer dereference at 0000000000000018
> [    0.024001] IP: [<ffffffff810e7f7a>] __kmalloc+0xc0/0x141
> [    0.024001] PGD 0
> [    0.024001] Oops: 0000 [#1] SMP
> [    0.024001] last sysfs file:
> [    0.024001] CPU 1
> [    0.024001] Modules linked in:
> [    0.024001] Pid: 0, comm: swapper Not tainted 2.6.32-5-amd64 #1 HVM domU
> [    0.024001] RIP: 0010:[<ffffffff810e7f7a>]  [<ffffffff810e7f7a>] __kmalloc+0xc0/0x141
> [    0.744015] Stuck ??
> [    0.744015] Booting processor 3 APIC 0x6 ip 0x6000
> [    0.024001] Initializing CPU#3
> [    0.024001] RSP: 0018:ffff88020f0b5d88  EFLAGS: 00010046
> [    0.024001] RAX: 0000000000000001 RBX: 00000000000000d0 RCX: 0000000200000010
> [    0.024001] RDX: 0000000000000000 RSI: 00000000000000d0 RDI: ffffffff81196c8d
> [    0.024001] RBP: 0000000000000246 R08: 000000000000000a R09: 0000000000000000
> [    0.024001] R10: 0000000000000000 R11: 00000000000186a0 R12: ffffffff81453f10
> [    0.024001] R13: 00000000000000d0 R14: 00000000000000d0 R15: 0000000000000007
> [    0.024001] FS:  0000000000000000(0000) GS:ffff880008c20000(0000) knlGS:0000000000000000
> [    0.024001] CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
> [    0.024001] CR2: 0000000000000018 CR3: 0000000001001000 CR4: 00000000000006e0
> [    0.024001] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> [    0.024001] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> [    0.024001] Process swapper (pid: 0, threadinfo ffff88020f0b4000, task ffff88020f093880)
> [    0.024001] Stack:
> [    0.024001]  ffffffffffffffff ffffffff81196c8d 0000003608c20000 00000000000000d0
> [    0.024001]<0>  ffff88020f0b5e38 0000000000000007 ffffffff813a0fcd 0000000000000000
> [    0.024001]<0>  0000000000000000 ffffffff81196c8d 0000000000000000 0000000000000000
> [    0.024001] Call Trace:
> [    0.024001]  [<ffffffff81196c8d>] ? kvasprintf+0x41/0x68
> [    0.024001]  [<ffffffff81196c8d>] ? kvasprintf+0x41/0x68
> [    0.024001]  [<ffffffff81196cfd>] ? kasprintf+0x49/0x54
> [    0.024001]  [<ffffffff8119774b>] ? __bitmap_weight+0x3a/0x7e
> [    0.024001]  [<ffffffff812f5a8f>] ? set_cpu_sibling_map+0x2f4/0x311
> [    0.024001]  [<ffffffff8100dee4>] ? xen_setup_timer+0x2c/0xa2
> [    0.024001]  [<ffffffff8100df71>] ? xen_hvm_setup_cpu_clockevents+0x17/0x1d
> [    0.024001]  [<ffffffff812f5c6a>] ? start_secondary+0x17c/0x185
> [    0.024001] Code: 10 74 05 e8 90 33 21 00 9c 58 66 66 90 66 90 48 89 c5 fa 66 66 90 66 66 90 65 8b 04 25 a8 e3 00 00 48 98 49 8b 94 c4 f0 02 00 00<8b>  4a 18 89 4c 24 14 48 8b 1a 48 85 db 74 0c 8b 42 14 48 8b 04
> [    0.024001] RIP  [<ffffffff810e7f7a>] __kmalloc+0xc0/0x141

This looks vagualy familiar. Like this:
https://lkml.org/lkml/2011/7/8/127

I wonder if the kernel is just compiled with MAX_CPUs of 4 and we try to stuff
more in and end up well, hitting disaster zone.

Is there a .config of this kernel?

Re: Reporting some xen 4.1.2* issues like limitations to 4 VCPUs for debian squeeze HVMs

[Mark Schneider]

[-- Attachment #1: Type: text/plain, Size: 5169 bytes --]

Am 24.08.2011 23:02, schrieb Konrad Rzeszutek Wilk:
>> [    0.024001] installing Xen timer for CPU 1
>> [    0.024001] BUG: unable to handle kernel NULL pointer dereference at 0000000000000018
>> [    0.024001] IP: [<ffffffff810e7f7a>] __kmalloc+0xc0/0x141
>> [    0.024001] PGD 0
>> [    0.024001] Oops: 0000 [#1] SMP
>> [    0.024001] last sysfs file:
>> [    0.024001] CPU 1
>> [    0.024001] Modules linked in:
>> [    0.024001] Pid: 0, comm: swapper Not tainted 2.6.32-5-amd64 #1 HVM domU
>> [    0.024001] RIP: 0010:[<ffffffff810e7f7a>]  [<ffffffff810e7f7a>] __kmalloc+0xc0/0x141
>> [    0.744015] Stuck ??
>> [    0.744015] Booting processor 3 APIC 0x6 ip 0x6000
>> [    0.024001] Initializing CPU#3
>> [    0.024001] RSP: 0018:ffff88020f0b5d88  EFLAGS: 00010046
>> [    0.024001] RAX: 0000000000000001 RBX: 00000000000000d0 RCX: 0000000200000010
>> [    0.024001] RDX: 0000000000000000 RSI: 00000000000000d0 RDI: ffffffff81196c8d
>> [    0.024001] RBP: 0000000000000246 R08: 000000000000000a R09: 0000000000000000
>> [    0.024001] R10: 0000000000000000 R11: 00000000000186a0 R12: ffffffff81453f10
>> [    0.024001] R13: 00000000000000d0 R14: 00000000000000d0 R15: 0000000000000007
>> [    0.024001] FS:  0000000000000000(0000) GS:ffff880008c20000(0000) knlGS:0000000000000000
>> [    0.024001] CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
>> [    0.024001] CR2: 0000000000000018 CR3: 0000000001001000 CR4: 00000000000006e0
>> [    0.024001] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
>> [    0.024001] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
>> [    0.024001] Process swapper (pid: 0, threadinfo ffff88020f0b4000, task ffff88020f093880)
>> [    0.024001] Stack:
>> [    0.024001]  ffffffffffffffff ffffffff81196c8d 0000003608c20000 00000000000000d0
>> [    0.024001]<0>   ffff88020f0b5e38 0000000000000007 ffffffff813a0fcd 0000000000000000
>> [    0.024001]<0>   0000000000000000 ffffffff81196c8d 0000000000000000 0000000000000000
>> [    0.024001] Call Trace:
>> [    0.024001]  [<ffffffff81196c8d>] ? kvasprintf+0x41/0x68
>> [    0.024001]  [<ffffffff81196c8d>] ? kvasprintf+0x41/0x68
>> [    0.024001]  [<ffffffff81196cfd>] ? kasprintf+0x49/0x54
>> [    0.024001]  [<ffffffff8119774b>] ? __bitmap_weight+0x3a/0x7e
>> [    0.024001]  [<ffffffff812f5a8f>] ? set_cpu_sibling_map+0x2f4/0x311
>> [    0.024001]  [<ffffffff8100dee4>] ? xen_setup_timer+0x2c/0xa2
>> [    0.024001]  [<ffffffff8100df71>] ? xen_hvm_setup_cpu_clockevents+0x17/0x1d
>> [    0.024001]  [<ffffffff812f5c6a>] ? start_secondary+0x17c/0x185
>> [    0.024001] Code: 10 74 05 e8 90 33 21 00 9c 58 66 66 90 66 90 48 89 c5 fa 66 66 90 66 66 90 65 8b 04 25 a8 e3 00 00 48 98 49 8b 94 c4 f0 02 00 00<8b>   4a 18 89 4c 24 14 48 8b 1a 48 85 db 74 0c 8b 42 14 48 8b 04
>> [    0.024001] RIP  [<ffffffff810e7f7a>] __kmalloc+0xc0/0x141
>>      
> This looks vagualy familiar. Like this:
> https://lkml.org/lkml/2011/7/8/127
>
> I wonder if the kernel is just compiled with MAX_CPUs of 4 and we try to stuff
> more in and end up well, hitting disaster zone.
>
> Is there a .config of this kernel?
>    
Thank you for your answer Konrad.

I have used the regular debian net-install image for HVM installation as 
follows:
disk        = [ 'phy:/dev/vg_xen/squeeze,ioemu:hda,w',
                      
'file:/ftp/debian-6.0.2.1-amd64-i386-netinst.iso,ioemu:hdc:cdrom,r']

Please have a look at the original kernel config of domU domain (s. 
below and attachment):
root@squeezehvm:~# uname -a
Linux squeezehvm 2.6.32-5-amd64 #1 SMP Tue Jun 14 09:42:28 UTC 2011 
x86_64 GNU/Linux

root@squeezehvm:/boot# grep -i cpu config-2.6.32-5-amd64
CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y
CONFIG_ARCH_HAS_CPU_RELAX=y
CONFIG_HAVE_SETUP_PER_CPU_AREA=y
CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y
CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y
CONFIG_HAVE_CPUMASK_OF_CPU_MAP=y
CONFIG_ARCH_CPU_PROBE_RELEASE=y
CONFIG_CPUSETS=y
CONFIG_PROC_PID_CPUSET=y
CONFIG_CGROUP_CPUACCT=y
CONFIG_GENERIC_CPU=y
CONFIG_X86_CPU=y
CONFIG_X86_MINIMUM_CPU_FAMILY=64
CONFIG_CPU_SUP_INTEL=y
CONFIG_CPU_SUP_AMD=y
CONFIG_CPU_SUP_CENTAUR=y
CONFIG_NR_CPUS=512
CONFIG_X86_CPUID=m
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_HOTPLUG_CPU=y
CONFIG_ACPI_HOTPLUG_CPU=y
# CPU Frequency scaling
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=y
# CONFIG_CPU_FREQ_DEBUG is not set
CONFIG_CPU_FREQ_STAT=m
# CONFIG_CPU_FREQ_STAT_DETAILS is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=m
CONFIG_CPU_FREQ_GOV_USERSPACE=m
CONFIG_CPU_FREQ_GOV_ONDEMAND=y
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=m
# CPUFreq processor drivers
CONFIG_X86_ACPI_CPUFREQ=m
CONFIG_CPU_IDLE=y
CONFIG_CPU_IDLE_GOV_LADDER=y
CONFIG_CPU_IDLE_GOV_MENU=y
CONFIG_SENSORS_VIA_CPUTEMP=m
CONFIG_CPU5_WDT=m
# on-CPU RTC drivers
# CONFIG_RCU_CPU_STALL_DETECTOR is not set
# CONFIG_DEBUG_FORCE_WEAK_PER_CPU is not set
# CONFIG_DEBUG_PER_CPU_MAPS is not set

Thank you / regards,
Mark

-- 
ms@it-infrastrukturen.org


[-- Attachment #2: config-2.6.32-5-amd64.gz --]
[-- Type: application/gzip, Size: 27081 bytes --]

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: Reporting some xen 4.1.2* issues like limitations to 4 VCPUs for debian squeeze HVMs

[Stefano Stabellini]

Hi Mark,
does the appended patch to Xen help by any chances?

- Stefano

---


diff -r a79c1d5b946e xen/arch/x86/irq.c
--- a/xen/arch/x86/irq.c	Fri Aug 19 10:00:25 2011 +0100
+++ b/xen/arch/x86/irq.c	Thu Aug 25 15:40:02 2011 +0000
@@ -1876,7 +1876,7 @@ int hvm_domain_use_pirq(struct domain *d
         return 0;
 
     emuirq = domain_pirq_to_emuirq(d, pirq);
-    if ( emuirq != IRQ_UNBOUND && d->pirq_to_evtchn[pirq] != 0 )
+    if ( emuirq != IRQ_UNBOUND )
         return 1;
     else
         return 0;
diff -r a79c1d5b946e xen/arch/x86/physdev.c
--- a/xen/arch/x86/physdev.c	Fri Aug 19 10:00:25 2011 +0100
+++ b/ xen/arch/x86/physdev.c	Thu Aug 25 15:40:02 2011 +0000
@@ -202,9 +202,6 @@ static int physdev_map_pirq(struct physd
     if ( ret == 0 )
         map->pirq = pirq;
 
-    if ( !ret && is_hvm_domain(d) )
-        map_domain_emuirq_pirq(d, pirq, IRQ_PT);
-
  done:
     spin_unlock(&d->event_lock);
     spin_unlock(&pcidevs_lock);
@@ -267,7 +264,7 @@ ret_t do_physdev_op(int cmd, XEN_GUEST_H
         if ( v->domain->arch.pirq_eoi_map )
             evtchn_unmask(v->domain->pirq_to_evtchn[eoi.irq]);
         if ( !is_hvm_domain(v->domain) ||
-             domain_pirq_to_emuirq(v->domain, eoi.irq) == IRQ_PT )
+             domain_pirq_to_irq(v->domain, eoi.irq) > 0 )
             ret = pirq_guest_eoi(v->domain, eoi.irq);
         else
             ret = 0;
@@ -326,7 +323,7 @@ ret_t do_physdev_op(int cmd, XEN_GUEST_H
             break;
         irq_status_query.flags = 0;
         if ( is_hvm_domain(v->domain) &&
-             domain_pirq_to_emuirq(v->domain, irq) != IRQ_PT )
+             domain_pirq_to_irq(v->domain, irq) > 0 )
         {
             ret = copy_to_guest(arg, &irq_status_query, 1) ? -EFAULT : 0;
             break;
diff -r a79c1d5b946e xen/common/event_channel.c
--- a/xen/common/event_channel.c	Fri Aug 19 10:00:25 2011 +0100
+++ b/xen/common/event_channel.c	Thu Aug 25 15:40:02 2011 +0000
@@ -361,6 +361,9 @@ static long evtchn_bind_pirq(evtchn_bind
 
     bind->port = port;
 
+    if ( is_hvm_domain(d) && domain_pirq_to_irq(d, pirq) > 0 )
+        map_domain_emuirq_pirq(d, pirq, IRQ_PT);
+
  out:
     spin_unlock(&d->event_lock);
 
@@ -409,6 +412,8 @@ static long __evtchn_close(struct domain
             pirq_guest_unbind(d1, chn1->u.pirq.irq);
         d1->pirq_to_evtchn[chn1->u.pirq.irq] = 0;
         unlink_pirq_port(chn1, d1->vcpu[chn1->notify_vcpu_id]);
+        if ( is_hvm_domain(d1) && domain_pirq_to_irq(d1, chn1->u.pirq.irq) > 0 )
+            unmap_domain_pirq_emuirq(d1, chn1->u.pirq.irq);
         break;
 
     case ECS_VIRQ: