|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] [PATCH] xen: implement vector callback for evtchn delive
Here we go:- <domain type="xen" id="4"> <name>LucidHVM</name> <uuid>0f26e840-836d-18f3-9438-0f12d1e42677</uuid> <memory>2097152</memory> <currentMemory>2097152</currentMemory> <vcpu>2</vcpu> <os> <type>hvm</type> <loader>/usr/lib/xen/boot/hvmloader</loader> <boot dev="hd"/> </os> <features> <acpi/> <apic/> <pae/> </features> <clock offset="utc"/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/lib64/xen/bin/qemu-dm</emulator> ************************************************************ <disk type="block"
device="disk"> <driver name="phy"/> <source dev="/dev/sda7"/> <target dev="hda" bus="ide"/> </disk> <disk type="file" device="cdrom"> <target dev="hdc" bus="ide"/> <readonly/> ************************************************************* </disk> <interface type="bridge"> <mac address="00:16:36:2a:cd:af"/> <source bridge="br0"/> <script path="/etc/xen/scripts/vif-bridge"/> <target dev="vif4.0"/> </interface> <serial type="pty"> <source path="/dev/pts/0"/> <target port="0"/> </serial> <console type="pty" tty="/dev/pts/0"> <source path="/dev/pts/0"/> <target port="0"/> </console> <input type="mouse" bus="ps2"/> <graphics type="vnc" port="5900" autoport="yes" keymap="en-us"/> <sound
model="es1370"/> </devices> </domain>
That's XML profile kept by virt-manager after it's own install HVM DomU on F13
Boris.
--- On Thu, 5/27/10, Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> wrote:
From: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> Subject: Re: [Xen-devel] [PATCH] xen: implement vector callback for evtchn delivery To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx> Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxxx>, "Stefano Stabellini" <Stefano.Stabellini@xxxxxxxxxxxxx> Date: Thursday, May 27, 2010, 10:58 AM
On Thu, 27 May 2010, Boris Derzhavets wrote: > root@LucidSRV:~# cat /proc/interrupts >
CPU0 CPU1 > 0: 29 0 IO-APIC-edge timer > 1: 107 0 IO-APIC-edge i8042 > 4: 1 0 IO-APIC-edge > 6: 2 0 IO-APIC-edge floppy > 8:
0 0 IO-APIC-edge rtc0 > 9: 0 0 IO-APIC-fasteoi acpi > 12: 187 496 IO-APIC-edge i8042 > 14: 0 0 IO-APIC-edge ata_piix > 15: 933 0 IO-APIC-edge ata_piix > 16: 293
0 xen-dyn-event xenbus > 17: 5059 0 xen-dyn-event blkif > 18: 0 0 xen-dyn-event blkif > 19: 72 0 xen-dyn-event eth0 > 23: 0 0 IO-APIC-fasteoi uhci_hcd:usb1 > 36: 0 0 IO-APIC-fasteoi Ensoniq
AudioPCI > NMI: 0 0 Non-maskable interrupts > LOC: 2767 2901 Local timer interrupts > SPU: 0 0 Spurious interrupts > PMI: 0 0 Performance monitoring interrupts > PND: 0 0 Performance pending work > PLT: 5211 0 Platform interrupts >
RES: 1189 1949 Rescheduling interrupts > CAL: 130 89 Function call interrupts > TLB: 230 179 TLB shootdowns > TRM: 0 0 Thermal event interrupts > THR: 0 0 Threshold APIC interrupts > MCE: 0 0 Machine check exceptions > MCP:
1 1 Machine check polls > ERR: 0 > MIS: 0 >
You definitely have the vector callback enabled. I am not sure why you receive so many ata_piix interrupts given that you shouldn't be using the emulated disk at all. Maybe you are reading from an emulated cdrom? -----Inline Attachment Follows-----
|
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|