RE: Hot Spare Virtual Machines
This sounds similar to what Kemari was looking to achieve: http://wiki.qemu.org/Features/FaultTolerance But unfortunately, I believe Kemari development has halted. -Original Message- From: kvm-ow...@vger.kernel.org [mailto:kvm-ow...@vger.kernel.org] On Behalf Of Valentin Zagura Sent: Saturday, May 11, 2013 8:30 AM To: kvm@vger.kernel.org Subject: Hot Spare Virtual Machines I was thinking the other day if one can modify the live migration feature of KVM to allow keeping a remote hot copy of a virtual machine snapshot every say 10 seconds. And in the same time to use LVM or something similar so the modifications to the storage would be committed at every succesfull snapshot stored remotely. This way, whenever the hardware that runs the VM has a hardware problem, the spare could continue from the snapshot. I imagine that there can also be a software on the router between the VM and the Internet that could log all the traffic from the outside done since the last snapshot and could eventually replay it to the new hot spare VM that just started whenever is needed. Would this be feasible? :) Valentin Zagura http://zagura.com -- 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: [KVM][Kemari]: Build error fix
Is Kemari still in active development?
On Sun, Dec 4, 2011 at 9:45 PM, OHMURA Kei wrote:
> On 2011/12/02 21:51, Pradeep Kumar wrote:
>> It fixes build failure.
>>
>> I hit this error, after succsfull migration and sync.
>>
>> (qemu) qemu-system-x86_64: fill buffer failed, Interrupted system call
>>
>> qemu-system-x86_64: recv header failed
>>
>> qemu-system-x86_64: recv ack failed
>>
>> qemu_transaction_begin failed
>
> Did you use master branch?
> It is not latest version. next branch is latest and fixed error.
>
> git://kemari.git.sourceforge.net/gitroot/kemari/kemari next
>
> Thanks,
> Kei
>
>>
>> Any one working on this now?
>>
>>>From 827c04da6574be80d8352acd7c40b0b4524af5f4 Mon Sep 17 00:00:00 2001
>> Date: Fri, 2 Dec 2011 18:11:40 +0530
>> Subject: [PATCH] [Qemu][Kemari]: Build Failure
>> Signed-off-by: pradeep
>> modified: ft_trans_file.c
>>
>> ---
>> ft_trans_file.c | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/ft_trans_file.c b/ft_trans_file.c
>> index 4e33034..dc36757 100644
>> --- a/ft_trans_file.c
>> +++ b/ft_trans_file.c
>> @@ -174,7 +174,7 @@ static int ft_trans_send_header(QEMUFileFtTrans *s,
>> static int ft_trans_put_buffer(void *opaque, const uint8_t *buf, int64_t
>> pos, int size)
>> {
>> QEMUFileFtTrans *s = opaque;
>> - ssize_t ret;
>> + ssize_t ret = 0;
>>
>> trace_ft_trans_put_buffer(size, pos);
>>
> --
> 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: Reboot Problem
The Linux kernel does not reboot on panic by default. Read here: http://www.cyberciti.biz/tips/reboot-linux-box-after-a-kernel-panic.html - Original Message - From: "Chaitra Gorantla" To: kvm@vger.kernel.org Sent: Sunday, June 6, 2010 10:59:11 PM Subject: Reboot Problem Hi all, We know that kernel reboots after any panic or crash. I am using 2.6.21 kernel (HOST machine) and KVM-88 package. After inserting kvm-intel.ko , if any kernel crash occurs, the Host halts= . The kernel never reboots. Please suggest regarding this. Thanks in advance, Chaitra This Email may contain confidential or privileged information for the intended recipient (s) If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system. __ -- 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
Live migration between Intel Q6600 and AMD Phenom II
I've read that it's possible to live migrate KVM guests between Intel and AMD CPUs, is it also possible to migrate from a CPU without NPT/EPT to the Phenom II that supports NPT? Will I lose out on any of the benefits NPT allows without shutting down and restarting the guest? Also, any thoughts on how much more performant a 3.0GHz Phenom II will be for running KVM guests than the 2.4GHz Intel Q6600? Thanks in advance. -- 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: Qemu 0.10.50 CAN NOT get ip from dhcp server
I have noticed the same thing with KVM-87 and either the e1000 or the rtl8139
network models. I am on a 64-bit 2.6.18 RHEL 5.3 kernel with an Intel Q9300
processor.
Even statically assigning an IP to my bridged guest doesn't allow it to
communicate with my network.
Specifying virtio as the NIC model allows a Fedora 11 live CD to network
properly. KVM-86 allows the same Fedora 11 live CD to network properly
regardless of which NIC model I choose.
- Original Message -
From: "John Wong"
To: "KVM list"
Sent: Sunday, July 5, 2009 10:13:12 PM GMT -05:00 US/Canada Eastern
Subject: Qemu 0.10.50 CAN NOT get ip from dhcp server
I notice that, when i use qemu 0.10.50 (which from kvm-0.87.tar.gz), the
guest OS CAN NOT get the ip from dhcp server.
When i use qemu 0.10.0 (which from debian's kvm-0.85 package), the guest
OS CAN get the ip from the SAME dhcp server.
Please help, thank you.
My kvm network use bridge mode
My kvm launch script:
#!/bin/sh
NUM="9"
IMG="./openbsd-amd64.qcow2"
CDROM="/ntfs2/iso-cdrom/clonezilla-live-1.2.1-39.iso"
#CDROM="/kdchome/john/software/install46.iso"
#KVM="/usr/bin/kvm" # <- 0.10.0 which from debian kvm 0.85 package
KVM="/opt/kvm/bin/qemu-system-x86_64 -L /opt/kvm/share/qemu/" #
<- 0.10.50 which from kvm-0.87.tar.gz source code
USERID="$(whoami)"
PID="./pid.log"
iface="$(sudo /usr/sbin/tunctl -t tap${NUM} -b -u ${USERID})"
${KVM} -hda ${IMG} \
-net nic,vlan=${NUM},model=e1000,macaddr=00:AA:BB:CC:DD:0${NUM} \
-net
tap,vlan=${NUM},ifname="${iface}",script=/etc/kvm/kvm-ifup,downscript=/etc/kvm/kvm-ifdown
\
-localtime \
-usb -usbdevice tablet \
-k en-us -monitor stdio \
-soundhw all \
-cdrom ${CDROM} \
-m 1024 -vga cirrus -boot d $@
sleep 3
sudo /usr/sbin/tunctl -d ${iface}
exit $?
--
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: Weird Windows license issue
What do you mean by "rejected"? Is the installer not taking your key (I doubt this would be caused by anything KVM specific), or is it failing to activate over the internet (it may be that you have just hit the limit for how many times a given key can be activated)? - Original Message - From: "Michael Jinks" To: kvm@vger.kernel.org Sent: Thursday, July 2, 2009 6:22:58 PM GMT -05:00 US/Canada Eastern Subject: Weird Windows license issue My group has a license code for multiple instances of Win2K3 r2 Enterprise, which has worked fine for me when Windows runs as a guest on VMware and Xen, but now when I try to use it for my first Windows KVM guest, it's being rejected. I wouldn't think that the virtualization platform would matter for this purpose but it's the only variable I can see between our current working and non-working installs. Is this a known issue? Like, maybe Windows pays attention to the MAC address or CPU info when processing the license key and doesn't like some checksum somewhere? I know others are using Win2K3 on KVM so I know it should work... Thanks, --Michael -- 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: [kvm] Re: 3525MB RAM Limit
Is this a problem in the latest (kvm-84) or just in an older version that Fedora 10 provides? - Original Message - From: "Daniel Scott" To: "Alex Williamson" Cc: "Brian Jackson" , kvm@vger.kernel.org Sent: Thursday, April 9, 2009 2:54:11 PM GMT -05:00 US/Canada Eastern Subject: Re: [kvm] Re: 3525MB RAM Limit Brian, Alex, 2009/4/9 Alex Williamson : > On Thu, 2009-04-09 at 10:39 -0500, Brian Jackson wrote: >> some subjects to look for: >> * Can't boot guest with more than 3585MB when using large pages >> There was a patch from Marcelo that was supposed to fix it. >> * kvm-84 and guests with more than 3536 MB Ram? >> there were suggestions to make sure to use the correct bios and the OP >> stated >> that upgrading his kernel actually fixed the problem >> >> I could swear there was another one, but maybe I'm thinking of the IRC >> channel. If you are still unable to get it to work, you should reply back >> with >> more info. Kernel version, KVM version, etc. > > It could also be related to the guest trimming away memory due to the > way we used to report the MTRRs. This would show up in dmesg on the > guest. Try the latest kvm by hand and see if the problem goes away. Thanks for the suggestions. After more research, it looks like upgrading the software will fix the problem: http://www.func.nl/community/knowledgebase/running-kvm-guest-35-gb-ram We see the same BIOS message as in the above link. It seems like this will be fixed in Fedora 11 so we'll probably wait for a month or two and then upgrade Fedora on our host system. Thanks again, Dan -- 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
32-bit windows 2k3 guest hangs with more than ~3.5GB memory
I am running a compiled kvm-83 and have tried both a 2.6.18 and 2.6.24 64-bit kernel on a system with an Intel Q6600 CPU and 8GB of ram. My 32-bit Windows 2003 guest works properly with 3.5GB of memory allocated to it and four virtual CPUs. Here is the command I am using to start the guest: /usr/local/kvm/bin/qemu-system-x86_64 -m 3584 -smp 4 -drive file=/kvm/termserver1.kvm,if=scsi,cache=writeback,boot=on \ -daemonize -vnc :1 \ -boot c \ -serial none \ -parallel none \ -net nic,model=virtio -net tap,script=/kvm/qemu-bridge-ifup The machine is using a raw disk image and a simple script to create a tap device and add it to an existing bridge. When I try to give the machine 4GB of memory or more, it hangs during the Windows boot process (when the Windows logo appears above a progress bar). There is very little cpu usage for the kvm process on the host at this point and no disk I/O. I have to manually quit the VM, adjust the memory back down to 3.5GB or slightly higher, and restart. Does KVM not currently support PAE for 32-bit guests? Thanks in advance, Sterling Windmill -- 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
routed tap devices
I am using kvm-82 on a 64-bit host and giving my virtual machines routed tap devices and utilizing proxy arp to provide them connectivity. My host has two ethernet adapters, one connected to the WAN and the other is a private link to another server with a private IP address. Even though I'm assigning device names (on the host) based upon mac address, it seems that depending upon the order in which the linux kernel sees my ethernet adapters they are behaving differently in terms of ip forwarding. If I run `ip link` I see eth1 listed before eth0 and a virtual machine running behind a tap device that is using ip forwarding sees eth1's IP as it's first hop in a traceroute. If I swap eth0 and eth1 (via their configuration), the first hop in the guest's traceroute is eth0's IP and `ip link` shows eth0 first. Is there a way to control this behavior other than switching physical ethernet adapters? I may be paranoid, but I don't want the virtual machines to "see" my private IP address when using standard tools such as traceroute. Anyone have any ideas? -- 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
routing vs bridging with tap
I'm playing with KVM for purposes of eventually deploying it into a hosting environment and am using tap devices for my guest networking. I've routed a single IP to the tap device of a guest and enabled proxy_arp on the tap device used for the guest and the host's physical ethernet device. Networking works fine inside of the guest in this configuration, but a side effect seems to be that when migrating this guest from one host to another, the guest holds arp cache entries which point to the old MAC address and cause issues with networking. After clearing the guest's arp table proper network behavior resumes on the new host. Unfortunately, this work around causes a loss in connectivity until the arp cache can be cleared and I won't have access to log into the guests and do this once my setup is in production. I'm using routed tap devices instead of bridging the tap devices with the physical ethernet on the host because I have it in my mind that routing is better than bridging from a security and isolation standpoint when dealing with potentially untrusted guest virtual machines. Am I causing myself unnecessary pain? Should I just bridge everything together? Any ideas? Thanks in advance, Sterling Windmill -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Fwd: freebsd 7.0 32-bit won't boot with kvm scsi
Is there a bugzilla I can post this issue to? I'm still unable to get freebsd 7.0 booting after install with if=scsi on kvm-77 Thanks in advance, Sterling Windmill - Forwarded Message - From: "Sterling Windmill" <[EMAIL PROTECTED]> To: "Avi Kivity" <[EMAIL PROTECTED]> Cc: kvm@vger.kernel.org Sent: Wednesday, October 1, 2008 9:05:54 AM GMT -05:00 US/Canada Eastern Subject: Re: freebsd 7.0 32-bit won't boot with kvm scsi The only difference between my working IDE config and the broken SCSI is the "if=" parameter. Here is how I am calling qemu for this virtual machine: /usr/local/kvm/bin/qemu-system-x86_64 -m 512 -drive file=/dev/mapper/storage-freebsd,if=scsi,boot=on -net nic,model=e1000 -net tap,script=/root/kvmstuff/qemu-ifup -daemonize -vnc :2 \ -boot c -cdrom /root/kvmstuff/7.0-RELEASE-i386-disc1.iso Interestingly, I also note that while IDE seems to work fine, restarting the guest by issuing a shutdown -r while logged into freebsd or by sending a ctrl+alt+del to the virtual machine via VNC results in a boot failure. Shutting down the qemu instance and starting it up again allows freebsd to boot properly. Thanks again, Sterling Windmill - Original Message - From: "Avi Kivity" <[EMAIL PROTECTED]> To: "Sterling Windmill" <[EMAIL PROTECTED]> Cc: kvm@vger.kernel.org Sent: Wednesday, October 1, 2008 3:34:26 AM GMT -05:00 US/Canada Eastern Subject: Re: freebsd 7.0 32-bit won't boot with kvm scsi Sterling Windmill wrote: > I am attempting to get freebsd 7.0 32-bit running under kvm-76 and have been > successful with the emulated ide interface and e1000 networking. > > When I try to use kvm's scsi interface, I am able to complete the freebsd > install but get a bootloader message stating that the kernel cannot be found > upon attempting to boot into freebsd. > > Has anyone else experienced this? > Have you enabled extboot (-drive ...,boot=on)? -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] 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 [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: freebsd 7.0 32-bit won't boot with kvm scsi
The only difference between my working IDE config and the broken SCSI is the "if=" parameter. Here is how I am calling qemu for this virtual machine: /usr/local/kvm/bin/qemu-system-x86_64 -m 512 -drive file=/dev/mapper/storage-freebsd,if=scsi,boot=on -net nic,model=e1000 -net tap,script=/root/kvmstuff/qemu-ifup -daemonize -vnc :2 \ -boot c -cdrom /root/kvmstuff/7.0-RELEASE-i386-disc1.iso Interestingly, I also note that while IDE seems to work fine, restarting the guest by issuing a shutdown -r while logged into freebsd or by sending a ctrl+alt+del to the virtual machine via VNC results in a boot failure. Shutting down the qemu instance and starting it up again allows freebsd to boot properly. Thanks again, Sterling Windmill - Original Message - From: "Avi Kivity" <[EMAIL PROTECTED]> To: "Sterling Windmill" <[EMAIL PROTECTED]> Cc: kvm@vger.kernel.org Sent: Wednesday, October 1, 2008 3:34:26 AM GMT -05:00 US/Canada Eastern Subject: Re: freebsd 7.0 32-bit won't boot with kvm scsi Sterling Windmill wrote: > I am attempting to get freebsd 7.0 32-bit running under kvm-76 and have been > successful with the emulated ide interface and e1000 networking. > > When I try to use kvm's scsi interface, I am able to complete the freebsd > install but get a bootloader message stating that the kernel cannot be found > upon attempting to boot into freebsd. > > Has anyone else experienced this? > Have you enabled extboot (-drive ...,boot=on)? -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
freebsd 7.0 32-bit won't boot with kvm scsi
I am attempting to get freebsd 7.0 32-bit running under kvm-76 and have been successful with the emulated ide interface and e1000 networking. When I try to use kvm's scsi interface, I am able to complete the freebsd install but get a bootloader message stating that the kernel cannot be found upon attempting to boot into freebsd. Has anyone else experienced this? Thanks, Sterling Windmill -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: installing kvm-76 on 2.6.24
I am able to run kvm-76 after recompiling my kernel with DMAR unset. Thanks for the help! - Original Message - From: "Sheng Yang" <[EMAIL PROTECTED]> To: "Sterling Windmill" <[EMAIL PROTECTED]> Cc: "kvm" Sent: Monday, September 29, 2008 11:29:56 AM GMT -05:00 US/Canada Eastern Subject: Re: installing kvm-76 on 2.6.24 On Mon, Sep 29, 2008 at 11:18 PM, Sterling Windmill <[EMAIL PROTECTED]> wrote: > It seems as though I need to insert vtd.o instead of vtd.c Yeah... That's vtd.o :) And I forgot, if you want to compile vtd.c, you need compile kvm kernel space rather than other kernel version for we modified host kernel side. Sorry for I don't have a box by hand so that I can't check every detail... I suppose you want to keep your kernel? Maybe disable CONFIG_DMAR is more easy... -- regards, Yang, Sheng > > My Kbuild file now looks like this: > > # trick to get the kvm-specific CONFIG_KVM_* definitions, > # because the kernel source tree won't have them > include $(obj)/../config.kbuild > > obj-m := kvm.o kvm-intel.o kvm-amd.o > kvm-objs := vtd.o kvm_main.o x86.o mmu.o x86_emulate.o ../anon_inodes.o irq.o > i8 259.o \ > lapic.o ioapic.o preempt.o i8254.o coalesced_mmio.o \ > ../external-module-compat.o > ifeq ($(EXT_CONFIG_KVM_TRACE),y) > kvm-objs += kvm_trace.o > endif > kvm-intel-objs := vmx.o vmx-debug.o ../external-module-compat.o > kvm-amd-objs := svm.o ../external-module-compat.o > > CFLAGS_kvm_main.o = -DKVM_MAIN > > The modules do compile with this option specified. > > Unfortunately, the error inserting the modules still persists. > > Any other ideas? > > - Original Message - > From: "Sheng Yang" <[EMAIL PROTECTED]> > To: "Sterling Windmill" <[EMAIL PROTECTED]> > Cc: "kvm" > Sent: Monday, September 29, 2008 10:51:53 AM GMT -05:00 US/Canada Eastern > Subject: Re: installing kvm-76 on 2.6.24 > > On Mon, Sep 29, 2008 at 10:42 PM, Sterling Windmill <[EMAIL PROTECTED]> > wrote: >> Thank you for the information. I apologize for posting twice to the mailing >> list on the same issue. I was just trying to add some additional >> information. >> >> Could you tell me how to edit the Kbuild file for this purpose? I can also >> recompile my kernel, but that's a bit more difficult. > > Add vtd.c to kvm-userspace/kernel/x86/Kbuild kvm-objs item should get it > done. > > -- > regards, > Yang, Sheng >> >> Thanks in advance, >> Sterling Windmill >> >> - Original Message - >> From: "Sheng Yang" <[EMAIL PROTECTED]> >> To: "Sterling Windmill" <[EMAIL PROTECTED]> >> Cc: "kvm" >> Sent: Monday, September 29, 2008 10:21:10 AM GMT -05:00 US/Canada Eastern >> Subject: Re: installing kvm-76 on 2.6.24 >> >> On Mon, Sep 29, 2008 at 1:09 PM, Sterling Windmill <[EMAIL PROTECTED]> >> wrote: >>> I am running a custom compiled 2.6.24 kernel on a 64-bit Intel system and >>> had no issues compling and running kvm-75. >>> >>> I downloaded kvm-76 and compiled and installed it, but I cannot get the >>> modules to load properly. >>> >>> I have temporarily gone back to kvm-75. >>> >>> I am seeing this output in dmesg: >>> >>> kvm: Unknown symbol kvm_iommu_map_pages >>> kvm: Unknown symbol kvm_iommu_map_guest >>> kvm: Unknown symbol kvm_iommu_unmap_guest >> >> Seems you enabled CONFIG_DMAR in host kernel side? In theory, we >> should use CONFIG_DMAR with newly VT-d support in KVM, but the problem >> now is that userspace including compile option is not ready, so here >> comes compile problem. >> >> If you want to try kvm-76, you may try to disable CONFIG_DMAR in host >> kernel. Or just wait to userspace VT-d support merge (of course you >> can add vtd.c manually in Kbuild to overcome this compile issue). :) >> >> -- >> regards, >> Yang, Sheng >> > -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: installing kvm-76 on 2.6.24
It seems as though I need to insert vtd.o instead of vtd.c My Kbuild file now looks like this: # trick to get the kvm-specific CONFIG_KVM_* definitions, # because the kernel source tree won't have them include $(obj)/../config.kbuild obj-m := kvm.o kvm-intel.o kvm-amd.o kvm-objs := vtd.o kvm_main.o x86.o mmu.o x86_emulate.o ../anon_inodes.o irq.o i8259.o \ lapic.o ioapic.o preempt.o i8254.o coalesced_mmio.o \ ../external-module-compat.o ifeq ($(EXT_CONFIG_KVM_TRACE),y) kvm-objs += kvm_trace.o endif kvm-intel-objs := vmx.o vmx-debug.o ../external-module-compat.o kvm-amd-objs := svm.o ../external-module-compat.o CFLAGS_kvm_main.o = -DKVM_MAIN The modules do compile with this option specified. Unfortunately, the error inserting the modules still persists. Any other ideas? - Original Message - From: "Sheng Yang" <[EMAIL PROTECTED]> To: "Sterling Windmill" <[EMAIL PROTECTED]> Cc: "kvm" Sent: Monday, September 29, 2008 10:51:53 AM GMT -05:00 US/Canada Eastern Subject: Re: installing kvm-76 on 2.6.24 On Mon, Sep 29, 2008 at 10:42 PM, Sterling Windmill <[EMAIL PROTECTED]> wrote: > Thank you for the information. I apologize for posting twice to the mailing > list on the same issue. I was just trying to add some additional information. > > Could you tell me how to edit the Kbuild file for this purpose? I can also > recompile my kernel, but that's a bit more difficult. Add vtd.c to kvm-userspace/kernel/x86/Kbuild kvm-objs item should get it done. -- regards, Yang, Sheng > > Thanks in advance, > Sterling Windmill > > - Original Message - > From: "Sheng Yang" <[EMAIL PROTECTED]> > To: "Sterling Windmill" <[EMAIL PROTECTED]> > Cc: "kvm" > Sent: Monday, September 29, 2008 10:21:10 AM GMT -05:00 US/Canada Eastern > Subject: Re: installing kvm-76 on 2.6.24 > > On Mon, Sep 29, 2008 at 1:09 PM, Sterling Windmill <[EMAIL PROTECTED]> wrote: >> I am running a custom compiled 2.6.24 kernel on a 64-bit Intel system and >> had no issues compling and running kvm-75. >> >> I downloaded kvm-76 and compiled and installed it, but I cannot get the >> modules to load properly. >> >> I have temporarily gone back to kvm-75. >> >> I am seeing this output in dmesg: >> >> kvm: Unknown symbol kvm_iommu_map_pages >> kvm: Unknown symbol kvm_iommu_map_guest >> kvm: Unknown symbol kvm_iommu_unmap_guest > > Seems you enabled CONFIG_DMAR in host kernel side? In theory, we > should use CONFIG_DMAR with newly VT-d support in KVM, but the problem > now is that userspace including compile option is not ready, so here > comes compile problem. > > If you want to try kvm-76, you may try to disable CONFIG_DMAR in host > kernel. Or just wait to userspace VT-d support merge (of course you > can add vtd.c manually in Kbuild to overcome this compile issue). :) > > -- > regards, > Yang, Sheng > -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: installing kvm-76 on 2.6.24
Thank you for the information. I apologize for posting twice to the mailing list on the same issue. I was just trying to add some additional information. Could you tell me how to edit the Kbuild file for this purpose? I can also recompile my kernel, but that's a bit more difficult. Thanks in advance, Sterling Windmill - Original Message - From: "Sheng Yang" <[EMAIL PROTECTED]> To: "Sterling Windmill" <[EMAIL PROTECTED]> Cc: "kvm" Sent: Monday, September 29, 2008 10:21:10 AM GMT -05:00 US/Canada Eastern Subject: Re: installing kvm-76 on 2.6.24 On Mon, Sep 29, 2008 at 1:09 PM, Sterling Windmill <[EMAIL PROTECTED]> wrote: > I am running a custom compiled 2.6.24 kernel on a 64-bit Intel system and had > no issues compling and running kvm-75. > > I downloaded kvm-76 and compiled and installed it, but I cannot get the > modules to load properly. > > I have temporarily gone back to kvm-75. > > I am seeing this output in dmesg: > > kvm: Unknown symbol kvm_iommu_map_pages > kvm: Unknown symbol kvm_iommu_map_guest > kvm: Unknown symbol kvm_iommu_unmap_guest Seems you enabled CONFIG_DMAR in host kernel side? In theory, we should use CONFIG_DMAR with newly VT-d support in KVM, but the problem now is that userspace including compile option is not ready, so here comes compile problem. If you want to try kvm-76, you may try to disable CONFIG_DMAR in host kernel. Or just wait to userspace VT-d support merge (of course you can add vtd.c manually in Kbuild to overcome this compile issue). :) -- regards, Yang, Sheng -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
kvm-76 won't load on x86_64 2.6.24 with openvz
I am attempting to use kvm-76 with a x86_64 2.6.24 kernel from openvz.org The kernel .rpm and src .rpm can be found here: http://wiki.openvz.org/Download/kernel/2.6.24/2.6.24-ovz006.1 kvm-75 works fine with this kernel, but after compiling kvm-76 I get the following error when attempting to modprobe kvm_intel: WARNING: Error inserting kvm (/lib/modules/2.6.24-ovz006.1/extra/kvm.ko): Unknown symbol in module, or unknown parameter (see dmesg) FATAL: Error inserting kvm_intel (/lib/modules/2.6.24-ovz006.1/extra/kvm-intel.ko): Unknown symbol in module, or unknown parameter (see dmesg) I also see the following in dmesg: kvm: Unknown symbol kvm_iommu_map_pages kvm: Unknown symbol kvm_iommu_map_guest kvm: Unknown symbol kvm_iommu_unmap_guest kvm_intel: Unknown symbol kvm_clear_guest_page kvm_intel: Unknown symbol kvm_exit kvm_intel: Unknown symbol kvm_init kvm_intel: Unknown symbol kvm_enable_efer_bits kvm_intel: Unknown symbol kvm_timer_intr_post kvm_intel: Unknown symbol kvm_mmu_set_nonpresent_ptes kvm_intel: Unknown symbol gfn_to_page kvm_intel: Unknown symbol segment_base kvm_intel: Unknown symbol kvm_get_msr_common kvm_intel: Unknown symbol __kvm_set_memory_region kvm_intel: Unknown symbol kvm_vcpu_uninit kvm_intel: Unknown symbol kvm_emulate_halt kvm_intel: Unknown symbol kvm_set_apic_base kvm_intel: Unknown symbol kvm_report_emulation_failure kvm_intel: Unknown symbol kvm_lapic_find_highest_irr kvm_intel: Unknown symbol kvm_task_switch kvm_intel: Unknown symbol kvm_enable_tdp kvm_intel: Unknown symbol kvm_disable_tdp kvm_intel: Unknown symbol kvm_lmsw kvm_intel: Unknown symbol kvm_set_memory_region kvm_intel: Unknown symbol kvm_queue_exception kvm_intel: Unknown symbol emulate_instruction kvm_intel: Unknown symbol kvm_write_guest_page kvm_intel: Unknown symbol fx_init kvm_intel: Unknown symbol kvm_cpu_has_interrupt kvm_intel: Unknown symbol kvm_lapic_get_cr8 kvm_intel: Unknown symbol kvm_set_cr3 kvm_intel: Unknown symbol kvm_get_cr8 kvm_intel: Unknown symbol kvm_x86_ops kvm_intel: Unknown symbol kvm_vcpu_cache kvm_intel: Unknown symbol kvm_emulate_hypercall kvm_intel: Unknown symbol load_pdptrs kvm_intel: Unknown symbol kvm_handle_fault_on_reboot kvm_intel: Unknown symbol kvm_mmu_unprotect_page_virt kvm_intel: Unknown symbol kvm_set_cr4 kvm_intel: Unknown symbol kvm_set_cr0 kvm_intel: Unknown symbol kvm_set_cr8 kvm_intel: Unknown symbol kvm_lapic_enabled kvm_intel: Unknown symbol kvm_mmu_page_fault kvm_intel: Unknown symbol kvm_mmu_reset_context kvm_intel: Unknown symbol kvm_queue_exception_e kvm_intel: Unknown symbol kvm_emulate_cpuid kvm_intel: Unknown symbol kvm_vcpu_init kvm_intel: Unknown symbol gfn_to_hva kvm_intel: Unknown symbol kvm_mmu_invlpg kvm_intel: Unknown symbol kvm_set_msr_common kvm_intel: Unknown symbol kvm_mmu_set_base_ptes kvm_intel: Unknown symbol kvm_cpu_get_interrupt kvm_intel: Unknown symbol kvm_emulate_pio kvm_intel: Unknown symbol kvm_mmu_set_mask_ptes kvm_intel: Unknown symbol kvm_is_error_hva Here is a link to the .config file used when this kernel was compiled: http://download.openvz.org/kernel/branches/2.6.24/2.6.24-ovz006.1/configs/kernel-2.6.24-x86_64.config.ovz -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
installing kvm-76 on 2.6.24
I am running a custom compiled 2.6.24 kernel on a 64-bit Intel system and had no issues compling and running kvm-75. I downloaded kvm-76 and compiled and installed it, but I cannot get the modules to load properly. I have temporarily gone back to kvm-75. I am seeing this output in dmesg: kvm: Unknown symbol kvm_iommu_map_pages kvm: Unknown symbol kvm_iommu_map_guest kvm: Unknown symbol kvm_iommu_unmap_guest kvm_intel: Unknown symbol kvm_clear_guest_page kvm_intel: Unknown symbol kvm_exit kvm_intel: Unknown symbol kvm_init kvm_intel: Unknown symbol kvm_enable_efer_bits kvm_intel: Unknown symbol kvm_timer_intr_post kvm_intel: Unknown symbol kvm_mmu_set_nonpresent_ptes kvm_intel: Unknown symbol gfn_to_page kvm_intel: Unknown symbol segment_base kvm_intel: Unknown symbol kvm_get_msr_common kvm_intel: Unknown symbol __kvm_set_memory_region kvm_intel: Unknown symbol kvm_vcpu_uninit kvm_intel: Unknown symbol kvm_emulate_halt kvm_intel: Unknown symbol kvm_set_apic_base kvm_intel: Unknown symbol kvm_report_emulation_failure kvm_intel: Unknown symbol kvm_lapic_find_highest_irr kvm_intel: Unknown symbol kvm_task_switch kvm_intel: Unknown symbol kvm_enable_tdp kvm_intel: Unknown symbol kvm_disable_tdp kvm_intel: Unknown symbol kvm_lmsw kvm_intel: Unknown symbol kvm_set_memory_region kvm_intel: Unknown symbol kvm_queue_exception kvm_intel: Unknown symbol emulate_instruction kvm_intel: Unknown symbol kvm_write_guest_page kvm_intel: Unknown symbol fx_init kvm_intel: Unknown symbol kvm_cpu_has_interrupt kvm_intel: Unknown symbol kvm_lapic_get_cr8 kvm_intel: Unknown symbol kvm_set_cr3 kvm_intel: Unknown symbol kvm_get_cr8 kvm_intel: Unknown symbol kvm_x86_ops kvm_intel: Unknown symbol kvm_vcpu_cache kvm_intel: Unknown symbol kvm_emulate_hypercall kvm_intel: Unknown symbol load_pdptrs kvm_intel: Unknown symbol kvm_handle_fault_on_reboot kvm_intel: Unknown symbol kvm_mmu_unprotect_page_virt kvm_intel: Unknown symbol kvm_set_cr4 kvm_intel: Unknown symbol kvm_set_cr0 kvm_intel: Unknown symbol kvm_set_cr8 kvm_intel: Unknown symbol kvm_lapic_enabled kvm_intel: Unknown symbol kvm_mmu_page_fault kvm_intel: Unknown symbol kvm_mmu_reset_context kvm_intel: Unknown symbol kvm_queue_exception_e kvm_intel: Unknown symbol kvm_emulate_cpuid kvm_intel: Unknown symbol kvm_vcpu_init kvm_intel: Unknown symbol gfn_to_hva kvm_intel: Unknown symbol kvm_mmu_invlpg kvm_intel: Unknown symbol kvm_set_msr_common kvm_intel: Unknown symbol kvm_mmu_set_base_ptes kvm_intel: Unknown symbol kvm_cpu_get_interrupt kvm_intel: Unknown symbol kvm_emulate_pio kvm_intel: Unknown symbol kvm_mmu_set_mask_ptes kvm_intel: Unknown symbol kvm_is_error_hva -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
