* Re: test report for Xen 4.3 RC1
@ 2013-06-16 4:10 Ren, Yongjie
2013-06-17 14:23 ` Konrad Rzeszutek Wilk
0 siblings, 1 reply; 17+ messages in thread
From: Ren, Yongjie @ 2013-06-16 4:10 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk
Cc: george.dunlap, Xu, YongweiX, Liu, SongtaoX, Tian, Yongxue, xen-devel
[-- Attachment #1: Type: text/plain, Size: 5088 bytes --]
> -----Original Message-----
> From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]
> Sent: Wednesday, June 05, 2013 10:50 PM
> To: Ren, Yongjie
> Cc: george.dunlap@eu.citrix.com; Xu, YongweiX; Liu, SongtaoX; Tian,
> Yongxue; xen-devel@lists.xen.org
> Subject: Re: [Xen-devel] test report for Xen 4.3 RC1
>
> > >
> http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1851
> > > > >
> > > > > That looks like you are hitting the udev race.
> > > > >
> > > > > Could you verify that these patches:
> > > > > https://lkml.org/lkml/2013/5/13/520
> > > > >
> > > > > fix the issue (They are destined for v3.11)
> > > > >
> > > > Not tried yet. I'll update it to you later.
> > >
> > > Thanks!
> > > >
> > We tested kernel 3.9.3 with the 2 patches you mentioned, and found this
> > bug still exist. For example, we did CPU online-offline for Dom0 for 100
> times,
> > and found 2 times (of 100 times) failed.
>
> Hm, does it fail b/c udev can't online the sysfs entry?
>
I think no.
When it fails to online CPU #3 (trying online #1~#3), it doesn't show any info
about CPU #3 via the output of "devadm monitor --env" CMD. It does show
info about #1 and #2 which are onlined succefully.
> .. snip..
> > > >
> > > > > >
> > > > > > Old bugs: (11)
> > > > > > 1. [ACPI] Dom0 can't resume from S3 sleep
> > > > > > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1707
> > > > >
> > > > > That should be fixed in v3.11 (as now we have the fixes)
> > > > > Could you try v3.10 with the Rafael's ACPI tree merged in?
> > > > > (so the patches that he wants to submit for v3.11)
> > > > >
> > > > I re-tested with Rafel's linux-pm.git tree (master and acpi-hotplug
> > > branch),
> > > > and found Dom0 S3 sleep/resume can't work, either.
> > >
> > > The patches he has to submit for v3.11 are in the linux-next branch.
> > > You need to use that branch.
> > >
> > Dom0 S3 sleep/resume doesn't work with linux-next branch, either.
> > attached the log.
>
> It does work on my box. So I am not sure if this is related to the
> IvyTown box you are using. Does it work on other machines?
>
No, it doesn't work on other machines, either. I also tried on SandyBridge,
IvyBridge desktop and Haswell mobile machines.
> >
> > > >
> > > > > > 2. [XL]"xl vcpu-set" causes dom0 crash or panic
> > > > > > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1730
> > > > >
> > > > > That I think is fixed in v3.10. Could you please check v3.10-rc3?
> > > > >
> > > > Still exists on v3.10-rc3.
> > > > The following command lines can reproduce it:
> > > > # xl vcpu-set 0 1
> > > > # xl vcpu-set 0 20
> > >
> > > Ugh, same exact stack trace? And can you attach the full dmesg or
> serial
> > > output (so that Ican see what there is at bootup)
> > >
> > Yes, the same. Also attached in this mail.
>
> One of the fixes is this one:
> http://www.gossamer-threads.com/lists/xen/devel/284897
>
> but the other ones I had not seen. I am wondering if the
> update_sd_lb_stats is b/c of the previous conditions (that is the
> tick_nohz_idle_start hadn't been called).
>
> It is a shoot in the dark - but if you use the above mentioned patch
> do you still see the update_sd_lb_stats crash?
>
Yes, with the patch we still see the update_sd_lb_stats crash.
It has almost the same trace log as before. Log file is attached.
> > > >
> > > > > > 4. 'xl vcpu-set' can't decrease the vCPU number of a HVM guest
> > > > > > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1822
> > > > >
> > > > > That I believe was an QEMU bug:
> > > > >
> http://lists.xen.org/archives/html/xen-devel/2013-05/msg01054.html
> > > > >
> > > > > which should be in QEMU traditional now (05-21 was when it went
> > > > > in the tree)
> > > > >
> > > > In this year or past year, this bug always exists (at least in our
> testing).
> > > > 'xl vcpu-set' can't decrease the vCPU number of a HVM guest
> > >
> > > Could you retry with Xen 4.3 please?
> > >
> > With Xen 4.3 & Linux:3.10.0-rc3, I can't decrease the vCPU number of a
> guest.
>
sorry, when I said this message, I still use rhel6.4 kernel as the guest.
After upgrading guest kernel to 3.10.0-rc3, the result became better.
Basically vCPU increment/decrement can work fine. I'll close that bug.
But there's still a minor issue as following.
After booting guest with 'vcpus=4' and 'maxvcpus=32', change its vCPU number.
# xl vcpu-set $domID 32
then you can only get less than 32 (e.g. 19) CPUs in the guest; again, you set
vCPU number to 32 (from 19), then it works to get 32vCPU for the guest.
but 'xl vcpu-set $domID 8' can work fine as we expected.
vCPU decrement has the same result.
Can you also have a try to reproduce my issue?
> Could you give some more details? Could you include the
> /var/log/xen/qemu-... log file?
>
Attached the qemu log.
> You are using the traditional QEMU right? (you need to have this in your
> guest
> config:
> device_model_version = 'qemu-xen-traditional'
>
Yes.
--
Jay
[-- Attachment #2: xl_vcpu-set_dom0_call_trace.log --]
[-- Type: application/octet-stream, Size: 111651 bytes --]
[-- Attachment #3: xl_vcpu-set_HVM_from_4_to_32_qemu-dm.log --]
[-- Type: application/octet-stream, Size: 2994 bytes --]
domid: 1
-videoram option does not work with cirrus vga device model. Videoram set to 4M.
Using xvda for guest's hda
Strip off blktap sub-type prefix to /root/terrence/rhel6u4.qcow (drv 'qcow2')
Using file /root/terrence/rhel6u4.qcow in read-write mode
Watching /local/domain/0/device-model/1/logdirty/cmd
Watching /local/domain/0/device-model/1/command
Watching /local/domain/1/cpu
qemu_map_cache_init nr_buckets = 10000 size 4194304
shared page at pfn feffd
buffered io page at pfn feffb
Guest uuid = 1de3707c-7c52-4f5b-8fcd-44306e6bbe79
populating video RAM at ff000000
mapping video RAM from ff000000
Register xen platform.
Done register platform.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.
xs_read(/local/domain/0/device-model/1/xen_extended_power_mgmt): read error
xs_read(): vncpasswd get error. /vm/1de3707c-7c52-4f5b-8fcd-44306e6bbe79/vncpasswd.
Log-dirty: no command yet.
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
vcpu-set: watch node error.
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
xs_read(/local/domain/1/log-throttling): read error
qemu: ignoring not-understood drive `/local/domain/1/log-throttling'
medium change watch on `/local/domain/1/log-throttling' - unknown device, ignored
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
cirrus vga map change while on lfb mode
mapping vram to f0000000 - f0400000
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state.
Unknown PV product 3 loaded in guest
PV driver build 1
region type 1 at [c100,c200).
region type 0 at [f3001000,f3001100).
squash iomem [f3001000, f3001100).
Add vcpu 4
Add vcpu 5
Add vcpu 6
Add vcpu 7
Add vcpu 8
Add vcpu 9
Add vcpu 10
Add vcpu 11
Add vcpu 12
Add vcpu 13
Add vcpu 14
Add vcpu 15
Add vcpu 16
Add vcpu 17
Add vcpu 18
Add vcpu 19
Add vcpu 20
Add vcpu 21
Add vcpu 22
Add vcpu 23
Add vcpu 24
Add vcpu 25
Add vcpu 26
Add vcpu 27
Add vcpu 28
Add vcpu 29
Add vcpu 30
Add vcpu 31
[-- Attachment #4: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: test report for Xen 4.3 RC1
2013-06-16 4:10 test report for Xen 4.3 RC1 Ren, Yongjie
@ 2013-06-17 14:23 ` Konrad Rzeszutek Wilk
2013-06-17 20:35 ` Konrad Rzeszutek Wilk
2013-06-20 2:53 ` Ren, Yongjie
0 siblings, 2 replies; 17+ messages in thread
From: Konrad Rzeszutek Wilk @ 2013-06-17 14:23 UTC (permalink / raw)
To: Ren, Yongjie
Cc: george.dunlap, Xu, YongweiX, Liu, SongtaoX, Tian, Yongxue, xen-devel
On Sun, Jun 16, 2013 at 04:10:22AM +0000, Ren, Yongjie wrote:
> > -----Original Message-----
> > From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]
> > Sent: Wednesday, June 05, 2013 10:50 PM
> > To: Ren, Yongjie
> > Cc: george.dunlap@eu.citrix.com; Xu, YongweiX; Liu, SongtaoX; Tian,
> > Yongxue; xen-devel@lists.xen.org
> > Subject: Re: [Xen-devel] test report for Xen 4.3 RC1
> >
> > > >
> > http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1851
> > > > > >
> > > > > > That looks like you are hitting the udev race.
> > > > > >
> > > > > > Could you verify that these patches:
> > > > > > https://lkml.org/lkml/2013/5/13/520
> > > > > >
> > > > > > fix the issue (They are destined for v3.11)
> > > > > >
> > > > > Not tried yet. I'll update it to you later.
> > > >
> > > > Thanks!
> > > > >
> > > We tested kernel 3.9.3 with the 2 patches you mentioned, and found this
> > > bug still exist. For example, we did CPU online-offline for Dom0 for 100
> > times,
> > > and found 2 times (of 100 times) failed.
> >
> > Hm, does it fail b/c udev can't online the sysfs entry?
> >
> I think no.
> When it fails to online CPU #3 (trying online #1~#3), it doesn't show any info
> about CPU #3 via the output of "devadm monitor --env" CMD. It does show
> info about #1 and #2 which are onlined succefully.
And if you re-trigger the the 'xl vcpu-set' it eventually comes back up right?
>
> > .. snip..
> > > > >
> > > > > > >
> > > > > > > Old bugs: (11)
> > > > > > > 1. [ACPI] Dom0 can't resume from S3 sleep
> > > > > > > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1707
> > > > > >
> > > > > > That should be fixed in v3.11 (as now we have the fixes)
> > > > > > Could you try v3.10 with the Rafael's ACPI tree merged in?
> > > > > > (so the patches that he wants to submit for v3.11)
> > > > > >
> > > > > I re-tested with Rafel's linux-pm.git tree (master and acpi-hotplug
> > > > branch),
> > > > > and found Dom0 S3 sleep/resume can't work, either.
> > > >
> > > > The patches he has to submit for v3.11 are in the linux-next branch.
> > > > You need to use that branch.
> > > >
> > > Dom0 S3 sleep/resume doesn't work with linux-next branch, either.
> > > attached the log.
> >
> > It does work on my box. So I am not sure if this is related to the
> > IvyTown box you are using. Does it work on other machines?
> >
> No, it doesn't work on other machines, either. I also tried on SandyBridge,
> IvyBridge desktop and Haswell mobile machines.
I just double checked on my AMD machines with v3.10-rc5 with
these extra patches:
ebe2886 x86/cpa: Use pte_attrs instead of pte_flags on CPA/set_p.._wb/wc operations.
7c4ae96 Revert "xen/pat: Disable PAT support for now."
729c6ec Revert "xen/pat: Disable PAT using pat_enabled value."
bd4fd16 microcode_xen: Add support for AMD family >= 15h
6271c21 x86/microcode: check proper return code.
b9a48c8 xen: add CPU microcode update driver
c62566c cpu: make sure that cpu/online file created before KOBJ_ADD is emitted
0790542 cpu: fix "crash_notes" and "crash_notes_size" leaks in register_cpu()
f90099b xen / ACPI / sleep: Register an acpi_suspend_lowlevel callback.
29ca6e9 x86 / ACPI / sleep: Provide registration for acpi_suspend_lowlevel.
and it worked. Let me recompile a kernel without most of them to doublecheck
whether those patches are making the ACPI S3 suspend/resume working.
This is with Xen 4.3 (82cb411). The machine is M5A97, BIOS 1208 04/18/2012
with 01:00.0 VGA compatible controller: NVIDIA Corporation G84 [GeForce 8600 GT] (rev a1)
as its graphic card.
>
> > >
> > > > >
> > > > > > > 2. [XL]"xl vcpu-set" causes dom0 crash or panic
> > > > > > > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1730
> > > > > >
> > > > > > That I think is fixed in v3.10. Could you please check v3.10-rc3?
> > > > > >
> > > > > Still exists on v3.10-rc3.
> > > > > The following command lines can reproduce it:
> > > > > # xl vcpu-set 0 1
> > > > > # xl vcpu-set 0 20
> > > >
> > > > Ugh, same exact stack trace? And can you attach the full dmesg or
> > serial
> > > > output (so that Ican see what there is at bootup)
> > > >
> > > Yes, the same. Also attached in this mail.
> >
> > One of the fixes is this one:
> > http://www.gossamer-threads.com/lists/xen/devel/284897
> >
> > but the other ones I had not seen. I am wondering if the
> > update_sd_lb_stats is b/c of the previous conditions (that is the
> > tick_nohz_idle_start hadn't been called).
> >
> > It is a shoot in the dark - but if you use the above mentioned patch
> > do you still see the update_sd_lb_stats crash?
> >
> Yes, with the patch we still see the update_sd_lb_stats crash.
> It has almost the same trace log as before. Log file is attached.
Would it be possible to do a bit of 'git bisect' to figure out why
this started?
>
> > > > >
> > > > > > > 4. 'xl vcpu-set' can't decrease the vCPU number of a HVM guest
> > > > > > > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1822
> > > > > >
> > > > > > That I believe was an QEMU bug:
> > > > > >
> > http://lists.xen.org/archives/html/xen-devel/2013-05/msg01054.html
> > > > > >
> > > > > > which should be in QEMU traditional now (05-21 was when it went
> > > > > > in the tree)
> > > > > >
> > > > > In this year or past year, this bug always exists (at least in our
> > testing).
> > > > > 'xl vcpu-set' can't decrease the vCPU number of a HVM guest
> > > >
> > > > Could you retry with Xen 4.3 please?
> > > >
> > > With Xen 4.3 & Linux:3.10.0-rc3, I can't decrease the vCPU number of a
> > guest.
> >
> sorry, when I said this message, I still use rhel6.4 kernel as the guest.
> After upgrading guest kernel to 3.10.0-rc3, the result became better.
> Basically vCPU increment/decrement can work fine. I'll close that bug.
Excellent!
> But there's still a minor issue as following.
> After booting guest with 'vcpus=4' and 'maxvcpus=32', change its vCPU number.
> # xl vcpu-set $domID 32
> then you can only get less than 32 (e.g. 19) CPUs in the guest; again, you set
> vCPU number to 32 (from 19), then it works to get 32vCPU for the guest.
> but 'xl vcpu-set $domID 8' can work fine as we expected.
> vCPU decrement has the same result.
> Can you also have a try to reproduce my issue?
Sure. Now how many PCPUS do you have? And what version of QEMU traditional
were you using?
>
> > Could you give some more details? Could you include the
> > /var/log/xen/qemu-... log file?
> >
> Attached the qemu log.
Thank you.
>
> > You are using the traditional QEMU right? (you need to have this in your
> > guest
> > config:
> > device_model_version = 'qemu-xen-traditional'
> >
> Yes.
>
> --
> Jay
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: test report for Xen 4.3 RC1
2013-06-17 14:23 ` Konrad Rzeszutek Wilk
@ 2013-06-17 20:35 ` Konrad Rzeszutek Wilk
2013-06-17 20:36 ` Konrad Rzeszutek Wilk
2013-06-20 2:53 ` Ren, Yongjie
1 sibling, 1 reply; 17+ messages in thread
From: Konrad Rzeszutek Wilk @ 2013-06-17 20:35 UTC (permalink / raw)
To: Ren, Yongjie
Cc: george.dunlap, Xu, YongweiX, Liu, SongtaoX, Tian, Yongxue, xen-devel
> I just double checked on my AMD machines with v3.10-rc5 with
> these extra patches:
>
> ebe2886 x86/cpa: Use pte_attrs instead of pte_flags on CPA/set_p.._wb/wc operations.
> 7c4ae96 Revert "xen/pat: Disable PAT support for now."
> 729c6ec Revert "xen/pat: Disable PAT using pat_enabled value."
> bd4fd16 microcode_xen: Add support for AMD family >= 15h
> 6271c21 x86/microcode: check proper return code.
> b9a48c8 xen: add CPU microcode update driver
> c62566c cpu: make sure that cpu/online file created before KOBJ_ADD is emitted
> 0790542 cpu: fix "crash_notes" and "crash_notes_size" leaks in register_cpu()
> f90099b xen / ACPI / sleep: Register an acpi_suspend_lowlevel callback.
> 29ca6e9 x86 / ACPI / sleep: Provide registration for acpi_suspend_lowlevel.
>
> and it worked. Let me recompile a kernel without most of them to doublecheck
> whether those patches are making the ACPI S3 suspend/resume working.
Still works. I removed all but:
c62566c cpu: make sure that cpu/online file created before KOBJ_ADD is emitted
0790542 cpu: fix "crash_notes" and "crash_notes_size" leaks in register_cpu()
on top of 3.10-rc6 and the suspend/resume on the host works.
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: test report for Xen 4.3 RC1
2013-06-17 20:35 ` Konrad Rzeszutek Wilk
@ 2013-06-17 20:36 ` Konrad Rzeszutek Wilk
0 siblings, 0 replies; 17+ messages in thread
From: Konrad Rzeszutek Wilk @ 2013-06-17 20:36 UTC (permalink / raw)
To: Ren, Yongjie
Cc: george.dunlap, Xu, YongweiX, Liu, SongtaoX, Tian, Yongxue, xen-devel
On Mon, Jun 17, 2013 at 04:35:39PM -0400, Konrad Rzeszutek Wilk wrote:
> > I just double checked on my AMD machines with v3.10-rc5 with
> > these extra patches:
> >
> > ebe2886 x86/cpa: Use pte_attrs instead of pte_flags on CPA/set_p.._wb/wc operations.
> > 7c4ae96 Revert "xen/pat: Disable PAT support for now."
> > 729c6ec Revert "xen/pat: Disable PAT using pat_enabled value."
> > bd4fd16 microcode_xen: Add support for AMD family >= 15h
> > 6271c21 x86/microcode: check proper return code.
> > b9a48c8 xen: add CPU microcode update driver
> > c62566c cpu: make sure that cpu/online file created before KOBJ_ADD is emitted
> > 0790542 cpu: fix "crash_notes" and "crash_notes_size" leaks in register_cpu()
> > f90099b xen / ACPI / sleep: Register an acpi_suspend_lowlevel callback.
> > 29ca6e9 x86 / ACPI / sleep: Provide registration for acpi_suspend_lowlevel.
> >
> > and it worked. Let me recompile a kernel without most of them to doublecheck
> > whether those patches are making the ACPI S3 suspend/resume working.
>
> Still works. I removed all but:
>
> c62566c cpu: make sure that cpu/online file created before KOBJ_ADD is emitted
> 0790542 cpu: fix "crash_notes" and "crash_notes_size" leaks in register_cpu()
>
> on top of 3.10-rc6 and the suspend/resume on the host works.
Correction. This is v3.10-rc6 + Rafaels' linux-next branch which had:
f90099b xen / ACPI / sleep: Register an acpi_suspend_lowlevel callback.
29ca6e9 x86 / ACPI / sleep: Provide registration for acpi_suspend_lowlevel.
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: test report for Xen 4.3 RC1
2013-06-17 14:23 ` Konrad Rzeszutek Wilk
2013-06-17 20:35 ` Konrad Rzeszutek Wilk
@ 2013-06-20 2:53 ` Ren, Yongjie
2013-06-21 18:17 ` Konrad Rzeszutek Wilk
1 sibling, 1 reply; 17+ messages in thread
From: Ren, Yongjie @ 2013-06-20 2:53 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk
Cc: george.dunlap, Xu, YongweiX, Liu, SongtaoX, Tian, Yongxue, xen-devel
[-- Attachment #1: Type: text/plain, Size: 8540 bytes --]
> -----Original Message-----
> From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]
> Sent: Monday, June 17, 2013 10:23 PM
> To: Ren, Yongjie
> Cc: george.dunlap@eu.citrix.com; Xu, YongweiX; Liu, SongtaoX; Tian,
> Yongxue; xen-devel@lists.xen.org
> Subject: Re: [Xen-devel] test report for Xen 4.3 RC1
>
> On Sun, Jun 16, 2013 at 04:10:22AM +0000, Ren, Yongjie wrote:
> > > -----Original Message-----
> > > From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]
> > > Sent: Wednesday, June 05, 2013 10:50 PM
> > > To: Ren, Yongjie
> > > Cc: george.dunlap@eu.citrix.com; Xu, YongweiX; Liu, SongtaoX; Tian,
> > > Yongxue; xen-devel@lists.xen.org
> > > Subject: Re: [Xen-devel] test report for Xen 4.3 RC1
> > >
> > > > >
> > >
> http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1851
> > > > > > >
> > > > > > > That looks like you are hitting the udev race.
> > > > > > >
> > > > > > > Could you verify that these patches:
> > > > > > > https://lkml.org/lkml/2013/5/13/520
> > > > > > >
> > > > > > > fix the issue (They are destined for v3.11)
> > > > > > >
> > > > > > Not tried yet. I'll update it to you later.
> > > > >
> > > > > Thanks!
> > > > > >
> > > > We tested kernel 3.9.3 with the 2 patches you mentioned, and found
> this
> > > > bug still exist. For example, we did CPU online-offline for Dom0 for
> 100
> > > times,
> > > > and found 2 times (of 100 times) failed.
> > >
> > > Hm, does it fail b/c udev can't online the sysfs entry?
> > >
> > I think no.
> > When it fails to online CPU #3 (trying online #1~#3), it doesn't show any
> info
> > about CPU #3 via the output of "devadm monitor --env" CMD. It does
> show
> > info about #1 and #2 which are onlined succefully.
>
> And if you re-trigger the the 'xl vcpu-set' it eventually comes back up right?
>
We don't use 'xl vcpu-set' command when doing the CPU hot-plug.
We just call the xc_cpu_online/offline() in tools/libxc/xc_cpu_hotplug.c to test.
(see the attachment about my test code in that bugzilla.)
And, yes, if a CPU failed to online, it can also be onlined again when we re-trigger
online function.
> >
> > > .. snip..
> > > > > >
> > > > > > > >
> > > > > > > > Old bugs: (11)
> > > > > > > > 1. [ACPI] Dom0 can't resume from S3 sleep
> > > > > > > > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1707
> > > > > > >
> > > > > > > That should be fixed in v3.11 (as now we have the fixes)
> > > > > > > Could you try v3.10 with the Rafael's ACPI tree merged in?
> > > > > > > (so the patches that he wants to submit for v3.11)
> > > > > > >
> > > > > > I re-tested with Rafel's linux-pm.git tree (master and acpi-hotplug
> > > > > branch),
> > > > > > and found Dom0 S3 sleep/resume can't work, either.
> > > > >
> > > > > The patches he has to submit for v3.11 are in the linux-next branch.
> > > > > You need to use that branch.
> > > > >
> > > > Dom0 S3 sleep/resume doesn't work with linux-next branch, either.
> > > > attached the log.
> > >
> > > It does work on my box. So I am not sure if this is related to the
> > > IvyTown box you are using. Does it work on other machines?
> > >
> > No, it doesn't work on other machines, either. I also tried on
> SandyBridge,
> > IvyBridge desktop and Haswell mobile machines.
>
> I just double checked on my AMD machines with v3.10-rc5 with
> these extra patches:
>
> ebe2886 x86/cpa: Use pte_attrs instead of pte_flags on
> CPA/set_p.._wb/wc operations.
> 7c4ae96 Revert "xen/pat: Disable PAT support for now."
> 729c6ec Revert "xen/pat: Disable PAT using pat_enabled value."
> bd4fd16 microcode_xen: Add support for AMD family >= 15h
> 6271c21 x86/microcode: check proper return code.
> b9a48c8 xen: add CPU microcode update driver
> c62566c cpu: make sure that cpu/online file created before KOBJ_ADD is
> emitted
> 0790542 cpu: fix "crash_notes" and "crash_notes_size" leaks in
> register_cpu()
> f90099b xen / ACPI / sleep: Register an acpi_suspend_lowlevel callback.
> 29ca6e9 x86 / ACPI / sleep: Provide registration for
> acpi_suspend_lowlevel.
>
> and it worked. Let me recompile a kernel without most of them to
> doublecheck
> whether those patches are making the ACPI S3 suspend/resume working.
> This is with Xen 4.3 (82cb411). The machine is M5A97, BIOS 1208
> 04/18/2012
> with 01:00.0 VGA compatible controller: NVIDIA Corporation G84 [GeForce
> 8600 GT] (rev a1)
> as its graphic card.
>
After re-testing with linux-pm.git tree (kernel:3.10.rc6+ commit: a913b188df) on
my IvyTown-EP and IvyBridge desktop systems, Dom0 S3 sleep/resume can work!
When these codes are upstreamed to linux.git tree, I can close this bug.
> >
> > > >
> > > > > >
> > > > > > > > 2. [XL]"xl vcpu-set" causes dom0 crash or panic
> > > > > > > > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1730
> > > > > > >
> > > > > > > That I think is fixed in v3.10. Could you please check v3.10-rc3?
> > > > > > >
> > > > > > Still exists on v3.10-rc3.
> > > > > > The following command lines can reproduce it:
> > > > > > # xl vcpu-set 0 1
> > > > > > # xl vcpu-set 0 20
> > > > >
> > > > > Ugh, same exact stack trace? And can you attach the full dmesg or
> > > serial
> > > > > output (so that Ican see what there is at bootup)
> > > > >
> > > > Yes, the same. Also attached in this mail.
> > >
> > > One of the fixes is this one:
> > > http://www.gossamer-threads.com/lists/xen/devel/284897
> > >
> > > but the other ones I had not seen. I am wondering if the
> > > update_sd_lb_stats is b/c of the previous conditions (that is the
> > > tick_nohz_idle_start hadn't been called).
> > >
> > > It is a shoot in the dark - but if you use the above mentioned patch
> > > do you still see the update_sd_lb_stats crash?
> > >
> > Yes, with the patch we still see the update_sd_lb_stats crash.
> > It has almost the same trace log as before. Log file is attached.
>
> Would it be possible to do a bit of 'git bisect' to figure out why
> this started?
>
It's hard.
This issue exists for a long time. We don't even know which version of
linux upstream as dom0 can work for this bug.
> > > > > > > > 4. 'xl vcpu-set' can't decrease the vCPU number of a HVM
> guest
> > > > > > > > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1822
> > > > > > >
> > > > > > > That I believe was an QEMU bug:
> > > > > > >
> > > http://lists.xen.org/archives/html/xen-devel/2013-05/msg01054.html
> > > > > > >
> > > > > > > which should be in QEMU traditional now (05-21 was when it
> went
> > > > > > > in the tree)
> > > > > > >
> > > > > > In this year or past year, this bug always exists (at least in our
> > > testing).
> > > > > > 'xl vcpu-set' can't decrease the vCPU number of a HVM guest
> > > > >
> > > > > Could you retry with Xen 4.3 please?
> > > > >
> > > > With Xen 4.3 & Linux:3.10.0-rc3, I can't decrease the vCPU number of
> a
> > > guest.
> > >
> > sorry, when I said this message, I still use rhel6.4 kernel as the guest.
> > After upgrading guest kernel to 3.10.0-rc3, the result became better.
> > Basically vCPU increment/decrement can work fine. I'll close that bug.
>
> Excellent!
> > But there's still a minor issue as following.
> > After booting guest with 'vcpus=4' and 'maxvcpus=32', change its vCPU
> number.
> > # xl vcpu-set $domID 32
> > then you can only get less than 32 (e.g. 19) CPUs in the guest; again, you
> set
> > vCPU number to 32 (from 19), then it works to get 32vCPU for the guest.
> > but 'xl vcpu-set $domID 8' can work fine as we expected.
> > vCPU decrement has the same result.
> > Can you also have a try to reproduce my issue?
>
This issue doesn't exist when using the latest QEMU traditional tree.
My pervious QEMU was old (March 2013), and I found some of your patches
were applied in May 2013. These fixes can fix the issue we reported.
Close this bug.
But, it introduced another issue: when doing 'xl vcpu-set' for HVM several
times (e.g. 5 times), the guest will panic. Log is attached.
Before your patches in qemu traditional tree in May 2013, we never meet
guest kernel panic.
dom0: 3.10.0-rc3
Xen: 4.3.0-RCx
QEMU: the latest traditional tree
guest kernel: 3.10.0-RC3
I'll file another bug to track this bug ?
Can you reproduce this ?
> Sure. Now how many PCPUS do you have? And what version of QEMU
> traditional
> were you using?
>
There're 32 pCPU in that system we used.
Best Regards,
Yongjie (Jay)
[-- Attachment #2: guest-panic-_vcpu-set.log --]
[-- Type: application/octet-stream, Size: 34875 bytes --]
[-- Attachment #3: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: test report for Xen 4.3 RC1
2013-06-20 2:53 ` Ren, Yongjie
@ 2013-06-21 18:17 ` Konrad Rzeszutek Wilk
2013-07-02 8:09 ` Ren, Yongjie
0 siblings, 1 reply; 17+ messages in thread
From: Konrad Rzeszutek Wilk @ 2013-06-21 18:17 UTC (permalink / raw)
To: Ren, Yongjie
Cc: george.dunlap, Xu, YongweiX, Liu, SongtaoX, Tian, Yongxue, xen-devel
On Thu, Jun 20, 2013 at 02:53:06AM +0000, Ren, Yongjie wrote:
> > -----Original Message-----
> > From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]
> > Sent: Monday, June 17, 2013 10:23 PM
> > To: Ren, Yongjie
> > Cc: george.dunlap@eu.citrix.com; Xu, YongweiX; Liu, SongtaoX; Tian,
> > Yongxue; xen-devel@lists.xen.org
> > Subject: Re: [Xen-devel] test report for Xen 4.3 RC1
> >
> > On Sun, Jun 16, 2013 at 04:10:22AM +0000, Ren, Yongjie wrote:
> > > > -----Original Message-----
> > > > From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]
> > > > Sent: Wednesday, June 05, 2013 10:50 PM
> > > > To: Ren, Yongjie
> > > > Cc: george.dunlap@eu.citrix.com; Xu, YongweiX; Liu, SongtaoX; Tian,
> > > > Yongxue; xen-devel@lists.xen.org
> > > > Subject: Re: [Xen-devel] test report for Xen 4.3 RC1
> > > >
> > > > > >
> > > >
> > http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1851
> > > > > > > >
> > > > > > > > That looks like you are hitting the udev race.
> > > > > > > >
> > > > > > > > Could you verify that these patches:
> > > > > > > > https://lkml.org/lkml/2013/5/13/520
> > > > > > > >
> > > > > > > > fix the issue (They are destined for v3.11)
> > > > > > > >
> > > > > > > Not tried yet. I'll update it to you later.
> > > > > >
> > > > > > Thanks!
> > > > > > >
> > > > > We tested kernel 3.9.3 with the 2 patches you mentioned, and found
> > this
> > > > > bug still exist. For example, we did CPU online-offline for Dom0 for
> > 100
> > > > times,
> > > > > and found 2 times (of 100 times) failed.
> > > >
> > > > Hm, does it fail b/c udev can't online the sysfs entry?
> > > >
> > > I think no.
> > > When it fails to online CPU #3 (trying online #1~#3), it doesn't show any
> > info
> > > about CPU #3 via the output of "devadm monitor --env" CMD. It does
> > show
> > > info about #1 and #2 which are onlined succefully.
> >
> > And if you re-trigger the the 'xl vcpu-set' it eventually comes back up right?
> >
> We don't use 'xl vcpu-set' command when doing the CPU hot-plug.
> We just call the xc_cpu_online/offline() in tools/libxc/xc_cpu_hotplug.c to test.
Oh. That is very different than what I thought. You are not offlining/onlining
vCPUS - you offlining/onlining pCPUS! So Xen has to cramp the dom0 vCPUs in the
remaining vCPUS.
There should be no vCPU re-sizing correct?
> (see the attachment about my test code in that bugzilla.)
> And, yes, if a CPU failed to online, it can also be onlined again when we re-trigger
> online function.
>
> > >
> > > > .. snip..
> > > > > > >
> > > > > > > > >
> > > > > > > > > Old bugs: (11)
> > > > > > > > > 1. [ACPI] Dom0 can't resume from S3 sleep
> > > > > > > > > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1707
> > > > > > > >
> > > > > > > > That should be fixed in v3.11 (as now we have the fixes)
> > > > > > > > Could you try v3.10 with the Rafael's ACPI tree merged in?
> > > > > > > > (so the patches that he wants to submit for v3.11)
> > > > > > > >
> > > > > > > I re-tested with Rafel's linux-pm.git tree (master and acpi-hotplug
> > > > > > branch),
> > > > > > > and found Dom0 S3 sleep/resume can't work, either.
> > > > > >
> > > > > > The patches he has to submit for v3.11 are in the linux-next branch.
> > > > > > You need to use that branch.
> > > > > >
> > > > > Dom0 S3 sleep/resume doesn't work with linux-next branch, either.
> > > > > attached the log.
> > > >
> > > > It does work on my box. So I am not sure if this is related to the
> > > > IvyTown box you are using. Does it work on other machines?
> > > >
> > > No, it doesn't work on other machines, either. I also tried on
> > SandyBridge,
> > > IvyBridge desktop and Haswell mobile machines.
> >
> > I just double checked on my AMD machines with v3.10-rc5 with
> > these extra patches:
> >
> > ebe2886 x86/cpa: Use pte_attrs instead of pte_flags on
> > CPA/set_p.._wb/wc operations.
> > 7c4ae96 Revert "xen/pat: Disable PAT support for now."
> > 729c6ec Revert "xen/pat: Disable PAT using pat_enabled value."
> > bd4fd16 microcode_xen: Add support for AMD family >= 15h
> > 6271c21 x86/microcode: check proper return code.
> > b9a48c8 xen: add CPU microcode update driver
> > c62566c cpu: make sure that cpu/online file created before KOBJ_ADD is
> > emitted
> > 0790542 cpu: fix "crash_notes" and "crash_notes_size" leaks in
> > register_cpu()
> > f90099b xen / ACPI / sleep: Register an acpi_suspend_lowlevel callback.
> > 29ca6e9 x86 / ACPI / sleep: Provide registration for
> > acpi_suspend_lowlevel.
> >
> > and it worked. Let me recompile a kernel without most of them to
> > doublecheck
> > whether those patches are making the ACPI S3 suspend/resume working.
> > This is with Xen 4.3 (82cb411). The machine is M5A97, BIOS 1208
> > 04/18/2012
> > with 01:00.0 VGA compatible controller: NVIDIA Corporation G84 [GeForce
> > 8600 GT] (rev a1)
> > as its graphic card.
> >
> After re-testing with linux-pm.git tree (kernel:3.10.rc6+ commit: a913b188df) on
> my IvyTown-EP and IvyBridge desktop systems, Dom0 S3 sleep/resume can work!
> When these codes are upstreamed to linux.git tree, I can close this bug.
Yes! Thought Ben found another issue with extended sleep - where it will
not use the hypercall. <sigh>
>
> > >
> > > > >
> > > > > > >
> > > > > > > > > 2. [XL]"xl vcpu-set" causes dom0 crash or panic
> > > > > > > > > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1730
> > > > > > > >
> > > > > > > > That I think is fixed in v3.10. Could you please check v3.10-rc3?
> > > > > > > >
> > > > > > > Still exists on v3.10-rc3.
> > > > > > > The following command lines can reproduce it:
> > > > > > > # xl vcpu-set 0 1
> > > > > > > # xl vcpu-set 0 20
> > > > > >
> > > > > > Ugh, same exact stack trace? And can you attach the full dmesg or
> > > > serial
> > > > > > output (so that Ican see what there is at bootup)
> > > > > >
> > > > > Yes, the same. Also attached in this mail.
> > > >
> > > > One of the fixes is this one:
> > > > http://www.gossamer-threads.com/lists/xen/devel/284897
> > > >
> > > > but the other ones I had not seen. I am wondering if the
> > > > update_sd_lb_stats is b/c of the previous conditions (that is the
> > > > tick_nohz_idle_start hadn't been called).
> > > >
> > > > It is a shoot in the dark - but if you use the above mentioned patch
> > > > do you still see the update_sd_lb_stats crash?
> > > >
> > > Yes, with the patch we still see the update_sd_lb_stats crash.
> > > It has almost the same trace log as before. Log file is attached.
> >
> > Would it be possible to do a bit of 'git bisect' to figure out why
> > this started?
> >
> It's hard.
> This issue exists for a long time. We don't even know which version of
> linux upstream as dom0 can work for this bug.
Then a bit of digging will be needed. Sadly I am out of time to do this
ATM.
>
> > > > > > > > > 4. 'xl vcpu-set' can't decrease the vCPU number of a HVM
> > guest
> > > > > > > > > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1822
> > > > > > > >
> > > > > > > > That I believe was an QEMU bug:
> > > > > > > >
> > > > http://lists.xen.org/archives/html/xen-devel/2013-05/msg01054.html
> > > > > > > >
> > > > > > > > which should be in QEMU traditional now (05-21 was when it
> > went
> > > > > > > > in the tree)
> > > > > > > >
> > > > > > > In this year or past year, this bug always exists (at least in our
> > > > testing).
> > > > > > > 'xl vcpu-set' can't decrease the vCPU number of a HVM guest
> > > > > >
> > > > > > Could you retry with Xen 4.3 please?
> > > > > >
> > > > > With Xen 4.3 & Linux:3.10.0-rc3, I can't decrease the vCPU number of
> > a
> > > > guest.
> > > >
> > > sorry, when I said this message, I still use rhel6.4 kernel as the guest.
> > > After upgrading guest kernel to 3.10.0-rc3, the result became better.
> > > Basically vCPU increment/decrement can work fine. I'll close that bug.
> >
> > Excellent!
> > > But there's still a minor issue as following.
> > > After booting guest with 'vcpus=4' and 'maxvcpus=32', change its vCPU
> > number.
> > > # xl vcpu-set $domID 32
> > > then you can only get less than 32 (e.g. 19) CPUs in the guest; again, you
> > set
> > > vCPU number to 32 (from 19), then it works to get 32vCPU for the guest.
> > > but 'xl vcpu-set $domID 8' can work fine as we expected.
> > > vCPU decrement has the same result.
> > > Can you also have a try to reproduce my issue?
> >
> This issue doesn't exist when using the latest QEMU traditional tree.
> My pervious QEMU was old (March 2013), and I found some of your patches
> were applied in May 2013. These fixes can fix the issue we reported.
> Close this bug.
Yes!
>
> But, it introduced another issue: when doing 'xl vcpu-set' for HVM several
> times (e.g. 5 times), the guest will panic. Log is attached.
> Before your patches in qemu traditional tree in May 2013, we never meet
> guest kernel panic.
> dom0: 3.10.0-rc3
> Xen: 4.3.0-RCx
> QEMU: the latest traditional tree
> guest kernel: 3.10.0-RC3
> I'll file another bug to track this bug ?
Please.
> Can you reproduce this ?
Could you tell me how you are doing 'xl vcpu-set'? Is there a particular
test script you are using?
>
> > Sure. Now how many PCPUS do you have? And what version of QEMU
> > traditional
> > were you using?
> >
> There're 32 pCPU in that system we used.
>
> Best Regards,
> Yongjie (Jay)
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: test report for Xen 4.3 RC1
2013-06-21 18:17 ` Konrad Rzeszutek Wilk
@ 2013-07-02 8:09 ` Ren, Yongjie
2013-07-02 13:36 ` Konrad Rzeszutek Wilk
0 siblings, 1 reply; 17+ messages in thread
From: Ren, Yongjie @ 2013-07-02 8:09 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk
Cc: george.dunlap, Xu, YongweiX, Liu, SongtaoX, Tian, Yongxue, xen-devel
> -----Original Message-----
> From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]
> Sent: Saturday, June 22, 2013 2:18 AM
> To: Ren, Yongjie
> Cc: george.dunlap@eu.citrix.com; Xu, YongweiX; Liu, SongtaoX; Tian,
> Yongxue; xen-devel@lists.xen.org
> Subject: Re: [Xen-devel] test report for Xen 4.3 RC1
>
> > >
> http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1851
> > > > > > > > >
> > > > > > > > > That looks like you are hitting the udev race.
> > > > > > > > >
> > > > > > > > > Could you verify that these patches:
> > > > > > > > > https://lkml.org/lkml/2013/5/13/520
> > > > > > > > >
> > > > > > > > > fix the issue (They are destined for v3.11)
> > > > > > > > >
> > > > > > > > Not tried yet. I'll update it to you later.
> > > > > > >
> > > > > > > Thanks!
> > > > > > > >
> > > > > > We tested kernel 3.9.3 with the 2 patches you mentioned, and
> found
> > > this
> > > > > > bug still exist. For example, we did CPU online-offline for Dom0 for
> > > 100
> > > > > times,
> > > > > > and found 2 times (of 100 times) failed.
> > > > >
> > > > > Hm, does it fail b/c udev can't online the sysfs entry?
> > > > >
> > > > I think no.
> > > > When it fails to online CPU #3 (trying online #1~#3), it doesn't show
> any
> > > info
> > > > about CPU #3 via the output of "devadm monitor --env" CMD. It does
> > > show
> > > > info about #1 and #2 which are onlined succefully.
> > >
> > > And if you re-trigger the the 'xl vcpu-set' it eventually comes back up
> right?
> > >
> > We don't use 'xl vcpu-set' command when doing the CPU hot-plug.
> > We just call the xc_cpu_online/offline() in tools/libxc/xc_cpu_hotplug.c to
> test.
>
> Oh. That is very different than what I thought. You are not offlining/onlining
> vCPUS - you offlining/onlining pCPUS! So Xen has to cramp the dom0 vCPUs
> in the
> remaining vCPUS.
>
> There should be no vCPU re-sizing correct?
>
Yes, for this case we do online/offline for pCPUs not vCPUs.
(vCPU number doesn't change.)
> > (see the attachment about my test code in that bugzilla.)
> > And, yes, if a CPU failed to online, it can also be onlined again when we
> re-trigger
> > online function.
> >
> > > >
> > > > > > > > > > 4. 'xl vcpu-set' can't decrease the vCPU number of a HVM
> > > guest
> > > > > > > > > > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1822
> > > > > > > > >
> > > > > > > > > That I believe was an QEMU bug:
> > > > > > > > >
> > > > >
> http://lists.xen.org/archives/html/xen-devel/2013-05/msg01054.html
> > > > > > > > >
> > > > > > > > > which should be in QEMU traditional now (05-21 was when it
> > > went
> > > > > > > > > in the tree)
> > > > > > > > >
> > > > > > > > In this year or past year, this bug always exists (at least in our
> > > > > testing).
> > > > > > > > 'xl vcpu-set' can't decrease the vCPU number of a HVM guest
> > > > > > >
> > > > > > > Could you retry with Xen 4.3 please?
> > > > > > >
> > > > > > With Xen 4.3 & Linux:3.10.0-rc3, I can't decrease the vCPU
> number of
> > > a
> > > > > guest.
> > > > >
> > > > sorry, when I said this message, I still use rhel6.4 kernel as the guest.
> > > > After upgrading guest kernel to 3.10.0-rc3, the result became better.
> > > > Basically vCPU increment/decrement can work fine. I'll close that
> bug.
> > >
> > > Excellent!
> > > > But there's still a minor issue as following.
> > > > After booting guest with 'vcpus=4' and 'maxvcpus=32', change its
> vCPU
> > > number.
> > > > # xl vcpu-set $domID 32
> > > > then you can only get less than 32 (e.g. 19) CPUs in the guest; again,
> you
> > > set
> > > > vCPU number to 32 (from 19), then it works to get 32vCPU for the
> guest.
> > > > but 'xl vcpu-set $domID 8' can work fine as we expected.
> > > > vCPU decrement has the same result.
> > > > Can you also have a try to reproduce my issue?
> > >
> > This issue doesn't exist when using the latest QEMU traditional tree.
> > My pervious QEMU was old (March 2013), and I found some of your
> patches
> > were applied in May 2013. These fixes can fix the issue we reported.
> > Close this bug.
>
> Yes!
> >
> > But, it introduced another issue: when doing 'xl vcpu-set' for HVM
> several
> > times (e.g. 5 times), the guest will panic. Log is attached.
> > Before your patches in qemu traditional tree in May 2013, we never
> meet
> > guest kernel panic.
> > dom0: 3.10.0-rc3
> > Xen: 4.3.0-RCx
> > QEMU: the latest traditional tree
> > guest kernel: 3.10.0-RC3
> > I'll file another bug to track this bug ?
>
> Please.
> > Can you reproduce this ?
>
> Could you tell me how you are doing 'xl vcpu-set'? Is there a particular
> test script you are using?
>
1. xl vcpu-set $domID 2
2. xl vcpu-set $domID 20
3. repeat step #1 and #2 for several times. (guest kernel panic ...)
I also filed a bug in bugzilla to track this.
You can get more info in the following link.
http://bugzilla.xenproject.org/bugzilla/show_bug.cgi?id=1860
--
Jay
> >
> > > Sure. Now how many PCPUS do you have? And what version of QEMU
> > > traditional
> > > were you using?
> > >
> > There're 32 pCPU in that system we used.
> >
> > Best Regards,
> > Yongjie (Jay)
>
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: test report for Xen 4.3 RC1
2013-07-02 8:09 ` Ren, Yongjie
@ 2013-07-02 13:36 ` Konrad Rzeszutek Wilk
0 siblings, 0 replies; 17+ messages in thread
From: Konrad Rzeszutek Wilk @ 2013-07-02 13:36 UTC (permalink / raw)
To: Ren, Yongjie
Cc: george.dunlap, Xu, YongweiX, Liu, SongtaoX, Tian, Yongxue, xen-devel
On Tue, Jul 02, 2013 at 08:09:48AM +0000, Ren, Yongjie wrote:
> > -----Original Message-----
> > From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]
> > Sent: Saturday, June 22, 2013 2:18 AM
> > To: Ren, Yongjie
> > Cc: george.dunlap@eu.citrix.com; Xu, YongweiX; Liu, SongtaoX; Tian,
> > Yongxue; xen-devel@lists.xen.org
> > Subject: Re: [Xen-devel] test report for Xen 4.3 RC1
> >
> > > >
> > http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1851
> > > > > > > > > >
> > > > > > > > > > That looks like you are hitting the udev race.
> > > > > > > > > >
> > > > > > > > > > Could you verify that these patches:
> > > > > > > > > > https://lkml.org/lkml/2013/5/13/520
> > > > > > > > > >
> > > > > > > > > > fix the issue (They are destined for v3.11)
> > > > > > > > > >
> > > > > > > > > Not tried yet. I'll update it to you later.
> > > > > > > >
> > > > > > > > Thanks!
> > > > > > > > >
> > > > > > > We tested kernel 3.9.3 with the 2 patches you mentioned, and
> > found
> > > > this
> > > > > > > bug still exist. For example, we did CPU online-offline for Dom0 for
> > > > 100
> > > > > > times,
> > > > > > > and found 2 times (of 100 times) failed.
> > > > > >
> > > > > > Hm, does it fail b/c udev can't online the sysfs entry?
> > > > > >
> > > > > I think no.
> > > > > When it fails to online CPU #3 (trying online #1~#3), it doesn't show
> > any
> > > > info
> > > > > about CPU #3 via the output of "devadm monitor --env" CMD. It does
> > > > show
> > > > > info about #1 and #2 which are onlined succefully.
> > > >
> > > > And if you re-trigger the the 'xl vcpu-set' it eventually comes back up
> > right?
> > > >
> > > We don't use 'xl vcpu-set' command when doing the CPU hot-plug.
> > > We just call the xc_cpu_online/offline() in tools/libxc/xc_cpu_hotplug.c to
> > test.
> >
> > Oh. That is very different than what I thought. You are not offlining/onlining
> > vCPUS - you offlining/onlining pCPUS! So Xen has to cramp the dom0 vCPUs
> > in the
> > remaining vCPUS.
> >
> > There should be no vCPU re-sizing correct?
> >
> Yes, for this case we do online/offline for pCPUs not vCPUs.
> (vCPU number doesn't change.)
OK, so nothing to do with Linux but mostly with Xen hypervisor. Do you know
who added this functionality? Can they help?
>
> > > (see the attachment about my test code in that bugzilla.)
> > > And, yes, if a CPU failed to online, it can also be onlined again when we
> > re-trigger
> > > online function.
> > >
> > > > >
>
>
> > > > > > > > > > > 4. 'xl vcpu-set' can't decrease the vCPU number of a HVM
> > > > guest
> > > > > > > > > > > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1822
> > > > > > > > > >
> > > > > > > > > > That I believe was an QEMU bug:
> > > > > > > > > >
> > > > > >
> > http://lists.xen.org/archives/html/xen-devel/2013-05/msg01054.html
> > > > > > > > > >
> > > > > > > > > > which should be in QEMU traditional now (05-21 was when it
> > > > went
> > > > > > > > > > in the tree)
> > > > > > > > > >
> > > > > > > > > In this year or past year, this bug always exists (at least in our
> > > > > > testing).
> > > > > > > > > 'xl vcpu-set' can't decrease the vCPU number of a HVM guest
> > > > > > > >
> > > > > > > > Could you retry with Xen 4.3 please?
> > > > > > > >
> > > > > > > With Xen 4.3 & Linux:3.10.0-rc3, I can't decrease the vCPU
> > number of
> > > > a
> > > > > > guest.
> > > > > >
> > > > > sorry, when I said this message, I still use rhel6.4 kernel as the guest.
> > > > > After upgrading guest kernel to 3.10.0-rc3, the result became better.
> > > > > Basically vCPU increment/decrement can work fine. I'll close that
> > bug.
> > > >
> > > > Excellent!
> > > > > But there's still a minor issue as following.
> > > > > After booting guest with 'vcpus=4' and 'maxvcpus=32', change its
> > vCPU
> > > > number.
> > > > > # xl vcpu-set $domID 32
> > > > > then you can only get less than 32 (e.g. 19) CPUs in the guest; again,
> > you
> > > > set
> > > > > vCPU number to 32 (from 19), then it works to get 32vCPU for the
> > guest.
> > > > > but 'xl vcpu-set $domID 8' can work fine as we expected.
> > > > > vCPU decrement has the same result.
> > > > > Can you also have a try to reproduce my issue?
> > > >
> > > This issue doesn't exist when using the latest QEMU traditional tree.
> > > My pervious QEMU was old (March 2013), and I found some of your
> > patches
> > > were applied in May 2013. These fixes can fix the issue we reported.
> > > Close this bug.
> >
> > Yes!
> > >
> > > But, it introduced another issue: when doing 'xl vcpu-set' for HVM
> > several
> > > times (e.g. 5 times), the guest will panic. Log is attached.
> > > Before your patches in qemu traditional tree in May 2013, we never
> > meet
> > > guest kernel panic.
> > > dom0: 3.10.0-rc3
> > > Xen: 4.3.0-RCx
> > > QEMU: the latest traditional tree
> > > guest kernel: 3.10.0-RC3
> > > I'll file another bug to track this bug ?
> >
> > Please.
> > > Can you reproduce this ?
> >
> > Could you tell me how you are doing 'xl vcpu-set'? Is there a particular
> > test script you are using?
> >
> 1. xl vcpu-set $domID 2
> 2. xl vcpu-set $domID 20
> 3. repeat step #1 and #2 for several times. (guest kernel panic ...)
>
> I also filed a bug in bugzilla to track this.
> You can get more info in the following link.
> http://bugzilla.xenproject.org/bugzilla/show_bug.cgi?id=1860
OK, thank you.
I am a bit busy right now tracking down some other bugs that I promised
I would look after. But after that I should have some time.
>
> --
> Jay
>
>
> > >
> > > > Sure. Now how many PCPUS do you have? And what version of QEMU
> > > > traditional
> > > > were you using?
> > > >
> > > There're 32 pCPU in that system we used.
> > >
> > > Best Regards,
> > > Yongjie (Jay)
> >
>
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: test report for Xen 4.3 RC1
2013-05-28 15:24 ` George Dunlap
@ 2013-11-11 10:22 ` Ian Campbell
0 siblings, 0 replies; 17+ messages in thread
From: Ian Campbell @ 2013-11-11 10:22 UTC (permalink / raw)
To: George Dunlap; +Cc: xen-devel
On Tue, 2013-05-28 at 16:24 +0100, George Dunlap wrote:
> > create !
> > title -1 "linux, xenbus mutex hangs when rebooting dom0 and guests hung."
>
> 1. I think that these commands have to come at the top
> 2. You don't need quotes in the title
> 3. You need to be polite and say "thanks" at the end so it knows it can
> stop paying attention. :-)
4. Use Bcc and not Cc so that the entirely subsequent thread doesn't get
sent to the bot when folks reply-all.
Ian.
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: test report for Xen 4.3 RC1
2013-06-05 10:14 Ren, Yongjie
@ 2013-06-05 14:50 ` Konrad Rzeszutek Wilk
0 siblings, 0 replies; 17+ messages in thread
From: Konrad Rzeszutek Wilk @ 2013-06-05 14:50 UTC (permalink / raw)
To: Ren, Yongjie
Cc: george.dunlap, Xu, YongweiX, Liu, SongtaoX, Tian, Yongxue, xen-devel
> > http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1851
> > > >
> > > > That looks like you are hitting the udev race.
> > > >
> > > > Could you verify that these patches:
> > > > https://lkml.org/lkml/2013/5/13/520
> > > >
> > > > fix the issue (They are destined for v3.11)
> > > >
> > > Not tried yet. I'll update it to you later.
> >
> > Thanks!
> > >
> We tested kernel 3.9.3 with the 2 patches you mentioned, and found this
> bug still exist. For example, we did CPU online-offline for Dom0 for 100 times,
> and found 2 times (of 100 times) failed.
Hm, does it fail b/c udev can't online the sysfs entry?
.. snip..
> > >
> > > > >
> > > > > Old bugs: (11)
> > > > > 1. [ACPI] Dom0 can't resume from S3 sleep
> > > > > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1707
> > > >
> > > > That should be fixed in v3.11 (as now we have the fixes)
> > > > Could you try v3.10 with the Rafael's ACPI tree merged in?
> > > > (so the patches that he wants to submit for v3.11)
> > > >
> > > I re-tested with Rafel's linux-pm.git tree (master and acpi-hotplug
> > branch),
> > > and found Dom0 S3 sleep/resume can't work, either.
> >
> > The patches he has to submit for v3.11 are in the linux-next branch.
> > You need to use that branch.
> >
> Dom0 S3 sleep/resume doesn't work with linux-next branch, either.
> attached the log.
It does work on my box. So I am not sure if this is related to the
IvyTown box you are using. Does it work on other machines?
>
> > >
> > > > > 2. [XL]"xl vcpu-set" causes dom0 crash or panic
> > > > > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1730
> > > >
> > > > That I think is fixed in v3.10. Could you please check v3.10-rc3?
> > > >
> > > Still exists on v3.10-rc3.
> > > The following command lines can reproduce it:
> > > # xl vcpu-set 0 1
> > > # xl vcpu-set 0 20
> >
> > Ugh, same exact stack trace? And can you attach the full dmesg or serial
> > output (so that Ican see what there is at bootup)
> >
> Yes, the same. Also attached in this mail.
One of the fixes is this one:
http://www.gossamer-threads.com/lists/xen/devel/284897
but the other ones I had not seen. I am wondering if the
update_sd_lb_stats is b/c of the previous conditions (that is the
tick_nohz_idle_start hadn't been called).
It is a shoot in the dark - but if you use the above mentioned patch
do you still see the update_sd_lb_stats crash?
> > >
> > > > > 4. 'xl vcpu-set' can't decrease the vCPU number of a HVM guest
> > > > > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1822
> > > >
> > > > That I believe was an QEMU bug:
> > > > http://lists.xen.org/archives/html/xen-devel/2013-05/msg01054.html
> > > >
> > > > which should be in QEMU traditional now (05-21 was when it went
> > > > in the tree)
> > > >
> > > In this year or past year, this bug always exists (at least in our testing).
> > > 'xl vcpu-set' can't decrease the vCPU number of a HVM guest
> >
> > Could you retry with Xen 4.3 please?
> >
> With Xen 4.3 & Linux:3.10.0-rc3, I can't decrease the vCPU number of a guest.
Could you give some more details? Could you include the /var/log/xen/qemu-... log file?
You are using the traditional QEMU right? (you need to have this in your guest
config:
device_model_version = 'qemu-xen-traditional'
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: test report for Xen 4.3 RC1
@ 2013-06-05 10:14 Ren, Yongjie
2013-06-05 14:50 ` Konrad Rzeszutek Wilk
0 siblings, 1 reply; 17+ messages in thread
From: Ren, Yongjie @ 2013-06-05 10:14 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk
Cc: george.dunlap, Xu, YongweiX, Liu, SongtaoX, Tian, Yongxue, xen-devel
[-- Attachment #1: Type: text/plain, Size: 10333 bytes --]
> -----Original Message-----
> From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]
> Sent: Wednesday, June 05, 2013 12:36 AM
> To: Ren, Yongjie
> Cc: george.dunlap@eu.citrix.com; Xu, YongweiX; Liu, SongtaoX; Tian,
> Yongxue; xen-devel@lists.xen.org
> Subject: Re: [Xen-devel] test report for Xen 4.3 RC1
>
> On Tue, Jun 04, 2013 at 03:59:33PM +0000, Ren, Yongjie wrote:
> > Sorry for replying late. :-)
> >
> > > -----Original Message-----
> > > From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]
> > > Sent: Tuesday, May 28, 2013 11:16 PM
> > > To: Ren, Yongjie; george.dunlap@eu.citrix.com
> > > Cc: xen-devel@lists.xen.org; Xu, YongweiX; Liu, SongtaoX; Tian,
> Yongxue
> > > Subject: Re: [Xen-devel] test report for Xen 4.3 RC1
> > >
> > > On Mon, May 27, 2013 at 03:49:27AM +0000, Ren, Yongjie wrote:
> > > > Hi All,
> > > > This is a report based on our testing for Xen 4.3.0 RC1 on Intel
> platforms.
> > > > (Sorry it's a little late. :-) If the status changes, I'll have an update
> > > later.)
> > >
> > > OK, I've some updates and ideas that can help with narrowing some of
> > > these
> > > issues down. Thank you for doing this.
> > >
> > > >
> > > > Test environment:
> > > > Xen: Xen 4.3 RC1 with qemu-upstream-unstable.git
> > > > Dom0: Linux kernel 3.9.3
> > >
> > > Could you please test v3.10-rc3. There have been some changes
> > > for the VCPU hotplug added in v3.10 that I am not sure whether
> > > they are in v3.9?
> > I didn't try every bug with v3.10.-rc3, but most of them still exist.
> >
> > > > Hardware: Intel Sandy Bridge, Ivy Bridge, Haswell systems
> > > >
> > > > Below are the features we tested.
> > > > - PV and HVM guest booting (HVM: Ubuntu, Fedora, RHEL, Windows)
> > > > - Save/Restore and live migration
> > > > - PCI device assignment and SR-IOV
> > > > - power management: C-state/P-state, Dom0 S3, HVM S3
> > > > - AVX and XSAVE instruction set
> > > > - MCE
> > > > - CPU online/offline for Dom0
> > > > - vCPU hot-plug
> > > > - Nested Virtualization (Please look at my report in the following
> link.)
> > > >
> http://lists.xen.org/archives/html/xen-devel/2013-05/msg01145.html
> > > >
> > > > New bugs (4): (some of which are not regressions)
> > > > 1. sometimes failed to online cpu in Dom0
> > > >
> > >
> http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1851
> > >
> > > That looks like you are hitting the udev race.
> > >
> > > Could you verify that these patches:
> > > https://lkml.org/lkml/2013/5/13/520
> > >
> > > fix the issue (They are destined for v3.11)
> > >
> > Not tried yet. I'll update it to you later.
>
> Thanks!
> >
We tested kernel 3.9.3 with the 2 patches you mentioned, and found this
bug still exist. For example, we did CPU online-offline for Dom0 for 100 times,
and found 2 times (of 100 times) failed.
> > > > 2. dom0 call trace when running sriov hvm guest with igbvf
> > > >
> > >
> http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1852
> > > > -- a regression in Linux kernel (Dom0).
> > >
> > > Hm, the call-trace you refer too:
> > >
> > > [ 68.404440] Already setup the GSI :37
> > >
> > > [ 68.405105] igb 0000:04:00.0: Enabling SR-IOV VFs using the
> module
> > > parameter is deprecated - please use the pci sysfs interface.
> > >
> > > [ 68.506230] ------------[ cut here ]------------
> > >
> > > [ 68.506265] WARNING: at
> > >
> /home/www/builds_xen_unstable/xen-src-27009-20130509/linux-2.6-pvop
> > > s.git/fs/sysfs/dir.c:536 sysfs_add_one+0xcc/0xf0()
> > >
> > > [ 68.506279] Hardware name: S2600CP
> > >
> > > is a deprecated warning. Did you follow the 'pci sysfs' interface way?
> > >
> > > Looking at da36b64736cf2552e7fb5109c0255d4af804f5e7
> > > ixgbe: Implement PCI SR-IOV sysfs callback operation
> > > it says it is using this:
> > >
> > > commit 1789382a72a537447d65ea4131d8bcc1ad85ce7b
> > > Author: Donald Dutile <ddutile@redhat.com>
> > > Date: Mon Nov 5 15:20:36 2012 -0500
> > >
> > > PCI: SRIOV control and status via sysfs
> > >
> > > Provide files under sysfs to determine the maximum number of
> VFs
> > > an SR-IOV-capable PCIe device supports, and methods to enable
> and
> > > disable the VFs on a per-device basis.
> > >
> > > Currently, VF enablement by SR-IOV-capable PCIe devices is done
> > > via driver-specific module parameters. If not setup in modprobe
> > > files,
> > > it requires admin to unload & reload PF drivers with number of
> desired
> > > VFs to enable. Additionally, the enablement is system wide: all
> > > devices controlled by the same driver have the same number of
> VFs
> > > enabled. Although the latter is probably desired, there are PCI
> > > configurations setup by system BIOS that may not enable that to
> > > occur.
> > >
> > > Two files are created for the PF of PCIe devices with SR-IOV
> support:
> > >
> > > sriov_totalvfs Contains the maximum number of VFs the
> device
> > > could support as reported by the
> TotalVFs
> > > register
> > > in the SR-IOV extended capability.
> > >
> > > sriov_numvfs Contains the number of VFs currently
> enabled
> > > on
> > > this device as reported by the NumVFs
> > > register in
> > > the SR-IOV extended capability.
> > >
> > > Writing zero to this file disables all VFs.
> > >
> > > Writing a positive number to this file
> enables
> > > that
> > > number of VFs.
> > >
> > > These files are readable for all SR-IOV PF devices. Writes to the
> > > sriov_numvfs file are effective only if a driver that supports the
> > > sriov_configure() method is attached.
> > >
> > > Signed-off-by: Donald Dutile <ddutile@redhat.com>
> > >
> > >
> > > Can you try that please?
> > >
> > Recently, one of my workmates already had a fix as below.
> > https://lkml.org/lkml/2013/5/30/20
> > And, seems also already been fixed by another guy.
> > https://patchwork.kernel.org/patch/2613481/
> >
>
> Great! Care to update the bug with said relevant information?
Yes, updated in bugzilla.
> > >
> > > > 3. Booting multiple guests will lead Dom0 call trace
> > > >
> > >
> http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1853
> > >
> > > That one worries me. Did you do a git bisect to figure out what
> > > is commit is causing this?
> > >
> > I only found this bug on some Intel ~EX server.
> > I don't know which version on Xen/Dom0 can work fine.
> > If anyone want to reproduce or debug it, it should be good.
> > And our team is trying to debug it internally first.
>
> Ah, OK. Then please continue on debugging it. Thanks!
> >
> > > > 4. After live migration, guest console continuously prints
> "Clocksource
> > > tsc unstable"
> > > >
> > >
> http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1854
> > >
> > > This looks like a current bug with QEMU unstable missing a ACPI table?
> > >
> > > Did you try booting the guest with the old QEMU?
> > >
> > > device_model_version = 'qemu-xen-traditional'
> > >
> > This issue still exists with traditional qemu-xen.
> > After more testing, this bug can't reproduced by some other guests.
> > RHEL6.4 guest will have this issue after live migration, while RHEL6.3 &
> > Fedora 17 & Ubuntu 12.10 guests can work fine.
>
> There is a recent thread on this where the culprit was the PV timeclock
> not being updated correctly. But that would seem to be at odds with
> your reporting - where you are using Fedora 17 and it works fine.
>
> Hm, I am at loss on this one.
>
Hm, but my test result is as I described.
> >
> > > >
> > > > Old bugs: (11)
> > > > 1. [ACPI] Dom0 can't resume from S3 sleep
> > > > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1707
> > >
> > > That should be fixed in v3.11 (as now we have the fixes)
> > > Could you try v3.10 with the Rafael's ACPI tree merged in?
> > > (so the patches that he wants to submit for v3.11)
> > >
> > I re-tested with Rafel's linux-pm.git tree (master and acpi-hotplug
> branch),
> > and found Dom0 S3 sleep/resume can't work, either.
>
> The patches he has to submit for v3.11 are in the linux-next branch.
> You need to use that branch.
>
Dom0 S3 sleep/resume doesn't work with linux-next branch, either.
attached the log.
> >
> > > > 2. [XL]"xl vcpu-set" causes dom0 crash or panic
> > > > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1730
> > >
> > > That I think is fixed in v3.10. Could you please check v3.10-rc3?
> > >
> > Still exists on v3.10-rc3.
> > The following command lines can reproduce it:
> > # xl vcpu-set 0 1
> > # xl vcpu-set 0 20
>
> Ugh, same exact stack trace? And can you attach the full dmesg or serial
> output (so that Ican see what there is at bootup)
>
Yes, the same. Also attached in this mail.
> >
> > > > 3. Sometimes Xen panic on ia32pae Sandybridge when restore guest
> > > > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1747
> > >
> > > That looks to be with v2.6.32. Is the issue present with v3.9
> > > or v3.10-rc3?
> > >
> > We didn't test ia32pae Xen for a long time.
> > Now, we only cover ia32e Xen/Dom0.
> > So, this bug is only a legacy issue.
> > If we have effort to verify it, we'll update it in the bugzilla.
>
> How about just dropping that bug as 'WONTFIX'.
>
Agree. I'll close it as "WONTFIX".
> >
> > > > 4. 'xl vcpu-set' can't decrease the vCPU number of a HVM guest
> > > > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1822
> > >
> > > That I believe was an QEMU bug:
> > > http://lists.xen.org/archives/html/xen-devel/2013-05/msg01054.html
> > >
> > > which should be in QEMU traditional now (05-21 was when it went
> > > in the tree)
> > >
> > In this year or past year, this bug always exists (at least in our testing).
> > 'xl vcpu-set' can't decrease the vCPU number of a HVM guest
>
> Could you retry with Xen 4.3 please?
>
With Xen 4.3 & Linux:3.10.0-rc3, I can't decrease the vCPU number of a guest.
[-- Attachment #2: dom0-s3.log --]
[-- Type: application/octet-stream, Size: 690914 bytes --]
[-- Attachment #3: xl-vcpu-set-dom0-trace.log --]
[-- Type: application/octet-stream, Size: 129096 bytes --]
__ __ _ _ _____ _ _ _
\ \/ /___ _ __ | || | |___ / _ _ _ __ ___| |_ __ _| |__ | | ___
\ // _ \ '_ \ | || |_ |_ \ __| | | | '_ \/ __| __/ _` | '_ \| |/ _ \
/ \ __/ | | | |__ _| ___) |__| |_| | | | \__ \ || (_| | |_) | | __/
/_/\_\___|_| |_| |_|(_)____/ \__,_|_| |_|___/\__\__,_|_.__/|_|\___|
(XEN) Xen version 4.3-unstable (build@tsp.org) (gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-3)) debug=y Fri May 17 09:34:05 CST 2013
(XEN) Latest ChangeSet: Wed May 15 14:34:05 2013 +0200 hg:407dc3dde3cb-dirty
(XEN) Bootloader: GNU GRUB 0.97
(XEN) Command line: dom0_mem=4096M iommu=1 loglvl=all guest_loglvl=all unrestricted_guest=1 msi=1 console=com1,115200,8n1 conring_size=16M hap_1gb=1 3
(XEN) Video information:
(XEN) VGA is text mode 80x25, font 8x16
(XEN) VBE/DDC methods: none; EDID transfer time: 0 seconds
(XEN) EDID info not retrieved because no DDC retrieval method detected
(XEN) Disc information:
(XEN) Found 1 MBR signatures
(XEN) Found 1 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN) 0000000000000000 - 000000000009bc00 (usable)
(XEN) 000000000009bc00 - 00000000000a0000 (reserved)
(XEN) 00000000000e0000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 00000000ba804000 (usable)
(XEN) 00000000ba804000 - 00000000bad10000 (reserved)
(XEN) 00000000bad10000 - 00000000bb0a6000 (ACPI NVS)
(XEN) 00000000bb0a6000 - 00000000bd957000 (reserved)
(XEN) 00000000bd957000 - 00000000bdb5c000 (ACPI NVS)
(XEN) 00000000bdb5c000 - 00000000bdde7000 (reserved)
(XEN) 00000000bdde7000 - 00000000bde33000 (ACPI NVS)
(XEN) 00000000bde33000 - 00000000bdf08000 (ACPI data)
(XEN) 00000000bdf08000 - 00000000bdf0a000 (ACPI NVS)
(XEN) 00000000bdf0a000 - 00000000bdf28000 (ACPI data)
(XEN) 00000000bdf28000 - 00000000be000000 (ACPI NVS)
(XEN) 00000000be000000 - 00000000d0000000 (reserved)
(XEN) 00000000fec00000 - 00000000fec01000 (reserved)
(XEN) 00000000fed19000 - 00000000fed1a000 (reserved)
(XEN) 00000000fed1c000 - 00000000fed20000 (reserved)
(XEN) 00000000fee00000 - 00000000fee01000 (reserved)
(XEN) 00000000ffc00000 - 0000000100000000 (reserved)
(XEN) 0000000100000000 - 0000001040000000 (usable)
(XEN) ACPI: RSDP 000F0410, 0024 (r2 INTEL)
(XEN) ACPI: XSDT BDF25D98, 008C (r1 INTEL ROMLEY 6222004 INTL 20090903)
(XEN) ACPI: FACP BDF25A98, 00F4 (r4 INTEL ROMLEY 6222004 INTL 20090903)
(XEN) ACPI: DSDT BDF0A018, 19B86 (r2 INTEL ROMLEY 21 INTL 20100331)
(XEN) ACPI: FACS BDF25F40, 0040
(XEN) ACPI: APIC BDF24018, 0BAA (r3 INTEL ROMLEY 6222004 INTL 20090903)
(XEN) ACPI: SPMI BDF27F18, 0040 (r5 INTEL ROMLEY 6222004 INTL 20090903)
(XEN) ACPI: MCFG BDF27E98, 003C (r1 INTEL ROMLEY 6222004 INTL 20090903)
(XEN) ACPI: SRAT BDF07E18, 01A8 (r3 INTEL ROMLEY 6222004 INTL 20090903)
(XEN) ACPI: SLIT BDF27D98, 0030 (r1 INTEL ROMLEY 6222004 INTL 20090903)
(XEN) ACPI: MSCT BDF27D18, 004E (r1 INTEL ROMLEY 6222004 INTL 20090903)
(XEN) ACPI: HPET BDF27E18, 0038 (r1 INTEL ROMLEY 6222004 INTL 20090903)
(XEN) ACPI: SSDT BDF27C98, 002B (r2 INTEL PtidDevc 1000 INTL 20100331)
(XEN) ACPI: BOOT BDF27C18, 0028 (r1 INTEL ROMLEY 6222004 INTL 20090903)
(XEN) ACPI: SSDT BDE33018, D3050 (r2 INTEL CpuPm 4000 INTL 20100331)
(XEN) ACPI: DMAR BDF25918, 0120 (r1 INTEL ROMLEY 6222004 INTL 20090903)
(XEN) ACPI: BDAT BDF27B98, 0030 (r1 INTEL ROMLEY 6222004 INTL 20090903)
(XEN) System RAM: 65447MB (67018364kB)
(XEN) SRAT: PXM 0 -> APIC 2 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 4 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 6 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 8 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 16 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 18 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 20 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 22 -> Node 0
(XEN) SRAT: PXM 1 -> APIC 34 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 36 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 38 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 40 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 48 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 50 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 52 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 54 -> Node 1
(XEN) SRAT: Node 0 PXM 0 0-c0000000
(XEN) SRAT: Node 0 PXM 0 100000000-840000000
(XEN) SRAT: Node 1 PXM 1 840000000-1040000000
(XEN) NUMA: Allocated memnodemap from 103dd8f000 - 103dd90000
(XEN) NUMA: Using 18 for the hash shift.
(XEN) Domain heap initialised DMA width 32 bits
(XEN) found SMP MP-table at 000fca90
(XEN) DMI 2.6 present.
(XEN) x2APIC mode is already enabled by BIOS.
(XEN) Using APIC driver x2apic_cluster
(XEN) ACPI: PM-Timer IO Port: 0x408
(XEN) ACPI: SLEEP INFO: pm1x_cnt[404,0], pm1x_evt[400,0]
(XEN) ACPI: wakeup_vec[bdf25f4c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x02] enabled)
(XEN) Processor #2 7:14 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x04] enabled)
(XEN) Processor #4 7:14 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x06] enabled)
(XEN) Processor #6 7:14 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x08] enabled)
(XEN) Processor #8 7:14 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x10] enabled)
(XEN) Processor #16 7:14 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x12] enabled)
(XEN) Processor #18 7:14 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x14] enabled)
(XEN) Processor #20 7:14 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x16] enabled)
(XEN) Processor #22 7:14 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x22] enabled)
(XEN) Processor #34 7:14 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x09] lapic_id[0x24] enabled)
(XEN) Processor #36 7:14 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x26] enabled)
(XEN) Processor #38 7:14 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x28] enabled)
(XEN) Processor #40 7:14 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x30] enabled)
(XEN) Processor #48 7:14 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x32] enabled)
(XEN) Processor #50 7:14 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x34] enabled)
(XEN) Processor #52 7:14 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x36] enabled)
(XEN) Processor #54 7:14 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x10] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x11] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x12] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x13] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x14] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x15] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x16] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x17] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x18] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x19] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x1a] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x1b] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x1c] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x1d] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x1e] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x1f] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x20] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x21] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x22] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x23] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x24] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x25] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x26] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x27] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x28] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x29] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x2a] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x2b] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x2c] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x2d] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x2e] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x2f] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x30] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x31] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x32] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x33] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x34] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x35] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x36] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x37] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x38] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x39] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x3a] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x3b] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x3c] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x3d] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x3e] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x3f] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x40] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x41] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x42] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x43] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x44] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x45] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x46] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x47] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x48] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x49] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x4a] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x4b] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x4c] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x4d] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x4e] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x4f] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x50] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x51] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x52] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x53] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x54] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x55] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x56] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x57] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x58] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x59] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x5a] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x5b] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x5c] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x5d] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x5e] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x5f] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x60] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x61] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x62] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x63] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x64] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x65] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x66] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x67] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x68] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x69] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x6a] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x6b] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x6c] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x6d] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x6e] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x6f] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x70] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x71] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x72] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x73] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x74] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x75] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x76] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x77] lapic_id[0xff] disabled)
(XEN) ACPI: X2APIC (apic_id[0x00] uid[0x00] disabled)
(XEN) ACPI: X2APIC (apic_id[0x01] uid[0x01] disabled)
(XEN) ACPI: X2APIC (apic_id[0x02] uid[0x02] disabled)
(XEN) ACPI: X2APIC (apic_id[0x03] uid[0x03] disabled)
(XEN) ACPI: X2APIC (apic_id[0x04] uid[0x04] disabled)
(XEN) ACPI: X2APIC (apic_id[0x05] uid[0x05] disabled)
(XEN) ACPI: X2APIC (apic_id[0x06] uid[0x06] disabled)
(XEN) ACPI: X2APIC (apic_id[0x07] uid[0x07] disabled)
(XEN) ACPI: X2APIC (apic_id[0x08] uid[0x08] disabled)
(XEN) ACPI: X2APIC (apic_id[0x09] uid[0x09] disabled)
(XEN) ACPI: X2APIC (apic_id[0x0a] uid[0x0a] disabled)
(XEN) ACPI: X2APIC (apic_id[0x0b] uid[0x0b] disabled)
(XEN) ACPI: X2APIC (apic_id[0x0c] uid[0x0c] disabled)
(XEN) ACPI: X2APIC (apic_id[0x0d] uid[0x0d] disabled)
(XEN) ACPI: X2APIC (apic_id[0x0e] uid[0x0e] disabled)
(XEN) ACPI: X2APIC (apic_id[0x0f] uid[0x0f] disabled)
(XEN) ACPI: X2APIC (apic_id[0x10] uid[0x10] disabled)
(XEN) ACPI: X2APIC (apic_id[0x11] uid[0x11] disabled)
(XEN) ACPI: X2APIC (apic_id[0x12] uid[0x12] disabled)
(XEN) ACPI: X2APIC (apic_id[0x13] uid[0x13] disabled)
(XEN) ACPI: X2APIC (apic_id[0x14] uid[0x14] disabled)
(XEN) ACPI: X2APIC (apic_id[0x15] uid[0x15] disabled)
(XEN) ACPI: X2APIC (apic_id[0x16] uid[0x16] disabled)
(XEN) ACPI: X2APIC (apic_id[0x17] uid[0x17] disabled)
(XEN) ACPI: X2APIC (apic_id[0x18] uid[0x18] disabled)
(XEN) ACPI: X2APIC (apic_id[0x19] uid[0x19] disabled)
(XEN) ACPI: X2APIC (apic_id[0x1a] uid[0x1a] disabled)
(XEN) ACPI: X2APIC (apic_id[0x1b] uid[0x1b] disabled)
(XEN) ACPI: X2APIC (apic_id[0x1c] uid[0x1c] disabled)
(XEN) ACPI: X2APIC (apic_id[0x1d] uid[0x1d] disabled)
(XEN) ACPI: X2APIC (apic_id[0x1e] uid[0x1e] disabled)
(XEN) ACPI: X2APIC (apic_id[0x1f] uid[0x1f] disabled)
(XEN) ACPI: X2APIC (apic_id[0x20] uid[0x20] disabled)
(XEN) ACPI: X2APIC (apic_id[0x21] uid[0x21] disabled)
(XEN) ACPI: X2APIC (apic_id[0x22] uid[0x22] disabled)
(XEN) ACPI: X2APIC (apic_id[0x23] uid[0x23] disabled)
(XEN) ACPI: X2APIC (apic_id[0x24] uid[0x24] disabled)
(XEN) ACPI: X2APIC (apic_id[0x25] uid[0x25] disabled)
(XEN) ACPI: X2APIC (apic_id[0x26] uid[0x26] disabled)
(XEN) ACPI: X2APIC (apic_id[0x27] uid[0x27] disabled)
(XEN) ACPI: X2APIC (apic_id[0x28] uid[0x28] disabled)
(XEN) ACPI: X2APIC (apic_id[0x29] uid[0x29] disabled)
(XEN) ACPI: X2APIC (apic_id[0x2a] uid[0x2a] disabled)
(XEN) ACPI: X2APIC (apic_id[0x2b] uid[0x2b] disabled)
(XEN) ACPI: X2APIC (apic_id[0x2c] uid[0x2c] disabled)
(XEN) ACPI: X2APIC (apic_id[0x2d] uid[0x2d] disabled)
(XEN) ACPI: X2APIC (apic_id[0x2e] uid[0x2e] disabled)
(XEN) ACPI: X2APIC (apic_id[0x2f] uid[0x2f] disabled)
(XEN) ACPI: X2APIC (apic_id[0x30] uid[0x30] disabled)
(XEN) ACPI: X2APIC (apic_id[0x31] uid[0x31] disabled)
(XEN) ACPI: X2APIC (apic_id[0x32] uid[0x32] disabled)
(XEN) ACPI: X2APIC (apic_id[0x33] uid[0x33] disabled)
(XEN) ACPI: X2APIC (apic_id[0x34] uid[0x34] disabled)
(XEN) ACPI: X2APIC (apic_id[0x35] uid[0x35] disabled)
(XEN) ACPI: X2APIC (apic_id[0x36] uid[0x36] disabled)
(XEN) ACPI: X2APIC (apic_id[0x37] uid[0x37] disabled)
(XEN) ACPI: X2APIC (apic_id[0x38] uid[0x38] disabled)
(XEN) ACPI: X2APIC (apic_id[0x39] uid[0x39] disabled)
(XEN) ACPI: X2APIC (apic_id[0x3a] uid[0x3a] disabled)
(XEN) ACPI: X2APIC (apic_id[0x3b] uid[0x3b] disabled)
(XEN) ACPI: X2APIC (apic_id[0x3c] uid[0x3c] disabled)
(XEN) ACPI: X2APIC (apic_id[0x3d] uid[0x3d] disabled)
(XEN) ACPI: X2APIC (apic_id[0x3e] uid[0x3e] disabled)
(XEN) ACPI: X2APIC (apic_id[0x3f] uid[0x3f] disabled)
(XEN) ACPI: X2APIC (apic_id[0x40] uid[0x40] disabled)
(XEN) ACPI: X2APIC (apic_id[0x41] uid[0x41] disabled)
(XEN) ACPI: X2APIC (apic_id[0x42] uid[0x42] disabled)
(XEN) ACPI: X2APIC (apic_id[0x43] uid[0x43] disabled)
(XEN) ACPI: X2APIC (apic_id[0x44] uid[0x44] disabled)
(XEN) ACPI: X2APIC (apic_id[0x45] uid[0x45] disabled)
(XEN) ACPI: X2APIC (apic_id[0x46] uid[0x46] disabled)
(XEN) ACPI: X2APIC (apic_id[0x47] uid[0x47] disabled)
(XEN) ACPI: X2APIC (apic_id[0x48] uid[0x48] disabled)
(XEN) ACPI: X2APIC (apic_id[0x49] uid[0x49] disabled)
(XEN) ACPI: X2APIC (apic_id[0x4a] uid[0x4a] disabled)
(XEN) ACPI: X2APIC (apic_id[0x4b] uid[0x4b] disabled)
(XEN) ACPI: X2APIC (apic_id[0x4c] uid[0x4c] disabled)
(XEN) ACPI: X2APIC (apic_id[0x4d] uid[0x4d] disabled)
(XEN) ACPI: X2APIC (apic_id[0x4e] uid[0x4e] disabled)
(XEN) ACPI: X2APIC (apic_id[0x4f] uid[0x4f] disabled)
(XEN) ACPI: X2APIC (apic_id[0x50] uid[0x50] disabled)
(XEN) ACPI: X2APIC (apic_id[0x51] uid[0x51] disabled)
(XEN) ACPI: X2APIC (apic_id[0x52] uid[0x52] disabled)
(XEN) ACPI: X2APIC (apic_id[0x53] uid[0x53] disabled)
(XEN) ACPI: X2APIC (apic_id[0x54] uid[0x54] disabled)
(XEN) ACPI: X2APIC (apic_id[0x55] uid[0x55] disabled)
(XEN) ACPI: X2APIC (apic_id[0x56] uid[0x56] disabled)
(XEN) ACPI: X2APIC (apic_id[0x57] uid[0x57] disabled)
(XEN) ACPI: X2APIC (apic_id[0x58] uid[0x58] disabled)
(XEN) ACPI: X2APIC (apic_id[0x59] uid[0x59] disabled)
(XEN) ACPI: X2APIC (apic_id[0x5a] uid[0x5a] disabled)
(XEN) ACPI: X2APIC (apic_id[0x5b] uid[0x5b] disabled)
(XEN) ACPI: X2APIC (apic_id[0x5c] uid[0x5c] disabled)
(XEN) ACPI: X2APIC (apic_id[0x5d] uid[0x5d] disabled)
(XEN) ACPI: X2APIC (apic_id[0x5e] uid[0x5e] disabled)
(XEN) ACPI: X2APIC (apic_id[0x5f] uid[0x5f] disabled)
(XEN) ACPI: X2APIC (apic_id[0x60] uid[0x60] disabled)
(XEN) ACPI: X2APIC (apic_id[0x61] uid[0x61] disabled)
(XEN) ACPI: X2APIC (apic_id[0x62] uid[0x62] disabled)
(XEN) ACPI: X2APIC (apic_id[0x63] uid[0x63] disabled)
(XEN) ACPI: X2APIC (apic_id[0x64] uid[0x64] disabled)
(XEN) ACPI: X2APIC (apic_id[0x65] uid[0x65] disabled)
(XEN) ACPI: X2APIC (apic_id[0x66] uid[0x66] disabled)
(XEN) ACPI: X2APIC (apic_id[0x67] uid[0x67] disabled)
(XEN) ACPI: X2APIC (apic_id[0x68] uid[0x68] disabled)
(XEN) ACPI: X2APIC (apic_id[0x69] uid[0x69] disabled)
(XEN) ACPI: X2APIC (apic_id[0x6a] uid[0x6a] disabled)
(XEN) ACPI: X2APIC (apic_id[0x6b] uid[0x6b] disabled)
(XEN) ACPI: X2APIC (apic_id[0x6c] uid[0x6c] disabled)
(XEN) ACPI: X2APIC (apic_id[0x6d] uid[0x6d] disabled)
(XEN) ACPI: X2APIC (apic_id[0x6e] uid[0x6e] disabled)
(XEN) ACPI: X2APIC (apic_id[0x6f] uid[0x6f] disabled)
(XEN) ACPI: X2APIC (apic_id[0x70] uid[0x70] disabled)
(XEN) ACPI: X2APIC (apic_id[0x71] uid[0x71] disabled)
(XEN) ACPI: X2APIC (apic_id[0x72] uid[0x72] disabled)
(XEN) ACPI: X2APIC (apic_id[0x73] uid[0x73] disabled)
(XEN) ACPI: X2APIC (apic_id[0x74] uid[0x74] disabled)
(XEN) ACPI: X2APIC (apic_id[0x75] uid[0x75] disabled)
(XEN) ACPI: X2APIC (apic_id[0x76] uid[0x76] disabled)
(XEN) ACPI: X2APIC (apic_id[0x77] uid[0x77] disabled)
(XEN) ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1])
(XEN) ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: IOAPIC (id[0x01] address[0xfec3f000] gsi_base[24])
(XEN) IOAPIC[1]: apic_id 1, version 32, address 0xfec3f000, GSI 24-47
(XEN) ACPI: IOAPIC (id[0x02] address[0xfec7f000] gsi_base[48])
(XEN) IOAPIC[2]: apic_id 2, version 32, address 0xfec7f000, GSI 48-71
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) ACPI: HPET id: 0x8086a701 base: 0xfed00000
(XEN) ERST table was not found
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) SMP: Allowing 240 CPUs (224 hotplug CPUs)
(XEN) IRQ limits: 72 GSI, 3016 MSI/MSI-X
(XEN) Switched to APIC driver x2apic_cluster.
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 2793.355 MHz processor.
(XEN) Initing memory sharing.
(XEN) xstate_init: using cntxt_size: 0x340 and states: 0x7
(XEN) mce_intel.c:717: MCA Capability: BCAST 1 SER 1 CMCI 1 firstbank 0 extended MCE MSR 0
(XEN) Intel machine check reporting enabled
(XEN) PCI: MCFG configuration 0: base c0000000 segment 0000 buses 00 - ff
(XEN) PCI: MCFG area at c0000000 reserved in E820
(XEN) PCI: Using MCFG for segment 0000 bus 00-ff
(XEN) Intel VT-d iommu 0 supported page sizes: 4kB, 2MB, 1GB.
(XEN) Intel VT-d iommu 1 supported page sizes: 4kB, 2MB, 1GB.
(XEN) Intel VT-d Snoop Control enabled.
(XEN) Intel VT-d Dom0 DMA Passthrough not enabled.
(XEN) Intel VT-d Queued Invalidation enabled.
(XEN) Intel VT-d Interrupt Remapping enabled.
(XEN) Intel VT-d Shared EPT tables enabled.
(XEN) I/O virtualisation enabled
(XEN) - Dom0 mode: Relaxed
(XEN) Interrupt remapping enabled
(XEN) Enabled directed EOI with ioapic_ack_old on!
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using old ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) TSC deadline timer enabled
(XEN) Using standard rendezvous
(XEN) Platform timer is 14.318MHz HPET
(XEN) Allocated console ring of 16384 KiB.
(XEN) mwait-idle: MWAIT substates: 0x1120
(XEN) mwait-idle: v0.4 model 0x3e
(XEN) mwait-idle: lapic_timer_reliable_states 0xffffffff
(XEN) VMX: Supported advanced features:
(XEN) - APIC MMIO access virtualisation
(XEN) - APIC TPR shadow
(XEN) - Extended Page Tables (EPT)
(XEN) - Virtual-Processor Identifiers (VPID)
(XEN) - Virtual NMI
(XEN) - MSR direct-access bitmap
(XEN) - Unrestricted Guest
(XEN) - APIC Register Virtualization
(XEN) - Virtual Interrupt Delivery
(XEN) - Posted Interrupt Processing
(XEN) HVM: ASIDs enabled.
(XEN) HVM: VMX enabled
(XEN) HVM: Hardware Assisted Paging (HAP) detected
(XEN) HVM: HAP page sizes: 4kB, 2MB, 1GB
(XEN) Brought up 16 CPUs
(XEN) ACPI sleep modes: S3
(XEN) mcheck_poll: Machine check polling timer started.
(XEN) *** LOADING DOMAIN 0 ***
(XEN) elf_parse_binary: phdr: paddr=0x1000000 memsz=0xa33000
(XEN) elf_parse_binary: phdr: paddr=0x1c00000 memsz=0xa90f0
(XEN) elf_parse_binary: phdr: paddr=0x1caa000 memsz=0x14940
(XEN) elf_parse_binary: phdr: paddr=0x1cbf000 memsz=0x61c000
(XEN) elf_parse_binary: memory: 0x1000000 -> 0x22db000
(XEN) elf_xen_parse_note: GUEST_OS = "linux"
(XEN) elf_xen_parse_note: GUEST_VERSION = "2.6"
(XEN) elf_xen_parse_note: XEN_VERSION = "xen-3.0"
(XEN) elf_xen_parse_note: VIRT_BASE = 0xffffffff80000000
(XEN) elf_xen_parse_note: ENTRY = 0xffffffff81cbf1e0
(XEN) elf_xen_parse_note: HYPERCALL_PAGE = 0xffffffff81001000
(XEN) elf_xen_parse_note: FEATURES = "!writable_page_tables|pae_pgdir_above_4gb"
(XEN) elf_xen_parse_note: PAE_MODE = "yes"
(XEN) elf_xen_parse_note: LOADER = "generic"
(XEN) elf_xen_parse_note: unknown xen elf note (0xd)
(XEN) elf_xen_parse_note: SUSPEND_CANCEL = 0x1
(XEN) elf_xen_parse_note: HV_START_LOW = 0xffff800000000000
(XEN) elf_xen_parse_note: PADDR_OFFSET = 0x0
(XEN) elf_xen_addr_calc_check: addresses:
(XEN) virt_base = 0xffffffff80000000
(XEN) elf_paddr_offset = 0x0
(XEN) virt_offset = 0xffffffff80000000
(XEN) virt_kstart = 0xffffffff81000000
(XEN) virt_kend = 0xffffffff822db000
(XEN) virt_entry = 0xffffffff81cbf1e0
(XEN) p2m_base = 0xffffffffffffffff
(XEN) Xen kernel: 64-bit, lsb, compat32
(XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x22db000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 0000001010000000->0000001014000000 (1029139 pages to be allocated)
(XEN) Init. ramdisk: 000000103f413000->0000001040000000
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: ffffffff81000000->ffffffff822db000
(XEN) Init. ramdisk: ffffffff822db000->ffffffff82ec8000
(XEN) Phys-Mach map: ffffffff82ec8000->ffffffff836c8000
(XEN) Start info: ffffffff836c8000->ffffffff836c84b4
(XEN) Page tables: ffffffff836c9000->ffffffff836e8000
(XEN) Boot stack: ffffffff836e8000->ffffffff836e9000
(XEN) TOTAL: ffffffff80000000->ffffffff83800000
(XEN) ENTRY ADDRESS: ffffffff81cbf1e0
(XEN) Dom0 has maximum 16 VCPUs
(XEN) elf_load_binary: phdr 0 at 0xffffffff81000000 -> 0xffffffff81a33000
(XEN) elf_load_binary: phdr 1 at 0xffffffff81c00000 -> 0xffffffff81ca90f0
(XEN) elf_load_binary: phdr 2 at 0xffffffff81caa000 -> 0xffffffff81cbe940
(XEN) elf_load_binary: phdr 3 at 0xffffffff81cbf000 -> 0xffffffff81dc2000
(XEN) Scrubbing Free RAM: .......................................................................................................................................................................................................................................................................................................................*** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) .....................................*** Serial input -> Xen (type 'CTRL-a' three times to switch input to DOM0)
(XEN) ............................*** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) ..........................*** Serial input -> Xen (type 'CTRL-a' three times to switch input to DOM0)
(XEN) ............................*** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) ...............................*** Serial input -> Xen (type 'CTRL-a' three times to switch input to DOM0)
(XEN) .......................................*** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) ............................*** Serial input -> Xen (type 'CTRL-a' three times to switch input to DOM0)
(XEN) ..........................*** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) .................................................done.
(XEN) Initial low memory virq threshold set at 0x4000 pages.
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) *** Serial input -> Xen (type 'CTRL-a' three times to switch input to DOM0)
(XEN) Freed 272kB init memory.
mapping kernel into physical memory
about to get started...
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Initializing cgroup subsys cpuacct
[ 0.000000] Linux version 3.10.0-rc3 (root@vt-ivt1) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-3) (GCC) ) #1 SMP Wed Jun 5 10:06:25 CST 2013
[ 0.000000] Command line: ro root=UUID=6b431eba-2c2b-4621-a4e3-6f8a991f1b70 console=hvc0 pci=noaer max_loop=64 3 debug
[ 0.000000] Freeing 9b-100 pfn range: 101 pages freed
[ 0.000000] 1-1 mapping on 9b->100
[ 0.000000] Freeing ba804-100000 pfn range: 284668 pages freed
[ 0.000000] 1-1 mapping on ba804->100000
[ 0.000000] Released 284769 pages of unused memory
[ 0.000000] Set 284769 page(s) to 1-1 mapping
[ 0.000000] Populating 100000-145861 pfn range: 284769 pages added
[ 0.000000] e820: BIOS-provided physical RAM map:
[ 0.000000] Xen: [mem 0x0000000000000000-0x000000000009afff] usable
[ 0.000000] Xen: [mem 0x000000000009bc00-0x00000000000fffff] reserved
[ 0.000000] Xen: [mem 0x0000000000100000-0x00000000ba803fff] usable
[ 0.000000] Xen: [mem 0x00000000ba804000-0x00000000bad0ffff] reserved
[ 0.000000] Xen: [mem 0x00000000bad10000-0x00000000bb0a5fff] ACPI NVS
[ 0.000000] Xen: [mem 0x00000000bb0a6000-0x00000000bd956fff] reserved
[ 0.000000] Xen: [mem 0x00000000bd957000-0x00000000bdb5bfff] ACPI NVS
[ 0.000000] Xen: [mem 0x00000000bdb5c000-0x00000000bdde6fff] reserved
[ 0.000000] Xen: [mem 0x00000000bdde7000-0x00000000bde32fff] ACPI NVS
[ 0.000000] Xen: [mem 0x00000000bde33000-0x00000000bdf07fff] ACPI data
[ 0.000000] Xen: [mem 0x00000000bdf08000-0x00000000bdf09fff] ACPI NVS
[ 0.000000] Xen: [mem 0x00000000bdf0a000-0x00000000bdf27fff] ACPI data
[ 0.000000] Xen: [mem 0x00000000bdf28000-0x00000000bdffffff] ACPI NVS
[ 0.000000] Xen: [mem 0x00000000be000000-0x00000000cfffffff] reserved
[ 0.000000] Xen: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[ 0.000000] Xen: [mem 0x00000000fed19000-0x00000000fed19fff] reserved
[ 0.000000] Xen: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
[ 0.000000] Xen: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
[ 0.000000] Xen: [mem 0x00000000ffc00000-0x00000000ffffffff] reserved
[ 0.000000] Xen: [mem 0x0000000100000000-0x0000000dfcc2afff] usable
[ 0.000000] Xen: [mem 0x0000000dfcc2b000-0x000000103fffffff] unusable
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] SMBIOS 2.6 present.
[ 0.000000] DMI: Intel Corporation S2600CP/S2600CP, BIOS RMLSDP.86I.R2.21.D636.1301031557 01/03/2013
[ 0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
[ 0.000000] No AGP bridge found
[ 0.000000] e820: last_pfn = 0xdfcc2b max_arch_pfn = 0x400000000
[ 0.000000] e820: last_pfn = 0xba804 max_arch_pfn = 0x400000000
[ 0.000000] Scanning 1 areas for low memory corruption
[ 0.000000] Base memory trampoline at [ffff880000094000] 94000 size 28672
[ 0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
[ 0.000000] [mem 0x00000000-0x000fffff] page 4k
[ 0.000000] init_memory_mapping: [mem 0x145600000-0x1457fffff]
[ 0.000000] [mem 0x145600000-0x1457fffff] page 4k
[ 0.000000] BRK [0x01ed3000, 0x01ed3fff] PGTABLE
[ 0.000000] BRK [0x01ed4000, 0x01ed4fff] PGTABLE
[ 0.000000] init_memory_mapping: [mem 0x144000000-0x1455fffff]
[ 0.000000] [mem 0x144000000-0x1455fffff] page 4k
[ 0.000000] BRK [0x01ed5000, 0x01ed5fff] PGTABLE
[ 0.000000] BRK [0x01ed6000, 0x01ed6fff] PGTABLE
[ 0.000000] BRK [0x01ed7000, 0x01ed7fff] PGTABLE
[ 0.000000] init_memory_mapping: [mem 0x100000000-0x143ffffff]
[ 0.000000] [mem 0x100000000-0x143ffffff] page 4k
[ 0.000000] init_memory_mapping: [mem 0x00100000-0xba803fff]
[ 0.000000] [mem 0x00100000-0xba803fff] page 4k
[ 0.000000] init_memory_mapping: [mem 0x145800000-0xdfcc2afff]
[ 0.000000] [mem 0x145800000-0xdfcc2afff] page 4k
[ 0.000000] RAMDISK: [mem 0x022db000-0x02ec7fff]
[ 0.000000] ACPI: RSDP 00000000000f0410 00024 (v02 INTEL)
[ 0.000000] ACPI: XSDT 00000000bdf25d98 0008C (v01 INTEL ROMLEY 06222004 INTL 20090903)
[ 0.000000] ACPI: FACP 00000000bdf25a98 000F4 (v04 INTEL ROMLEY 06222004 INTL 20090903)
[ 0.000000] ACPI BIOS Bug: Warning: Invalid length for FADT/Pm1aControlBlock: 32, using default 16 (20130328/tbfadt-653)
[ 0.000000] ACPI: DSDT 00000000bdf0a018 19B86 (v02 INTEL ROMLEY 00000021 INTL 20100331)
[ 0.000000] ACPI: FACS 00000000bdf25f40 00040
[ 0.000000] ACPI: APIC 00000000bdf24018 00BAA (v03 INTEL ROMLEY 06222004 INTL 20090903)
[ 0.000000] ACPI: SPMI 00000000bdf27f18 00040 (v05 INTEL ROMLEY 06222004 INTL 20090903)
[ 0.000000] ACPI: MCFG 00000000bdf27e98 0003C (v01 INTEL ROMLEY 06222004 INTL 20090903)
[ 0.000000] ACPI: SRAT 00000000bdf07e18 001A8 (v03 INTEL ROMLEY 06222004 INTL 20090903)
[ 0.000000] ACPI: SLIT 00000000bdf27d98 00030 (v01 INTEL ROMLEY 06222004 INTL 20090903)
[ 0.000000] ACPI: MSCT 00000000bdf27d18 0004E (v01 INTEL ROMLEY 06222004 INTL 20090903)
[ 0.000000] ACPI: HPET 00000000bdf27e18 00038 (v01 INTEL ROMLEY 06222004 INTL 20090903)
[ 0.000000] ACPI: SSDT 00000000bdf27c98 0002B (v02 INTEL PtidDevc 00001000 INTL 20100331)
[ 0.000000] ACPI: BOOT 00000000bdf27c18 00028 (v01 INTEL ROMLEY 06222004 INTL 20090903)
[ 0.000000] ACPI: SSDT 00000000bde33018 D3050 (v02 INTEL CpuPm 00004000 INTL 20100331)
[ 0.000000] ACPI: XMAR 00000000bdf25918 00120 (v01 INTEL ROMLEY 06222004 INTL 20090903)
[ 0.000000] ACPI: BDAT 00000000bdf27b98 00030 (v01 INTEL ROMLEY 06222004 INTL 20090903)
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x00001000-0x00ffffff]
[ 0.000000] DMA32 [mem 0x01000000-0xffffffff]
[ 0.000000] Normal [mem 0x100000000-0xdfcc2afff]
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x00001000-0x0009afff]
[ 0.000000] node 0: [mem 0x00100000-0xba803fff]
[ 0.000000] node 0: [mem 0x100000000-0xdfcc2afff]
[ 0.000000] On node 0 totalpages: 14382025
[ 0.000000] DMA zone: 64 pages used for memmap
[ 0.000000] DMA zone: 22 pages reserved
[ 0.000000] DMA zone: 3994 pages, LIFO batch:0
[ 0.000000] DMA32 zone: 11873 pages used for memmap
[ 0.000000] DMA32 zone: 759812 pages, LIFO batch:31
[ 0.000000] Normal zone: 212785 pages used for memmap
[ 0.000000] Normal zone: 13618219 pages, LIFO batch:31
[ 0.000000] ACPI: PM-Timer IO Port: 0x408
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: X2APIC (apic_id[0x00] uid[0x00] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x01] uid[0x01] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x02] uid[0x02] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x03] uid[0x03] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x04] uid[0x04] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x05] uid[0x05] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x06] uid[0x06] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x07] uid[0x07] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x08] uid[0x08] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x09] uid[0x09] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x0a] uid[0x0a] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x0b] uid[0x0b] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x0c] uid[0x0c] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x0d] uid[0x0d] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x0e] uid[0x0e] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x0f] uid[0x0f] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x10] uid[0x10] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x11] uid[0x11] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x12] uid[0x12] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x13] uid[0x13] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x14] uid[0x14] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x15] uid[0x15] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x16] uid[0x16] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x17] uid[0x17] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x18] uid[0x18] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x19] uid[0x19] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x1a] uid[0x1a] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x1b] uid[0x1b] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x1c] uid[0x1c] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x1d] uid[0x1d] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x1e] uid[0x1e] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x1f] uid[0x1f] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x20] uid[0x20] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x21] uid[0x21] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x22] uid[0x22] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x23] uid[0x23] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x24] uid[0x24] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x25] uid[0x25] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x26] uid[0x26] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x27] uid[0x27] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x28] uid[0x28] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x29] uid[0x29] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x2a] uid[0x2a] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x2b] uid[0x2b] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x2c] uid[0x2c] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x2d] uid[0x2d] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x2e] uid[0x2e] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x2f] uid[0x2f] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x30] uid[0x30] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x31] uid[0x31] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x32] uid[0x32] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x33] uid[0x33] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x34] uid[0x34] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x35] uid[0x35] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x36] uid[0x36] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x37] uid[0x37] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x38] uid[0x38] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x39] uid[0x39] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x3a] uid[0x3a] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x3b] uid[0x3b] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x3c] uid[0x3c] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x3d] uid[0x3d] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x3e] uid[0x3e] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x3f] uid[0x3f] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x40] uid[0x40] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x41] uid[0x41] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x42] uid[0x42] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x43] uid[0x43] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x44] uid[0x44] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x45] uid[0x45] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x46] uid[0x46] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x47] uid[0x47] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x48] uid[0x48] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x49] uid[0x49] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x4a] uid[0x4a] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x4b] uid[0x4b] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x4c] uid[0x4c] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x4d] uid[0x4d] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x4e] uid[0x4e] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x4f] uid[0x4f] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x50] uid[0x50] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x51] uid[0x51] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x52] uid[0x52] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x53] uid[0x53] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x54] uid[0x54] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x55] uid[0x55] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x56] uid[0x56] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x57] uid[0x57] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x58] uid[0x58] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x59] uid[0x59] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x5a] uid[0x5a] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x5b] uid[0x5b] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x5c] uid[0x5c] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x5d] uid[0x5d] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x5e] uid[0x5e] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x5f] uid[0x5f] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x60] uid[0x60] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x61] uid[0x61] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x62] uid[0x62] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x63] uid[0x63] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x64] uid[0x64] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x65] uid[0x65] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x66] uid[0x66] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x67] uid[0x67] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x68] uid[0x68] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x69] uid[0x69] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x6a] uid[0x6a] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x6b] uid[0x6b] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x6c] uid[0x6c] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x6d] uid[0x6d] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x6e] uid[0x6e] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x6f] uid[0x6f] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x70] uid[0x70] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x71] uid[0x71] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x72] uid[0x72] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x73] uid[0x73] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x74] uid[0x74] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x75] uid[0x75] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x76] uid[0x76] disabled)
[ 0.000000] ACPI: X2APIC (apic_id[0x77] uid[0x77] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x02] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x04] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x06] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x08] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x10] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x12] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x14] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x16] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x22] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x24] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x26] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x28] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x30] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x32] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x34] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x36] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0xff] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0xff] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0xff] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0xff] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x14] lapic_id[0xff] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x15] lapic_id[0xff] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x16] lapic_id[0xff] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x17] lapic_id[0xff] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0xff] disab[ 31.555862] ACPI: Interpreter enabled
[ 31.555899] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20130328/hwxface-568)
[ 31.555958] ACPI: (supports S0 S1 S3 S5)
[ 31.555969] ACPI: Using IOAPIC for interrupt routing
[ 31.556369] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[ 31.660171] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
[ 31.661344] PCI host bridge to bus 0000:00
[ 31.661361] pci_bus 0000:00: root bus resource [bus 00-7e]
[ 31.661372] pci_bus 0000:00: root bus resource [io 0x0000-0xbfff]
[ 31.661383] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
[ 31.661401] pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000c3fff]
[ 31.661411] pci_bus 0000:00: root bus resource [mem 0x000c4000-0x000c7fff]
[ 31.661421] pci_bus 0000:00: root bus resource [mem 0x000c8000-0x000cbfff]
[ 31.661432] pci_bus 0000:00: root bus resource [mem 0x000cc000-0x000cffff]
[ 31.661442] pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000d3fff]
[ 31.661452] pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff]
[ 31.661462] pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff]
[ 31.661473] pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff]
[ 31.661483] pci_bus 0000:00: root bus resource [mem 0x000e0000-0x000e3fff]
[ 31.661493] pci_bus 0000:00: root bus resource [mem 0x000e4000-0x000e7fff]
[ 31.661503] pci_bus 0000:00: root bus resource [mem 0x000e8000-0x000ebfff]
[ 31.661514] pci_bus 0000:00: root bus resource [mem 0x000ec000-0x000effff]
[ 31.661524] pci_bus 0000:00: root bus resource [mem 0x000f0000-0x000fffff]
[ 31.661534] pci_bus 0000:00: root bus resource [mem 0xd0000000-0xebffffff]
[ 31.661545] pci_bus 0000:00: root bus resource [mem 0x380000000000-0x38007fffffff]
[ 31.661605] pci 0000:00:00.0: [8086:0e00] type 00 class 0x060000
[ 31.661892] pci 0000:00:00.0: PME# supported from D0 D3hot D3cold
(XEN) PCI add device 0000:00:00.0
[ 31.662585] pci 0000:00:01.0: [8086:0e02] type 01 class 0x060400
[ 31.662878] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
[ 31.663159] pci 0000:00:01.0: System wakeup disabled by ACPI
(XEN) PCI add device 0000:00:01.0
[ 31.663448] pci 0000:00:01.1: [8086:0e03] type 01 class 0x060400
[ 31.663763] pci 0000:00:01.1: PME# supported from D0 D3hot D3cold
[ 31.664034] pci 0000:00:01.1: System wakeup disabled by ACPI
(XEN) PCI add device 0000:00:01.1
[ 31.664389] pci 0000:00:02.0: [8086:0e04] type 01 class 0x060400
[ 31.664668] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
[ 31.664927] pci 0000:00:02.0: System wakeup disabled by ACPI
(XEN) PCI add device 0000:00:02.0
[ 31.665285] pci 0000:00:02.2: [8086:0e06] type 01 class 0x060400
[ 31.665594] pci 0000:00:02.2: PME# supported from D0 D3hot D3cold
[ 31.665851] pci 0000:00:02.2: System wakeup disabled by ACPI
(XEN) PCI add device 0000:00:02.2
[ 31.666218] pci 0000:00:03.0: [8086:0e08] type 01 class 0x060400
[ 31.666567] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
[ 31.666853] pci 0000:00:03.0: System wakeup disabled by ACPI
(XEN) PCI add device 0000:00:03.0
[ 31.667143] pci 0000:00:03.2: [8086:0e0a] type 01 class 0x060400
[ 31.667489] pci 0000:00:03.2: PME# supported from D0 D3hot D3cold
[ 31.667755] pci 0000:00:03.2: System wakeup disabled by ACPI
(XEN) PCI add device 0000:00:03.2
[ 31.668045] pci 0000:00:04.0: [8086:0e20] type 00 class 0x088000
[ 31.668118] pci 0000:00:04.0: reg 10: [mem 0xebf90000-0xebf93fff 64bit]
(XEN) PCI add device 0000:00:04.0
[ 31.669028] pci 0000:00:04.1: [8086:0e21] type 00 class 0x088000
[ 31.669097] pci 0000:00:04.1: reg 10: [mem 0xebf80000-0xebf83fff 64bit]
(XEN) PCI add device 0000:00:04.1
[ 31.670091] pci 0000:00:04.2: [8086:0e22] type 00 class 0x088000
[ 31.670162] pci 0000:00:04.2: reg 10: [mem 0xebf70000-0xebf73fff 64bit]
(XEN) PCI add device 0000:00:04.2
[ 31.671034] pci 0000:00:04.3: [8086:0e23] type 00 class 0x088000
[ 31.671071] pci 0000:00:04.3: reg 10: [mem 0xebf60000-0xebf63fff 64bit]
(XEN) PCI add device 0000:00:04.3
[ 31.672016] pci 0000:00:04.4: [8086:0e24] type 00 class 0x088000
[ 31.672087] pci 0000:00:04.4: reg 10: [mem 0xebf50000-0xebf53fff 64bit]
(XEN) PCI add device 0000:00:04.4
[ 31.672921] pci 0000:00:04.5: [8086:0e25] type 00 class 0x088000
[ 31.673001] pci 0000:00:04.5: reg 10: [mem 0xebf40000-0xebf43fff 64bit]
(XEN) PCI add device 0000:00:04.5
[ 31.673894] pci 0000:00:04.6: [8086:0e26] type 00 class 0x088000
[ 31.673949] pci 0000:00:04.6: reg 10: [mem 0xebf30000-0xebf33fff 64bit]
(XEN) PCI add device 0000:00:04.6
[ 31.674838] pci 0000:00:04.7: [8086:0e27] type 00 class 0x088000
[ 31.674914] pci 0000:00:04.7: reg 10: [mem 0xebf20000-0xebf23fff 64bit]
(XEN) PCI add device 0000:00:04.7
[ 31.675746] pci 0000:00:05.0: [8086:0e28] type 00 class 0x088000
(XEN) PCI add device 0000:00:05.0
[ 31.676618] pci 0000:00:05.1: [8086:0e29] type 00 class 0x088000
(XEN) PCI add device 0000:00:05.1
[ 31.677556] pci 0000:00:05.2: [8086:0e2a] type 00 class 0x088000
(XEN) PCI add device 0000:00:05.2
[ 31.678440] pci 0000:00:05.4: [8086:0e2c] type 00 class 0x080020
[ 31.678487] pci 0000:00:05.4: reg 10: [mem 0xd1260000-0xd1260fff]
(XEN) PCI add device 0000:00:05.4
[ 31.679338] pci 0000:00:05.6: [8086:0e39] type 00 class 0x110100
(XEN) PCI add device 0000:00:05.6
[ 31.680186] pci 0000:00:06.0: [8086:0e10] type 00 class 0x088000
(XEN) PCI add device 0000:00:06.0
[ 31.681026] pci 0000:00:06.1: [8086:0e11] type 00 class 0x088000
(XEN) PCI add device 0000:00:06.1
[ 31.681981] pci 0000:00:06.2: [8086:0e12] type 00 class 0x088000
(XEN) PCI add device 0000:00:06.2
[ 31.682875] pci 0000:00:06.3: [8086:0e13] type 00 class 0x088000
(XEN) PCI add device 0000:00:06.3
[ 31.683708] pci 0000:00:06.4: [8086:0e14] type 00 class 0x088000
(XEN) PCI add device 0000:00:06.4
[ 31.684554] pci 0000:00:06.5: [8086:0e15] type 00 class 0x088000
(XEN) PCI add device 0000:00:06.5
[ 31.685388] pci 0000:00:06.6: [8086:0e16] type 00 class 0x088000
(XEN) PCI add device 0000:00:06.6
[ 31.686272] pci 0000:00:06.7: [8086:0e17] type 00 class 0x088000
(XEN) PCI add device 0000:00:06.7
[ 31.687138] pci 0000:00:07.0: [8086:0e18] type 00 class 0x088000
(XEN) PCI add device 0000:00:07.0
[ 31.688025] pci 0000:00:07.1: [8086:0e19] type 00 class 0x088000
(XEN) PCI add device 0000:00:07.1
[ 31.688842] pci 0000:00:07.2: [8086:0e1a] type 00 class 0x088000
(XEN) PCI add device 0000:00:07.2
[ 31.689707] pci 0000:00:07.3: [8086:0e1b] type 00 class 0x088000
(XEN) PCI add device 0000:00:07.3
[ 31.690613] pci 0000:00:07.4: [8086:0e1c] type 00 class 0x088000
(XEN) PCI add device 0000:00:07.4
[ 31.691598] pci 0000:00:1a.0: [8086:1d2d] type 00 class 0x0c0320
[ 31.691671] pci 0000:00:1a.0: reg 10: [mem 0xd1220000-0xd12203ff]
[ 31.692048] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
[ 31.692453] pci 0000:00:1a.0: System wakeup disabled by ACPI
(XEN) PCI add device 0000:00:1a.0
[ 31.692725] pci 0000:00:1c.0: [8086:1d10] type 01 class 0x060400
[ 31.693065] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
[ 31.693287] pci 0000:00:1c.0: System wakeup disabled by ACPI
(XEN) PCI add device 0000:00:1c.0
[ 31.693617] pci 0000:00:1c.7: [8086:1d1e] type 01 class 0x060400
[ 31.693947] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
[ 31.694189] pci 0000:00:1c.7: System wakeup disabled by ACPI
(XEN) PCI add device 0000:00:1c.7
[ 31.694503] pci 0000:00:1d.0: [8086:1d26] type 00 class 0x0c0320
[ 31.694585] pci 0000:00:1d.0: reg 10: [mem 0xd1210000-0xd12103ff]
[ 31.694945] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
[ 31.695309] pci 0000:00:1d.0: System wakeup disabled by ACPI
(XEN) PCI add device 0000:00:1d.0
[ 31.695606] pci 0000:00:1e.0: [8086:244e] type 01 class 0x060401
[ 31.695882] pci 0000:00:1e.0: System wakeup disabled by ACPI
(XEN) PCI add device 0000:00:1e.0
[ 31.696106] pci 0000:00:1f.0: [8086:1d41] type 00 class 0x060100
(XEN) PCI add device 0000:00:1f.0
[ 31.696825] pci 0000:00:1f.2: [8086:1d02] type 00 class 0x010601
[ 31.696916] pci 0000:00:1f.2: reg 10: [io 0x6070-0x6077]
[ 31.696954] pci 0000:00:1f.2: reg 14: [io 0x6060-0x6063]
[ 31.696996] pci 0000:00:1f.2: reg 18: [io 0x6050-0x6057]
[ 31.697038] pci 0000:00:1f.2: reg 1c: [io 0x6040-0x6043]
[ 31.697061] pci 0000:00:1f.2: reg 20: [io 0x6020-0x603f]
[ 31.697109] pci 0000:00:1f.2: reg 24: [mem 0xd1200000-0xd12007ff]
[ 31.697330] pci 0000:00:1f.2: PME# supported from D3hot
(XEN) PCI add device 0000:00:1f.2
[ 31.697954] pci 0000:00:1f.3: [8086:1d22] type 00 class 0x0c0500
[ 31.698025] pci 0000:00:1f.3: reg 10: [mem 0xebf10000-0xebf100ff 64bit]
[ 31.698118] pci 0000:00:1f.3: reg 20: [io 0x6000-0x601f]
(XEN) PCI add device 0000:00:1f.3
[ 31.698833] pci 0000:00:1f.6: [8086:1d24] type 00 class 0x118000
[ 31.698920] pci 0000:00:1f.6: reg 10: [mem 0xebf00000-0xebf00fff 64bit]
(XEN) PCI add device 0000:00:1f.6
[ 31.700139] pci 0000:01:00.0: [8086:1d74] type 01 class 0x060400
[ 31.700212] pci 0000:01:00.0: reg 10: [mem 0xd1000000-0xd1003fff]
[ 31.700544] pci 0000:01:00.0: PME# supported from D0 D3hot D3cold
(XEN) PCI add device 0000:01:00.0
[ 31.703401] pci 0000:00:01.0: PCI bridge to [bus 01-03]
[ 31.703421] pci 0000:00:01.0: bridge window [io 0x5000-0x5fff]
[ 31.703440] pci 0000:00:01.0: bridge window [mem 0xd0f00000-0xd10fffff]
[ 31.703471] pci 0000:00:01.0: bridge window [mem 0xeb000000-0xeb9fffff 64bit pref]
[ 31.704034] pci 0000:02:08.0: [8086:1d3f] type 01 class 0x060400
[ 31.704491] pci 0000:02:08.0: PME# supported from D0 D3hot D3cold
(XEN) PCI add device 0000:02:08.0
[ 31.704950] pci 0000:01:00.0: PCI bridge to [bus 02-03]
[ 31.704990] pci 0000:01:00[ 32.550852] VFS: Disk quotas dquot_6.5.2
[ 32.551294] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 32.553564] msgmni has been set to 5830
[ 32.554150] SELinux: Registering netfilter hooks
[ 32.558014] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
[ 32.558041] io scheduler noop registered
[ 32.558061] io scheduler deadline registered
[ 32.558430] io scheduler cfq registered (default)
[ 32.565941] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 32.570261] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0
[ 32.570295] ACPI: Power Button [PWRF]
[ 32.574457] ACPI: Requesting acpi_cpufreq
[ 32.605691] Monitor-Mwait will be used to enter C-1 state
[ 32.605718] Monitor-Mwait will be used to enter C-2 state
[ 33.050327] Warning: Processor Platform Limit not supported.
[ 33.052828] Event-channel device installed.
[ 33.053887] xen-pciback: backend is vpci
[ 33.056974] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 33.078338] 00:08: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
[ 33.081175] hpet_acpi_add: no address or irqs in _CRS
[ 33.081827] Non-volatile memory driver v1.3
[ 33.081834] Linux agpgart interface v0.103
[ 33.083843] [drm] Initialized drm 1.1.0 20060810
[ 33.120060] loop: module loaded
[ 33.120316] tun: Universal TUN/TAP device driver, 1.6
[ 33.120322] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[ 33.121067] e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
[ 33.121073] e100: Copyright(c) 1999-2006 Intel Corporation
[ 33.121612] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
[ 33.121619] e1000: Copyright (c) 1999-2006 Intel Corporation.
[ 33.122101] sky2: driver version 1.30
[ 33.123066] Initialising Xen virtual ethernet driver.
[ 33.128305] usbcore: registered new interface driver usblp
[ 33.129275] i8042: PNP: No PS/2 controller found. Probing ports directly.
[ 33.648852] i8042: Can't read CTR while initializing i8042
[ 33.648874] i8042: probe of i8042 failed with error -5
[ 33.650129] mousedev: PS/2 mouse device common for all mice
[ 33.651106] rtc_cmos 00:05: RTC can wake from S4
[ 33.651443] rtc_cmos 00:05: rtc core: registered rtc_cmos as rtc0
[ 33.651537] rtc_cmos 00:05: alarms up to one month, y3k, 242 bytes nvram
[ 33.651993] xen: registering gsi 18 triggering 0 polarity 1
[ 33.652015] xen: --> pirq=18 -> irq=18 (gsi=18)
[ 33.652079] ACPI Warning: 0x0000000000006000-0x000000000000601f SystemIO conflicts with Region \_SB_.PCI0.SBUS.SMBI 1 (20130328/utaddress-251)
[ 33.652091] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 33.652154] xen: registering gsi 29 triggering 0 polarity 1
[ 33.652167] xen: --> pirq=29 -> irq=29 (gsi=29)
[ 33.652306] i801_smbus 0000:03:00.3: SMBus using PCI Interrupt
[ 33.652553] xen: registering gsi 29 triggering 0 polarity 1
[ 33.652560] Already setup the GSI :29
[ 33.652580] i801_smbus 0000:03:00.4: SMBus using PCI Interrupt
[ 33.653010] xen_wdt: Xen WatchDog Timer Driver v0.01
[ 33.653708] xen_wdt: initialized (timeout=60s, nowayout=0)
[ 33.654391] device-mapper: ioctl: 4.24.0-ioctl (2013-01-15) initialised: dm-devel@redhat.com
[ 33.654717] hidraw: raw HID events driver (C) Jiri Kosina
[ 33.658199] usbcore: registered new interface driver usbhid
[ 33.658220] usbhid: USB HID core driver
[ 33.664728] Netfilter messages via NETLINK v0.30.
[ 33.664753] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[ 33.665043] ctnetlink v0.93: registering with nfnetlink.
[ 33.665157] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 33.665221] TCP: cubic registered
[ 33.665229] Initializing XFRM netlink socket
[ 33.665996] NET: Registered protocol family 10
[ 33.666257] ip6_tables: (C) 2000-2006 Netfilter Core Team
[ 33.666323] sit: IPv6 over IPv4 tunneling driver
[ 33.666933] NET: Registered protocol family 17
[ 33.666957] Key type dns_resolver registered
[ 33.670774] registered taskstats version 1
[ 33.673662] Magic number: 1:200:156
[ 33.673746] acpi device:23: hash matches
[ 33.673759] acpi PNP0A08:00: hash matches
[ 33.673859] console [netcon0] enabled
[ 33.673863] netconsole: network logging started
[ 33.674015] rtc_cmos 00:05: setting system clock to 2013-06-05 02:11:24 UTC (1370398284)
[ 33.674836] ALSA device list:
[ 33.674841] No soundcards found.
[ 33.675539] Freeing unused kernel memory: 1096k freed
[ 33.675815] Write protecting the kernel read-only data: 12288k
[ 33.681503] Freeing unused kernel memory: 1140k freed
[ 33.682598] Freeing unused kernel memory: 1844k freed
[ 33.773463] dracut: dracut-004-303.el6
Running in PV context on Xen v4.3.
[ 33.822414] udev: starting version 147
[ 33.822658] udevd (1473): /proc/1473/oom_adj is deprecated, please use /proc/1473/oom_score_adj instead.
[ 34.096791] dracut: Starting plymouth daemon
G[ 34.701636] SCSI subsystem initialized
[ 34.704064] ACPI: bus type ATA registered
[ 34.705102] libata version 3.00 loaded.
[ 34.706746] ahci 0000:00:1f.2: version 3.0
[ 34.707414] xen: registering gsi 19 triggering 0 polarity 1
[ 34.707436] Already setup the GSI :19
[ 34.707752] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x3 impl SATA mode
[ 34.707768] ahci 0000:00:1f.2: flags: 64bit ncq sntf pm led clo pio slum part ems apst
[ 34.707791] ahci 0000:00:1f.2: setting latency timer to 64
[ 34.714821] scsi0 : ahci
[ 34.715509] scsi1 : ahci
[ 34.716135] scsi2 : ahci
[ 34.716774] scsi3 : ahci
[ 34.717369] scsi4 : ahci
[ 34.717940] scsi5 : ahci
[ 34.718400] ata1: SATA max UDMA/133 abar m2048@0xd1200000 port 0xd1200100 irq 203
[ 34.718414] ata2: SATA max UDMA/133 abar m2048@0xd1200000 port 0xd1200180 irq 203
[ 34.718424] ata3: DUMMY
[ 34.718431] ata4: DUMMY
[ 34.718438] ata5: DUMMY
[ 34.718444] ata6: DUMMY
[ 35.023305] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 35.023371] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 35.025524] ata2.00: ATA-8: WDC WD1002FAEX-00Z3A0, 05.01D05, max UDMA/133
[ 35.025531] ata2.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[ 35.026773] ata1.00: ATAPI: ATAPI iHAS124 C, LL08, max UDMA/100
[ 35.027631] ata1.00: configured for UDMA/100
[ 35.027799] ata2.00: configured for UDMA/133
[ 35.030063] scsi 0:0:0:0: CD-ROM ATAPI iHAS124 C LL08 PQ: 0 ANSI: 5
[ 35.031838] scsi 1:0:0:0: Direct-Access ATA WDC WD1002FAEX-0 05.0 PQ: 0 ANSI: 5
[ 36.095010] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
[ 36.095028] cdrom: Uniform CD-ROM driver Revision: 3.20
[ 36.095836] sr 0:0:0:0: Attached scsi CD-ROM sr0
[ 36.104280] sd 1:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[ 36.104841] sd 1:0:0:0: [sda] Write Protect is off
[ 36.104859] sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 36.105042] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 36.136276] sda: sda1 sda2
[ 36.138126] sd 1:0:0:0: [sda] Attached SCSI disk
[ 36.469093] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[ 36.554086] dracut: Mounted root filesystem /dev/sda1
[ 36.883062] SELinux: Disabled at runtime.
[ 36.883354] SELinux: Unregistering netfilter hooks
[ 36.914283] type=1404 audit(1370398287.740:2): selinux=0 auid=4294967295 ses=4294967295
[ 36.915430] dracut:
[ 37.045263] dracut: Switching root
[ 38.149058] readahead: starting
Welcome to Red Hat Enterprise Linux Server
Starting udev: [ 39.339728] udev: starting version 147
[ 39.988701] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version 3.13.10-k
[ 39.988724] ixgbe: Copyright (c) 1999-2013 Intel Corporation.
[ 39.988919] xen: registering gsi 32 triggering 0 polarity 1
[ 39.988953] xen: --> pirq=32 -> irq=32 (gsi=32)
[ 40.114553] ixgbe 0000:05:00.0: Enabling SR-IOV VFs using the module parameter is deprecated - please use the pci sysfs interface.
[ 40.216324] pci 0000:05:10.0: [8086:10ed] type 00 class 0x020000
(XEN) PCI add extended function 0000:05:10.0
[ 40.217481] pci 0000:05:10.2: [8086:10ed] type 00 class 0x020000
(XEN) PCI add extended function 0000:05:10.2
[ 40.218477] pci 0000:05:10.4: [8086:10ed] type 00 class 0x020000
(XEN) PCI add extended function 0000:05:10.4
[ 40.219453] pci 0000:05:10.6: [8086:10ed] type 00 class 0x020000
(XEN) PCI add extended function 0000:05:10.6
[ 40.220231] ixgbe 0000:05:00.0 (unregistered net_device): SR-IOV enabled with 4 VFs
[ 40.244761] ixgbe 0000:05:00.0: Multiqueue Disabled: Rx Queue count = 1, Tx Queue count = 1
[ 40.244925] ixgbe 0000:05:00.0: (PCI Express:5.0GT/s:Width x8) 00:1b:21:3c:ab:70
[ 40.245034] ixgbe 0000:05:00.0: MAC: 2, PHY: 15, SFP+: 5, PBA No: E66562-003
[ 40.251090] ixgbe 0000:05:00.0 eth0: IOV is enabled with 4 VFs
[ 40.251171] ixgbe 0000:05:00.0: Intel(R) 10 Gigabit Network Connection
[ 40.251876] xen: registering gsi 36 triggering 0 polarity 1
[ 40.251940] xen: --> pirq=36 -> irq=36 (gsi=36)
[ 40.378525] ixgbe 0000:05:00.1: Enabling SR-IOV VFs using the module parameter is deprecated - please use the pci sysfs interface.
[ 40.480384] pci 0000:05:10.1: [8086:10ed] type 00 class 0x020000
(XEN) PCI add extended function 0000:05:10.1
[ 40.482265] pci 0000:05:10.3: [8086:10ed] type 00 class 0x020000
(XEN) PCI add extended function 0000:05:10.3
[ 40.483899] pci 0000:05:10.5: [8086:10ed] type 00 class 0x020000
(XEN) PCI add extended function 0000:05:10.5
[ 40.485671] pci 0000:05:10.7: [8086:10ed] type 00 class 0x020000
(XEN) PCI add extended function 0000:05:10.7
[ 40.487380] ixgbe 0000:05:00.1 (unregistered net_device): SR-IOV enabled with 4 VFs
[ 40.511593] ixgbe 0000:05:00.1: Multiqueue Disabled: Rx Queue count = 1, Tx Queue count = 1
[ 40.511741] ixgbe 0000:05:00.1: (PCI Express:5.0GT/s:Width x8) 00:1b:21:3c:ab:71
[ 40.511847] ixgbe 0000:05:00.1: MAC: 2, PHY: 15, SFP+: 6, PBA No: E66562-003
[ 40.517547] ixgbe 0000:05:00.1 eth1: IOV is enabled with 4 VFs
[ 40.517600] ixgbe 0000:05:00.1: Intel(R) 10 Gigabit Network Connection
G[ 42.177001] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 42.177040] ehci_hcd: block sizes: qh 112 qtd 96 itd 192 sitd 96
[ 42.181819] ehci-pci: EHCI PCI platform driver
[ 42.185291] xen: registering gsi 16 triggering 0 polarity 1
[ 42.185320] Already setup the GSI :16
[ 42.185418] ehci-pci 0000:00:1a.0: setting latency timer to 64
[ 42.187052] ehci-pci 0000:00:1a.0: EHCI Host Controller
[ 42.187285] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
[ 42.187369] ehci-pci 0000:00:1a.0: debug port 2
[ 42.187403] ehci-pci 0000:00:1a.0: reset hcs_params 0x200002 dbg=2 cc=0 pcc=0 ordered !ppc ports=2
[ 42.187430] ehci-pci 0000:00:1a.0: reset hcc_params 36881 caching frame 1024 64 bit addr
[ 42.187558] ehci-pci 0000:00:1a.0: reset command 0080002 (park)=0 ithresh=8 period=1024 Reset HALT
[ 42.191511] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
[ 42.191547] ehci-pci 0000:00:1a.0: supports USB remote wakeup
[ 42.195100] ehci-pci 0000:00:1a.0: irq 16, io mem 0xd1220000
[ 42.195119] ehci-pci 0000:00:1a.0: init command 0010001 (park)=0 ithresh=1 period=1024 RUN
[ 42.200270] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
[ 42.200604] usb usb1: default language 0x0409
[ 42.200743] usb usb1: udev 1, busnum 1, minor = 0
[ 42.200771] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 42.200795] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 42.200815] usb usb1: Product: EHCI Host Controller
[ 42.200842] usb usb1: Manufacturer: Linux 3.10.0-rc3 ehci_hcd
[ 42.200860] usb usb1: SerialNumber: 0000:00:1a.0
[ 42.201314] usb usb1: usb_probe_device
[ 42.201336] usb usb1: configuration #1 chosen from 1 choice
[ 42.201409] usb usb1: adding 1-0:1.0 (config #1, interface 0)
[ 42.201552] hub 1-0:1.0: usb_probe_interface
[ 42.201582] hub 1-0:1.0: usb_probe_interface - got id
[ 42.201612] hub 1-0:1.0: USB hub found
[ 42.201668] hub 1-0:1.0: 2 ports detected
[ 42.201690] hub 1-0:1.0: standalone hub
[ 42.201724] hub 1-0:1.0: no power switching (usb 1.0)
[ 42.201753] hub 1-0:1.0: individual port over-current protection
[ 42.201784] hub 1-0:1.0: power on to power good time: 20ms
[ 42.201864] hub 1-0:1.0: local power source is good
[ 42.202176] usb usb1: usb port1's DeviceRemovable is changed to 1 according to platform information.
[ 42.202225] hub 1-0:1.0: trying to enable port power on non-switchable hub
[ 42.207017] xen: registering gsi 23 triggering 0 polarity 1
[ 42.207042] Already setup the GSI :23
[ 42.207131] ehci-pci 0000:00:1d.0: setting latency timer to 64
[ 42.208841] ehci-pci 0000:00:1d.0: EHCI Host Controller
[ 42.209078] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
[ 42.209157] ehci-pci 0000:00:1d.0: debug port 2
[ 42.209186] ehci-pci 0000:00:1d.0: reset hcs_params 0x200002 dbg=2 cc=0 pcc=0 ordered !ppc ports=2
[ 42.209240] ehci-pci 0000:00:1d.0: reset hcc_params 36881 caching frame 1024 64 bit addr
[ 42.209354] ehci-pci 0000:00:1d.0: reset command 0080002 (park)=0 ithresh=8 period=1024 Reset HALT
[ 42.213297] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
[ 42.213329] ehci-pci 0000:00:1d.0: supports USB remote wakeup
[ 42.213722] ehci-pci 0000:00:1d.0: irq 23, io mem 0xd1210000
[ 42.213750] ehci-pci 0000:00:1d.0: init command 0010001 (park)=0 ithresh=1 period=1024 RUN
[ 42.219249] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
[ 42.219510] usb usb2: default language 0x0409
[ 42.219587] usb usb2: udev 1, busnum 2, minor = 128
[ 42.219613] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[ 42.219646] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 42.219676] usb usb2: Product: EHCI Host Controller
[ 42.219703] usb usb2: Manufacturer: Linux 3.10.0-rc3 ehci_hcd
[ 42.219733] usb usb2: SerialNumber: 0000:00:1d.0
[ 42.220094] usb usb2: usb_probe_device
[ 42.220114] usb usb2: configuration #1 chosen from 1 choice
[ 42.220156] usb usb2: adding 2-0:1.0 (config #1, interface 0)
[ 42.220317] hub 2-0:1.0: usb_probe_interface
[ 42.220355] hub 2-0:1.0: usb_probe_interface - got id
[ 42.220376] hub 2-0:1.0: USB hub found
[ 42.220423] hub 2-0:1.0: 2 ports detected
[ 42.220443] hub 2-0:1.0: standalone hub
[ 42.220466] hub 2-0:1.0: no power switching (usb 1.0)
[ 42.220484] hub 2-0:1.0: individual port over-current protection
[ 42.220500] hub 2-0:1.0: power on to power good time: 20ms
[ 42.220555] hub 2-0:1.0: local power source is good
[ 42.220921] usb usb2: usb port1's DeviceRemovable is changed to 1 according to platform information.
[ 42.220952] hub 2-0:1.0: trying to enable port power on non-switchable hub
[ 42.254612] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.0.3-k
[ 42.254645] igb: Copyright (c) 2007-2013 Intel Corporation.
[ 42.255423] xen: registering gsi 16 triggering 0 polarity 1
[ 42.255451] Already setup the GSI :16
[ 42.256064] igb 0000:0a:00.0: Enabling SR-IOV VFs using the module parameter is deprecated - please use the pci sysfs interface.
[ 42.303282] ehci-pci 0000:00:1a.0: GetStatus port:1 status 001803 0 ACK POWER sig=j CSC CONNECT
[ 42.303339] hub 1-0:1.0: port 1: status 0501 change 0001
[ 42.321897] ehci-pci 0000:00:1d.0: GetStatus port:1 status 001803 0 ACK POWER sig=j CSC CONNECT
[ 42.321946] hub 2-0:1.0: port 1: status 0501 change 0001
[ 42.359505] pci 0000:0b:10.0: [8086:1520] type 00 class 0x020000
(XEN) PCI add device 0000:0b:10.0
[ 42.361498] pci 0000:0b:10.4: [8086:1520] type 00 class 0x020000
(XEN) PCI add device 0000:0b:10.4
[ 42.363354] pci 0000:0b:11.0: [8086:1520] type 00 class 0x020000
(XEN) PCI add device 0000:0b:11.0
[ 42.365089] pci 0000:0b:11.4: [8086:1520] type 00 class 0x020000
(XEN) PCI add device 0000:0b:11.4
[ 42.366780] igb 0000:0a:00.0: 4 VFs allocated
[ 42.403312] hub 1-0:1.0: state 7 ports 2 chg 0002 evt 0000
[ 42.403372] hub 1-0:1.0: port 1, status 0501, change 0000, 480 Mb/s
[ 42.436910] igb 0000:0a:00.0: added PHC on eth0
[ 42.436931] igb 0000:0a:00.0: Intel(R) Gigabit Ethernet Network Connection
[ 42.436945] igb 0000:0a:00.0: eth0: (PCIe:5.0Gb/s:Width x4) 00:1e:67:65:83:93
[ 42.437032] igb 0000:0a:00.0: eth0: PBA No: 100000-000
[ 42.437045] igb 0000:0a:00.0: Using MSI-X interrupts. 1 rx queue(s), 1 tx queue(s)
[ 42.437412] xen: registering gsi 17 triggering 0 polarity 1
[ 42.437472] xen: --> pirq=17 -> irq=17 (gsi=17)
[ 42.438071] igb 0000:0a:00.1: Enabling SR-IOV VFs using the module parameter is deprecated - please use the pci sysfs interface.
[ 42.454548] ehci-pci 0000:00:1a.0: port 1 reset complete, port enabled
[ 42.454571] ehci-pci 0000:00:1a.0: GetStatus port:1 status 001005 0 ACK POWER sig=se0 PE CONNECT
[ 42.505305] usb 1-1: new high-speed USB device number 2 using ehci-pci
[ 42.539349] pci 0000:0b:10.1: [8086:1520] type 00 class 0x020000
(XEN) PCI add device 0000:0b:10.1
[ 42.540295] pci 0000:0b:10.5: [8086:1520] type 00 class 0x020000
(XEN) PCI add device 0000:0b:10.5
[ 42.541366] pci 0000:0b:11.1: [8086:1520] type 00 class 0x020000
(XEN) PCI add device 0000:0b:11.1
[ 42.542372] pci 0000:0b:11.5: [8086:1520] type 00 class 0x020000
(XEN) PCI add device 0000:0b:11.5
[ 42.543316] igb 0000:0a:00.1: 4 VFs allocated
[ 42.556542] ehci-pci 0000:00:1a.0: port 1 reset complete, port enabled
[ 42.556552] ehci-pci 0000:00:1a.0: GetStatus port:1 status 001005 0 ACK POWER sig=se0 PE CONNECT
[ 42.613253] igb 0000:0a:00.1: added PHC on eth1
[ 42.613262] igb 0000:0a:00.1: Intel(R) Gigabit Ethernet Network Connection
[ 42.613269] igb 0000:0a:00.1: eth1: (PCIe:5.0Gb/s:Width x4) 00:1e:67:65:83:94
[ 42.613352] igb 0000:0a:00.1: eth1: PBA No: 100000-000
[ 42.613357] igb 0000:0a:00.1: Using MSI-X interrupts. 1 rx queue(s), 1 tx queue(s)
[ 42.613471] xen: registering gsi 18 triggering 0 polarity 1
[ 42.613480] Already setup the GSI :18
[ 42.613831] igb 0000:0a:00.2: Enabling SR-IOV VFs using the module parameter is deprecated - please use the pci sysfs interface.
[ 42.619749] usb 1-1: udev 2, busnum 1, minor = 1
[ 42.619758] usb 1-1: New USB device found, idVendor=8087, idProduct=0024
[ 42.619763] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 42.619826] usb 1-1: usb_probe_device
[ 42.619833] usb 1-1: configuration #1 chosen from 1 choice
[ 42.619978] usb 1-1: adding 1-1:1.0 (config #1, interface 0)
[ 42.620009] hub 1-1:1.0: usb_probe_interface
[ 42.620028] hub 1-1:1.0: usb_probe_interface - got id
[ 42.620032] hub 1-1:1.0: USB hub found
[ 42.620260] hub 1-1:1.0: 6 ports detected
[ 42.620267] hub 1-1:1.0: standalone hub
[ 42.620271] hub 1-1:1.0: individual port power switching
[ 42.620277] hub 1-1:1.0: individual port over-current protection
[ 42.620283] hub 1-1:1.0: Single TT
[ 42.620293] hub 1-1:1.0: TT requires at most 8 FS bit times (666 ns)
[ 42.620298] hub 1-1:1.0: power on to power good time: 100ms
[ 42.620585] hub 1-1:1.0: local power source is good
[ 42.620890] hub 1-1:1.0: enabling power on all ports
[ 42.621758] hub 2-0:1.0: state 7 ports 2 chg 0002 evt 0000
[ 42.621781] hub 2-0:1.0: port 1, status 0501, change 0000, 480 Mb/s
[ 42.672539] ehci-pci 0000:00:1d.0: port 1 reset complete, port enabled
[ 42.672548] ehci-pci 0000:00:1d.0: GetStatus port:1 status 001005 0 ACK POWER sig=se0 PE CONNECT
[ 42.714348] pci 0000:0b:10.2: [8086:1520] type 00 class 0x020000
(XEN) PCI add device 0000:0b:10.2
[ 42.715170] pci 0000:0b:10.6: [8086:1520] type 00 class 0x020000
(XEN) PCI add device 0000:0b:10.6
[ 42.716058] pci 0000:0b:11.2: [8086:1520] type 00 class 0x020000
(XEN) PCI add device 0000:0b:11.2
[ 42.716998] pci 0000:0b:11.6: [8086:1520] type 00 class 0x020000
(XEN) PCI add device 0000:0b:11.6
[ 42.717917] igb 0000:0a:00.2: 4 VFs allocated
[ 42.722066] usb 1-1: link qh256-0001/ffff88010018e500 start 1 [1/0 us]
[ 42.723267] usb 2-1: new high-speed USB device number 2 using ehci-pci
[ 42.772999] igb 0000:0a:00.2: added PHC on eth2
[ 42.773015] igb 0000:0a:00.2: Intel(R) Gigabit Ethernet Network Connection
[ 42.773027] igb 0000:0a:00.2: eth2: (PCIe:5.0Gb/s:Width x4) 00:1e:67:65:83:95
[ 42.773113] igb 0000:0a:00.2: eth2: PBA No: 100000-000
[ 42.773124] igb 0000:0a:00.2: Using MSI-X interrupts. 1 rx queue(s), 1 tx queue(s)
[ 42.773342] xen: registering gsi 19 triggering 0 polarity 1
[ 42.773357] Already setup the GSI :19
[ 42.773911] igb 0000:0a:00.3: Enabling SR-IOV VFs using the module parameter is deprecated - please use the pci sysfs interface.
[ 42.774532] ehci-pci 0000:00:1d.0: port 1 reset complete, port enabled
[ 42.774541] ehci-pci 0000:00:1d.0: GetStatus port:1 status 001005 0 ACK POWER sig=se0 PE CONNECT
[ 42.837741] usb 2-1: udev 2, busnum 2, minor = 129
[ 42.837781] usb 2-1: New USB device found, idVendor=8087, idProduct=0024
[ 42.837786] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 42.837835] usb 2-1: usb_probe_device
[ 42.837839] usb 2-1: configuration #1 chosen from 1 choice
[ 42.838006] usb 2-1: adding 2-1:1.0 (config #1, interface 0)
[ 42.838043] hub 2-1:1.0: usb_probe_interface
[ 42.838049] hub 2-1:1.0: usb_probe_interface - got id
[ 42.838053] hub 2-1:1.0: USB hub found
[ 42.838245] hub 2-1:1.0: 8 ports detected
[ 42.838252] hub 2-1:1.0: standalone hub
[ 42.838255] hub 2-1:1.0: individual port power switching
[ 42.838259] hub 2-1:1.0: individual port over-current protection
[ 42.838264] hub 2-1:1.0: Single TT
[ 42.838268] hub 2-1:1.0: TT requires at most 8 FS bit times (666 ns)
[ 42.838273] hub 2-1:1.0: power on to power good time: 100ms
[ 42.838597] hub 2-1:1.0: local power source is good
[ 42.838866] hub 2-1:1.0: enabling power on all ports
[ 42.839879] hub 1-1:1.0: state 7 ports 6 chg 0000 evt 0000
[ 42.875339] pci 0000:0b:10.3: [8086:1520] type 00 class 0x020000
(XEN) PCI add device 0000:0b:10.3
[ 42.876168] pci 0000:0b:10.7: [8086:1520] type 00 class 0x020000
(XEN) PCI add device 0000:0b:10.7
[ 42.877133] pci 0000:0b:11.3: [8086:1520] type 00 class 0x020000
(XEN) PCI add device 0000:0b:11.3
[ 42.877835] pci 0000:0b:11.7: [8086:1520] type 00 class 0x020000
(XEN) PCI add device 0000:0b:11.7
[ 42.878750] igb 0000:0a:00.3: 4 VFs allocated
[ 42.931975] igb 0000:0a:00.3: added PHC on eth3
[ 42.931991] igb 0000:0a:00.3: Intel(R) Gigabit Ethernet Network Connection
[ 42.932005] igb 0000:0a:00.3: eth3: (PCIe:5.0Gb/s:Width x4) 00:1e:67:65:83:96
[ 42.932093] igb 0000:0a:00.3: eth3: PBA No: 100000-000
[ 42.932104] igb 0000:0a:00.3: Using MSI-X interrupts. 1 rx queue(s), 1 tx queue(s)
[ 42.939576] hub 2-1:1.0: port 2: status 0101 change 0001
[ 42.939953] hub 2-1:1.0: port 4: status 0101 change 0001
[ 43.040272] usb 2-1: link qh256-0001/ffff88010018e880 start 1 [1/0 us]
[ 43.040338] hub 2-1:1.0: state 7 ports 8 chg 0014 evt 0000
[ 43.040623] hub 2-1:1.0: port 2, status 0101, change 0000, 12 Mb/s
[ 43.051492] hub 2-1:1.0: port 2 not reset yet, waiting 10ms
[ 43.055872] sr 0:0:0:0: Attached scsi generic sg0 type 5
[ 43.055934] sd 1:0:0:0: Attached scsi generic sg1 type 0
[ 43.113501] usb 2-1.2: new low-speed USB device number 3 using ehci-pci
[ 43.128488] hub 2-1:1.0: port 2 not reset yet, waiting 10ms
[ 43.225612] usb 2-1.2: skipped 1 descriptor after interface
[ 43.225621] usb 2-1.2: skipped 1 descriptor after interface
[ 43.227873] usb 2-1.2: default language 0x0409
[ 43.242120] usb 2-1.2: udev 3, busnum 2, minor = 130
[ 43.242127] usb 2-1.2: New USB device found, idVendor=0557, idProduct=2217
[ 43.242132] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 43.242137] usb 2-1.2: Product: ATEN CS-1716/08/04
[ 43.242141] usb 2-1.2: Manufacturer: ATEN
[ 43.242203] usb 2-1.2: usb_probe_device
[ 43.242212] usb 2-1.2: configuration #1 chosen from 1 choice
[ 43.242582] usb 2-1.2: adding 2-1.2:1.0 (config #1, interface 0)
[ 43.244353] usbhid 2-1.2:1.0: usb_probe_interface
[ 43.244360] usbhid 2-1.2:1.0: usb_probe_interface - got id
[ 43.262448] input: ATEN ATEN CS-1716/08/04 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/input/input1
[ 43.262490] usb 2-1.2: link qh8-0e01/ffff88010018e180 start 2 [1/2 us]
[ 43.262564] hid-generic 0003:0557:2217.0001: input,hidraw0: USB HID v1.10 Keyboard [ATEN ATEN CS-1716/08/04] on usb-0000:00:1d.0-1.2/input0
[ 43.262615] usb 2-1.2: adding 2-1.2:1.1 (config #1, interface 1)
[ 43.267436] usbhid 2-1.2:1.1: usb_probe_interface
[ 43.267450] usbhid 2-1.2:1.1: usb_probe_interface - got id
[ 43.282674] input: ATEN ATEN CS-1716/08/04 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.1/input/input2
[ 43.282800] hid-generic 0003:0557:2217.0002: input,hidraw1: USB HID v1.10 Mouse [ATEN ATEN CS-1716/08/04] on usb-0000:00:1d.0-1.2/input1
[ 43.283029] hub 2-1:1.0: port 4, status 0101, change 0000, 12 Mb/s
[ 43.345512] usb 2-1.4: new full-speed USB device number 4 using ehci-pci
[ 43.356512] hub 2-1:1.0: port 4 not reset yet, waiting 10ms
[ 43.446598] usb 2-1.4: skipped 1 descriptor after interface
[ 43.446606] usb 2-1.4: skipped 1 descriptor after interface
[ 43.446843] usb 2-1.4: default language 0x0409
[ 43.447465] usb 2-1.4: udev 4, busnum 2, minor = 131
[ 43.447472] usb 2-1.4: New USB device found, idVendor=046b, idProduct=ff10
[ 43.447479] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 43.447486] usb 2-1.4: Product: Virtual Keyboard and Mouse
[ 43.447491] usb 2-1.4: Manufacturer: American Megatrends Inc.
[ 43.447496] usb 2-1.4: SerialNumber: serial
[ 43.447560] usb 2-1.4: usb_probe_device
[ 43.447565] usb 2-1.4: configuration #1 chosen from 1 choice
[ 43.447849] usb 2-1.4: adding 2-1.4:1.0 (config #1, interface 0)
[ 43.448122] usbhid 2-1.4:1.0: usb_probe_interface
[ 43.448129] usbhid 2-1.4:1.0: usb_probe_interface - got id
[ 43.448927] input: American Megatrends Inc. Virtual Keyboard and Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input3
[ 43.448962] usb 2-1.4: link qh8-0e01/ffff88010018e300 start 3 [1/2 us]
[ 43.449024] hid-generic 0003:046B:FF10.0003: input,hidraw2: USB HID v1.10 Keyboard [American Megatrends Inc. Virtual Keyboard and Mouse] on usb-0000:00:1d.0-1.4/input0
[ 43.449074] usb 2-1.4: adding 2-1.4:1.1 (config #1, interface 1)
[ 43.449390] usbhid 2-1.4:1.1: usb_probe_interface
[ 43.449396] usbhid 2-1.4:1.1: usb_probe_interface - got id
[ 43.450323] input: American Megatrends Inc. Virtual Keyboard and Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.1/input/input4
[ 43.450410] hid-generic 0003:046B:FF10.0004: input,hidraw3: USB HID v1.10 Mouse [American Megatrends Inc. Virtual Keyboard and Mouse] on usb-0000:00:1d.0-1.4/input1
[ OK ]
Setting hostname vt-ivt1: [ OK ]
Setting up Logical Volume Management: No volume groups found
[ OK ]
Checking filesystems
Checking all file systems.
[/sbin/fsck.ext4 (1) -- /] fsck.ext4 -a /dev/sda1
/dev/sda1: clean, 1631261/60399616 files, 56212843/241568768 blocks
[ OK ]
Remounting root filesystem in read-write mode: [ 44.944787] EXT4-fs (sda1): re-mounted. Opts: (null)
[ OK ]
Mounting local filesystems: [ OK ]
Enabling local filesystem quotas: [ OK ]
Enabling /etc/fstab swaps: [ 45.509868] Adding 10485756k swap on /dev/sda2. Priority:-1 extents:1 across:10485756k
[ OK ]
Entering non-interactive startup
Calling the system activity data collector (sadc):
Starting cgconfig service: Error: cannot mount memory to /cgroup/memory: No such file or directory
Loading configuration file /etc/cgconfig.conf failed
Cgroup mounting failed
Failed to parse /etc/cgconfig.conf[FAILED]
Bringing up loopback interface: [ OK ]
Bringing up interface eth0:
Determining IP information for eth0...[ 47.060280] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 50.888697] igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[ 50.888942] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
done.
[ OK ]
Starting portreserve: [ OK ]
Starting system logger: [ OK ]
Starting irqbalance: [ OK ]
Starting rpcbind: [ OK ]
Starting cgdcbxd: /usr/sbin/cgdcbxd: libcgroup initialization failed: Cgroup is not mounted
cgdcbxd: libcgroup initialization failed: Cgroup is not mounted
[FAILED]
Kdump is not supported on this kernel[FAILED]
Starting lldpad: [ OK ]
Starting FCoE initiator service: [ OK ]
Starting FCoE Target:
Loading modules... failed
FATAL: Module configfs not found.
[FAILED]
Starting system message bus: [ OK ]
Starting NFS statd: [ OK ]
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
Starting RPC idmapd: [ 59.859420] RPC: Registered named UNIX socket transport module.
[ 59.859448] RPC: Registered udp transport module.
[ 59.859453] RPC: Registered tcp transport module.
[ 59.859458] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ OK ]
Starting cups: [ OK ]
Starting ibacm daemon:[ OK ]
Mounting other filesystems: [ OK ]
Starting acpi daemon: [ OK ]
Starting HAL daemon: [ OK ]
Starting Hyper-V KVP daemon [ OK ]
Retrigger failed udev events[ OK ]
Starting PC/SC smart card daemon (pcscd): [ OK ]
Starting automount: [ OK ]
Enabling Bluetooth devices:
Starting mcelog daemon
[ OK ]Starting sshd: [ OK ]
Starting xinetd: [ OK ]
Starting postfix: [ OK ]
Starting abrt daemon: [ OK ]
Starting crond: [ OK ]
Starting VNC server: 1:root
New 'vt-ivt1:1 (root)' desktop is vt-ivt1:1
Starting applications specified in /root/.vnc/xstartup
Log file is /root/.vnc/vt-ivt1:1.log
2:root
New 'vt-ivt1:2 (root)' desktop is vt-ivt1:2
Starting applications specified in /root/.vnc/xstartup
Log file is /root/.vnc/vt-ivt1:2.log
[ OK ]
Starting atd: [ OK ]
Starting jexec servicesStarting rhsmcertd...[ OK ]
Starting certmonger: [ OK ]
+ touch /var/lock/subsys/local
+ sleep 10
+ sleep 2
+ /net.sh
+ sh /usr/tet/XVS/bin/pciback.sh 07:00.0
[ 88.534346] pciback 0000:07:00.0: seizing device
[ 88.534628] xen: registering gsi 34 triggering 0 polarity 1
[ 88.534700] xen: --> pirq=34 -> irq=34 (gsi=34)
Binding 0000:07:00.0 to pciback
+ ip link set eth0 vf 0 mac 00:2B:21:66:D8:11
[ 88.563682] igb 0000:0a:00.0: setting MAC 00:2b:21:66:d8:11 on VF 0
[ 88.563705] igb 0000:0a:00.0: Reload the VF driver to make this change effective.
+ ip link set eth0 vf 1 mac 00:2B:21:66:D8:12
[ 88.570322] igb 0000:0a:00.0: setting MAC 00:2b:21:66:d8:12 on VF 1
[ 88.570339] igb 0000:0a:00.0: Reload the VF driver to make this change effective.
+ ip link set eth0 vf 2 mac 00:2B:21:66:D8:13
[ 88.576403] igb 0000:0a:00.0: setting MAC 00:2b:21:66:d8:13 on VF 2
[ 88.576421] igb 0000:0a:00.0: Reload the VF driver to make this change effective.
+ ip link set eth0 vf 3 mac 00:2B:21:66:D8:14
[ 88.582135] igb 0000:0a:00.0: setting MAC 00:2b:21:66:d8:14 on VF 3
[ 88.582152] igb 0000:0a:00.0: Reload the VF driver to make this change effective.
+ ip link set eth61 vf 0 mac 00:2B:21:66:D8:25
[ 88.586421] ixgbe 0000:05:00.1: setting MAC 00:2b:21:66:d8:25 on VF 0
[ 88.586431] ixgbe 0000:05:00.1: Reload the VF driver to make this change effective.
[ 88.586439] ixgbe 0000:05:00.1: The VF MAC address has been set, but the PF device is not up.
[ 88.586447] ixgbe 0000:05:00.1: Bring the PF device up before attempting to use the VF device.
+ ip link set eth61 vf 1 mac 00:2B:21:66:D8:26
[ 88.594463] ixgbe 0000:05:00.1: setting MAC 00:2b:21:66:d8:26 on VF 1
[ 88.594478] ixgbe 0000:05:00.1: Reload the VF driver to make this change effective.
[ 88.594485] ixgbe 0000:05:00.1: The VF MAC address has been set, but the PF device is not up.
[ 88.594491] ixgbe 0000:05:00.1: Bring the PF device up before attempting to use the VF device.
+ ip link set eth61 vf 2 mac 00:2B:21:66:D8:27
[ 88.601695] ixgbe 0000:05:00.1: setting MAC 00:2b:21:66:d8:27 on VF 2
[ 88.601729] ixgbe 0000:05:00.1: Reload the VF driver to make this change effective.
[ 88.601757] ixgbe 0000:05:00.1: The VF MAC address has been set, but the PF device is not up.
[ 88.601786] ixgbe 0000:05:00.1: Bring the PF device up before attempting to use the VF device.
+ ip link set eth61 vf 3 mac 00:2B:21:66:D8:28
[ 88.609104] ixgbe 0000:05:00.1: setting MAC 00:2b:21:66:d8:28 on VF 3
[ 88.609125] ixgbe 0000:05:00.1: Reload the VF driver to make this change effective.
[ 88.609139] ixgbe 0000:05:00.1: The VF MAC address has been set, but the PF device is not up.
[ 88.609172] ixgbe 0000:05:00.1: Bring the PF device up before attempting to use the VF device.
+ ip route show
default via 192.168.199.1 dev eth0
169.254.0.0/16 dev eth0 scope link metric 1005
192.168.0.0/16 dev eth0 proto kernel scope link src 192.168.199.111
+ ip route flush table main
+ ip route show
+ route del -net 192.168.0.0 netmask 255.255.0.0
SIOCDELRT: No such process
+ route del -net 192.168.0.0 netmask 255.255.0.0
SIOCDELRT: No such process
+ route del default
SIOCDELRT: No such process
+ sleep 2
+ ifconfig eth0 0
+ brctl addbr xenbr0
+ brctl addif xenbr0 eth0
[ 92.221766] device eth0 entered promiscuous mode
+ ifconfig xenbr0 192.168.199.111 netmask 255.255.0.0
[ 92.229301] xenbr0: port 1(eth0) entered forwarding state
[ 92.229367] xenbr0: port 1(eth0) entered forwarding state
++ expr + 1
+ num=1
+ pkill dhclient
+ sleep 3
+ dhclient eth61
[ 95.462689] ixgbe 0000:05:00.1: registered PHC device on eth61
[ 95.563639] IPv6: ADDRCONF(NETDEV_UP): eth61: link is not ready
[ 95.625754] ixgbe 0000:05:00.1 eth61: detected SFP+: 6
[ 96.497315] ixgbe 0000:05:00.1 eth61: NIC Link is Up 1 Gbps, Flow Control: RX/TX
[ 96.497549] IPv6: ADDRCONF(NETDEV_CHANGE): eth61: link becomes ready
(XEN) *** Serial input -> Xen (type 'CTRL-a' three times to switch input to DOM0)
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) *** Serial input -> Xen (type 'CTRL-a' three times to switch input to DOM0)
++ route -n
++ awk '{print $8}'
++ grep eth
+ for i in '$(route -n | awk '\''{print $8}'\''| grep eth)'
+ route del -net 192.168.0.0 netmask 255.255.0.0 dev eth61
+ for i in '$(route -n | awk '\''{print $8}'\''| grep eth)'
+ route del -net 192.168.0.0 netmask 255.255.0.0 dev eth0
+ for i in '$(route -n | awk '\''{print $8}'\''| grep eth)'
+ route del -net 192.168.0.0 netmask 255.255.0.0 dev eth0
SIOCDELRT: No such process
+ for i in '$(route -n | awk '\''{print $8}'\''| grep eth)'
+ route del -net 192.168.0.0 netmask 255.255.0.0 dev eth61
SIOCDELRT: No such process
+ route del default
+ route del -net 192.168.0.0 netmask 255.255.0.0 dev xenbr0
+ brctl stp xenbr0 on
+ ifconfig eth0 0
+ route add -net 192.168.0.0 netmask 255.255.0.0 dev xenbr0
+ route add default gw 192.168.199.1 dev xenbr0
+ /etc/init.d/xencommons start
[ 100.677943] xen-acpi-processor: Uploading Xen processor PM info
Starting C xenstored...
Setting domain 0 name...
Starting xenconsoled...
Starting QEMU as disk backend for dom0
+ sleep 6
[ 107.274275] xenbr0: port 1(eth0) entered forwarding state
+ mount vt-nfs:/images /share/xvs/img
[ 109.873970] NFS: Registering the id_resolver key type
[ 109.874012] Key type id_resolver registered
[ 109.874022] Key type id_legacy registered
+ sleep 3
+ mount vt-nfs:/linux_vmm/tools /share/xvs/tools
+ ntpdate vt-master
5 Jun 10:12:44 ntpdate[11782]: adjust time server 10.239.48.245 offset 0.477890 sec
Sleep 1 second ...
Check XVS lock ...
xvs_num: 1
Last XVS run is completed
Red Hat Enterprise Linux Server release 6.4 (Santiago)
Kernel 3.10.0-rc3 on an x86_64
vt-ivt1 login: [ 262.488584] device vif4.0 entered promiscuous mode
[ 262.495196] IPv6: ADDRCONF(NETDEV_UP): vif4.0: link is not ready
[ 262.751839] device vif4.0-emu entered promiscuous mode
[ 262.758342] xenbr0: port 3(vif4.0-emu) entered listening state
[ 262.758396] xenbr0: port 3(vif4.0-emu) entered listening state
(XEN) HVM4: HVM Loader
(XEN) HVM4: Detected Xen v4.3-unstable
(XEN) HVM4: Xenbus rings @0xfeffc000, event channel 18
(XEN) HVM4: System requested ROMBIOS
(XEN) HVM4: CPU speed is 2793 MHz
(XEN) irq.c:270: Dom4 PCI link 0 changed 0 -> 5
(XEN) HVM4: PCI-ISA link 0 routed to IRQ5
(XEN) irq.c:270: Dom4 PCI link 1 changed 0 -> 10
(XEN) HVM4: PCI-ISA link 1 routed to IRQ10
(XEN) irq.c:270: Dom4 PCI link 2 changed 0 -> 11
(XEN) HVM4: PCI-ISA link 2 routed to IRQ11
(XEN) irq.c:270: Dom4 PCI link 3 changed 0 -> 5
(XEN) HVM4: PCI-ISA link 3 routed to IRQ5
(XEN) HVM4: pci dev 01:3 INTA->IRQ10
(XEN) HVM4: pci dev 03:0 INTA->IRQ5
(XEN) HVM4: pci dev 04:0 INTA->IRQ5
(XEN) HVM4: pci dev 02:0 bar 10 size lx: 02000000
(XEN) HVM4: pci dev 03:0 bar 14 size lx: 01000000
(XEN) HVM4: pci dev 02:0 bar 14 size lx: 00001000
(XEN) HVM4: pci dev 03:0 bar 10 size lx: 00000100
(XEN) HVM4: pci dev 04:0 bar 10 size lx: 00000100
(XEN) HVM4: pci dev 04:0 bar 14 size lx: 00000100
(XEN) HVM4: pci dev 01:1 bar 20 size lx: 00000010
(XEN) HVM4: Multiprocessor initialisation:
(XEN) HVM4: - CPU0 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM4: - CPU1 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM4: - CPU2 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM4: - CPU3 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM4: - CPU4 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM4: - CPU5 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM4: - CPU6 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM4: - CPU7 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM4: - CPU8 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM4: - CPU9 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM4: - CPU10 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM4: - CPU11 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM4: - CPU12 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM4: - CPU13 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM4: - CPU14 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM4: - CPU15 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM4: Testing HVM environment:
(XEN) HVM4: - REP INSB across page boundaries ... passed
(XEN) HVM4: - GS base MSRs and SWAPGS ... passed
(XEN) HVM4: Passed 2 of 2 tests
(XEN) HVM4: Writing SMBIOS tables ...
(XEN) HVM4: Loading ROMBIOS ...
(XEN) HVM4: 9628 bytes of ROMBIOS high-memory extensions:
(XEN) HVM4: Relocating to 0xfc001000-0xfc00359c ... done
(XEN) HVM4: Creating MP tables ...
(XEN) HVM4: Loading Cirrus VGABIOS ...
(XEN) HVM4: Loading PCI Option ROM ...
(XEN) HVM4: - Manufacturer: http://ipxe.org
(XEN) HVM4: - Product name: iPXE
(XEN) HVM4: Option ROMs:
(XEN) HVM4: c0000-c8fff: VGA BIOS
(XEN) HVM4: c9000-d8fff: Etherboot ROM
(XEN) HVM4: Loading ACPI ...
(XEN) HVM4: vm86 TSS at fc015180
(XEN) HVM4: BIOS map:
(XEN) HVM4: f0000-fffff: Main BIOS
(XEN) HVM4: E820 table:
(XEN) HVM4: [00]: 00000000:00000000 - 00000000:0009e000: RAM
(XEN) HVM4: [01]: 00000000:0009e000 - 00000000:000a0000: RESERVED
(XEN) HVM4: HOLE: 00000000:000a0000 - 00000000:000e0000
(XEN) HVM4: [02]: 00000000:000e0000 - 00000000:00100000: RESERVED
(XEN) HVM4: [03]: 00000000:00100000 - 00000000:7f800000: RAM
(XEN) HVM4: HOLE: 00000000:7f800000 - 00000000:fc000000
(XEN) HVM4: [04]: 00000000:fc000000 - 00000001:00000000: RESERVED
(XEN) HVM4: Invoking ROMBIOS ...
(XEN) HVM4: $Revision: 1.221 $ $Date: 2008/12/07 17:32:29 $
(XEN) stdvga.c:147:d4 entering stdvga and caching modes
(XEN) HVM4: VGABios $Id: vgabios.c,v 1.67 2008/01/27 09:44:12 vruppert Exp $
(XEN) HVM4: Bochs BIOS - build: 06/23/99
(XEN) HVM4: $Revision: 1.221 $ $Date: 2008/12/07 17:32:29 $
(XEN) HVM4: Options: apmbios pcibios eltorito PMM
(XEN) HVM4:
(XEN) HVM4: ata0-0: PCHS=16383/16/63 translation=lba LCHS=1024/255/63
(XEN) HVM4: ata0 master: QEMU HARDDISK ATA-7 Hard-Disk (8192 MBytes)
(XEN) HVM4: IDE time out
(XEN) HVM4:
(XEN) HVM4:
(XEN) HVM4:
(XEN) HVM4: Press F12 for boot menu.
(XEN) HVM4:
(XEN) HVM4: Booting from Hard Disk...
(XEN) HVM4: Booting from 0000:7c00
(XEN) HVM4: int13_harddisk: function 41, unmapped device for ELDL=81
(XEN) HVM4: int13_harddisk: function 08, unmapped device for ELDL=81
(XEN) HVM4: *** int 15h function AX=00c0, BX=0000 not yet supported!
(XEN) HVM4: *** int 15h function AX=ec00, BX=0002 not yet supported!
(XEN) HVM4: KBD: unsupported int 16h function 03
(XEN) HVM4: *** int 15h function AX=e980, BX=0000 not yet supported!
(XEN) HVM4: int13_harddisk: function 41, unmapped device for ELDL=81
(XEN) HVM4: int13_harddisk: function 02, unmapped device for ELDL=81
(XEN) HVM4: int13_harddisk: function 41, unmapped device for ELDL=82
(XEN) HVM4: int13_harddisk: function 02, unmapped device for ELDL=82
(XEN) HVM4: int13_harddisk: function 41, unmapped device for ELDL=83
(XEN) HVM4: int13_harddisk: function 02, unmapped device for ELDL=83
(XEN) HVM4: int13_harddisk: function 41, unmapped device for ELDL=84
(XEN) HVM4: int13_harddisk: function 02, unmapped device for ELDL=84
(XEN) HVM4: int13_harddisk: function 41, unmapped device for ELDL=85
(XEN) HVM4: int13_harddisk: function 02, unmapped device for ELDL=85
(XEN) HVM4: int13_harddisk: function 41, unmapped device for ELDL=86
(XEN) HVM4: int13_harddisk: function 02, unmapped device for ELDL=86
(XEN) HVM4: int13_harddisk: function 41, unmapped device for ELDL=87
(XEN) HVM4: int13_harddisk: function 02, unmapped device for ELDL=87
(XEN) HVM4: int13_harddisk: function 41, ELDL out of range 88
(XEN) HVM4: int13_harddisk: function 02, ELDL out of range 88
(XEN) HVM4: int13_harddisk: function 41, ELDL out of range 89
(XEN) HVM4: int13_harddisk: function 02, ELDL out of range 89
(XEN) HVM4: int13_harddisk: function 41, ELDL out of range 8a
(XEN) HVM4: int13_harddisk: function 02, ELDL out of range 8a
(XEN) HVM4: int13_harddisk: function 41, ELDL out of range 8b
(XEN) HVM4: int13_harddisk: function 02, ELDL out of range 8b
(XEN) HVM4: int13_harddisk: function 41, ELDL out of range 8c
(XEN) HVM4: int13_harddisk: function 02, ELDL out of range 8c
(XEN) HVM4: int13_harddisk: function 41, ELDL out of range 8d
(XEN) HVM4: int13_harddisk: function 02, ELDL out of range 8d
(XEN) HVM4: int13_harddisk: function 41, ELDL out of range 8e
(XEN) HVM4: int13_harddisk: function 02, ELDL out of range 8e
(XEN) HVM4: int13_harddisk: function 41, ELDL out of range 8f
(XEN) HVM4: int13_harddisk: function 02, ELDL out of range 8f
[ 276.933427] xenbr0: port 3(vif4.0-emu) entered disabled state
[ 276.933975] device vif4.0-emu left promiscuous mode
[ 276.933999] xenbr0: port 3(vif4.0-emu) entered disabled state
(XEN) irq.c:375: Dom4 callback via changed to Direct Vector 0xe9
(XEN) irq.c:270: Dom4 PCI link 0 changed 5 -> 0
(XEN) irq.c:270: Dom4 PCI link 1 changed 10 -> 0
(XEN) irq.c:270: Dom4 PCI link 2 changed 11 -> 0
(XEN) irq.c:270: Dom4 PCI link 3 changed 5 -> 0
[ 286.203928] IPv6: ADDRCONF(NETDEV_CHANGE): vif4.0: link becomes ready
[ 286.204126] xenbr0: port 2(vif4.0) entered listening state
[ 286.204180] xenbr0: port 2(vif4.0) entered listening state
[ 301.229803] xenbr0: port 2(vif4.0) entered learning state
[ 316.262323] xenbr0: topology change detected, sending tcn bpdu
[ 316.262377] xenbr0: port 2(vif4.0) entered forwarding state
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) *** Serial input -> Xen (type 'CTRL-a' three times to switch input to DOM0)
[ 410.119289] xenbr0: port 2(vif4.0) entered disabled state
[ 410.119807] device vif4.0 left promiscuous mode
[ 410.119823] xenbr0: port 2(vif4.0) entered disabled state
[ 456.605724] device vif5.0 entered promiscuous mode
[ 456.612814] IPv6: ADDRCONF(NETDEV_UP): vif5.0: link is not ready
[ 456.823176] device vif5.0-emu entered promiscuous mode
[ 456.829565] xenbr0: port 3(vif5.0-emu) entered listening state
[ 456.829615] xenbr0: port 3(vif5.0-emu) entered listening state
(XEN) HVM5: HVM Loader
(XEN) HVM5: Detected Xen v4.3-unstable
(XEN) HVM5: Xenbus rings @0xfeffc000, event channel 26
(XEN) HVM5: System requested ROMBIOS
(XEN) HVM5: CPU speed is 2793 MHz
(XEN) irq.c:270: Dom5 PCI link 0 changed 0 -> 5
(XEN) HVM5: PCI-ISA link 0 routed to IRQ5
(XEN) irq.c:270: Dom5 PCI link 1 changed 0 -> 10
(XEN) HVM5: PCI-ISA link 1 routed to IRQ10
(XEN) irq.c:270: Dom5 PCI link 2 changed 0 -> 11
(XEN) HVM5: PCI-ISA link 2 routed to IRQ11
(XEN) irq.c:270: Dom5 PCI link 3 changed 0 -> 5
(XEN) HVM5: PCI-ISA link 3 routed to IRQ5
(XEN) HVM5: pci dev 01:3 INTA->IRQ10
(XEN) HVM5: pci dev 03:0 INTA->IRQ5
(XEN) HVM5: pci dev 04:0 INTA->IRQ5
(XEN) HVM5: pci dev 02:0 bar 10 size lx: 02000000
(XEN) HVM5: pci dev 03:0 bar 14 size lx: 01000000
(XEN) HVM5: pci dev 02:0 bar 14 size lx: 00001000
(XEN) HVM5: pci dev 03:0 bar 10 size lx: 00000100
(XEN) HVM5: pci dev 04:0 bar 10 size lx: 00000100
(XEN) HVM5: pci dev 04:0 bar 14 size lx: 00000100
(XEN) HVM5: pci dev 01:1 bar 20 size lx: 00000010
(XEN) HVM5: Multiprocessor initialisation:
(XEN) HVM5: - CPU0 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM5: - CPU1 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM5: - CPU2 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM5: - CPU3 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM5: - CPU4 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM5: - CPU5 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM5: - CPU6 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM5: - CPU7 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM5: - CPU8 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM5: - CPU9 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM5: - CPU10 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM5: - CPU11 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM5: - CPU12 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM5: - CPU13 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM5: - CPU14 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM5: - CPU15 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM5: - CPU16 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM5: - CPU17 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM5: - CPU18 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM5: - CPU19 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM5: - CPU20 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM5: - CPU21 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM5: - CPU22 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM5: - CPU23 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM5: Testing HVM environment:
(XEN) HVM5: - REP INSB across page boundaries ... passed
(XEN) HVM5: - GS base MSRs and SWAPGS ... passed
(XEN) HVM5: Passed 2 of 2 tests
(XEN) HVM5: Writing SMBIOS tables ...
(XEN) HVM5: Loading ROMBIOS ...
(XEN) HVM5: 9628 bytes of ROMBIOS high-memory extensions:
(XEN) HVM5: Relocating to 0xfc001000-0xfc00359c ... done
(XEN) HVM5: Creating MP tables ...
(XEN) HVM5: Loading Cirrus VGABIOS ...
(XEN) HVM5: Loading PCI Option ROM ...
(XEN) HVM5: - Manufacturer: http://ipxe.org
(XEN) HVM5: - Product name: iPXE
(XEN) HVM5: Option ROMs:
(XEN) HVM5: c0000-c8fff: VGA BIOS
(XEN) HVM5: c9000-d8fff: Etherboot ROM
(XEN) HVM5: Loading ACPI ...
(XEN) HVM5: vm86 TSS at fc015180
(XEN) HVM5: BIOS map:
(XEN) HVM5: f0000-fffff: Main BIOS
(XEN) HVM5: E820 table:
(XEN) HVM5: [00]: 00000000:00000000 - 00000000:0009e000: RAM
(XEN) HVM5: [01]: 00000000:0009e000 - 00000000:000a0000: RESERVED
(XEN) HVM5: HOLE: 00000000:000a0000 - 00000000:000e0000
(XEN) HVM5: [02]: 00000000:000e0000 - 00000000:00100000: RESERVED
(XEN) HVM5: [03]: 00000000:00100000 - 00000000:7f800000: RAM
(XEN) HVM5: HOLE: 00000000:7f800000 - 00000000:fc000000
(XEN) HVM5: [04]: 00000000:fc000000 - 00000001:00000000: RESERVED
(XEN) HVM5: Invoking ROMBIOS ...
(XEN) HVM5: $Revision: 1.221 $ $Date: 2008/12/07 17:32:29 $
(XEN) stdvga.c:147:d5 entering stdvga and caching modes
(XEN) HVM5: VGABios $Id: vgabios.c,v 1.67 2008/01/27 09:44:12 vruppert Exp $
(XEN) HVM5: Bochs BIOS - build: 06/23/99
(XEN) HVM5: $Revision: 1.221 $ $Date: 2008/12/07 17:32:29 $
(XEN) HVM5: Options: apmbios pcibios eltorito PMM
(XEN) HVM5:
(XEN) HVM5: ata0-0: PCHS=16383/16/63 translation=lba LCHS=1024/255/63
(XEN) HVM5: ata0 master: QEMU HARDDISK ATA-7 Hard-Disk (8192 MBytes)
(XEN) HVM5: IDE time out
(XEN) HVM5:
(XEN) HVM5:
(XEN) HVM5:
(XEN) HVM5: Press F12 for boot menu.
(XEN) HVM5:
(XEN) HVM5: Booting from Hard Disk...
(XEN) HVM5: Booting from 0000:7c00
(XEN) HVM5: int13_harddisk: function 41, unmapped device for ELDL=81
(XEN) HVM5: int13_harddisk: function 08, unmapped device for ELDL=81
(XEN) HVM5: *** int 15h function AX=00c0, BX=0000 not yet supported!
(XEN) HVM5: *** int 15h function AX=ec00, BX=0002 not yet supported!
(XEN) HVM5: KBD: unsupported int 16h function 03
(XEN) HVM5: *** int 15h function AX=e980, BX=0000 not yet supported!
(XEN) HVM5: int13_harddisk: function 41, unmapped device for ELDL=81
(XEN) HVM5: int13_harddisk: function 02, unmapped device for ELDL=81
(XEN) HVM5: int13_harddisk: function 41, unmapped device for ELDL=82
(XEN) HVM5: int13_harddisk: function 02, unmapped device for ELDL=82
(XEN) HVM5: int13_harddisk: function 41, unmapped device for ELDL=83
(XEN) HVM5: int13_harddisk: function 02, unmapped device for ELDL=83
(XEN) HVM5: int13_harddisk: function 41, unmapped device for ELDL=84
(XEN) HVM5: int13_harddisk: function 02, unmapped device for ELDL=84
(XEN) HVM5: int13_harddisk: function 41, unmapped device for ELDL=85
(XEN) HVM5: int13_harddisk: function 02, unmapped device for ELDL=85
(XEN) HVM5: int13_harddisk: function 41, unmapped device for ELDL=86
(XEN) HVM5: int13_harddisk: function 02, unmapped device for ELDL=86
(XEN) HVM5: int13_harddisk: function 41, unmapped device for ELDL=87
(XEN) HVM5: int13_harddisk: function 02, unmapped device for ELDL=87
(XEN) HVM5: int13_harddisk: function 41, ELDL out of range 88
(XEN) HVM5: int13_harddisk: function 02, ELDL out of range 88
(XEN) HVM5: int13_harddisk: function 41, ELDL out of range 89
(XEN) HVM5: int13_harddisk: function 02, ELDL out of range 89
(XEN) HVM5: int13_harddisk: function 41, ELDL out of range 8a
(XEN) HVM5: int13_harddisk: function 02, ELDL out of range 8a
(XEN) HVM5: int13_harddisk: function 41, ELDL out of range 8b
(XEN) HVM5: int13_harddisk: function 02, ELDL out of range 8b
(XEN) HVM5: int13_harddisk: function 41, ELDL out of range 8c
(XEN) HVM5: int13_harddisk: function 02, ELDL out of range 8c
(XEN) HVM5: int13_harddisk: function 41, ELDL out of range 8d
(XEN) HVM5: int13_harddisk: function 02, ELDL out of range 8d
(XEN) HVM5: int13_harddisk: function 41, ELDL out of range 8e
(XEN) HVM5: int13_harddisk: function 02, ELDL out of range 8e
(XEN) HVM5: int13_harddisk: function 41, ELDL out of range 8f
(XEN) HVM5: int13_harddisk: function 02, ELDL out of range 8f
[ 470.161311] xenbr0: port 3(vif5.0-emu) entered disabled state
[ 470.161634] device vif5.0-emu left promiscuous mode
[ 470.161639] xenbr0: port 3(vif5.0-emu) entered disabled state
(XEN) irq.c:375: Dom5 callback via changed to Direct Vector 0xe9
(XEN) irq.c:270: Dom5 PCI link 0 changed 5 -> 0
(XEN) irq.c:270: Dom5 PCI link 1 changed 10 -> 0
(XEN) irq.c:270: Dom5 PCI link 2 changed 11 -> 0
(XEN) irq.c:270: Dom5 PCI link 3 changed 5 -> 0
[ 475.900305] IPv6: ADDRCONF(NETDEV_CHANGE): vif5.0: link becomes ready
[ 475.900456] xenbr0: port 2(vif5.0) entered listening state
[ 475.900486] xenbr0: port 2(vif5.0) entered listening state
[ 490.893942] xenbr0: port 2(vif5.0) entered learning state
[ 504.147517] xenbr0: port 2(vif5.0) entered disabled state
[ 504.148144] device vif5.0 left promiscuous mode
[ 504.148161] xenbr0: port 2(vif5.0) entered disabled state
[ 521.612168] device vif6.0 entered promiscuous mode
[ 521.619208] IPv6: ADDRCONF(NETDEV_UP): vif6.0: link is not ready
[ 521.828684] device vif6.0-emu entered promiscuous mode
[ 521.834800] xenbr0: port 3(vif6.0-emu) entered listening state
[ 521.834857] xenbr0: port 3(vif6.0-emu) entered listening state
(XEN) HVM6: HVM Loader
(XEN) HVM6: Detected Xen v4.3-unstable
(XEN) HVM6: Xenbus rings @0xfeffc000, event channel 18
(XEN) HVM6: System requested ROMBIOS
(XEN) HVM6: CPU speed is 2793 MHz
(XEN) irq.c:270: Dom6 PCI link 0 changed 0 -> 5
(XEN) HVM6: PCI-ISA link 0 routed to IRQ5
(XEN) irq.c:270: Dom6 PCI link 1 changed 0 -> 10
(XEN) HVM6: PCI-ISA link 1 routed to IRQ10
(XEN) irq.c:270: Dom6 PCI link 2 changed 0 -> 11
(XEN) HVM6: PCI-ISA link 2 routed to IRQ11
(XEN) irq.c:270: Dom6 PCI link 3 changed 0 -> 5
(XEN) HVM6: PCI-ISA link 3 routed to IRQ5
(XEN) HVM6: pci dev 01:3 INTA->IRQ10
(XEN) HVM6: pci dev 03:0 INTA->IRQ5
(XEN) HVM6: pci dev 04:0 INTA->IRQ5
(XEN) HVM6: pci dev 02:0 bar 10 size lx: 02000000
(XEN) HVM6: pci dev 03:0 bar 14 size lx: 01000000
(XEN) HVM6: pci dev 02:0 bar 14 size lx: 00001000
(XEN) HVM6: pci dev 03:0 bar 10 size lx: 00000100
(XEN) HVM6: pci dev 04:0 bar 10 size lx: 00000100
(XEN) HVM6: pci dev 04:0 bar 14 size lx: 00000100
(XEN) HVM6: pci dev 01:1 bar 20 size lx: 00000010
(XEN) HVM6: Multiprocessor initialisation:
(XEN) HVM6: - CPU0 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM6: - CPU1 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM6: - CPU2 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM6: - CPU3 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM6: - CPU4 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM6: - CPU5 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM6: - CPU6 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM6: - CPU7 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM6: - CPU8 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM6: - CPU9 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM6: - CPU10 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM6: - CPU11 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM6: - CPU12 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM6: - CPU13 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM6: - CPU14 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM6: - CPU15 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM6: Testing HVM environment:
(XEN) HVM6: - REP INSB across page boundaries ... passed
(XEN) HVM6: - GS base MSRs and SWAPGS ... passed
(XEN) HVM6: Passed 2 of 2 tests
(XEN) HVM6: Writing SMBIOS tables ...
(XEN) HVM6: Loading ROMBIOS ...
(XEN) HVM6: 9628 bytes of ROMBIOS high-memory extensions:
(XEN) HVM6: Relocating to 0xfc001000-0xfc00359c ... done
(XEN) HVM6: Creating MP tables ...
(XEN) HVM6: Loading Cirrus VGABIOS ...
(XEN) HVM6: Loading PCI Option ROM ...
(XEN) HVM6: - Manufacturer: http://ipxe.org
(XEN) HVM6: - Product name: iPXE
(XEN) HVM6: Option ROMs:
(XEN) HVM6: c0000-c8fff: VGA BIOS
(XEN) HVM6: c9000-d8fff: Etherboot ROM
(XEN) HVM6: Loading ACPI ...
(XEN) HVM6: vm86 TSS at fc015180
(XEN) HVM6: BIOS map:
(XEN) HVM6: f0000-fffff: Main BIOS
(XEN) HVM6: E820 table:
(XEN) HVM6: [00]: 00000000:00000000 - 00000000:0009e000: RAM
(XEN) HVM6: [01]: 00000000:0009e000 - 00000000:000a0000: RESERVED
(XEN) HVM6: HOLE: 00000000:000a0000 - 00000000:000e0000
(XEN) HVM6: [02]: 00000000:000e0000 - 00000000:00100000: RESERVED
(XEN) HVM6: [03]: 00000000:00100000 - 00000000:7f800000: RAM
(XEN) HVM6: HOLE: 00000000:7f800000 - 00000000:fc000000
(XEN) HVM6: [04]: 00000000:fc000000 - 00000001:00000000: RESERVED
(XEN) HVM6: Invoking ROMBIOS ...
(XEN) HVM6: $Revision: 1.221 $ $Date: 2008/12/07 17:32:29 $
(XEN) stdvga.c:147:d6 entering stdvga and caching modes
(XEN) HVM6: VGABios $Id: vgabios.c,v 1.67 2008/01/27 09:44:12 vruppert Exp $
(XEN) HVM6: Bochs BIOS - build: 06/23/99
(XEN) HVM6: $Revision: 1.221 $ $Date: 2008/12/07 17:32:29 $
(XEN) HVM6: Options: apmbios pcibios eltorito PMM
(XEN) HVM6:
(XEN) HVM6: ata0-0: PCHS=16383/16/63 translation=lba LCHS=1024/255/63
(XEN) HVM6: ata0 master: QEMU HARDDISK ATA-7 Hard-Disk (8192 MBytes)
(XEN) HVM6: IDE time out
(XEN) HVM6:
(XEN) HVM6:
(XEN) HVM6:
(XEN) HVM6: Press F12 for boot menu.
(XEN) HVM6:
(XEN) HVM6: Booting from Hard Disk...
(XEN) HVM6: Booting from 0000:7c00
(XEN) HVM6: int13_harddisk: function 41, unmapped device for ELDL=81
(XEN) HVM6: int13_harddisk: function 08, unmapped device for ELDL=81
(XEN) HVM6: *** int 15h function AX=00c0, BX=0000 not yet supported!
[ 536.855164] xenbr0: port 3(vif6.0-emu) entered learning state
(XEN) HVM6: *** int 15h function AX=ec00, BX=0002 not yet supported!
(XEN) HVM6: KBD: unsupported int 16h function 03
(XEN) HVM6: *** int 15h function AX=e980, BX=0000 not yet supported!
(XEN) HVM6: int13_harddisk: function 41, unmapped device for ELDL=81
(XEN) HVM6: int13_harddisk: function 02, unmapped device for ELDL=81
(XEN) HVM6: int13_harddisk: function 41, unmapped device for ELDL=82
(XEN) HVM6: int13_harddisk: function 02, unmapped device for ELDL=82
(XEN) HVM6: int13_harddisk: function 41, unmapped device for ELDL=83
(XEN) HVM6: int13_harddisk: function 02, unmapped device for ELDL=83
(XEN) HVM6: int13_harddisk: function 41, unmapped device for ELDL=84
(XEN) HVM6: int13_harddisk: function 02, unmapped device for ELDL=84
(XEN) HVM6: int13_harddisk: function 41, unmapped device for ELDL=85
(XEN) HVM6: int13_harddisk: function 02, unmapped device for ELDL=85
(XEN) HVM6: int13_harddisk: function 41, unmapped device for ELDL=86
(XEN) HVM6: int13_harddisk: function 02, unmapped device for ELDL=86
(XEN) HVM6: int13_harddisk: function 41, unmapped device for ELDL=87
(XEN) HVM6: int13_harddisk: function 02, unmapped device for ELDL=87
(XEN) HVM6: int13_harddisk: function 41, ELDL out of range 88
(XEN) HVM6: int13_harddisk: function 02, ELDL out of range 88
(XEN) HVM6: int13_harddisk: function 41, ELDL out of range 89
(XEN) HVM6: int13_harddisk: function 02, ELDL out of range 89
(XEN) HVM6: int13_harddisk: function 41, ELDL out of range 8a
(XEN) HVM6: int13_harddisk: function 02, ELDL out of range 8a
(XEN) HVM6: int13_harddisk: function 41, ELDL out of range 8b
(XEN) HVM6: int13_harddisk: function 02, ELDL out of range 8b
(XEN) HVM6: int13_harddisk: function 41, ELDL out of range 8c
(XEN) HVM6: int13_harddisk: function 02, ELDL out of range 8c
(XEN) HVM6: int13_harddisk: function 41, ELDL out of range 8d
(XEN) HVM6: int13_harddisk: function 02, ELDL out of range 8d
(XEN) HVM6: int13_harddisk: function 41, ELDL out of range 8e
(XEN) HVM6: int13_harddisk: function 02, ELDL out of range 8e
(XEN) HVM6: int13_harddisk: function 41, ELDL out of range 8f
(XEN) HVM6: int13_harddisk: function 02, ELDL out of range 8f
[ 540.118328] xenbr0: port 3(vif6.0-emu) entered disabled state
[ 540.118895] device vif6.0-emu left promiscuous mode
[ 540.118911] xenbr0: port 3(vif6.0-emu) entered disabled state
(XEN) irq.c:375: Dom6 callback via changed to Direct Vector 0xe9
(XEN) irq.c:270: Dom6 PCI link 0 changed 5 -> 0
(XEN) irq.c:270: Dom6 PCI link 1 changed 10 -> 0
(XEN) irq.c:270: Dom6 PCI link 2 changed 11 -> 0
(XEN) irq.c:270: Dom6 PCI link 3 changed 5 -> 0
[ 546.684649] IPv6: ADDRCONF(NETDEV_CHANGE): vif6.0: link becomes ready
[ 546.684775] xenbr0: port 2(vif6.0) entered listening state
[ 546.684806] xenbr0: port 2(vif6.0) entered listening state
[ 561.706561] xenbr0: port 2(vif6.0) entered learning state
[ 576.739016] xenbr0: topology change detected, sending tcn bpdu
[ 576.739075] xenbr0: port 2(vif6.0) entered forwarding state
[ 717.094846] xenbr0: port 2(vif6.0) entered disabled state
[ 717.095523] device vif6.0 left promiscuous mode
[ 717.095541] xenbr0: port 2(vif6.0) entered disabled state
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) *** Serial input -> Xen (type 'CTRL-a' three times to switch input to DOM0)
[ 730.424559] Broke affinity for irq 203
[ 730.427900] Broke affinity for irq 206
[ 730.445773] Broke affinity for irq 209
[ 732.389288] installing Xen timer for CPU 3
[ 732.389351] cpu 3 spinlock event irq 96
[ 732.391656] ------------[ cut here ]------------
[ 732.391674] WARNING: at kernel/time/tick-sched.c:935 tick_nohz_idle_exit+0x1b7/0x1d0()
[ 732.391679] Modules linked in: nfsv3 nfs_acl auth_rpcgss oid_registry nfsv4 nfs lockd xen_acpi_processor xen_blkback xen_gntalloc sunrpc fcoe libfcoe libfc scsi_transport_fc sg igb ehci_pci ehci_hcd ixgbe mdio ext4 jbd2 mbcache sd_mod sr_mod cdrom ahci libahci libata scsi_mod
[ 732.391749] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 3.10.0-rc3 #1
[ 732.391754] Hardware name: Intel Corporation S2600CP/S2600CP, BIOS RMLSDP.86I.R2.21.D636.1301031557 01/03/2013
[ 732.391760] ffffffff8197807a ffff880100613e60 ffffffff816cd9b8 ffff880100613ea0
[ 732.391771] ffffffff810a0d6b 000000000000e030 ffff880106a6e2c0 ffff880100612010
[ 732.391781] 0000000000000003 ffff880100612000 ffff880100612010 ffff880100613eb0
[ 732.391791] Call Trace:
[ 732.391803] [<ffffffff816cd9b8>] dump_stack+0x19/0x21
[ 732.391813] [<ffffffff810a0d6b>] warn_slowpath_common+0x6b/0xa0
[ 732.391820] [<ffffffff810a0db5>] warn_slowpath_null+0x15/0x20
[ 732.391826] [<ffffffff810ee827>] tick_nohz_idle_exit+0x1b7/0x1d0
[ 732.391835] [<ffffffff810e4795>] cpu_startup_entry+0x175/0x260
[ 732.391844] [<ffffffff816be8f6>] cpu_bringup_and_idle+0x13/0x15
[ 732.391849] ---[ end trace 948f64ae14939722 ]---
[ 732.398855] installing Xen timer for CPU 2
[ 732.398908] cpu 2 spinlock event irq 103
[ 732.402592] installing Xen timer for CPU 12
[ 732.402657] cpu 12 spinlock event irq 110
[ 732.405743] installing Xen timer for CPU 4
[ 732.405812] cpu 4 spinlock event irq 117
[ 732.408153] BUG: unable to handle kernel NULL pointer dereference at 0000000000000004
[ 732.408181] IP: [<ffffffff810d9f50>] update_sd_lb_stats+0x2c0/0x6c0
[ 732.408195] PGD a9473067 PUD aa18f067 PMD 0
[ 732.408234] Oops: 0000 [#1] SMP
[ 732.408248] Modules linked in: nfsv3 nfs_acl auth_rpcgss oid_registry nfsv4 nfs lockd xen_acpi_processor xen_blkback xen_gntalloc sunrpc fcoe libfcoe libfc scsi_transport_fc sg igb ehci_pci ehci_hcd ixgbe mdio ext4 jbd2 mbcache sd_mod sr_mod cdrom ahci libahci libata scsi_mod
[ 732.408405] CPU: 2 PID: 10864 Comm: gpk-update-icon Tainted: G W 3.10.0-rc3 #1
[ 732.408414] Hardware name: Intel Corporation S2600CP/S2600CP, BIOS RMLSDP.86I.R2.21.D636.1301031557 01/03/2013
[ 732.408420] task: ffff8800aa2dcba0 ti: ffff8800b28d6000 task.ti: ffff8800b28d6000
[ 732.408432] RIP: e030:[<ffffffff810d9f50>] [<ffffffff810d9f50>] update_sd_lb_stats+0x2c0/0x6c0
[ 732.408449] RSP: e02b:ffff8800b28d7698 EFLAGS: 00010046
[ 732.408459] RAX: 0000000000000040 RBX: 0000000000013d00 RCX: 0000000000000000
[ 732.408465] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff8800b3651e60
[ 732.408476] RBP: ffff8800b28d7798 R08: 0000000000000000 R09: 0000000000000040
[ 732.408485] R10: 0000000000000000 R11: 000000000018c800 R12: 0000000000000040
[ 732.408493] R13: ffffffffffffffff R14: 0000000000000000 R15: 0000000000000000
[ 732.408502] FS: 00007f7ac9394920(0000) GS:ffff880106a40000(0000) knlGS:0000000000000000
[ 732.408536] CS: e033 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 732.408541] CR2: 0000000000000004 CR3: 00000000aad38000 CR4: 0000000000042660
[ 732.408553] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 732.408564] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 732.408574] Stack:
[ 732.408581] 0000000000000003 0000000000000001 ffff8800b28d7974 0000000000000200
[ 732.408608] 00000000a1659680 ffff8800b28d7728 fffffffffffffff8 ffffffff00000020
[ 732.408625] 0000000000000200 0000000000013d00 00000000b28d7728 ffff8800b28d77a8
[ 732.408642] Call Trace:
[ 732.408655] [<ffffffff810dd6a1>] find_busiest_group+0x31/0x4d0
[ 732.408669] [<ffffffff810ddc40>] load_balance+0x100/0x870
[ 732.408678] [<ffffffff810de7e9>] idle_balance+0xe9/0x150
[ 732.408687] [<ffffffff816cf8ed>] __schedule+0x7ad/0x8a0
[ 732.408701] [<ffffffff816cfc04>] schedule+0x24/0x70
[ 732.408717] [<ffffffff816ce8b1>] schedule_hrtimeout_range_clock+0xb1/0x140
[ 732.408739] [<ffffffff810ca510>] ? update_rmtp+0x80/0x80
[ 732.408779] [<ffffffff810cb80f>] ? hrtimer_start_range_ns+0xf/0x20
[ 732.408784] [<ffffffff816ce94e>] schedule_hrtimeout_range+0xe/0x10
[ 732.408791] [<ffffffff811b4464>] poll_schedule_timeout+0x44/0x60
[ 732.408795] [<ffffffff811b543b>] do_sys_poll+0x49b/0x520
[ 732.408802] [<ffffffff811b4630>] ? __pollwait+0xf0/0xf0
[ 732.408807] [<ffffffff811b4630>] ? __pollwait+0xf0/0xf0
[ 732.408813] [<ffffffff811b4630>] ? __pollwait+0xf0/0xf0
[ 732.408816] [<ffffffff811b4630>] ? __pollwait+0xf0/0xf0
[ 732.408821] [<ffffffff811b4630>] ? __pollwait+0xf0/0xf0
[ 732.408825] [<ffffffff811b4630>] ? __pollwait+0xf0/0xf0
[ 732.408831] [<ffffffff811b4630>] ? __pollwait+0xf0/0xf0
[ 732.408837] [<ffffffff811b4630>] ? __pollwait+0xf0/0xf0
[ 732.408839] [<ffffffff811b4630>] ? __pollwait+0xf0/0xf0
[ 732.408842] [<ffffffff810c78a0>] ? wake_up_bit+0x40/0x40
[ 732.408850] [<ffffffff81056140>] ? xen_clocksource_read+0x20/0x30
[ 732.408853] [<ffffffff810562d9>] ? xen_clocksource_get_cycles+0x9/0x10
[ 732.408856] [<ffffffff810e67a7>] ? ktime_get_ts+0x47/0xf0
[ 732.408859] [<ffffffff811b440d>] ? poll_select_set_timeout+0x8d/0xa0
[ 732.408861] [<ffffffff811b552c>] SyS_poll+0x6c/0x100
[ 732.408866] [<ffffffff816d9c69>] system_call_fastpath+0x16/0x1b
[ 732.408916] Code: c8 48 0f 42 c1 e9 3a ff ff ff 90 8b b5 7c ff ff ff 4d 89 f0 85 f6 0f 85 8f 01 00 00 48 8b bd 60 ff ff ff 48 8b 57 10 48 8b 75 98 <8b> 4a 04 31 d2 48 89 f0 48 c1 e0 0a 48 f7 f1 48 8b 4d a0 48 85
[ 732.408921] RIP [<ffffffff810d9f50>] update_sd_lb_stats+0x2c0/0x6c0
[ 732.408923] RSP <ffff8800b28d7698>
[ 732.408927] CR2: 0000000000000004
[ 732.409327] ---[ end trace 948f64ae14939723 ]---
[ 732.409341] BUG: unable to handle kernel paging request at 0000007b0000000a
[ 732.409345] IP: [<ffffffff810d9457>] select_task_rq_fair+0x327/0x850
[ 732.409353] PGD a230e067 PUD 0
[ 732.409356] Oops: 0000 [#2] SMP
[ 732.409418] Modules linked in: nfsv3 nfs_acl auth_rpcgss oid_registry nfsv4 nfs lockd xen_acpi_processor xen_blkback xen_gntalloc sunrpc fcoe libfcoe libfc scsi_transport_fc sg igb ehci_pci ehci_hcd ixgbe mdio ext4 jbd2 mbcache sd_mod sr_mod cdrom ahci libahci libata scsi_mod
[ 732.409426] CPU: 3 PID: 13715 Comm: kdump Tainted: G D W 3.10.0-rc3 #1
[ 732.409427] Hardware name: Intel Corporation S2600CP/S2600CP, BIOS RMLSDP.86I.R2.21.D636.1301031557 01/03/2013
[ 732.409429] task: ffff8800a70b9e40 ti: ffff880002b90000 task.ti: ffff880002b90000
[ 732.409432] RIP: e030:[<ffffffff810d9457>] [<ffffffff810d9457>] select_task_rq_fair+0x327/0x850
[ 732.409437] RSP: e02b:ffff880002b91da0 EFLAGS: 00010006
[ 732.409439] RAX: 000000000058a400 RBX: 0000000000001629 RCX: 000000000000000f
[ 732.409445] RDX: 0000007b00000006 RSI: 0000000000000040 RDI: 0000000000000040
[ 732.409446] RBP: ffff880002b91e80 R08: ffff8800b3651238 R09: 0000000000000000
[ 732.409447] R10: 0000000000000000 R11: 0001f8f457d6ca7b R12: ffff8800b3651238
[ 732.409453] R13: 0000000000000000 R14: ffff8800b3651220 R15: 0000000000000000
[ 732.409459] FS: 00007fda57aba700(0000) GS:ffff880106a60000(0000) knlGS:0000000000000000
[ 732.409461] CS: e033 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 732.409466] CR2: 0000007b0000000a CR3: 00000000ac80a000 CR4: 0000000000042660
[ 732.409468] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 732.409470] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 732.409474] Stack:
[ 732.409479] ffff880002b91e20 ffffffff810c3756 0000000000000000 ffff8800b2ce4578
[ 732.409487] 0000000000013d00 0000000000013d00 ffff8801003b3e90 000000000000007d
[ 732.409499] ffff8800b3651900 00000000000004a5 0000000000013d00 0000000000013cf8
[ 732.409500] Call Trace:
[ 732.409507] [<ffffffff810c3756>] ? alloc_pid+0x456/0x540
[ 732.409516] [<ffffffff810d72d7>] wake_up_new_task+0x37/0x180
[ 732.409525] [<ffffffff81056140>] ? xen_clocksource_read+0x20/0x30
[ 732.409535] [<ffffffff810a043e>] do_fork+0x9e/0x2b0
[ 732.409541] [<ffffffff810b4891>] ? __set_current_blocked+0x61/0x80
[ 732.409544] [<ffffffff810a0661>] SyS_clone+0x11/0x20
[ 732.409547] [<ffffffff816d9fc9>] stub_clone+0x69/0x90
[ 732.409549] [<ffffffff816d9c69>] ? system_call_fastpath+0x16/0x1b
[ 732.409647] Code: 48 8b 55 c0 4d 8b 36 4c 3b 72 10 74 43 48 89 45 b0 e9 7e fe ff ff 66 0f 1f 44 00 00 4c 8b 75 88 48 89 d8 48 c1 e0 0a 49 8b 56 10 <8b> 4a 04 31 d2 48 f7 f1 45 85 ff 74 64 48 8b 55 c0 48 89 85 68
[ 732.409656] RIP [<ffffffff810d9457>] select_task_rq_fair+0x327/0x850
[ 732.409658] RSP <ffff880002b91da0>
[ 732.409659] CR2: 0000007b0000000a
[ 732.409667] ---[ end trace 948f64ae14939724 ]---
[ 732.409706] BUG: unable to handle kernel paging request at 0000007b0000000a
[ 732.409730] IP: [<ffffffff810d9457>] select_task_rq_fair+0x327/0x850
[ 732.409741] PGD 0
[ 732.409764] Oops: 0000 [#3] SMP
[ 732.410034] Modules linked in: nfsv3 nfs_acl auth_rpcgss oid_registry nfsv4 nfs lockd xen_acpi_processor xen_blkback xen_gntalloc sunrpc fcoe libfcoe libfc scsi_transport_fc sg igb ehci_pci ehci_hcd ixgbe mdio ext4 jbd2 mbcache sd_mod sr_mod cdrom ahci libahci libata scsi_mod
[ 732.410047] CPU: 12 PID: 13718 Comm: udevd Tainted: G D W 3.10.0-rc3 #1
[ 732.410067] Hardware name: Intel Corporation S2600CP/S2600CP, BIOS RMLSDP.86I.R2.21.D636.1301031557 01/03/2013
[ 732.410075] task: ffff880100063c80 ti: ffff8800b32f0000 task.ti: ffff8800b32f0000
[ 732.410092] RIP: e030:[<ffffffff810d9457>] [<ffffffff810d9457>] select_task_rq_fair+0x327/0x850
[ 732.410103] RSP: e02b:ffff8800b32f1da0 EFLAGS: 00010006
[ 732.410118] RAX: 000000000058a400 RBX: 0000000000001629 RCX: 000000000000000f
[ 732.410137] RDX: 0000007b00000006 RSI: 0000000000000040 RDI: 0000000000000040
[ 732.410160] RBP: ffff8800b32f1e80 R08: ffff8800b3651238 R09: 0000000000000000
[ 732.410169] R10: 0000000000000000 R11: 0001f8f457d2ca7c R12: ffff8800b3651238
[ 732.410183] R13: 0000000000000000 R14: ffff8800b3651220 R15: 00000000ffffffff
[ 732.410196] FS: 00007fdf1b95a7a0(0000) GS:ffff880106b80000(0000) knlGS:0000000000000000
[ 732.410213] CS: e033 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 732.410222] CR2: 0000007b0000000a CR3: 00000000b5a10000 CR4: 0000000000042660
[ 732.410239] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 732.410256] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 732.410275] Stack:
[ 732.410332] ffff8800b32f1e20 ffffffff810c3756 0000000000000000 ffff8800b2f47638
[ 732.410357] 0000000000013d00 0000000000013d00 ffff8800b1707380 000000000000007d
[ 732.410382] 0000000000000000 0000000000000000 0000000000013d00 0000000000013cf8
[ 732.410388] Call Trace:
[ 732.410413] [<ffffffff810c3756>] ? alloc_pid+0x456/0x540
[ 732.410437] [<ffffffff810d72d7>] wake_up_new_task+0x37/0x180
[ 732.410454] [<ffffffff811c08b4>] ? mntput_no_expire+0x44/0x150
[ 732.410473] [<ffffffff810a043e>] do_fork+0x9e/0x2b0
[ 732.410493] [<ffffffff811ac901>] ? final_putname+0x21/0x50
[ 732.410512] [<ffffffff811acaf6>] ? putname+0x26/0x40
[ 732.410526] [<ffffffff810a0661>] SyS_clone+0x11/0x20
[ 732.410541] [<ffffffff816d9fc9>] stub_clone+0x69/0x90
[ 732.410561] [<ffffffff816d9c69>] ? system_call_fastpath+0x16/0x1b
[ 732.410581] Code: 48 8b 55 c0 4d 8b 36 4c 3b 72 10 74 43 48 89 45 b0 e9 7e fe ff ff 66 0f 1f 44 00 00 4c 8b 75 88 48 89 d8 48 c1 e0 0a 49 8b 56 10 <8b> 4a 04 31 d2 48 f7 f1 45 85 ff 74 64 48 8b 55 c0 48 89 85 68
[ 732.411159] RIP [<ffffffff810d9457>] select_task_rq_fair+0x327/0x850
[ 732.411204] RSP <ffff8800b32f1da0>
[ 732.411225] CR2: 0000007b0000000a
[ 732.411260] ---[ end trace 948f64ae14939725 ]---
[ 732.411639] BUG: unable to handle kernel NULL pointer dereference at 0000000000000004
[ 732.411661] IP: [<ffffffff810d9f50>] update_sd_lb_stats+0x2c0/0x6c0
[ 732.411701] PGD 0
[ 732.411708] Oops: 0000 [#4] [ 732.411711] installing Xen timer for CPU 11
[ 732.411719] Modules linked in: nfsv3 nfs_acl auth_rpcgss oid_registry nfsv4 nfs lockd xen_acpi_processor xen_blkback xen_gntalloc sunrpc fcoe libfcoe libfc scsi_transport_fc sg igb ehci_pci ehci_hcd ixgbe mdio ext4 jbd2 mbcache sd_mod sr_mod cdrom ahci libahci libata scsi_mod
[ 732.411773] CPU: 3 PID: 9897 Comm: rs:main Q:Reg Tainted: G D W 3.10.0-rc3 #1
[ 732.411775] Hardware name: Intel Corporation S2600CP/S2600CP, BIOS RMLSDP.86I.R2.21.D636.1301031557 01/03/2013
[ 732.411776] task: ffff8800aeb369e0 ti: ffff8800b593e000 task.ti: ffff8800b593e000
[ 732.411778] RIP: e030:[<ffffffff810d9f50>] [<ffffffff810d9f50>] update_sd_lb_stats+0x2c0/0x6c0
[ 732.411783] RSP: e02b:ffff8800b593f868 EFLAGS: 00010046
[ 732.411788] RAX: 0000000000000040 RBX: 0000000000013d00 RCX: 0000000000000000
[ 732.411792] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff8800b3651e60
[ 732.411793] RBP: ffff8800b593f968 R08: 0000000000000000 R09: 0000000000000040
[ 732.411794] R10: 0000000000000000 R11: 00000000001b8800 R12: 0000000000000040
[ 732.411795] R13: ffffffffffffffff R14: 0000000000000000 R15: 0000000000000000
[ 732.411801] FS: 00007ffc9fa03700(0000) GS:ffff880106a60000(0000) knlGS:0000000000000000
[ 732.411806] CS: e033 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 732.411810] CR2: 0000000000000004 CR3: 00000000a8d3c000 CR4: 0000000000042660
[ 732.411813] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 732.411814] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 732.411815] Stack:
[ 732.411816] 0000000000000003 0000000000000000 ffff8800b593fb44 0000000000000200
[ 732.411821] 00000000b09d4a68 ffff8800b593f8f8 fffffffffffffff8 ffffffff000621e6
[ 732.411829] 0000000000000200 0000000000013d00 00000000aeb369e0 ffff8800b593f978
[ 732.411833] Call Trace:
[ 732.411836] [<ffffffff810dd6a1>] find_busiest_group+0x31/0x4d0
[ 732.411840] [<ffffffff810ddc40>] load_balance+0x100/0x870
[ 732.411845] [<ffffffff810de7e9>] idle_balance+0xe9/0x150
[ 732.411849] [<ffffffff816cf8ed>] __schedule+0x7ad/0x8a0
[ 732.411854] [<ffffffff816cfc04>] schedule+0x24/0x70
[ 732.411859] [<ffffffff810f08ae>] futex_wait_queue_me+0xce/0x110
[ 732.411864] [<ffffffff810f0a87>] futex_wait+0x197/0x2a0
[ 732.411869] [<ffffffffa00d110b>] ? ext4_file_write+0x5b/0x420 [ext4]
[ 732.411881] [<ffffffff811ac901>] ? final_putname+0x21/0x50
[ 732.411887] [<ffffffff810f2195>] do_futex+0xe5/0xc50
[ 732.411895] [<ffffffff811e0e3d>] ? fsnotify+0x1cd/0x2f0
[ 732.411902] [<ffffffff811a0afa>] ? do_sync_write+0x7a/0xb0
[ 732.411909] [<ffffffff810f2d78>] SyS_futex+0x78/0x170
[ 732.411913] [<ffffffff811a149c>] ? SyS_write+0x8c/0xa0
[ 732.411918] [<ffffffff816d9c69>] system_call_fastpath+0x16/0x1b
[ 732.411922] Code: c8 48 0f 42 c1 e9 3a ff ff ff 90 8b b5 7c ff ff ff 4d 89 f0 85 f6 0f 85 8f 01 00 00 48 8b bd 60 ff ff ff 48 8b 57 10 48 8b 75 98 <8b> 4a 04 31 d2 48 89 f0 48 c1 e0 0a 48 f7 f1 48 8b 4d a0 48 85
[ 732.412036] RIP [<ffffffff810d9f50>] update_sd_lb_stats+0x2c0/0x6c0
[ 732.412041] RSP <ffff8800b593f868>
[ 732.412043] CR2: 0000000000000004
[ 732.412050] ---[ end trace 948f64ae14939726 ]---
[ 732.412066] BUG: unable to handle kernel paging request at 0000007b0000000a
[ 732.412099] IP: [<ffffffff810d9457>] select_task_rq_fair+0x327/0x850
[ 732.412120] PGD 0
[ 732.412135] Oops: 0000 [#5] SMP
[ 732.412156] Modules linked in: nfsv3 nfs_acl auth_rpcgss oid_registry nfsv4 nfs lockd xen_acpi_processor xen_blkback xen_gntalloc sunrpc fcoe libfcoe libfc scsi_transport_fc sg igb ehci_pci ehci_hcd ixgbe mdio ext4 jbd2 mbcache sd_mod sr_mod cdrom ahci libahci libata scsi_mod
[ 732.412370] CPU: 12 PID: 13721 Comm: udevd Tainted: G D W 3.10.0-rc3 #1
[ 732.412377] Hardware name: Intel Corporation S2600CP/S2600CP, BIOS RMLSDP.86I.R2.21.D636.1301031557 01/03/2013
[ 732.412385] task: ffff8801000616b0 ti: ffff8800a4ba0000 task.ti: ffff8800a4ba0000
[ 732.412393] RIP: e030:[<ffffffff810d9457>] [<ffffffff810d9457>] select_task_rq_fair+0x32(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) *** Serial input -> Xen (type 'CTRL-a' three times to switch input to DOM0)
[-- Attachment #4: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: test report for Xen 4.3 RC1
2013-06-04 15:59 Ren, Yongjie
@ 2013-06-04 16:35 ` Konrad Rzeszutek Wilk
0 siblings, 0 replies; 17+ messages in thread
From: Konrad Rzeszutek Wilk @ 2013-06-04 16:35 UTC (permalink / raw)
To: Ren, Yongjie
Cc: george.dunlap, Xu, YongweiX, Liu, SongtaoX, Tian, Yongxue, xen-devel
On Tue, Jun 04, 2013 at 03:59:33PM +0000, Ren, Yongjie wrote:
> Sorry for replying late. :-)
>
> > -----Original Message-----
> > From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]
> > Sent: Tuesday, May 28, 2013 11:16 PM
> > To: Ren, Yongjie; george.dunlap@eu.citrix.com
> > Cc: xen-devel@lists.xen.org; Xu, YongweiX; Liu, SongtaoX; Tian, Yongxue
> > Subject: Re: [Xen-devel] test report for Xen 4.3 RC1
> >
> > On Mon, May 27, 2013 at 03:49:27AM +0000, Ren, Yongjie wrote:
> > > Hi All,
> > > This is a report based on our testing for Xen 4.3.0 RC1 on Intel platforms.
> > > (Sorry it's a little late. :-) If the status changes, I'll have an update
> > later.)
> >
> > OK, I've some updates and ideas that can help with narrowing some of
> > these
> > issues down. Thank you for doing this.
> >
> > >
> > > Test environment:
> > > Xen: Xen 4.3 RC1 with qemu-upstream-unstable.git
> > > Dom0: Linux kernel 3.9.3
> >
> > Could you please test v3.10-rc3. There have been some changes
> > for the VCPU hotplug added in v3.10 that I am not sure whether
> > they are in v3.9?
> I didn't try every bug with v3.10.-rc3, but most of them still exist.
>
> > > Hardware: Intel Sandy Bridge, Ivy Bridge, Haswell systems
> > >
> > > Below are the features we tested.
> > > - PV and HVM guest booting (HVM: Ubuntu, Fedora, RHEL, Windows)
> > > - Save/Restore and live migration
> > > - PCI device assignment and SR-IOV
> > > - power management: C-state/P-state, Dom0 S3, HVM S3
> > > - AVX and XSAVE instruction set
> > > - MCE
> > > - CPU online/offline for Dom0
> > > - vCPU hot-plug
> > > - Nested Virtualization (Please look at my report in the following link.)
> > > http://lists.xen.org/archives/html/xen-devel/2013-05/msg01145.html
> > >
> > > New bugs (4): (some of which are not regressions)
> > > 1. sometimes failed to online cpu in Dom0
> > >
> > http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1851
> >
> > That looks like you are hitting the udev race.
> >
> > Could you verify that these patches:
> > https://lkml.org/lkml/2013/5/13/520
> >
> > fix the issue (They are destined for v3.11)
> >
> Not tried yet. I'll update it to you later.
Thanks!
>
> > > 2. dom0 call trace when running sriov hvm guest with igbvf
> > >
> > http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1852
> > > -- a regression in Linux kernel (Dom0).
> >
> > Hm, the call-trace you refer too:
> >
> > [ 68.404440] Already setup the GSI :37
> >
> > [ 68.405105] igb 0000:04:00.0: Enabling SR-IOV VFs using the module
> > parameter is deprecated - please use the pci sysfs interface.
> >
> > [ 68.506230] ------------[ cut here ]------------
> >
> > [ 68.506265] WARNING: at
> > /home/www/builds_xen_unstable/xen-src-27009-20130509/linux-2.6-pvop
> > s.git/fs/sysfs/dir.c:536 sysfs_add_one+0xcc/0xf0()
> >
> > [ 68.506279] Hardware name: S2600CP
> >
> > is a deprecated warning. Did you follow the 'pci sysfs' interface way?
> >
> > Looking at da36b64736cf2552e7fb5109c0255d4af804f5e7
> > ixgbe: Implement PCI SR-IOV sysfs callback operation
> > it says it is using this:
> >
> > commit 1789382a72a537447d65ea4131d8bcc1ad85ce7b
> > Author: Donald Dutile <ddutile@redhat.com>
> > Date: Mon Nov 5 15:20:36 2012 -0500
> >
> > PCI: SRIOV control and status via sysfs
> >
> > Provide files under sysfs to determine the maximum number of VFs
> > an SR-IOV-capable PCIe device supports, and methods to enable and
> > disable the VFs on a per-device basis.
> >
> > Currently, VF enablement by SR-IOV-capable PCIe devices is done
> > via driver-specific module parameters. If not setup in modprobe
> > files,
> > it requires admin to unload & reload PF drivers with number of desired
> > VFs to enable. Additionally, the enablement is system wide: all
> > devices controlled by the same driver have the same number of VFs
> > enabled. Although the latter is probably desired, there are PCI
> > configurations setup by system BIOS that may not enable that to
> > occur.
> >
> > Two files are created for the PF of PCIe devices with SR-IOV support:
> >
> > sriov_totalvfs Contains the maximum number of VFs the device
> > could support as reported by the TotalVFs
> > register
> > in the SR-IOV extended capability.
> >
> > sriov_numvfs Contains the number of VFs currently enabled
> > on
> > this device as reported by the NumVFs
> > register in
> > the SR-IOV extended capability.
> >
> > Writing zero to this file disables all VFs.
> >
> > Writing a positive number to this file enables
> > that
> > number of VFs.
> >
> > These files are readable for all SR-IOV PF devices. Writes to the
> > sriov_numvfs file are effective only if a driver that supports the
> > sriov_configure() method is attached.
> >
> > Signed-off-by: Donald Dutile <ddutile@redhat.com>
> >
> >
> > Can you try that please?
> >
> Recently, one of my workmates already had a fix as below.
> https://lkml.org/lkml/2013/5/30/20
> And, seems also already been fixed by another guy.
> https://patchwork.kernel.org/patch/2613481/
>
Great! Care to update the bug with said relevant information?
> >
> > > 3. Booting multiple guests will lead Dom0 call trace
> > >
> > http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1853
> >
> > That one worries me. Did you do a git bisect to figure out what
> > is commit is causing this?
> >
> I only found this bug on some Intel ~EX server.
> I don't know which version on Xen/Dom0 can work fine.
> If anyone want to reproduce or debug it, it should be good.
> And our team is trying to debug it internally first.
Ah, OK. Then please continue on debugging it. Thanks!
>
> > > 4. After live migration, guest console continuously prints "Clocksource
> > tsc unstable"
> > >
> > http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1854
> >
> > This looks like a current bug with QEMU unstable missing a ACPI table?
> >
> > Did you try booting the guest with the old QEMU?
> >
> > device_model_version = 'qemu-xen-traditional'
> >
> This issue still exists with traditional qemu-xen.
> After more testing, this bug can't reproduced by some other guests.
> RHEL6.4 guest will have this issue after live migration, while RHEL6.3 &
> Fedora 17 & Ubuntu 12.10 guests can work fine.
There is a recent thread on this where the culprit was the PV timeclock
not being updated correctly. But that would seem to be at odds with
your reporting - where you are using Fedora 17 and it works fine.
Hm, I am at loss on this one.
>
> > >
> > > Old bugs: (11)
> > > 1. [ACPI] Dom0 can't resume from S3 sleep
> > > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1707
> >
> > That should be fixed in v3.11 (as now we have the fixes)
> > Could you try v3.10 with the Rafael's ACPI tree merged in?
> > (so the patches that he wants to submit for v3.11)
> >
> I re-tested with Rafel's linux-pm.git tree (master and acpi-hotplug branch),
> and found Dom0 S3 sleep/resume can't work, either.
The patches he has to submit for v3.11 are in the linux-next branch.
You need to use that branch.
>
> > > 2. [XL]"xl vcpu-set" causes dom0 crash or panic
> > > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1730
> >
> > That I think is fixed in v3.10. Could you please check v3.10-rc3?
> >
> Still exists on v3.10-rc3.
> The following command lines can reproduce it:
> # xl vcpu-set 0 1
> # xl vcpu-set 0 20
Ugh, same exact stack trace? And can you attach the full dmesg or serial
output (so that Ican see what there is at bootup)
>
> > > 3. Sometimes Xen panic on ia32pae Sandybridge when restore guest
> > > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1747
> >
> > That looks to be with v2.6.32. Is the issue present with v3.9
> > or v3.10-rc3?
> >
> We didn't test ia32pae Xen for a long time.
> Now, we only cover ia32e Xen/Dom0.
> So, this bug is only a legacy issue.
> If we have effort to verify it, we'll update it in the bugzilla.
How about just dropping that bug as 'WONTFIX'.
>
> > > 4. 'xl vcpu-set' can't decrease the vCPU number of a HVM guest
> > > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1822
> >
> > That I believe was an QEMU bug:
> > http://lists.xen.org/archives/html/xen-devel/2013-05/msg01054.html
> >
> > which should be in QEMU traditional now (05-21 was when it went
> > in the tree)
> >
> In this year or past year, this bug always exists (at least in our testing).
> 'xl vcpu-set' can't decrease the vCPU number of a HVM guest
Could you retry with Xen 4.3 please?
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: test report for Xen 4.3 RC1
@ 2013-06-04 15:59 Ren, Yongjie
2013-06-04 16:35 ` Konrad Rzeszutek Wilk
0 siblings, 1 reply; 17+ messages in thread
From: Ren, Yongjie @ 2013-06-04 15:59 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk, george.dunlap
Cc: Xu, YongweiX, Liu, SongtaoX, Tian, Yongxue, xen-devel
Sorry for replying late. :-)
> -----Original Message-----
> From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]
> Sent: Tuesday, May 28, 2013 11:16 PM
> To: Ren, Yongjie; george.dunlap@eu.citrix.com
> Cc: xen-devel@lists.xen.org; Xu, YongweiX; Liu, SongtaoX; Tian, Yongxue
> Subject: Re: [Xen-devel] test report for Xen 4.3 RC1
>
> On Mon, May 27, 2013 at 03:49:27AM +0000, Ren, Yongjie wrote:
> > Hi All,
> > This is a report based on our testing for Xen 4.3.0 RC1 on Intel platforms.
> > (Sorry it's a little late. :-) If the status changes, I'll have an update
> later.)
>
> OK, I've some updates and ideas that can help with narrowing some of
> these
> issues down. Thank you for doing this.
>
> >
> > Test environment:
> > Xen: Xen 4.3 RC1 with qemu-upstream-unstable.git
> > Dom0: Linux kernel 3.9.3
>
> Could you please test v3.10-rc3. There have been some changes
> for the VCPU hotplug added in v3.10 that I am not sure whether
> they are in v3.9?
I didn't try every bug with v3.10.-rc3, but most of them still exist.
> > Hardware: Intel Sandy Bridge, Ivy Bridge, Haswell systems
> >
> > Below are the features we tested.
> > - PV and HVM guest booting (HVM: Ubuntu, Fedora, RHEL, Windows)
> > - Save/Restore and live migration
> > - PCI device assignment and SR-IOV
> > - power management: C-state/P-state, Dom0 S3, HVM S3
> > - AVX and XSAVE instruction set
> > - MCE
> > - CPU online/offline for Dom0
> > - vCPU hot-plug
> > - Nested Virtualization (Please look at my report in the following link.)
> > http://lists.xen.org/archives/html/xen-devel/2013-05/msg01145.html
> >
> > New bugs (4): (some of which are not regressions)
> > 1. sometimes failed to online cpu in Dom0
> >
> http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1851
>
> That looks like you are hitting the udev race.
>
> Could you verify that these patches:
> https://lkml.org/lkml/2013/5/13/520
>
> fix the issue (They are destined for v3.11)
>
Not tried yet. I'll update it to you later.
> > 2. dom0 call trace when running sriov hvm guest with igbvf
> >
> http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1852
> > -- a regression in Linux kernel (Dom0).
>
> Hm, the call-trace you refer too:
>
> [ 68.404440] Already setup the GSI :37
>
> [ 68.405105] igb 0000:04:00.0: Enabling SR-IOV VFs using the module
> parameter is deprecated - please use the pci sysfs interface.
>
> [ 68.506230] ------------[ cut here ]------------
>
> [ 68.506265] WARNING: at
> /home/www/builds_xen_unstable/xen-src-27009-20130509/linux-2.6-pvop
> s.git/fs/sysfs/dir.c:536 sysfs_add_one+0xcc/0xf0()
>
> [ 68.506279] Hardware name: S2600CP
>
> is a deprecated warning. Did you follow the 'pci sysfs' interface way?
>
> Looking at da36b64736cf2552e7fb5109c0255d4af804f5e7
> ixgbe: Implement PCI SR-IOV sysfs callback operation
> it says it is using this:
>
> commit 1789382a72a537447d65ea4131d8bcc1ad85ce7b
> Author: Donald Dutile <ddutile@redhat.com>
> Date: Mon Nov 5 15:20:36 2012 -0500
>
> PCI: SRIOV control and status via sysfs
>
> Provide files under sysfs to determine the maximum number of VFs
> an SR-IOV-capable PCIe device supports, and methods to enable and
> disable the VFs on a per-device basis.
>
> Currently, VF enablement by SR-IOV-capable PCIe devices is done
> via driver-specific module parameters. If not setup in modprobe
> files,
> it requires admin to unload & reload PF drivers with number of desired
> VFs to enable. Additionally, the enablement is system wide: all
> devices controlled by the same driver have the same number of VFs
> enabled. Although the latter is probably desired, there are PCI
> configurations setup by system BIOS that may not enable that to
> occur.
>
> Two files are created for the PF of PCIe devices with SR-IOV support:
>
> sriov_totalvfs Contains the maximum number of VFs the device
> could support as reported by the TotalVFs
> register
> in the SR-IOV extended capability.
>
> sriov_numvfs Contains the number of VFs currently enabled
> on
> this device as reported by the NumVFs
> register in
> the SR-IOV extended capability.
>
> Writing zero to this file disables all VFs.
>
> Writing a positive number to this file enables
> that
> number of VFs.
>
> These files are readable for all SR-IOV PF devices. Writes to the
> sriov_numvfs file are effective only if a driver that supports the
> sriov_configure() method is attached.
>
> Signed-off-by: Donald Dutile <ddutile@redhat.com>
>
>
> Can you try that please?
>
Recently, one of my workmates already had a fix as below.
https://lkml.org/lkml/2013/5/30/20
And, seems also already been fixed by another guy.
https://patchwork.kernel.org/patch/2613481/
>
> > 3. Booting multiple guests will lead Dom0 call trace
> >
> http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1853
>
> That one worries me. Did you do a git bisect to figure out what
> is commit is causing this?
>
I only found this bug on some Intel ~EX server.
I don't know which version on Xen/Dom0 can work fine.
If anyone want to reproduce or debug it, it should be good.
And our team is trying to debug it internally first.
> > 4. After live migration, guest console continuously prints "Clocksource
> tsc unstable"
> >
> http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1854
>
> This looks like a current bug with QEMU unstable missing a ACPI table?
>
> Did you try booting the guest with the old QEMU?
>
> device_model_version = 'qemu-xen-traditional'
>
This issue still exists with traditional qemu-xen.
After more testing, this bug can't reproduced by some other guests.
RHEL6.4 guest will have this issue after live migration, while RHEL6.3 &
Fedora 17 & Ubuntu 12.10 guests can work fine.
> >
> > Old bugs: (11)
> > 1. [ACPI] Dom0 can't resume from S3 sleep
> > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1707
>
> That should be fixed in v3.11 (as now we have the fixes)
> Could you try v3.10 with the Rafael's ACPI tree merged in?
> (so the patches that he wants to submit for v3.11)
>
I re-tested with Rafel's linux-pm.git tree (master and acpi-hotplug branch),
and found Dom0 S3 sleep/resume can't work, either.
> > 2. [XL]"xl vcpu-set" causes dom0 crash or panic
> > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1730
>
> That I think is fixed in v3.10. Could you please check v3.10-rc3?
>
Still exists on v3.10-rc3.
The following command lines can reproduce it:
# xl vcpu-set 0 1
# xl vcpu-set 0 20
> > 3. Sometimes Xen panic on ia32pae Sandybridge when restore guest
> > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1747
>
> That looks to be with v2.6.32. Is the issue present with v3.9
> or v3.10-rc3?
>
We didn't test ia32pae Xen for a long time.
Now, we only cover ia32e Xen/Dom0.
So, this bug is only a legacy issue.
If we have effort to verify it, we'll update it in the bugzilla.
> > 4. 'xl vcpu-set' can't decrease the vCPU number of a HVM guest
> > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1822
>
> That I believe was an QEMU bug:
> http://lists.xen.org/archives/html/xen-devel/2013-05/msg01054.html
>
> which should be in QEMU traditional now (05-21 was when it went
> in the tree)
>
In this year or past year, this bug always exists (at least in our testing).
'xl vcpu-set' can't decrease the vCPU number of a HVM guest
- Jay
> > 5. Dom0 cannot be shutdown before PCI device detachment from guest
> > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1826
>
> Ok, I can reproduce that too.
>
> > 6. xl pci-list shows one PCI device (PF or VF) could be assigned to two
> different guests
> > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1834
>
> OK, I can reproduce that too:
>
> > xl create /vm-pv.cfg
> Parsing config from /vm-pv.cfg
> libxl: error: libxl_pci.c:1043:libxl__device_pci_add: PCI device 0:1:0.0 is not
> assignable
> Daemon running with PID 3933
>
> 15:11:17 # 16 :/mnt/lab/latest/
> > xl pci-list 1
> Vdev Device
> 05.0 0000:01:00.0
>
> > xl list
> Name ID Mem VCPUs
> State Time(s)
> Domain-0 0 2047 4
> r----- 26.7
> latest 1 2043 1
> -b---- 5.3
> latestadesa 4 1024 3
> -b---- 5.1
>
> 15:11:20 # 20 :/mnt/lab/latest/
> > xl pci-list 4
> Vdev Device
> 00.0 0000:01:00.0
>
>
> The rest I hadn't had a chance to look at. George, have you seen
> these issues?
>
> > 7. [upstream qemu] Guest free memory with upstream qemu is 14MB
> lower than that with qemu-xen-unstable.git
> > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1836
> > 8. [upstream qemu]'maxvcpus=NUM' item is not supported in upstream
> QEMU
> > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1837
> > 9. [upstream qemu] Guest console hangs after save/restore or
> live-migration when setting 'hpet=0' in guest config file
> > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1838
> > 10. [upstream qemu] 'xen_platform_pci=0' setting cannot make the
> guest use emulated PCI devices by default
> > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1839
> > 11. Live migration fail when migrating the same guest for more than 2
> times
> > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1845
> >
> > Best Regards,
> > Yongjie (Jay)
> >
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xen.org
> > http://lists.xen.org/xen-devel
> >
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: test report for Xen 4.3 RC1
2013-05-28 15:21 ` Konrad Rzeszutek Wilk
@ 2013-05-28 15:24 ` George Dunlap
2013-11-11 10:22 ` Ian Campbell
0 siblings, 1 reply; 17+ messages in thread
From: George Dunlap @ 2013-05-28 15:24 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk
Cc: Ren, Yongjie, Tian, Yongxue, xen-devel, Xu, YongweiX, xen, Liu, SongtaoX
On 28/05/13 16:21, Konrad Rzeszutek Wilk wrote:
>>> 5. Dom0 cannot be shutdown before PCI device detachment from guest
>>> http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1826
>> Ok, I can reproduce that too.
> This is what dom0 tells me:
>
> [ 483.586675] INFO: task init:4163 blocked for more than 120 seconds.
> [ 483.603675] "echo 0 > /proc/sys/kernel/hung_task_timG^G[ 483.620747] init D ffff880062b59c78 5904 4163 1 0x00000000
> [ 483.637699] ffff880062b59bc8 0000000000000^G[ 483.655189] ffff880062b58000 ffff880062b58000 ffff880062b58010 ffff880062b58000
> [ 483.672505] ffff880062b59fd8 ffff880062b58000 ffff880062f20180 ffff880078bca500
> [ 483.689527] Call Trace:
> [ 483.706298] [<ffffffff816a0814>] schedule+0x24/0x70
> [ 483.723604] [<ffffffff813bb0dd>] read_reply+0xad/0x160
> [ 483.741162] [<ffffffff810b6b10>] ? wake_up_bit+0x40/0x40
> [ 483.758572] [<ffffffff813bb274>] xs_talkv+0xe4/0x1f0
> [ 483.775741] [<ffffffff813bb3c6>] xs_single+0x46/0x60
> [ 483.792791] [<ffffffff813bbab4>] xenbus_transaction_start+0x24/0x60
> [ 483.809929] [<ffffffff813ba202>] __xenbus_switch_ste+0x32/0x120
> ^G[ 483.826947] [<ffffffff8142df39>] ? __dev_printk+0x39/0x90
> [ 483.843792] [<ffffffff8142dfde>] ? _dev_info+0x4e/0x50
> [ 483.860412] [<ffffffff813ba2fb>] xenbus_switch_state+0xb/0x10
> [ 483.877312] [<ffffffff813bd487>] xenbus_dev_shutdown+0x37/0xa0
> [ 483.894036] [<ffffffff8142e275>] device_shutdown+0x15/0x180
> [ 483.910605] [<ffffffff810a8841>] kernel_restart_prepare+0x31/0x40
> [ 483.927100] [<ffffffff810a88a1>] kernel_restart+0x11^G[ 483.943262] [<ffffffff810a8ab5>] SYSC_reboot+0x1b5/0x260
> [ 483.959480] [<ffffffff810ed52d>] ? trace_hardirqs_on_caller+0^G[ 483.975786] [<ffffffff810ed5fd>] ? trace_hardirqs_on+0xd/0x10
> [ 483.991819] [<ffffffff8119db03>] ? kmem_cache_free+0x123/0x360
> [ 484.007675] [<ffffffff8115c725>] ? __free_pages+0x25/0x^G[ 484.023336] [<ffffffff8115c9ac>] ? free_pages+0x4c/0x50
> [ 484.039176] [<ffffffff8108b527>] ? __mmdrop+0x67/0xd0
> [ 484.055174] [<ffffffff816aae95>] ? sysret_check+0x22/0x5d
> [ 484.070747] [<ffffffff810ed52d>] ? trace_hardirqs_on_caller+0x10d/0x1d0
> [ 484.086121] [<ffffffff810a8b69>] SyS_reboot+0x9/0x10
> [ 484.101318] [<ffffffff816aae69>] system_call_fastpath+0x16/0x1b
> [ 484.116585] 3 locks held by init/4163:
> [ 484.131650]+.+.+.}, at: [<ffffffff810a89e0>] SYSC_reboot+0xe0/0x260
> ^G^G^G^G^G^G[ 484.147704] #1: (&__lockdep_no_validate__){......}, at: [<ffffffff8142e323>] device_shutdown+0xc3/0x180
> [ 484.164359] #2: (&xs_state.request_mutex){+.+...}, at: [<ffffffff813bb1fb>] xs_talkv+0x6b/0x1f0
>
> create !
> title -1 "linux, xenbus mutex hangs when rebooting dom0 and guests hung."
1. I think that these commands have to come at the top
2. You don't need quotes in the title
3. You need to be polite and say "thanks" at the end so it knows it can
stop paying attention. :-)
-George
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: test report for Xen 4.3 RC1
2013-05-28 15:15 ` Konrad Rzeszutek Wilk
@ 2013-05-28 15:21 ` Konrad Rzeszutek Wilk
2013-05-28 15:24 ` George Dunlap
0 siblings, 1 reply; 17+ messages in thread
From: Konrad Rzeszutek Wilk @ 2013-05-28 15:21 UTC (permalink / raw)
To: Ren, Yongjie, george.dunlap, xen
Cc: Xu, YongweiX, Liu, SongtaoX, Tian, Yongxue, xen-devel
> > 5. Dom0 cannot be shutdown before PCI device detachment from guest
> > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1826
>
> Ok, I can reproduce that too.
This is what dom0 tells me:
[ 483.586675] INFO: task init:4163 blocked for more than 120 seconds.
[ 483.603675] "echo 0 > /proc/sys/kernel/hung_task_timG^G[ 483.620747] init D ffff880062b59c78 5904 4163 1 0x00000000
[ 483.637699] ffff880062b59bc8 0000000000000^G[ 483.655189] ffff880062b58000 ffff880062b58000 ffff880062b58010 ffff880062b58000
[ 483.672505] ffff880062b59fd8 ffff880062b58000 ffff880062f20180 ffff880078bca500
[ 483.689527] Call Trace:
[ 483.706298] [<ffffffff816a0814>] schedule+0x24/0x70
[ 483.723604] [<ffffffff813bb0dd>] read_reply+0xad/0x160
[ 483.741162] [<ffffffff810b6b10>] ? wake_up_bit+0x40/0x40
[ 483.758572] [<ffffffff813bb274>] xs_talkv+0xe4/0x1f0
[ 483.775741] [<ffffffff813bb3c6>] xs_single+0x46/0x60
[ 483.792791] [<ffffffff813bbab4>] xenbus_transaction_start+0x24/0x60
[ 483.809929] [<ffffffff813ba202>] __xenbus_switch_ste+0x32/0x120
^G[ 483.826947] [<ffffffff8142df39>] ? __dev_printk+0x39/0x90
[ 483.843792] [<ffffffff8142dfde>] ? _dev_info+0x4e/0x50
[ 483.860412] [<ffffffff813ba2fb>] xenbus_switch_state+0xb/0x10
[ 483.877312] [<ffffffff813bd487>] xenbus_dev_shutdown+0x37/0xa0
[ 483.894036] [<ffffffff8142e275>] device_shutdown+0x15/0x180
[ 483.910605] [<ffffffff810a8841>] kernel_restart_prepare+0x31/0x40
[ 483.927100] [<ffffffff810a88a1>] kernel_restart+0x11^G[ 483.943262] [<ffffffff810a8ab5>] SYSC_reboot+0x1b5/0x260
[ 483.959480] [<ffffffff810ed52d>] ? trace_hardirqs_on_caller+0^G[ 483.975786] [<ffffffff810ed5fd>] ? trace_hardirqs_on+0xd/0x10
[ 483.991819] [<ffffffff8119db03>] ? kmem_cache_free+0x123/0x360
[ 484.007675] [<ffffffff8115c725>] ? __free_pages+0x25/0x^G[ 484.023336] [<ffffffff8115c9ac>] ? free_pages+0x4c/0x50
[ 484.039176] [<ffffffff8108b527>] ? __mmdrop+0x67/0xd0
[ 484.055174] [<ffffffff816aae95>] ? sysret_check+0x22/0x5d
[ 484.070747] [<ffffffff810ed52d>] ? trace_hardirqs_on_caller+0x10d/0x1d0
[ 484.086121] [<ffffffff810a8b69>] SyS_reboot+0x9/0x10
[ 484.101318] [<ffffffff816aae69>] system_call_fastpath+0x16/0x1b
[ 484.116585] 3 locks held by init/4163:
[ 484.131650]+.+.+.}, at: [<ffffffff810a89e0>] SYSC_reboot+0xe0/0x260
^G^G^G^G^G^G[ 484.147704] #1: (&__lockdep_no_validate__){......}, at: [<ffffffff8142e323>] device_shutdown+0xc3/0x180
[ 484.164359] #2: (&xs_state.request_mutex){+.+...}, at: [<ffffffff813bb1fb>] xs_talkv+0x6b/0x1f0
create !
title -1 "linux, xenbus mutex hangs when rebooting dom0 and guests hung."
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: test report for Xen 4.3 RC1
2013-05-27 3:49 Ren, Yongjie
@ 2013-05-28 15:15 ` Konrad Rzeszutek Wilk
2013-05-28 15:21 ` Konrad Rzeszutek Wilk
0 siblings, 1 reply; 17+ messages in thread
From: Konrad Rzeszutek Wilk @ 2013-05-28 15:15 UTC (permalink / raw)
To: Ren, Yongjie, george.dunlap
Cc: Xu, YongweiX, Liu, SongtaoX, Tian, Yongxue, xen-devel
On Mon, May 27, 2013 at 03:49:27AM +0000, Ren, Yongjie wrote:
> Hi All,
> This is a report based on our testing for Xen 4.3.0 RC1 on Intel platforms.
> (Sorry it's a little late. :-) If the status changes, I'll have an update later.)
OK, I've some updates and ideas that can help with narrowing some of these
issues down. Thank you for doing this.
>
> Test environment:
> Xen: Xen 4.3 RC1 with qemu-upstream-unstable.git
> Dom0: Linux kernel 3.9.3
Could you please test v3.10-rc3. There have been some changes
for the VCPU hotplug added in v3.10 that I am not sure whether
they are in v3.9?
> Hardware: Intel Sandy Bridge, Ivy Bridge, Haswell systems
>
> Below are the features we tested.
> - PV and HVM guest booting (HVM: Ubuntu, Fedora, RHEL, Windows)
> - Save/Restore and live migration
> - PCI device assignment and SR-IOV
> - power management: C-state/P-state, Dom0 S3, HVM S3
> - AVX and XSAVE instruction set
> - MCE
> - CPU online/offline for Dom0
> - vCPU hot-plug
> - Nested Virtualization (Please look at my report in the following link.)
> http://lists.xen.org/archives/html/xen-devel/2013-05/msg01145.html
>
> New bugs (4): (some of which are not regressions)
> 1. sometimes failed to online cpu in Dom0
> http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1851
That looks like you are hitting the udev race.
Could you verify that these patches:
https://lkml.org/lkml/2013/5/13/520
fix the issue (They are destined for v3.11)
> 2. dom0 call trace when running sriov hvm guest with igbvf
> http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1852
> -- a regression in Linux kernel (Dom0).
Hm, the call-trace you refer too:
[ 68.404440] Already setup the GSI :37
[ 68.405105] igb 0000:04:00.0: Enabling SR-IOV VFs using the module parameter is deprecated - please use the pci sysfs interface.
[ 68.506230] ------------[ cut here ]------------
[ 68.506265] WARNING: at /home/www/builds_xen_unstable/xen-src-27009-20130509/linux-2.6-pvops.git/fs/sysfs/dir.c:536 sysfs_add_one+0xcc/0xf0()
[ 68.506279] Hardware name: S2600CP
is a deprecated warning. Did you follow the 'pci sysfs' interface way?
Looking at da36b64736cf2552e7fb5109c0255d4af804f5e7
ixgbe: Implement PCI SR-IOV sysfs callback operation
it says it is using this:
commit 1789382a72a537447d65ea4131d8bcc1ad85ce7b
Author: Donald Dutile <ddutile@redhat.com>
Date: Mon Nov 5 15:20:36 2012 -0500
PCI: SRIOV control and status via sysfs
Provide files under sysfs to determine the maximum number of VFs
an SR-IOV-capable PCIe device supports, and methods to enable and
disable the VFs on a per-device basis.
Currently, VF enablement by SR-IOV-capable PCIe devices is done
via driver-specific module parameters. If not setup in modprobe files,
it requires admin to unload & reload PF drivers with number of desired
VFs to enable. Additionally, the enablement is system wide: all
devices controlled by the same driver have the same number of VFs
enabled. Although the latter is probably desired, there are PCI
configurations setup by system BIOS that may not enable that to occur.
Two files are created for the PF of PCIe devices with SR-IOV support:
sriov_totalvfs Contains the maximum number of VFs the device
could support as reported by the TotalVFs register
in the SR-IOV extended capability.
sriov_numvfs Contains the number of VFs currently enabled on
this device as reported by the NumVFs register in
the SR-IOV extended capability.
Writing zero to this file disables all VFs.
Writing a positive number to this file enables that
number of VFs.
These files are readable for all SR-IOV PF devices. Writes to the
sriov_numvfs file are effective only if a driver that supports the
sriov_configure() method is attached.
Signed-off-by: Donald Dutile <ddutile@redhat.com>
Can you try that please?
> 3. Booting multiple guests will lead Dom0 call trace
> http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1853
That one worries me. Did you do a git bisect to figure out what
is commit is causing this?
> 4. After live migration, guest console continuously prints "Clocksource tsc unstable"
> http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1854
This looks like a current bug with QEMU unstable missing a ACPI table?
Did you try booting the guest with the old QEMU?
device_model_version = 'qemu-xen-traditional'
>
> Old bugs: (11)
> 1. [ACPI] Dom0 can't resume from S3 sleep
> http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1707
That should be fixed in v3.11 (as now we have the fixes)
Could you try v3.10 with the Rafael's ACPI tree merged in?
(so the patches that he wants to submit for v3.11)
> 2. [XL]"xl vcpu-set" causes dom0 crash or panic
> http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1730
That I think is fixed in v3.10. Could you please check v3.10-rc3?
> 3. Sometimes Xen panic on ia32pae Sandybridge when restore guest
> http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1747
That looks to be with v2.6.32. Is the issue present with v3.9
or v3.10-rc3?
> 4. 'xl vcpu-set' can't decrease the vCPU number of a HVM guest
> http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1822
That I believe was an QEMU bug:
http://lists.xen.org/archives/html/xen-devel/2013-05/msg01054.html
which should be in QEMU traditional now (05-21 was when it went
in the tree)
> 5. Dom0 cannot be shutdown before PCI device detachment from guest
> http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1826
Ok, I can reproduce that too.
> 6. xl pci-list shows one PCI device (PF or VF) could be assigned to two different guests
> http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1834
OK, I can reproduce that too:
> xl create /vm-pv.cfg
Parsing config from /vm-pv.cfg
libxl: error: libxl_pci.c:1043:libxl__device_pci_add: PCI device 0:1:0.0 is not assignable
Daemon running with PID 3933
15:11:17 # 16 :/mnt/lab/latest/
> xl pci-list 1
Vdev Device
05.0 0000:01:00.0
> xl list
Name ID Mem VCPUs State Time(s)
Domain-0 0 2047 4 r----- 26.7
latest 1 2043 1 -b---- 5.3
latestadesa 4 1024 3 -b---- 5.1
15:11:20 # 20 :/mnt/lab/latest/
> xl pci-list 4
Vdev Device
00.0 0000:01:00.0
The rest I hadn't had a chance to look at. George, have you seen
these issues?
> 7. [upstream qemu] Guest free memory with upstream qemu is 14MB lower than that with qemu-xen-unstable.git
> http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1836
> 8. [upstream qemu]'maxvcpus=NUM' item is not supported in upstream QEMU
> http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1837
> 9. [upstream qemu] Guest console hangs after save/restore or live-migration when setting 'hpet=0' in guest config file
> http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1838
> 10. [upstream qemu] 'xen_platform_pci=0' setting cannot make the guest use emulated PCI devices by default
> http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1839
> 11. Live migration fail when migrating the same guest for more than 2 times
> http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1845
>
> Best Regards,
> Yongjie (Jay)
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
^ permalink raw reply [flat|nested] 17+ messages in thread
* test report for Xen 4.3 RC1
@ 2013-05-27 3:49 Ren, Yongjie
2013-05-28 15:15 ` Konrad Rzeszutek Wilk
0 siblings, 1 reply; 17+ messages in thread
From: Ren, Yongjie @ 2013-05-27 3:49 UTC (permalink / raw)
To: xen-devel; +Cc: Xu, YongweiX, Liu, SongtaoX, Tian, Yongxue
Hi All,
This is a report based on our testing for Xen 4.3.0 RC1 on Intel platforms.
(Sorry it's a little late. :-) If the status changes, I'll have an update later.)
Test environment:
Xen: Xen 4.3 RC1 with qemu-upstream-unstable.git
Dom0: Linux kernel 3.9.3
Hardware: Intel Sandy Bridge, Ivy Bridge, Haswell systems
Below are the features we tested.
- PV and HVM guest booting (HVM: Ubuntu, Fedora, RHEL, Windows)
- Save/Restore and live migration
- PCI device assignment and SR-IOV
- power management: C-state/P-state, Dom0 S3, HVM S3
- AVX and XSAVE instruction set
- MCE
- CPU online/offline for Dom0
- vCPU hot-plug
- Nested Virtualization (Please look at my report in the following link.)
http://lists.xen.org/archives/html/xen-devel/2013-05/msg01145.html
New bugs (4): (some of which are not regressions)
1. sometimes failed to online cpu in Dom0
http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1851
2. dom0 call trace when running sriov hvm guest with igbvf
http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1852
-- a regression in Linux kernel (Dom0).
3. Booting multiple guests will lead Dom0 call trace
http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1853
4. After live migration, guest console continuously prints "Clocksource tsc unstable"
http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1854
Old bugs: (11)
1. [ACPI] Dom0 can't resume from S3 sleep
http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1707
2. [XL]"xl vcpu-set" causes dom0 crash or panic
http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1730
3. Sometimes Xen panic on ia32pae Sandybridge when restore guest
http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1747
4. 'xl vcpu-set' can't decrease the vCPU number of a HVM guest
http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1822
5. Dom0 cannot be shutdown before PCI device detachment from guest
http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1826
6. xl pci-list shows one PCI device (PF or VF) could be assigned to two different guests
http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1834
7. [upstream qemu] Guest free memory with upstream qemu is 14MB lower than that with qemu-xen-unstable.git
http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1836
8. [upstream qemu]'maxvcpus=NUM' item is not supported in upstream QEMU
http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1837
9. [upstream qemu] Guest console hangs after save/restore or live-migration when setting 'hpet=0' in guest config file
http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1838
10. [upstream qemu] 'xen_platform_pci=0' setting cannot make the guest use emulated PCI devices by default
http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1839
11. Live migration fail when migrating the same guest for more than 2 times
http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1845
Best Regards,
Yongjie (Jay)
^ permalink raw reply [flat|nested] 17+ messages in thread
end of thread, other threads:[~2013-11-11 10:22 UTC | newest]
Thread overview: 17+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-06-16 4:10 test report for Xen 4.3 RC1 Ren, Yongjie
2013-06-17 14:23 ` Konrad Rzeszutek Wilk
2013-06-17 20:35 ` Konrad Rzeszutek Wilk
2013-06-17 20:36 ` Konrad Rzeszutek Wilk
2013-06-20 2:53 ` Ren, Yongjie
2013-06-21 18:17 ` Konrad Rzeszutek Wilk
2013-07-02 8:09 ` Ren, Yongjie
2013-07-02 13:36 ` Konrad Rzeszutek Wilk
-- strict thread matches above, loose matches on Subject: below --
2013-06-05 10:14 Ren, Yongjie
2013-06-05 14:50 ` Konrad Rzeszutek Wilk
2013-06-04 15:59 Ren, Yongjie
2013-06-04 16:35 ` Konrad Rzeszutek Wilk
2013-05-27 3:49 Ren, Yongjie
2013-05-28 15:15 ` Konrad Rzeszutek Wilk
2013-05-28 15:21 ` Konrad Rzeszutek Wilk
2013-05-28 15:24 ` George Dunlap
2013-11-11 10:22 ` Ian Campbell
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.