Displaying 18 results from an estimated 18 matches for "hypervisior".
2013 Jan 02
3
Time
...ided this.
>
> Any suggestions for addressing this particular scenerio other
> than having to manually set a bunch of clocks?
>
I ran into this situation several times whilst testing KVM and the
lessons I learned from the experiences can be summarized as:
1. Never allow the kvm hypervisior to handle guests during a host
shutdown. Use 'virsh shutdown' on each of the guests first and then
shutdown the host. Use autostart to restart guests on a host's
reboot. Write a script to process 'virsh list' to feed active domains
to 'virsh shutdown' if automation is...
2007 Nov 23
0
Kernel-Panic : Xen, Drbd
...kernel : it''s ok, didn''t crash
- only drbd/lvm with a xen Debian kernel : it''s ok, didn''t crash
- only xend hypervisor, drbd/lvm with xen Debian Kernel : it''s ok, didn''t
crash
- xend hypervisor, 2 domU, drbd/lvm : crash ;''(
- xend hypervisior, 2 dom, drbd/lvm but with noapic nolapic acpi=off on dom0
grub : crash :''(
any idea ? any questions ?
thanks in advance
(I will come back with a Debian Testing + xen3.1 ...)
--
Guguin Benoit
Société Alixen 20 rue Jean Rostand 91 400 Orsay Cedex France
Tel : 01 60 19 72 31, Fax...
2009 Nov 16
2
grub entries for Dom0 kernel
I have compiled a Dom0 kernel
and kept in boot the images
xen-test-vmlinuz
initrd-test-2.6.29.img
xen-3.3.gz
my /boot/grub/menu.lst looks like this
title TEST Xen 3.3 / Ubuntu 9.04
uuid 32ce16fb-1400-4d71-bb37-c98ef140e501
kernel /xen-3.3.gz
module /xen-test-vmlinuz root=/dev/vga/dom0 ro console=tty0
module /initrd-test-2.6.29.2.img
quiet
I get
2011 Aug 15
9
[PATCH 0/8] Staging: hv: vmbus: Driver cleanup
Further cleanup of the vmbus driver:
1) Cleanup the interrupt handler by inlining some code.
2) Ensure message handling is performed on the same CPU that
takes the vmbus interrupt.
3) Check for events before messages (from the host).
4) Disable auto eoi for the vmbus interrupt since Linux will eoi the
interrupt anyway.
5) Some general cleanup.
Regards,
K. Y
2011 Aug 15
9
[PATCH 0/8] Staging: hv: vmbus: Driver cleanup
Further cleanup of the vmbus driver:
1) Cleanup the interrupt handler by inlining some code.
2) Ensure message handling is performed on the same CPU that
takes the vmbus interrupt.
3) Check for events before messages (from the host).
4) Disable auto eoi for the vmbus interrupt since Linux will eoi the
interrupt anyway.
5) Some general cleanup.
Regards,
K. Y
2010 Mar 04
1
[PATCH 1/1] Stage: hv: Corrected all header comments to follow kernel-doc format-CORRECTED
...+/*
* VmbusOnCleanup - Perform any cleanup when the driver is removed
*/
static void VmbusOnCleanup(struct hv_driver *drv)
@@ -168,7 +168,7 @@ static void VmbusOnCleanup(struct hv_driver *drv)
DPRINT_EXIT(VMBUS);
}
-/**
+/*
* VmbusOnMsgDPC - DPC routine to handle messages from the hypervisior
*/
static void VmbusOnMsgDPC(struct hv_driver *drv)
@@ -216,7 +216,7 @@ static void VmbusOnMsgDPC(struct hv_driver *drv)
}
}
-/**
+/*
* VmbusOnEventDPC - DPC routine to handle events from the hypervisior
*/
static void VmbusOnEventDPC(struct hv_driver *drv)
@@ -225,7 +225,7 @@ sta...
2010 Mar 04
1
[PATCH 1/1] Stage: hv: Corrected all header comments to follow kernel-doc format-CORRECTED
...+/*
* VmbusOnCleanup - Perform any cleanup when the driver is removed
*/
static void VmbusOnCleanup(struct hv_driver *drv)
@@ -168,7 +168,7 @@ static void VmbusOnCleanup(struct hv_driver *drv)
DPRINT_EXIT(VMBUS);
}
-/**
+/*
* VmbusOnMsgDPC - DPC routine to handle messages from the hypervisior
*/
static void VmbusOnMsgDPC(struct hv_driver *drv)
@@ -216,7 +216,7 @@ static void VmbusOnMsgDPC(struct hv_driver *drv)
}
}
-/**
+/*
* VmbusOnEventDPC - DPC routine to handle events from the hypervisior
*/
static void VmbusOnEventDPC(struct hv_driver *drv)
@@ -225,7 +225,7 @@ sta...
2011 Feb 26
1
[PATCH 4/6] Staging: hv: Unify the hyperv driver abstractions
...anup(struct hv_driver *drv)
+static void vmbus_cleanup(struct driver_context *drv)
{
/* struct vmbus_driver *driver = (struct vmbus_driver *)drv; */
@@ -221,7 +221,7 @@ static void vmbus_onmessage_work(struct work_struct *work)
/*
* vmbus_on_msg_dpc - DPC routine to handle messages from the hypervisior
*/
-static void vmbus_on_msg_dpc(struct hv_driver *drv)
+static void vmbus_on_msg_dpc(struct driver_context *drv)
{
int cpu = smp_processor_id();
void *page_addr = hv_context.synic_message_page[cpu];
@@ -267,7 +267,7 @@ static void vmbus_on_msg_dpc(struct hv_driver *drv)
/*
* vmbus_on_isr...
2011 Feb 26
1
[PATCH 4/6] Staging: hv: Unify the hyperv driver abstractions
...anup(struct hv_driver *drv)
+static void vmbus_cleanup(struct driver_context *drv)
{
/* struct vmbus_driver *driver = (struct vmbus_driver *)drv; */
@@ -221,7 +221,7 @@ static void vmbus_onmessage_work(struct work_struct *work)
/*
* vmbus_on_msg_dpc - DPC routine to handle messages from the hypervisior
*/
-static void vmbus_on_msg_dpc(struct hv_driver *drv)
+static void vmbus_on_msg_dpc(struct driver_context *drv)
{
int cpu = smp_processor_id();
void *page_addr = hv_context.synic_message_page[cpu];
@@ -267,7 +267,7 @@ static void vmbus_on_msg_dpc(struct hv_driver *drv)
/*
* vmbus_on_isr...
2010 Mar 04
3
[PATCH 1/1] Stage: hv: Corrected all header comments to follow kernel-doc format
...+/*
* VmbusOnCleanup - Perform any cleanup when the driver is removed
*/
static void VmbusOnCleanup(struct hv_driver *drv) @@ -168,7 +168,7 @@ static void VmbusOnCleanup(struct hv_driver *drv)
DPRINT_EXIT(VMBUS);
}
-/**
+/*
* VmbusOnMsgDPC - DPC routine to handle messages from the hypervisior
*/
static void VmbusOnMsgDPC(struct hv_driver *drv) @@ -216,7 +216,7 @@ static void VmbusOnMsgDPC(struct hv_driver *drv)
}
}
-/**
+/*
* VmbusOnEventDPC - DPC routine to handle events from the hypervisior
*/
static void VmbusOnEventDPC(struct hv_driver *drv) @@ -225,7 +225,7 @@ sta...
2010 Mar 04
3
[PATCH 1/1] Stage: hv: Corrected all header comments to follow kernel-doc format
...+/*
* VmbusOnCleanup - Perform any cleanup when the driver is removed
*/
static void VmbusOnCleanup(struct hv_driver *drv) @@ -168,7 +168,7 @@ static void VmbusOnCleanup(struct hv_driver *drv)
DPRINT_EXIT(VMBUS);
}
-/**
+/*
* VmbusOnMsgDPC - DPC routine to handle messages from the hypervisior
*/
static void VmbusOnMsgDPC(struct hv_driver *drv) @@ -216,7 +216,7 @@ static void VmbusOnMsgDPC(struct hv_driver *drv)
}
}
-/**
+/*
* VmbusOnEventDPC - DPC routine to handle events from the hypervisior
*/
static void VmbusOnEventDPC(struct hv_driver *drv) @@ -225,7 +225,7 @@ sta...
2011 Feb 26
1
[PATCH 5/6] Staging: hv: Rename driver_context to hyperv_driver
...(struct driver_context *drv)
+static void vmbus_cleanup(struct hyperv_driver *drv)
{
/* struct vmbus_driver *driver = (struct vmbus_driver *)drv; */
@@ -221,7 +221,7 @@ static void vmbus_onmessage_work(struct work_struct *work)
/*
* vmbus_on_msg_dpc - DPC routine to handle messages from the hypervisior
*/
-static void vmbus_on_msg_dpc(struct driver_context *drv)
+static void vmbus_on_msg_dpc(struct hyperv_driver *drv)
{
int cpu = smp_processor_id();
void *page_addr = hv_context.synic_message_page[cpu];
@@ -267,7 +267,7 @@ static void vmbus_on_msg_dpc(struct driver_context *drv)
/*
* vmb...
2011 Feb 26
1
[PATCH 5/6] Staging: hv: Rename driver_context to hyperv_driver
...(struct driver_context *drv)
+static void vmbus_cleanup(struct hyperv_driver *drv)
{
/* struct vmbus_driver *driver = (struct vmbus_driver *)drv; */
@@ -221,7 +221,7 @@ static void vmbus_onmessage_work(struct work_struct *work)
/*
* vmbus_on_msg_dpc - DPC routine to handle messages from the hypervisior
*/
-static void vmbus_on_msg_dpc(struct driver_context *drv)
+static void vmbus_on_msg_dpc(struct hyperv_driver *drv)
{
int cpu = smp_processor_id();
void *page_addr = hv_context.synic_message_page[cpu];
@@ -267,7 +267,7 @@ static void vmbus_on_msg_dpc(struct driver_context *drv)
/*
* vmb...
2011 Aug 27
46
[PATCH 0000/0046] Staging: hv: Driver cleanup
Further cleanup of the hv drivers.
1) Cleanup reference counting.
2) Handle all block devices using the storvsc driver. I have modified
the implementation here based on Christoph's feedback on my earlier
implementation.
3) Fix bugs.
4) Accomodate some host side scsi emulation bugs.
5) In case of scsi errors off-line the device.
This patch-set further reduces the size of
2011 Aug 27
46
[PATCH 0000/0046] Staging: hv: Driver cleanup
Further cleanup of the hv drivers.
1) Cleanup reference counting.
2) Handle all block devices using the storvsc driver. I have modified
the implementation here based on Christoph's feedback on my earlier
implementation.
3) Fix bugs.
4) Accomodate some host side scsi emulation bugs.
5) In case of scsi errors off-line the device.
This patch-set further reduces the size of
2011 Feb 24
4
[PATCH ] Staging: hv: Hyper-V driver cleanup
...eanup(struct hv_driver *drv)
+static void vmbus_cleanup(struct hyperv_driver *drv)
{
/* struct vmbus_driver *driver = (struct vmbus_driver *)drv; */
@@ -221,7 +220,7 @@ static void vmbus_onmessage_work(struct work_struct *work)
/*
* vmbus_on_msg_dpc - DPC routine to handle messages from the hypervisior
*/
-static void vmbus_on_msg_dpc(struct hv_driver *drv)
+static void vmbus_on_msg_dpc(struct hyperv_driver *drv)
{
int cpu = smp_processor_id();
void *page_addr = hv_context.synic_message_page[cpu];
@@ -267,7 +266,7 @@ static void vmbus_on_msg_dpc(struct hv_driver *drv)
/*
* vmbus_on_isr...
2011 Feb 24
4
[PATCH ] Staging: hv: Hyper-V driver cleanup
...eanup(struct hv_driver *drv)
+static void vmbus_cleanup(struct hyperv_driver *drv)
{
/* struct vmbus_driver *driver = (struct vmbus_driver *)drv; */
@@ -221,7 +220,7 @@ static void vmbus_onmessage_work(struct work_struct *work)
/*
* vmbus_on_msg_dpc - DPC routine to handle messages from the hypervisior
*/
-static void vmbus_on_msg_dpc(struct hv_driver *drv)
+static void vmbus_on_msg_dpc(struct hyperv_driver *drv)
{
int cpu = smp_processor_id();
void *page_addr = hv_context.synic_message_page[cpu];
@@ -267,7 +266,7 @@ static void vmbus_on_msg_dpc(struct hv_driver *drv)
/*
* vmbus_on_isr...
2007 Apr 18
33
[RFC PATCH 00/33] Xen i386 paravirtualization support
Unlike full virtualization in which the virtual machine provides
the same platform interface as running natively on the hardware,
paravirtualization requires modification to the guest operating system
to work with the platform interface provided by the hypervisor.
Xen was designed with performance in mind. Calls to the hypervisor
are minimized, batched if necessary, and non-critical codepaths