search for: pvhvm

Hello, While testing Fedora 16 Xen PVHVM guests I noticed the following problem: When starting F16 PVHVM guest I can see the vifX.0 and tapX.0 interfaces appear on dom0, but after the guest kernel (Linux 3.1.0) starts and loads PVHVM drivers the vif/tap interfaces disappear from dom0.. so the bridge in dom0 doesn''t have any v...

hello, I know this not quite a xen problem but im sure a fair number of people are using debian for their dom0 and maybe have some insight into this. I have a large number of dom0''s running squeeze and for a long time i was hoping for pvhvm to make into the official debian xen packages and recently during some periodic updates I noticed pvhvm working after a kernel package update. Now I have been testing wheezy to get familiar with migrating to xl toolstack and I''ve noticed that on my fully up to date wheezy system, pvhvm do...

Checked out the latest unstable version of Xen 4.4 but failed to create a PVHVM domU Configured Xen with ./configure --prefix=/usr DomU config file: name = "pvhvm" builder=''hvm'' device_model = ''qemu-xen'' memory = ''512'' vcpus = ''4'' pae=1 acpi=1 apic=1 vif = [ ''mac=00:16:3E:51:20:8C, bri...

...am seeing this weird behavior when using #linux-next + stable/for-jens-3.8 tree. Basically I can do ''pvscan'' on xvd* disk and quite often I get checksum errors: # pvscan /dev/xvdf PV /dev/xvdf2 VG VolGroup00 lvm2 [18.88 GiB / 0 free] PV /dev/dm-14 VG vg_x86_64-pvhvm lvm2 [4.00 GiB / 68.00 MiB free] PV /dev/dm-12 VG vg_i386-pvhvm lvm2 [4.00 GiB / 68.00 MiB free] PV /dev/dm-11 VG vg_i386 lvm2 [4.00 GiB / 68.00 MiB free] PV /dev/sda VG guests lvm2 [931.51 GiB / 220.51 GiB free] Total: 5 [962.38 GiB] / in use: 5 [962.38 G...

...2.6.36 if you wanted. I can resend without if you prefer. Ian. The following changes since commit da5cabf80e2433131bf0ed8993abc0f7ea618c73: Linus Torvalds (1): Linux 2.6.36-rc1 are available in the git repository at: git://xenbits.xensource.com/people/ianc/linux-2.6.git for-upstream/pvhvm Ian Campbell (3): xen: pvhvm: allow user to request no emulated device unplug xen: pvhvm: rename xen_emul_unplug=ignore to =unnnecessary xen: pvhvm: make it clearer that XEN_UNPLUG_* define bits in a bitfield Documentation/kernel-parameters.txt | 6 ++++-- arch/x86/xen/platf...

Hello users, I have a problem when I save/restore a PVHVM guest. I installed xen-4.1.2 on my server. And I run a PVHVM guest on LVM. And my PVHVM guest is ubuntu-12.04.2-desktop. Actually when I save a machine, it acts fine. (Of course, when I saved it, There were some processes like movie player) But, When I restore it, It seems more slow. Additionally...

Hi Jeremy, I backported the branch I have in linux-next plus some older PV on HVM fixes to stable-2.6.32.x. Please pull: git://xenbits.xen.org/people/sstabellini/linux-pvhvm.git stable-2.6.32-pvhvm Ian Campbell (11): xen: do not respond to unknown xenstore control requests xen: use new schedop interface for suspend xen: switch to new schedop hypercall by default. xen: suspend: use HYPERVISOR_suspend for PVHVM case instead of open coding x...

...ist, 0, buf); } When xen aware this, it will call xen_reboot(SHUTDOWN_crash) to send out an event with reason code - SHUTDOWN_crash. xen_panic_handler_init() is defined to register on panic_notifier_list but we only call it in xen_arch_setup which only be called by pvm, this patch is necessary for pvhvm. Signed-off-by: Vaughan Cao <vaughan.cao at oracle.com> --- arch/x86/xen/enlighten.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/x86/xen/enlighten.c b/arch/x86/xen/enlighten.c index 4aec5ed..53e5726 100644 --- a/arch/x86/xen/enlighten.c +++ b/arch/x86/xen/enlighten.c @@ -1713...

...ist, 0, buf); } When xen aware this, it will call xen_reboot(SHUTDOWN_crash) to send out an event with reason code - SHUTDOWN_crash. xen_panic_handler_init() is defined to register on panic_notifier_list but we only call it in xen_arch_setup which only be called by pvm, this patch is necessary for pvhvm. Signed-off-by: Vaughan Cao <vaughan.cao at oracle.com> --- arch/x86/xen/enlighten.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/x86/xen/enlighten.c b/arch/x86/xen/enlighten.c index 4aec5ed..53e5726 100644 --- a/arch/x86/xen/enlighten.c +++ b/arch/x86/xen/enlighten.c @@ -1713...

...ist, 0, buf); } When xen aware this, it will call xen_reboot(SHUTDOWN_crash) to send out an event with reason code - SHUTDOWN_crash. xen_panic_handler_init() is defined to register on panic_notifier_list but we only call it in xen_arch_setup which only be called by pvm, this patch is necessary for pvhvm. Signed-off-by: Vaughan Cao <vaughan.cao at oracle.com> --- arch/x86/xen/enlighten.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/x86/xen/enlighten.c b/arch/x86/xen/enlighten.c index 4aec5ed..53e5726 100644 --- a/arch/x86/xen/enlighten.c +++ b/arch/x86/xen/enlighten.c @@ -1713...

Moving to public discussion... This was found with Xen hypervisor version supporting device unplugging and the domU kernel having net-/blkfront and pci platform built-in (or as module). The block device is defined as hda and the NIC type=ioemu (so theoretically guests without pv support would work, too). Since both drivers are present, the kernel tries to unplug the emulated devices and

The initial values of the wallclock time in the shared info page are set for PVHVM guests when the hypercall page is initialized, since the hypercall page is not reinitialized on resume, the hypervisor wallclock time is not properly set on resume. Fix it by forcing an update of the wallclock values when the shared info page is mapped. Signed-off-by: Roger Pau Monné <roger.pa...

Hello, I'm looking for an example configuration for a PVHVM domU that works with 4.3.1. The one at http://wiki.xen.org/wiki/Xen_Linux_PV_on_HVM_drivers causes 3 warnings and some errors: WARNING: ignoring "kernel" directive for HVM guest. Use "firmware_override" instead if you really want a non-default firmware WARNING: ignoring device_...

.../kernel/git/konrad/xen.git stable/for-linus-3.10-rc0-tag which has just a couple of features and mostly bug-fixes. Here is the blurb copied from the signed tag: <tag> Features: - Populate the boot_params with EDD data. - Cleanups in the IRQ code. Bug-fixes: - CPU hotplug offline/online in PVHVM mode. - Re-upload processor PM data after ACPI S3 suspend/resume cycle. </tag> Please pull! arch/x86/pci/xen.c | 6 +-- arch/x86/xen/enlighten.c | 57 +++++++++++++++++++++++++++- arch/x86/xen/smp.c | 21 ++++++---- arch/x86/xen/spinlock.c | 2...

Hi, Commit 63753b3e0dc56efb1acf94fa46f3fee7bc59281c x86: allow VCPUOP_register_vcpu_info to work again on PVHVM guests Leaves HVM guests dangling after shutdown or destroy: xl list gives: (null) 16 0 4 --p--d 11.5 (null) 17 0 1 --ps-d 12.0 (first was destroyed, second shutdown) The actual xl and qe...

On 19/06/13 14:33, Jeroen van der Ham wrote: > > On 19 Jun 2013, at 14:20, Roger Pau Monné <roger.pau@citrix.com> wrote: >> That''s because Justin recently pushed a commit that changed the ad >> translation to ada, you should change your /etc/fstab to ada0p2. It''s >> commit 526f3ad11acb296481215d7c2915b3f30f1844f6. > > > Ah, you may want

Hi, On 19 Jun 2013, at 18:52, Justin T. Gibbs <gibbs@FreeBSD.org> wrote: >> I guess the kernel-toolchain takes a long time to build…and from what I can see it does a clean before rebuilding also. >> >> I''m doing the kernel-toolchain step only now and will report how long it took. This seems to be it, that took roughly 2 hours to build. The actual kernel is

Hi, After some more testing I thought it would be good to put this into production for my personal server. I''ve used pvhvm_v19 and built it without debugging options and installed it on a FreeBSD 9.1 system. I''ve run into some hiccups with 9.1 user land and a 10-CURRENT kernel, but that''s all solvable[0]. My VPS has some very limited memory (256M), but I''ve compensated with swap space (1G)...

Call update_domain_wallclock_time on hvm_latch_shinfo_size even if the bitness of the guest has already been set, this fixes the problem with the wallclock not being set for PVHVM guests on resume from migration. Signed-off-by: Roger Pau Monné <roger.pau@citrix.com> Cc: Jan Beulich <JBeulich@suse.com> Cc: Keir Fraser <keir@xen.org> Cc: George Dunlap <George.Dunlap@eu.citrix.com> --- Since this is a bug fix, I think it is suitable for inclusion in the...

I''ve been trying to compare memory access speed between bare-metal, xen-pv and xen-pvhvm (hvm with pv drivers). In all 3 setups I''m running the same kernel (3.6.6), built with support for xen, on a 64 core AMD Opteron 6378. The output of xm info (relevant parts): machine : x86_64 nr_cpus : 64 nr_nodes : 8 cores_per_socket : 16...