Displaying 3 results from an estimated 3 matches for "guest_os_id".
Did you mean:
guest_gs_d
2011 Sep 23
1
[PATCH] Add save/restore support for viridian APIC assist pfn
...static void dump_viridian(void)
+static void dump_viridian_domain(void)
{
- HVM_SAVE_TYPE(VIRIDIAN) p;
+ HVM_SAVE_TYPE(VIRIDIAN_DOMAIN) p;
READ(p);
- printf(" VIRIDIAN: hypercall gpa 0x%llx, guest ID 0x%llx\n",
+ printf(" VIRIDIAN_DOMAIN: hypercall gpa 0x%llx, guest_os_id 0x%llx\n",
(unsigned long long) p.hypercall_gpa,
(unsigned long long) p.guest_os_id);
}
+static void dump_viridian_vcpu(void)
+{
+ HVM_SAVE_TYPE(VIRIDIAN_VCPU) p;
+ READ(p);
+ printf(" VIRIDIAN_VCPU: apic_assist 0x%llx\n",
+...
BSOD "A clock interrupt was not recevied ona secondary processor within the allocated time interval"
2008 Dec 29
13
BSOD "A clock interrupt was not recevied ona secondary processor within the allocated time interval"
Hi,
When dom0 is under heavy load any Vista or Windows 2008 HVM''s that are
running and have multiple cpu''s assigned often BSOD with code
0x00000101 "A clock interrupt was not recevied ona secondary
processor within the allocated time interval"
It only happens if the load in dom0 is high enough to make the mouse
pointer lagged, once the mouse fails to track in
BSOD "A clock interrupt was not recevied ona secondary processor within the allocated time interval"
2008 Dec 29
13
BSOD "A clock interrupt was not recevied ona secondary processor within the allocated time interval"
Hi,
When dom0 is under heavy load any Vista or Windows 2008 HVM''s that are
running and have multiple cpu''s assigned often BSOD with code
0x00000101 "A clock interrupt was not recevied ona secondary
processor within the allocated time interval"
It only happens if the load in dom0 is high enough to make the mouse
pointer lagged, once the mouse fails to track in