Re: [Qemu-discuss] passing network options to the guest

2013-11-22 Thread Bandan Das
Mahmood Naderan writes: > Hi, I have installed a windows xp on qemu-x86 host with the option > "-net nic". However after installation, there is no network > connection. Think that you are installing a windows on a real machine > which has no network interface. Windows installer won't create a > n

Re: [Qemu-discuss] linux: ioctl(KVM_CREATE_VM) failed: 12 Cannot allocate memory

2015-02-26 Thread Bandan Das
> On Feb 26, 2015, at 9:12 PM, Ken Moffat wrote: > > I had kvm working fine (i686 guest) from a new x86_64 host system - > after fixing up some Xorg server issues - and then I decided to > create a new x86_64 guest (this is linuxfromscratch, so using an old > guest to build a new one). But now

Re: [Qemu-discuss] Error starting domain: vfio-pci

2015-05-19 Thread Bandan Das
Hello Gabriel, > On May 19, 2015, at 8:03 PM, Gabriel Laupre wrote: > > Hello everyone, > > I am using a Centos 7.1 machine with the kernel 3.10.229. I want to use my > host with SR-IOV to use a virtual function on my NIC as the vNIC in my new VM. > > I have an instance started with a old NI

Re: [Qemu-discuss] Error starting domain: vfio-pci

2015-05-19 Thread Bandan Das
ot 10, 196 May 18 11:54 vfio > The right should be okay I guess. > Yes, indeed it is. What distro is this ? Do you have SELinux or any other security feature enabled ? Can you please verify that the file has a appropriate label if SELinux is enabled ? (ls -lZ /dev/vfio/vfio) Bandan >

Re: [Qemu-discuss] Error starting domain: vfio-pci

2015-05-20 Thread Bandan Das
5157Z qemu-kvm: -device > vfio-pci,host=04:10.4,id=hostdev0,bus=pci.0,addr=0x3: Device > 'vfio-pci' could not be initialized > > > > > 2015-05-19 21:17 GMT-08:00 Bandan Das : > >> >> > On May 20, 2015, at 12:29 AM, Gabriel Laupre wrote: >>

Re: [Qemu-discuss] Error starting domain: vfio-pci

2015-05-20 Thread Bandan Das
Oh and one more thing! You already answered before but just wanted to confirm that you don't have apparmor running, right ? Bandan Das writes: > Gabriel Laupre writes: > >>> Yes, indeed it is. What distro is this ? Do you have SELinux or any other >> security featur

Re: [Qemu-discuss] Error starting domain: vfio-pci

2015-05-20 Thread Bandan Das
Gabriel Laupre writes: > Mmmhh, > My SELinux is disabled. Is Apparmor not only on debian/ubuntu and suse, am > I wrong? I have no idea on that :) Yeah, me neither :) I am just trying to rule out all possibilities. > 2015-05-20 11:23 GMT-07:00 Bandan Das : > >> Oh an

Re: [Qemu-discuss] Error starting domain: vfio-pci

2015-05-21 Thread Bandan Das
07:00 Karl Apsite : > >> AppArmor is Debian based, but that doesn't stop you from >> running/installing it >> on other distros >> >> $ dmesg | grep apparmor >> >> On 05/20/2015 02:56 PM, Bandan Das wrote: >> > Gabriel Laupre writes: >> &g

Re: [Qemu-discuss] Error starting domain: vfio-pci

2015-05-22 Thread Bandan Das
nterested and I will write down the steps. > 2015-05-21 13:32 GMT-07:00 Bandan Das : > >> Gabriel Laupre writes: >> >> >> AppArmor is Debian based, but that doesn't stop you from >> > running/installing it on other distros >> > >> &

Re: [Qemu-discuss] Error starting domain: vfio-pci

2015-05-22 Thread Bandan Das
stdio I think this should be enough to spit out the error, there's no need to actually boot a guest image. > 2015-05-22 10:46 GMT-07:00 Bandan Das : > >> Gabriel Laupre writes: >> >> >> Thanks for the update. Did you get a chance to run qemu standalone >> &g

Re: [Qemu-discuss] Error starting domain: vfio-pci

2015-05-22 Thread Bandan Das
slot is already used up in the guest. Just, try using a different slot number. > 2015-05-22 12:00 GMT-07:00 Bandan Das : > >> Gabriel Laupre writes: >> >> >>To rule out if it's a problem with your guest xml. Let me know if you are >> > interested a

Re: [Qemu-discuss] Error starting domain: vfio-pci

2015-05-22 Thread Bandan Das
and > # virsh nodedev-detach pci__04_01_4 You may need to detach all VFs if they are in the same iommu group. Also, check if dmesg has any relevant messages when this error occurs. > My goodness, what's going on :P Thank for you time Bandan, I really > appreciate > > 2015-05-

Re: [Qemu-discuss] Error starting domain: vfio-pci

2015-05-27 Thread Bandan Das
gt; and in my dmesg I have the new entry: > [14346.555141] vfio-pci :04:01.4: enabling device ( -> 0002) > > > > 2015-05-22 13:37 GMT-07:00 Bandan Das : > > Gabriel Laupre writes: > > >> Just, try using a different slot number. > > I changed the addr

Re: [Qemu-discuss] Error starting domain: vfio-pci

2015-06-08 Thread Bandan Das
-device > vfio-pci,host=04:02.4,id=hostdev0,bus=pci.0,addr=0x7,rombar=0: vfio: failed > to setup container for group 24 > 2015-06-05T21:41:43.855613Z qemu-kvm: -device > vfio-pci,host=04:02.4,id=hostdev0,bus=pci.0,addr=0x7,rombar=0: vfio: failed > to get group 24 > 2015-06-05T21:41:43

Re: [Qemu-discuss] run vxworks on kvm fail

2015-07-15 Thread Bandan Das
"2020human" writes: > Hello > I am run vxworks on kvm , My vxworks is bootable ISO, this iso working vmware > no problem,but the ISO can not start in the KVM. What version is the kernel version on the host ? Can you try latest upstream - 4.1 maybe ? Bandan > > error log: > 2015-07-15 03:48:0

Re: [Qemu-discuss] Unable to find any system Interface(s) -qemu-2.30 RHEL 7.1

2015-07-16 Thread Bandan Das
"Rapelly, Varun" writes: > Hi, > > I'm using following command line arguments to launch the KVM. KVM launches > successfully, but during boot process, it displays "Unable to find any System > Iterface(s), udevd[3393]: starting version 175" message, and it hangs there > only. > > [root@warmtong

Re: [Qemu-discuss] Supported hypervisors running VMs in nested VM

2015-10-03 Thread Bandan Das
... > Windows 2012 / 2016 technical preview 3 > > The installation via the "default" method of Add/Remove Features does > not work. Hyper-V displays the error message "A hypervisor is already > running". > > This check can be skipped by usin

Re: [Qemu-discuss] Supported hypervisors running VMs in nested VM

2015-10-05 Thread Bandan Das
: --H- > > Not sure how to do that in Qemu or what it does. Looking at > https://en.wikipedia.org/wiki/CPUID, it seems to disable the XSAVE > instruction(?). For fun, I passed -cpu ...-xsave, but it did not seem > to make any difference whats

Re: [Qemu-discuss] Supported hypervisors running VMs in nested VM

2015-10-05 Thread Bandan Das
ml/qemu-devel/2015-01/msg01371.html. > I guess it really IS important to know what you're googling for to > find things fast... > > That thread simply says that the kernel is too old. Well, my host is > running 4.2, so should be new enough. > I'm a bit stuck.

Re: [Qemu-discuss] Supported hypervisors running VMs in nested VM

2015-10-06 Thread Bandan Das
runs L2, you don’t have to worry about using —enable-kvm. Hyper-V should automatically detect available hardware features available to it and attempt to enable hardware virtualization. > Sincerely, > Roel Brook. > > 2015-10-05 23:17 GMT+02:00 Bandan Das : >> Rain Maker

Re: [Qemu-discuss] Supported hypervisors running VMs in nested VM

2015-10-08 Thread Bandan Das
p so far. BTW you are mixing up cases by using/not using "-enable-kvm" in your command line. What I mentioned is specific to kvm only, qemu probably will always return a 0 for certain msrs (like this one). > Roel Brook > > > > > 2015-10-07 5:07 GMT+02:00 Bandan Das : >&g

Re: [Qemu-discuss] Supported hypervisors running VMs in nested VM

2015-10-12 Thread Bandan Das
my host > machine, and do the same in L1 VMs. So it must be one of the other > ones. Unfortunately, most of them are not listed in the Intel spec.. I am assuming you are running a Windows L2. So, what might be happening is that the L2 guest might be trying to access the enlightenment msrs which ofco

Re: [Qemu-discuss] Qemu "-cpu host" option

2015-11-26 Thread Bandan Das
> On Nov 26, 2015, at 12:33 PM, Abhinav Sharma wrote: > > Hi, > What does Qemu do when invoked using "-cpu host" option that sets target CPU > same as the host CPU? > > Is it that when this option is used Qemu performs no binary translation? > Because the target CPU is same as host CPU, code

Re: [Qemu-discuss] Windows-10 virtualization and nested virtualization

2016-04-04 Thread Bandan Das
Jeff Forbes writes: > We have a Windows-10 application which uses a virtual as part of the > process. I am trying to get the application to work in a virtual > environment, which of course will require nested virtualization. > > Using a libvirt xml description for a RHEL virtual where nested

Re: [Qemu-discuss] Boot fail after compiling the Kernel.

2016-07-28 Thread Bandan Das
> On Jul 28, 2016, at 10:16 PM, John Y. wrote: > > Hi, > > I have a centos 5.8 guest with 2.6.18 kernel. > I compiled the kernel 2.6.35.4 and boot from it. > > (It could boot successfully in my labtop, but fail in guest created by > qemu-kvm) > But I get errors: > > > Kernel panic - not sy

Re: [Qemu-discuss] setting only x86_64 arch for qemu build (newbie)

2017-01-08 Thread Bandan Das
> On Jan 8, 2017, at 8:46 AM, Kevin Wilson wrote: > > Hi, all, > How do I set usage of only x86_64 arch for qemu build (newbie)? > ./configure —target-list=x86_64-softmmu > when I build the project after some trivial change in code (adding > debug message), I see > that the build process runs

Re: [Qemu-discuss] qemu 2.8.50 Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed

2017-02-02 Thread Bandan Das
"Matwey V. Kornilov" writes: > 02.02.2017 22:36, Matwey V. Kornilov пишет: >> >> Hello, >> >> I see the following when try to run qemu from master as the following: >> >> # ./x86_64-softmmu/qemu-system-x86_64 --version >> QEMU emulator version 2.8.50 (v2.8.0-1006-g4e9f524) >> Copyright (c) 200

Re: [Qemu-discuss] qemu 2.8.50 Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed

2017-02-02 Thread Bandan Das
"Matwey V. Kornilov" writes: > 2017-02-03 0:13 GMT+03:00 Bandan Das : >> "Matwey V. Kornilov" writes: >> >>> 02.02.2017 22:36, Matwey V. Kornilov пишет: >>>> >>>> Hello, >>>> >>>> I see the following

Re: [Qemu-discuss] qemu 2.8.50 Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed

2017-02-03 Thread Bandan Das
"Matwey V. Kornilov" writes: ... I think this means that KVM gave you a list of msrs but when you tried to set them, it could not set all of them and hence, the assert triggers. Are you using a modified kernel ? There could be something useful in the host dmesg

Re: [Qemu-discuss] Getting The Performance monitoring interrupt fired

2017-02-06 Thread Bandan Das
Parfait Tokponnon writes: > Hello > > I wrote some module in my hobby OS kernel to issue the performance > monitoring interrupt (PMI) on instructions counter overflow. It works well > on my machine (Intel core i5). But when I run it on qemu using > > qemu-system-x86_64 -enable-kvm -cpu host -m 25

Re: [Qemu-discuss] Getting The Performance monitoring interrupt fired

2017-02-10 Thread Bandan Das
Parfait Tokponnon writes: > Hello Bandan, > Thank you for your reply; > > 2017-02-07 0:14 GMT+01:00 Bandan Das : > >> KVM implements a subset but I think this should work. Could it be that >> interrupts >> are not firing exactly when you want them ? >