search for: lkvm

...9;t think that you can depend on the device to set the configuration >> > changed bit. >> > The virtio 1.0 spec seems to have fixed that. > Yes, virtio 0.9.5 has this bug. But in practice qemu always set this > bit, so for qemu we could do that unconditionally. Pekka's lkvm tool > doesn't unfortunately. It's easy to fix that, but it would be nicer to > additionally probe for old versions of the tool, and disable IRQF_SHARED > in that case. > > To complicate things, lkvm does not use a distinct subsystem vendor ID, > in spite of the fact the...

...9;t think that you can depend on the device to set the configuration >> > changed bit. >> > The virtio 1.0 spec seems to have fixed that. > Yes, virtio 0.9.5 has this bug. But in practice qemu always set this > bit, so for qemu we could do that unconditionally. Pekka's lkvm tool > doesn't unfortunately. It's easy to fix that, but it would be nicer to > additionally probe for old versions of the tool, and disable IRQF_SHARED > in that case. > > To complicate things, lkvm does not use a distinct subsystem vendor ID, > in spite of the fact the...

On Monday 01 September 2014 09:37:30, Michael S. Tsirkin wrote: > Why do we need INT#x? > How about setting IRQF_SHARED for the config interrupt > while using MSI-X? You'd have to read ISR to check that the > interrupt was intended for your device. The virtio 0.9.5 spec says that ISR is "unused" when in MSI-X mode. I don't think that you can depend on the device to

On Monday 01 September 2014 09:37:30, Michael S. Tsirkin wrote: > Why do we need INT#x? > How about setting IRQF_SHARED for the config interrupt > while using MSI-X? You'd have to read ISR to check that the > interrupt was intended for your device. The virtio 0.9.5 spec says that ISR is "unused" when in MSI-X mode. I don't think that you can depend on the device to

I'm curious exactly how KVM works. If i see things right it's virtualization that's still within a full base operating system load correct? How does KVM perform against VMware which uses a much smaller footprint? Is KVM really a hypervisor? I'm just trying figure out the basics of KVM..:) Thanks, William Warren

...MSI-X mode. I > don't think that you can depend on the device to set the configuration > changed bit. > The virtio 1.0 spec seems to have fixed that. Yes, virtio 0.9.5 has this bug. But in practice qemu always set this bit, so for qemu we could do that unconditionally. Pekka's lkvm tool doesn't unfortunately. It's easy to fix that, but it would be nicer to additionally probe for old versions of the tool, and disable IRQF_SHARED in that case. To complicate things, lkvm does not use a distinct subsystem vendor ID, in spite of the fact the virtio spec always required t...

...t; > >> > changed bit. >>>>> > >> > The virtio 1.0 spec seems to have fixed that. >>> > > Yes, virtio 0.9.5 has this bug. But in practice qemu always set this >>> > > bit, so for qemu we could do that unconditionally. Pekka's lkvm tool >>> > > doesn't unfortunately. It's easy to fix that, but it would be nicer to >>> > > additionally probe for old versions of the tool, and disable IRQF_SHARED >>> > > in that case. >>> > > >>> > > To complicat...

...t; > >> > changed bit. >>>>> > >> > The virtio 1.0 spec seems to have fixed that. >>> > > Yes, virtio 0.9.5 has this bug. But in practice qemu always set this >>> > > bit, so for qemu we could do that unconditionally. Pekka's lkvm tool >>> > > doesn't unfortunately. It's easy to fix that, but it would be nicer to >>> > > additionally probe for old versions of the tool, and disable IRQF_SHARED >>> > > in that case. >>> > > >>> > > To complicat...

...ce (the mount is just there for a quick test, in reality supermin itself should probably leave the unpacker dir around): > https://gist.github.com/anonymous/5cdbc18974f88d6ea9e0 > > Next step: kvmtool [3]. Avoids some delays introduced by legacy BIOS boot, and device probing, however > lkvm currently lacks support for additional virtio-serial channels, so - although the supermin appliance would boot - guestfsd wouldn't be able to communicate with the host: > https://gist.github.com/anonymous/e6b0a12e1da811f24e5b > > I tried QBoot [4], which requires that you first strip...

...o create the 9p device (the mount is just there for a quick test, in reality supermin itself should probably leave the unpacker dir around): https://gist.github.com/anonymous/5cdbc18974f88d6ea9e0 Next step: kvmtool [3]. Avoids some delays introduced by legacy BIOS boot, and device probing, however lkvm currently lacks support for additional virtio-serial channels, so - although the supermin appliance would boot - guestfsd wouldn't be able to communicate with the host: https://gist.github.com/anonymous/e6b0a12e1da811f24e5b I tried QBoot [4], which requires that you first strip down your kern...

...an depend on the device to set the configuration > >> > changed bit. > >> > The virtio 1.0 spec seems to have fixed that. > > Yes, virtio 0.9.5 has this bug. But in practice qemu always set this > > bit, so for qemu we could do that unconditionally. Pekka's lkvm tool > > doesn't unfortunately. It's easy to fix that, but it would be nicer to > > additionally probe for old versions of the tool, and disable IRQF_SHARED > > in that case. > > > > To complicate things, lkvm does not use a distinct subsystem vendor ID, >...

On 03/15/2016 21:34, Richard W.M. Jones wrote: > I was looking at Clear Containers last week. > [...] > > This is all very good analysis. Thanks, looks like I raised the question at a good time :) > > The issues that I had in brief were: > > (1) We could run kvmtool, perhaps by adding a new backend, but it > seems a better idea to add the required features to qemu.

On 11/18/2015 03:22 AM, Gerd Hoffmann wrote: > /me goes undust the kvmtool patches for seabios. > > (see https://www.kraxel.org/cgit/seabios/commit/?h=kvmtool, > build with CONFIG_KVMTOOL=y + CONFIG_DEBUG_LEVEL=9) > > nilsson kraxel ~# ~kraxel/projects/kvmtool/lkvm run --name seabios > --firmware /home/kraxel/projects/seabios/out-bios-kvmtool/bios.bin > --disk /vmdisk/cloud/persistent/Fedora-Cloud-Base-22-20150521.x86_64.raw > # lkvm run -k /boot/vmlinuz-3.10.0-324.el7.x86_64 -m 448 -c 4 --name > seabios Thanks for testing! I didn't even th...

On 11/18/2015 03:22 AM, Gerd Hoffmann wrote: > /me goes undust the kvmtool patches for seabios. > > (see https://www.kraxel.org/cgit/seabios/commit/?h=kvmtool, > build with CONFIG_KVMTOOL=y + CONFIG_DEBUG_LEVEL=9) > > nilsson kraxel ~# ~kraxel/projects/kvmtool/lkvm run --name seabios > --firmware /home/kraxel/projects/seabios/out-bios-kvmtool/bios.bin > --disk /vmdisk/cloud/persistent/Fedora-Cloud-Base-22-20150521.x86_64.raw > # lkvm run -k /boot/vmlinuz-3.10.0-324.el7.x86_64 -m 448 -c 4 --name > seabios Thanks for testing! I didn't even th...

...'t think that you can depend on the device to set the > > configuration changed bit. > > The virtio 1.0 spec seems to have fixed that. > > Yes, virtio 0.9.5 has this bug. But in practice qemu always set this > bit, so for qemu we could do that unconditionally. Pekka's lkvm > tool doesn't unfortunately. It's easy to fix that, but it would be > nicer to additionally probe for old versions of the tool, and > disable IRQF_SHARED in that case. What about other implementations? I think Linux should try to conform to the spec so that all device implement...

...'t think that you can depend on the device to set the > > configuration changed bit. > > The virtio 1.0 spec seems to have fixed that. > > Yes, virtio 0.9.5 has this bug. But in practice qemu always set this > bit, so for qemu we could do that unconditionally. Pekka's lkvm > tool doesn't unfortunately. It's easy to fix that, but it would be > nicer to additionally probe for old versions of the tool, and > disable IRQF_SHARED in that case. What about other implementations? I think Linux should try to conform to the spec so that all device implement...

Dear Gurus I have been unable to make sound (and microphone) work in Windows 7 (64-bit) as a VM with KVM. Google searches reveal this to be a common problem, with various solutions recommended, primarily Ubuntu oriented, none of which have worked for me. So I wonder if anyone has a working Windows sound condition with: Centos 6.5 with KVM, all on a 64-bit Intel platform. Sound works on the

...ck about the design > and to weed out major bugs people notice. Feedback is very welcome! /me goes undust the kvmtool patches for seabios. (see https://www.kraxel.org/cgit/seabios/commit/?h=kvmtool, build with CONFIG_KVMTOOL=y + CONFIG_DEBUG_LEVEL=9) nilsson kraxel ~# ~kraxel/projects/kvmtool/lkvm run --name seabios --firmware /home/kraxel/projects/seabios/out-bios-kvmtool/bios.bin --disk /vmdisk/cloud/persistent/Fedora-Cloud-Base-22-20150521.x86_64.raw # lkvm run -k /boot/vmlinuz-3.10.0-324.el7.x86_64 -m 448 -c 4 --name seabios Changing serial settings was 0/0 now 3/0 SeaBIOS (version rel...

...nks it needs to remain in the tree? Can we hold on a tiny bit so that I can verify we haven't regressed crosvm all the way into mainline? Daniel, is there any chance you could test with kvmtool as well on your setup? You can easily compile it as a static binary and run it from ChromeOS with: lkvm-static run -c 1 -p "earlycon=uart,mmio,0x3f8" -l Image which should start a UP guest and drop you to a shell. In the meantime, I'm starting to build crosvm on my kevin running mainline. Thanks, M. -- Jazz is not dead, it just smell funny.

...nks it needs to remain in the tree? Can we hold on a tiny bit so that I can verify we haven't regressed crosvm all the way into mainline? Daniel, is there any chance you could test with kvmtool as well on your setup? You can easily compile it as a static binary and run it from ChromeOS with: lkvm-static run -c 1 -p "earlycon=uart,mmio,0x3f8" -l Image which should start a UP guest and drop you to a shell. In the meantime, I'm starting to build crosvm on my kevin running mainline. Thanks, M. -- Jazz is not dead, it just smell funny.