search for: config_debug_level

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...

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...

...ing, support isn't upstream, ran into a bunch of issues[1][2] last time I tried to combine the two, ran into some issues and nobody seemed to care, so the seabios patches where just sitting in a branch in my repo ... > $ cat .config | grep 'KVMTOOL\|DEBUG' > CONFIG_KVMTOOL=y > CONFIG_DEBUG_LEVEL=9 Hmm, 'CONFIG_KVMTOOL=y > .config; make olddefconfig' should give you a working configuration. Setting 'CONFIG_DEBUG_LEVEL=9' is useful for trouble-shooting as it makes the virtio drivers more verbose, but not mandatory to have. Serial line support is needed to get output: C...

...ran into a bunch of issues[1][2] > last time I tried to combine the two, ran into some issues and nobody > seemed to care, so the seabios patches where just sitting in a branch in > my repo ... > >> $ cat .config | grep 'KVMTOOL\|DEBUG' >> CONFIG_KVMTOOL=y >> CONFIG_DEBUG_LEVEL=9 > > Hmm, 'CONFIG_KVMTOOL=y > .config; make olddefconfig' should give you a > working configuration. > > Setting 'CONFIG_DEBUG_LEVEL=9' is useful for trouble-shooting as it > makes the virtio drivers more verbose, but not mandatory to have. > > Serial...

...ran into a bunch of issues[1][2] > last time I tried to combine the two, ran into some issues and nobody > seemed to care, so the seabios patches where just sitting in a branch in > my repo ... > >> $ cat .config | grep 'KVMTOOL\|DEBUG' >> CONFIG_KVMTOOL=y >> CONFIG_DEBUG_LEVEL=9 > > Hmm, 'CONFIG_KVMTOOL=y > .config; make olddefconfig' should give you a > working configuration. > > Setting 'CONFIG_DEBUG_LEVEL=9' is useful for trouble-shooting as it > makes the virtio drivers more verbose, but not mandatory to have. > > Serial...

...n. > To sum it up: this is a lightly tested version for feedback 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...

Hi all, this is the tenth version of the patch series to introduce upstream qemu and seabios in the xen-unstable build system. Changes to v9: - rename QEMU_UPSTREAM_TAG to QEMU_UPSTREAM_REVISION: we are going to use it with a branch name by default; - set QEMU_UPSTREAM_REVISION to "master" by default; - set SEABIOS_UPSTREAM_URL to git://xenbits.xen.org/seabios.git by default; - add

This is a first go at adding support for the modern (based on the 1.0 virtio spec) virtio-pci implementation. kvmtool makes it simple to add additional transports such as this because of it's layering, so we are able to add it as a 3rd (after legacy virtio-pci and virtio-mmio) transport layer, and still allow users to choose to use either the legacy or the modern implementations (but setting

This is a first go at adding support for the modern (based on the 1.0 virtio spec) virtio-pci implementation. kvmtool makes it simple to add additional transports such as this because of it's layering, so we are able to add it as a 3rd (after legacy virtio-pci and virtio-mmio) transport layer, and still allow users to choose to use either the legacy or the modern implementations (but setting