[Bug 61971] New: Migration problem of qemu-kvm guests
https://bugzilla.kernel.org/show_bug.cgi?id=61971 Bug ID: 61971 Summary: Migration problem of qemu-kvm guests Product: Virtualization Version: unspecified Kernel Version: 3.10.5 Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: kvm Assignee: virtualization_...@kernel-bugs.osdl.org Reporter: mag...@boden.cx Regression: No Hello, I am having migration problems and would appreciate very much help in troubleshooting this further. I have installed two wheezy hosts (qemu-1.1.2) using glusterfs as backend storage and are running about 12 debian wheezy guests. Node A has newer hardware (AMD FX(tm)-8320 Eight-Core Processor) and node B is older (AMD Phenom(tm) II X6 1055T Processor). I am using libvirt and when migrating hosts from Node A to node B the always freeze indicating high cpu utilization in virt-manager for example. Migrations from Node B to Node A always works. I can start all gests on both hosts without problems. To rule out glusterfs as the problem I have also used nfs as backend storage with the same results. I have installed a freebsd-9.1 guest to rule out the guests linux kernel as the likely problem. The guests also freeze if they are in grub or the freebsd bootloader while being migrated. I have tried using this kernel parameter processor.max_cstate=1 and using changing clocksource to acpi_pm (defaults to kvm-clock). Neither of these had any effect on my problem. I have tried disabling the balloon driver and that didn't help either. Both hosts and all guests use ntp so the time is synced. At one point I reinstalled both machines as ubuntu 13.04 to get newer versions of qemu (1.4) and libvirt but the exact same problem was there also, as I prefer debian I went back to wheezy. -no-kvm-irqchip and -no-kvm-pit doesn't help either. Using -no-kvm the migration works both ways. My gut feeling is that it has something to do with the different cpu's, but I read that it was possible to migrate between intel and amd I guess this shouldn't be a problem. Anyone have any ide what could be the problem here? Best Regards Magnus Diff between cpuinfo of linux guest when booted on each host so no cpu flags differ in the guest. I have tried with Opteron_G2, qemu64 and kvm64 cpus all causes the guest to freeze. root@lazy:~# diff -Nru iron1-cpuinfo.txt iron2-cpuinfo.txt --- iron1-cpuinfo.txt 2013-09-19 20:59:24.407659093 +0200 +++ iron2-cpuinfo.txt 2013-09-19 21:01:03.326022357 +0200 @@ -5,14 +5,14 @@ model name : QEMU Virtual CPU version 1.1.2 stepping : 3 microcode : 0x165 -cpu MHz: 3511.722 +cpu MHz: 2812.460 cache size : 512 KB fpu: yes fpu_exception : yes cpuid level: 4 wp : yes flags : fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx lm up nopl pni cx16 popcnt hypervisor lahf_lm svm abm sse4a -bogomips : 7023.44 +bogomips : 5624.92 TLB size : 1024 4K pages clflush size : 64 cache_alignment: 64 Node A cpuinfo processor : 7 vendor_id : AuthenticAMD cpu family : 21 model : 2 model name : AMD FX(tm)-8320 Eight-Core Processor stepping: 0 microcode : 0x600081f cpu MHz : 1400.000 cache size : 2048 KB physical id : 0 siblings: 8 core id : 7 cpu cores : 4 apicid : 23 initial apicid : 7 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb arat cpb hw_pstate npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold bmi1 bogomips: 7023.38 TLB size: 1536 4K pages clflush size: 64 cache_alignment : 64 address sizes : 48 bits physical, 48 bits virtual power management: ts ttp tm 100mhzsteps hwpstate cpb eff_freq_ro Node B cpuinfo processor : 5 vendor_id : AuthenticAMD cpu family : 16 model : 10 model name : AMD Phenom(tm) II X6 1055T Processor stepping: 0 microcode : 0x1dc cpu MHz : 800.000 cache size : 512 KB physical id : 0 siblings: 6 core id : 5 cpu cores : 6 apicid : 5 initial apicid : 5 fpu : yes fpu_exception : yes cpuid level : 6 wp : yes flags :
Re: KVM Guest keymap issue
Not specific to KVM, adding qemu-devel. Matej Mailing mail...@tam.si writes: Dear list, I have a problem with a Windows XP guest that I connect to via VNC and is using sl keymap (option -k sl). The guest is Windows XP and the problematic characters are s, c and z with caron... when I type them via VNC, they are not printed at all in virtual system... I have checked the file /usr/share/kvm/keymaps/sl and it seems that it contains different codes than I get when doing showkey --ascii on the host machine (running Ubuntu 12.04). I have tried to change the KVM's keymap file 'sl' with the codes I get from showkey, but they are still not printed in virtual system to which I am connected via VNC... I am totally lost with this issue, thanks for your time and ideas. Required reading for anyone struggling with virtual keyboards: https://www.berrange.com/posts/2010/07/04/more-than-you-or-i-ever-wanted-to-know-about-virtual-keyboard-handling/ -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
How to share filesystem
I would like to have access to the same file system from the host and the guest. Can anyone recommend the best way to do this, considering ease of use, safety (concurrent access from guest and host does not corrupt) and performance? For example, I would like to restore files from backup using the host, but write to filesystems used by the guest. I have previously used kvm mostly with disks that are based on LVM logical volumes, e.g. -hda /dev/turtle/Squeeze00. Since the LVs are virtual disks, I can't just mount them in the host AFAIK. Among the alternatives I can think of are using NFS and using NBD. Maybe there's some kind of loopback device I could use on the disk image to access it from the host. Host: Debian GNU/Linux wheezy, amd64 architecture, qemu-kvm 1.1.2 Guest: Debian GNU/Linux lenny i386. Host processor is a recent i5 with good virtualization (flaga: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms) Thanks. Ross Boylan -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 1/6] kvm: Add KVM_GET_EMULATED_CPUID
On Mon, September 23, 2013 6:28 pm, Eduardo Habkost wrote: On Sun, Sep 22, 2013 at 04:44:50PM +0200, Borislav Petkov wrote: From: Borislav Petkov b...@suse.de Add a kvm ioctl which states which system functionality kvm emulates. The format used is that of CPUID and we return the corresponding CPUID bits set for which we do emulate functionality. Let me check if I understood the purpose of the new ioctl correctly: the only reason for GET_EMULATED_CPUID to exist is to allow userspace to differentiate features that are native or that are emulated efficiently (GET_SUPPORTED_CPUID) and features that are emulated not very efficiently (GET_EMULATED_CPUID)? Not only that - emulated features are not reported in CPUID so they can be enabled only when specifically and explicitly requested, i.e. +movbe. Basically, you want to emulate that feature for the guest but only for this specific guest - the others shouldn't see it. If that's the case, how do we decide how efficient emulation should be, to deserve inclusion in GET_SUPPORTED_CPUID? I am guessing that the criterion will be: if enabling it doesn't risk making performance worse, it can get in GET_SUPPORTED_CPUID. Well, in the MOVBE case, supported means, the host can execute this instruction natively. Now, you guys say you can emulate x2apic very efficiently and I'm guessing emulating x2apic doesn't bring any emulation overhead, thus SUPPORTED_CPUID. But for single instructions or group of instructions, the distinction should be very clear. At least this is how I see it but Gleb probably can comment too. Thanks. -- Regards/Gruss, Boris. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 1/6] kvm: Add KVM_GET_EMULATED_CPUID
On Tue, Sep 24, 2013 at 11:57:00AM +0200, Borislav Petkov wrote: On Mon, September 23, 2013 6:28 pm, Eduardo Habkost wrote: On Sun, Sep 22, 2013 at 04:44:50PM +0200, Borislav Petkov wrote: From: Borislav Petkov b...@suse.de Add a kvm ioctl which states which system functionality kvm emulates. The format used is that of CPUID and we return the corresponding CPUID bits set for which we do emulate functionality. Let me check if I understood the purpose of the new ioctl correctly: the only reason for GET_EMULATED_CPUID to exist is to allow userspace to differentiate features that are native or that are emulated efficiently (GET_SUPPORTED_CPUID) and features that are emulated not very efficiently (GET_EMULATED_CPUID)? Not only that - emulated features are not reported in CPUID so they can be enabled only when specifically and explicitly requested, i.e. +movbe. Basically, you want to emulate that feature for the guest but only for this specific guest - the others shouldn't see it. If that's the case, how do we decide how efficient emulation should be, to deserve inclusion in GET_SUPPORTED_CPUID? I am guessing that the criterion will be: if enabling it doesn't risk making performance worse, it can get in GET_SUPPORTED_CPUID. Well, in the MOVBE case, supported means, the host can execute this instruction natively. Now, you guys say you can emulate x2apic very efficiently and I'm guessing emulating x2apic doesn't bring any emulation overhead, thus SUPPORTED_CPUID. x2apic emulation has nothing to do with x2apic in a host. It is emulated same way no matter if host has it or not. x2apic is not really cpu feature, but apic one and apic is fully emulated by KVM anyway. But for single instructions or group of instructions, the distinction should be very clear. At least this is how I see it but Gleb probably can comment too. That's how I see it two. Basically you want to use movbe emulation (as opposite of virtualization) only if you have binary kernel that compiled for CPU with movbe (Borislav's use case), or you want to migrate temporarily from movbe enabled host to non movbe host because downtime is not an option. We should avoid enabling it by mistake. -- Gleb. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: How to share filesystem
Am Tue, 24 Sep 2013 01:38:39 -0700 schrieb Ross Boylan r...@biostat.ucsf.edu: I would like to have access to the same file system from the host and the guest. Can anyone recommend the best way to do this, considering ease of use, safety (concurrent access from guest and host does not corrupt) and performance? [...] Among the alternatives I can think of are using NFS and using NBD. Maybe there's some kind of loopback device I could use on the disk image to access it from the host. I've never tried it on my own, but there is also virtio-9p: http://wiki.qemu.org/Documentation/9psetup Maybe that's what you need? Thomas -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: How to share filesystem
You can as well try Qemu-GuestAgent which uses Virtio-Serial communication for Guest and Host. -Original Message- From: kvm-ow...@vger.kernel.org [mailto:kvm-ow...@vger.kernel.org] On Behalf Of Thomas Huth Sent: Tuesday, September 24, 2013 3:54 PM To: Ross Boylan Cc: kvm@vger.kernel.org Subject: Re: How to share filesystem Am Tue, 24 Sep 2013 01:38:39 -0700 schrieb Ross Boylan r...@biostat.ucsf.edu: I would like to have access to the same file system from the host and the guest. Can anyone recommend the best way to do this, considering ease of use, safety (concurrent access from guest and host does not corrupt) and performance? [...] Among the alternatives I can think of are using NFS and using NBD. Maybe there's some kind of loopback device I could use on the disk image to access it from the host. I've never tried it on my own, but there is also virtio-9p: http://wiki.qemu.org/Documentation/9psetup Maybe that's what you need? Thomas -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
KVM call for agenda for 2013-10-01
Hi Please, send any topic that you are interested in covering. Last week I forgot to send the call for topics. We still have a topic there. Thanks, Juan. Agenda so far: - Talk about qemu reverse executing (1st description was done this week) How to handle IO when we want to do reverse execution. How this relate to Kemari needs? And to icount changes? Call details: 10:00 AM to 11:00 AM EDT Every two weeks If you need phone number details, contact me privately. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[PATCH v2] arm32: kvm: rename CONFIG_KVM_ARM_MAX_VCPUS
Drop the _ARM_ part of the name. We can then introduce a config option like this to aarch64 and other arches using the same name - allowing grep to show them all. Also update the help text to describe the option more completely. Signed-off-by: Andrew Jones drjo...@redhat.com --- v2: reword help text some more --- arch/arm/include/asm/kvm_host.h | 4 ++-- arch/arm/kvm/Kconfig| 9 + 2 files changed, 7 insertions(+), 6 deletions(-) diff --git a/arch/arm/include/asm/kvm_host.h b/arch/arm/include/asm/kvm_host.h index 7d22517d80711..c614d3eb176c6 100644 --- a/arch/arm/include/asm/kvm_host.h +++ b/arch/arm/include/asm/kvm_host.h @@ -25,8 +25,8 @@ #include asm/fpstate.h #include kvm/arm_arch_timer.h -#if defined(CONFIG_KVM_ARM_MAX_VCPUS) -#define KVM_MAX_VCPUS CONFIG_KVM_ARM_MAX_VCPUS +#if defined(CONFIG_KVM_MAX_VCPUS) +#define KVM_MAX_VCPUS CONFIG_KVM_MAX_VCPUS #else #define KVM_MAX_VCPUS 0 #endif diff --git a/arch/arm/kvm/Kconfig b/arch/arm/kvm/Kconfig index ebf5015508b52..8e56ccf45edce 100644 --- a/arch/arm/kvm/Kconfig +++ b/arch/arm/kvm/Kconfig @@ -40,16 +40,17 @@ config KVM_ARM_HOST ---help--- Provides host support for ARM processors. -config KVM_ARM_MAX_VCPUS +config KVM_MAX_VCPUS int Number maximum supported virtual CPUs per VM depends on KVM_ARM_HOST default 4 help Static number of max supported virtual CPUs per VM. - If you choose a high number, the vcpu structures will be quite - large, so only choose a reasonable number that you expect to - actually use. + The default is set to the highest number of vcpus that + current hardware supports. Choosing a lower number decreases + the size of the VM data structure. This number may also be + increased. config KVM_ARM_VGIC bool KVM support for Virtual GIC -- 1.8.1.4 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 3/3] KVM: ARM: Transparent huge pages and hugetlbfs support
On Mon, Sep 23, 2013 at 11:11:07AM +0100, Marc Zyngier wrote:
Hi Christoffer,
Finally taking some time to review this patch. Sorry for the delay...
On 09/08/13 05:07, Christoffer Dall wrote:
From: Christoffer Dall cd...@cs.columbia.edu
[ snip ]
static int user_mem_abort(struct kvm_vcpu *vcpu, phys_addr_t fault_ipa,
- gfn_t gfn, struct kvm_memory_slot *memslot,
+ struct kvm_memory_slot *memslot,
unsigned long fault_status)
{
- pte_t new_pte;
- pfn_t pfn;
int ret;
- bool write_fault, writable;
+ bool write_fault, writable, hugetlb = false, force_pte = false;
unsigned long mmu_seq;
+ gfn_t gfn = fault_ipa PAGE_SHIFT;
+ unsigned long hva = gfn_to_hva(vcpu-kvm, gfn);
+ struct kvm *kvm = vcpu-kvm;
struct kvm_mmu_memory_cache *memcache = vcpu-arch.mmu_page_cache;
+ struct vm_area_struct *vma;
+ pfn_t pfn;
+ unsigned long psize;
write_fault = kvm_is_write_fault(kvm_vcpu_get_hsr(vcpu));
if (fault_status == FSC_PERM !write_fault) {
@@ -525,6 +638,27 @@ static int user_mem_abort(struct kvm_vcpu *vcpu,
phys_addr_t fault_ipa,
return -EFAULT;
}
+ /* Let's check if we will get back a huge page */
+ down_read(current-mm-mmap_sem);
+ vma = find_vma_intersection(current-mm, hva, hva + 1);
+ if (is_vm_hugetlb_page(vma)) {
+ hugetlb = true;
+ hva = PMD_MASK;
+ gfn = (fault_ipa PMD_MASK) PAGE_SHIFT;
+ psize = PMD_SIZE;
+ } else {
+ psize = PAGE_SIZE;
+ if (vma-vm_start ~PMD_MASK)
+ force_pte = true;
+ }
+ up_read(current-mm-mmap_sem);
+
+ pfn = gfn_to_pfn_prot(kvm, gfn, write_fault, writable);
+ if (is_error_pfn(pfn))
+ return -EFAULT;
How does this work with respect to the comment that talks about reading
mmu_seq before calling gfp_to_pfn_prot? Either the comment is wrong, or
we read this too early.
+ coherent_icache_guest_page(kvm, hva, psize);
+
/* We need minimum second+third level pages */
ret = mmu_topup_memory_cache(memcache, 2, KVM_NR_MEM_OBJS);
if (ret)
@@ -542,26 +676,34 @@ static int user_mem_abort(struct kvm_vcpu *vcpu,
phys_addr_t fault_ipa,
*/
smp_rmb();
- pfn = gfn_to_pfn_prot(vcpu-kvm, gfn, write_fault, writable);
- if (is_error_pfn(pfn))
- return -EFAULT;
-
- new_pte = pfn_pte(pfn, PAGE_S2);
- coherent_icache_guest_page(vcpu-kvm, gfn);
-
- spin_lock(vcpu-kvm-mmu_lock);
- if (mmu_notifier_retry(vcpu-kvm, mmu_seq))
+ spin_lock(kvm-mmu_lock);
+ if (mmu_notifier_retry(kvm, mmu_seq))
goto out_unlock;
- if (writable) {
- kvm_set_s2pte_writable(new_pte);
- kvm_set_pfn_dirty(pfn);
+ if (!hugetlb !force_pte)
+ hugetlb = transparent_hugepage_adjust(pfn, fault_ipa);
How do we ensure that there is no race between this pte being promoted
to a pmd and another page allocation in the same pmd somewhere else in
the system? We only hold the kvm lock here, so there must be some extra
implicit guarantee somewhere...
This isn't a promotion to a huge page, it is a mechanism to ensure that
pfn corresponds with the head page of a THP as that's where refcount
information is stored. I think this is safe.
I'm still getting my brain working with kvm, so sorry don't have any
other feedback yet sorry :-).
Cheers,
--
Steve
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: How to share filesystem
On Tue, 2013-09-24 at 12:24 +0200, Thomas Huth wrote: Am Tue, 24 Sep 2013 01:38:39 -0700 schrieb Ross Boylan r...@biostat.ucsf.edu: I would like to have access to the same file system from the host and the guest. Can anyone recommend the best way to do this, considering ease of use, safety (concurrent access from guest and host does not corrupt) and performance? [...] Among the alternatives I can think of are using NFS and using NBD. Maybe there's some kind of loopback device I could use on the disk image to access it from the host. I've never tried it on my own, but there is also virtio-9p: http://wiki.qemu.org/Documentation/9psetup Maybe that's what you need? Thomas At first I saw Plan 9 and figured it was irrelevant to linux, but the example seems to be Linux. So I'm puzzled. Ross -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Dobra droga dzień!
Dobra droga dzień! Jestem pewien, że ta wiadomość będzie przyjście do was jako niespodzianka, ponieważ nigdy nie spotkaliśmy się wcześniej i może być również pytaniem, dlaczego zdecydowałem się was wybrałem spośród wielu użytkowników internetu na świecie. Widziałem swój profil w Internecie, które złożyło mi zrealizować moje prośby. Jestem Pani Caroline Freund, bill i menedżer wymiana Cahoot Finansów Wielkiej Brytanii. W moim departamencie, odkryłem opuszczonej sumę 5,800,000.00 dolarów amerykańskich. (Pięć milionów osiemset tysięcy dolar amerykański), w związku z naszych zagranicznych klientów (MR Paul Louis Halley), którzy zginęli wraz z żoną w 2003 roku w katastrofie lotniczej. Proszę zobaczyć stronę internetową po więcej informacji. http://newswww.bbc.net.uk/2/hi/uk_news/england/oxfordshire/4537663.stm Według naszego prawa bankowego z 1990 r., jeśli pieniądze są nieodebrane po upływie dziesięciu (10) lat, jest własnością rządu. Dlatego zaplanowali na przesyłanie danych w systemie bankowym jako Next of Kin zmarłego pana Halleya, bo nie dają najbliższych krewnych na jego konto przed jego nagłej śmierci. I sprawdzić to konto przez ponad 4-5 lat i nikt nigdy nie przedstawiła zastrzeżenia funduszu. Ale odkryłem, że (Late Pan Paul Louis Halley) nie ma krewnego lub beneficjenta konta przed śmiercią. Tak więc, po przejściu przez jego sprawy w naszym banku. I szczerze i świadomie szukać zgody zaprezentować Państwu jak najbliższych krewnych / Czy beneficjent do tego konta, tak aby łączna wartość 5,800,000.00 dolarów amerykańskich, zostaną przekazane do naszego wspólnego dobra. Mam zamiar podzielić pieniądze w stosunku 60% do 40% mnie i dla Ciebie z Tobą. Twoja odpowiedź jest pilnie potrzebna. W odpowiedzi, dam ci więcej szczegółów, a następnie. Odpowiedzi na e-mail: carolinefreundcah...@yahoo.co.uk Czekam na pilną odpowiedź. Pozdrowienia. Pani Caroline Freund -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: How to share filesystem
You。can use. Virtio-9p. In. Linux. 发自我的 iPhone 在 2013年9月25日，0:37，Ross Boylan r...@biostat.ucsf.edu 写道： On Tue, 2013-09-24 at 12:24 +0200, Thomas Huth wrote: Am Tue, 24 Sep 2013 01:38:39 -0700 schrieb Ross Boylan r...@biostat.ucsf.edu: I would like to have access to the same file system from the host and the guest. Can anyone recommend the best way to do this, considering ease of use, safety (concurrent access from guest and host does not corrupt) and performance? [...] Among the alternatives I can think of are using NFS and using NBD. Maybe there's some kind of loopback device I could use on the disk image to access it from the host. I've never tried it on my own, but there is also virtio-9p: http://wiki.qemu.org/Documentation/9psetup Maybe that's what you need? Thomas At first I saw Plan 9 and figured it was irrelevant to linux, but the example seems to be Linux. So I'm puzzled. Ross -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: How to share filesystem
9p is a protocol that is created by plan 9 operation system. linux can use virtio-9p. 发自我的 iPhone 在 2013年9月25日，3:03，shendl1...@gmail.com 写道： You。can use. Virtio-9p. In. Linux. 发自我的 iPhone 在 2013年9月25日，0:37，Ross Boylan r...@biostat.ucsf.edu 写道： On Tue, 2013-09-24 at 12:24 +0200, Thomas Huth wrote: Am Tue, 24 Sep 2013 01:38:39 -0700 schrieb Ross Boylan r...@biostat.ucsf.edu: I would like to have access to the same file system from the host and the guest. Can anyone recommend the best way to do this, considering ease of use, safety (concurrent access from guest and host does not corrupt) and performance? [...] Among the alternatives I can think of are using NFS and using NBD. Maybe there's some kind of loopback device I could use on the disk image to access it from the host. I've never tried it on my own, but there is also virtio-9p: http://wiki.qemu.org/Documentation/9psetup Maybe that's what you need? Thomas At first I saw Plan 9 and figured it was irrelevant to linux, but the example seems to be Linux. So I'm puzzled. Ross -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[PATCH] ARM: kvm: rename cpu_reset to avoid name clash
From: Olof Johansson o...@lixom.net
cpu_reset is already #defined in asm/proc-fns.h as processor.reset,
so it expands here and causes problems.
Cc: sta...@vger.kernel.org
Signed-off-by: Olof Johansson o...@lixom.net
Signed-off-by: Christoffer Dall christoffer.d...@linaro.org
---
arch/arm/kvm/reset.c |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/arm/kvm/reset.c b/arch/arm/kvm/reset.c
index 71e08ba..c02ba4a 100644
--- a/arch/arm/kvm/reset.c
+++ b/arch/arm/kvm/reset.c
@@ -58,14 +58,14 @@ static const struct kvm_irq_level a15_vtimer_irq = {
*/
int kvm_reset_vcpu(struct kvm_vcpu *vcpu)
{
- struct kvm_regs *cpu_reset;
+ struct kvm_regs *reset_regs;
const struct kvm_irq_level *cpu_vtimer_irq;
switch (vcpu-arch.target) {
case KVM_ARM_TARGET_CORTEX_A15:
if (vcpu-vcpu_id a15_max_cpu_idx)
return -EINVAL;
- cpu_reset = a15_regs_reset;
+ reset_regs = a15_regs_reset;
vcpu-arch.midr = read_cpuid_id();
cpu_vtimer_irq = a15_vtimer_irq;
break;
@@ -74,7 +74,7 @@ int kvm_reset_vcpu(struct kvm_vcpu *vcpu)
}
/* Reset core registers */
- memcpy(vcpu-arch.regs, cpu_reset, sizeof(vcpu-arch.regs));
+ memcpy(vcpu-arch.regs, reset_regs, sizeof(vcpu-arch.regs));
/* Reset CP15 registers */
kvm_reset_coprocs(vcpu);
--
1.7.10.4
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
[GIT PULL] KVM/ARM Fixes for 3.12-rc2
The following changes since commit 62d228b8c676232eca579f91cc0782b060a59097: Merge branch 'fixes' of git://git.kernel.org/pub/scm/virt/kvm/kvm (2013-09-17 22:20:30 -0400) are available in the git repository at: git://git.linaro.org/people/cdall/linux-kvm-arm.git tags/kvm-arm-fixes-3.12-rc2 for you to fetch changes up to ac570e0493815e0b41681c89cb50d66421429d27: ARM: kvm: rename cpu_reset to avoid name clash (2013-09-24 11:15:05 -0700) KVM/ARM Fixes for 3.12-rc2 Fixes compilation error with KVM/ARM enabled. Olof Johansson (1): ARM: kvm: rename cpu_reset to avoid name clash arch/arm/kvm/reset.c |6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) -- 1.7.10.4 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: How to share filesystem
On Wed, 2013-09-25 at 03:06 +0800, shendl1...@gmail.com wrote: 9p is a protocol that is created by plan 9 operation system. linux can use virtio-9p. 发自我的 iPhone Is this the preferred way to go? At any rate, I don't think I can use it easily because the wiki says it needs linux 2.6.36.rc4 or newer, and Lenny uses 2.6.26 and backports only has 2.6.32. Ross 在 2013年9月25日，3:03，shendl1...@gmail.com 写道： You。can use. Virtio-9p. In. Linux. 发自我的 iPhone 在 2013年9月25日，0:37，Ross Boylan r...@biostat.ucsf.edu 写道： On Tue, 2013-09-24 at 12:24 +0200, Thomas Huth wrote: Am Tue, 24 Sep 2013 01:38:39 -0700 schrieb Ross Boylan r...@biostat.ucsf.edu: I would like to have access to the same file system from the host and the guest. Can anyone recommend the best way to do this, considering ease of use, safety (concurrent access from guest and host does not corrupt) and performance? [...] Among the alternatives I can think of are using NFS and using NBD. Maybe there's some kind of loopback device I could use on the disk image to access it from the host. I've never tried it on my own, but there is also virtio-9p: http://wiki.qemu.org/Documentation/9psetup Maybe that's what you need? Thomas At first I saw Plan 9 and figured it was irrelevant to linux, but the example seems to be Linux. So I'm puzzled. Ross -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] KVM: ARM: enable Cortex A7 hosts
On Thu, Sep 19, 2013 at 02:01:48PM +0200, Ulrich Hecht wrote:
KVM runs fine on Cortex A7 cores, so they should be enabled. Tested on an
APE6EVM board (r8a73a4 SoC).
Signed-off-by: Ulrich Hecht ulrich.he...@gmail.com
Hi Ulrich,
I'm not entirely sure but it seems to me that you should expand the
CC list of this patch someohow as it doesn't seem to have got any
attention in the week since you sent it.
# ./scripts/get_maintainer.pl -f arch/arm/kvm/guest.c
Christoffer Dall christoffer.d...@linaro.org (supporter:KERNEL VIRTUAL MA...)
Gleb Natapov g...@redhat.com (supporter:KERNEL VIRTUAL MA...)
Paolo Bonzini pbonz...@redhat.com (supporter:KERNEL VIRTUAL MA...)
Russell King li...@arm.linux.org.uk (maintainer:ARM PORT)
kvm...@lists.cs.columbia.edu (open list:KERNEL VIRTUAL MA...)
kvm@vger.kernel.org (open list:KERNEL VIRTUAL MA...)
linux-arm-ker...@lists.infradead.org (moderated list:ARM PORT)
linux-ker...@vger.kernel.org (open list)
---
arch/arm/kvm/guest.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/kvm/guest.c b/arch/arm/kvm/guest.c
index 152d036..05c62d5 100644
--- a/arch/arm/kvm/guest.c
+++ b/arch/arm/kvm/guest.c
@@ -192,6 +192,8 @@ int __attribute_const__ kvm_target_cpu(void)
switch (part_number) {
case ARM_CPU_PART_CORTEX_A15:
return KVM_ARM_TARGET_CORTEX_A15;
+ case ARM_CPU_PART_CORTEX_A7:
+ return KVM_ARM_TARGET_CORTEX_A15;
default:
return -EINVAL;
}
--
1.8.3.1
--
To unsubscribe from this list: send the line unsubscribe linux-sh in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
