KVM Forum 2018: Call For Participation
by Paolo Bonzini
================================================================
KVM Forum 2018: Call For Participation
October 24-26, 2018 - Edinburgh International Conference Centre - Edinburgh, UK
(All submissions must be received before midnight June 14, 2018)
=================================================================
KVM Forum is an annual event that presents a rare opportunity
for developers and users to meet, discuss the state of Linux
virtualization technology, and plan for the challenges ahead.
We invite you to lead part of the discussion by submitting a speaking
proposal for KVM Forum 2018.
At this highly technical conference, developers driving innovation
in the KVM virtualization stack (Linux, KVM, QEMU, libvirt) can
meet users who depend on KVM as part of their offerings, or to
power their data centers and clouds.
KVM Forum will include sessions on the state of the KVM
virtualization stack, planning for the future, and many
opportunities for attendees to collaborate. After more than ten
years of development in the Linux kernel, KVM continues to be a
critical part of the FOSS cloud infrastructure.
This year, KVM Forum is joining Open Source Summit in Edinburgh, UK. Selected
talks from KVM Forum will be presented on Wednesday October 24 to the full
audience of the Open Source Summit. Also, attendees of KVM Forum will have
access to all of the talks from Open Source Summit on Wednesday.
https://events.linuxfoundation.org/events/kvm-forum-2018/program/cfp/
Suggested topics:
* Scaling, latency optimizations, performance tuning, real-time guests
* Hardening and security
* New features
* Testing
KVM and the Linux kernel:
* Nested virtualization
* Resource management (CPU, I/O, memory) and scheduling
* VFIO: IOMMU, SR-IOV, virtual GPU, etc.
* Networking: Open vSwitch, XDP, etc.
* virtio and vhost
* Architecture ports and new processor features
QEMU:
* Management interfaces: QOM and QMP
* New devices, new boards, new architectures
* Graphics, desktop virtualization and virtual GPU
* New storage features
* High availability, live migration and fault tolerance
* Emulation and TCG
* Firmware: ACPI, UEFI, coreboot, U-Boot, etc.
Management and infrastructure
* Managing KVM: Libvirt, OpenStack, oVirt, etc.
* Storage: Ceph, Gluster, SPDK, etc.r
* Network Function Virtualization: DPDK, OPNFV, OVN, etc.
* Provisioning
===============
SUBMITTING YOUR PROPOSAL
===============
Abstracts due: June 14, 2018
Please submit a short abstract (~150 words) describing your presentation
proposal. Slots vary in length up to 45 minutes. Also include the proposal
type -- one of:
- technical talk
- end-user talk
Submit your proposal here:http://events.linuxfoundation.org/cfp
Please only use the categories "presentation" and "panel discussion"
You will receive a notification whether or not your presentation proposal
was accepted by August 10, 2018.
Speakers will receive a complimentary pass for the event. In the instance
that case your submission has multiple presenters, only the primary speaker for a
proposal will receive a complimentary event pass. For panel discussions, all
panelists will receive a complimentary event pass.
TECHNICAL TALKS
A good technical talk should not just report on what has happened over
the last year; it should present a concrete problem and how it impacts
the user and/or developer community. Whenever applicable, focus on
work that needs to be done, difficulties that haven't yet been solved,
and on decisions that other developers should be aware of. Summarizing
recent developments is okay but it should not be more than a small
portion of the overall talk.
END-USER TALKS
One of the big challenges as developers is to know what, where and how
people actually use our software. We will reserve a few slots for end
users talking about their deployment challenges and achievements.
If you are using KVM in production you are encouraged submit a speaking
proposal. Simply mark it as an end-user talk. As an end user, this is a
unique opportunity to get your input to developers.
HANDS-ON / BOF SESSIONS
We will reserve some time for people to get together and discuss
strategic decisions as well as other topics that are best solved within
smaller groups.
These sessions will be announced during the event. If you are interested
in organizing such a session, please add it to the list at
http://www.linux-kvm.org/page/KVM_Forum_2018_BOF
Let people you think who might be interested know about your BOF, and encourage
them to add their names to the wiki page as well. Please try to
add your ideas to the list before KVM Forum starts.
PANEL DISCUSSIONS
If you are proposing a panel discussion, please make sure that you list
all of your potential panelists in your the abstract. We will request full
biographies if a panel is acceped.
===============
HOTEL / TRAVEL
===============
This year's event will take place at the Edinburgh International Conference Centre.
For information about discounted hotel room rate for conference attendees
at the nearby Sheraton Grand Hotel & Spa, Edinburgh, please visit
https://events.linuxfoundation.org/events/kvm-forum-2018/attend/venue-tra...
===============
IMPORTANT DATES
===============
Submission deadline: June 14, 2018
Notification: August 10, 2018
Schedule announced: August 16, 2018
Event dates: October 24-26, 2018
Thank you for your interest in KVM. We're looking forward to your
submissions and seeing you at the KVM Forum 2018 in October!
-your KVM Forum 2018 Program Committee
Please contact us with any questions or comments at
kvm-forum-2018-pc(a)redhat.com
7 months, 1 week
[PATCH 0/6] qemu: add bochs-display support
by Gerd Hoffmann
Add support for the new bochs-display device in qemu.
Gerd Hoffmann (6):
pci,optionrom: enable non-vga display devices
cbvga: factor out cbvga_setup_modes()
qemu: add bochs-display support
cbvga_setup_modes: use real mode number instead of 0x140
cbvga_list_modes: don't list current mode twice
[workaround] cbvga_set_mode: disable clearmem
vgasrc/vgahw.h | 28 ++++++------
vgasrc/vgautil.h | 1 +
src/fw/pciinit.c | 15 +++++--
src/optionroms.c | 29 ++++++++++++-
vgasrc/cbvga.c | 127 +++++++++++++++++++++++++++++++++++++++++++------------
vgasrc/Kconfig | 17 ++++++++
6 files changed, 173 insertions(+), 44 deletions(-)
--
2.9.3
7 months, 3 weeks
Re: [SeaBIOS] [PATCH 0/6] qemu: add bochs-display support
by Patrick Rudolph
Patch 2, 4 and 5 looks good to me.
Patch 6 causes artifacts on mode change, if the new mode is smaller
than the previous.
Would it be possible to include a 32bit memset into seavgabios ?
That way there is no need to call a BIOS routine to clear the memory.
Regards,
Patrick
On Thu, 2018-05-31 at 08:33 +0200, Gerd Hoffmann wrote:
> Add support for the new bochs-display device in qemu.
>
> Gerd Hoffmann (6):
> pci,optionrom: enable non-vga display devices
> cbvga: factor out cbvga_setup_modes()
> qemu: add bochs-display support
> cbvga_setup_modes: use real mode number instead of 0x140
> cbvga_list_modes: don't list current mode twice
> [workaround] cbvga_set_mode: disable clearmem
>
> vgasrc/vgahw.h | 28 ++++++------
> vgasrc/vgautil.h | 1 +
> src/fw/pciinit.c | 15 +++++--
> src/optionroms.c | 29 ++++++++++++-
> vgasrc/cbvga.c | 127 +++++++++++++++++++++++++++++++++++++++++++------------
> vgasrc/Kconfig | 17 ++++++++
> 6 files changed, 173 insertions(+), 44 deletions(-)
>
7 months, 3 weeks
[PATCH] gitignore: ignore config.mak
by Ciro Santilli
---
Resending because I had not subscribed previously and it bounced.
.gitignore | 1 +
1 file changed, 1 insertion(+)
diff --git a/.gitignore b/.gitignore
index f9990fe..15c0b1a 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,3 +1,4 @@
+config.mak
out
*.pyc
.config
--
2.16.1
8 months
Re: [SeaBIOS] SecureDrive
by Аладышев Константин
I guess it is not possible.. Found this article on vendor site
https://www.transcend-info.com/Support/FAQ-409
"- Can the JetFlash be used as a bootable flash drive?"
"JetFlash series aims at being a portable storage device and not as a
bootable drive. No exclusive software tool is provided either."
Best Regards,
Aladyshev Konstantin
From: Аладышев Константин [mailto:aladyshev@nicevt.ru]
Sent: Thursday, May 17, 2018 2:50 PM
To: 'seabios(a)seabios.org'
Cc: kevin(a)koconnor.net
Subject: SecureDrive
I'm having problems with USB boot from Transcend JetFlash 620 drive 32GB.
SeaBIOS doesn't see it as boot device. I suppose the problem is in
SecureDrive technology that is used on this device. I tried to remove it
with "CD-ROM Remover_v1.0.0.3" tool that I've found. It removed CD partition
from OS, but SeaBIOS still can't see flash drive as boot device.
Does someone know how to solve this issue?
Best Regards,
Aladyshev Konstantin
8 months, 1 week
SecureDrive
by Аладышев Константин
I'm having problems with USB boot from Transcend JetFlash 620 drive 32GB.
SeaBIOS doesn't see it as boot device. I suppose the problem is in
SecureDrive technology that is used on this device. I tried to remove it
with "CD-ROM Remover_v1.0.0.3" tool that I've found. It removed CD partition
from OS, but SeaBIOS still can't see flash drive as boot device.
Does someone know how to solve this issue?
Best Regards,
Aladyshev Konstantin
8 months, 1 week
[PATCH] Enable shell-like * globing in bootorder entries
by Ian Kelling
Signed-off-by: Ian Kelling <ian(a)iankelling.org>
---
src/boot.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/src/boot.c b/src/boot.c
index ff705fd..ca64595 100644
--- a/src/boot.c
+++ b/src/boot.c
@@ -91,14 +91,14 @@ glob_prefix(const char *glob, const char *str)
}
}
-// Search the bootorder list for the given glob pattern.
+// Search the bootorder glob list for the given device description
static int
-find_prio(const char *glob)
+find_prio(const char *desc)
{
- dprintf(1, "Searching bootorder for: %s\n", glob);
+ dprintf(1, "Searching bootorder for: %s\n", desc);
int i;
for (i = 0; i < BootorderCount; i++)
- if (glob_prefix(glob, Bootorder[i]))
+ if (glob_prefix(Bootorder[i], desc))
return i+1;
return -1;
}
--
2.7.4
8 months, 1 week
Re: [SeaBIOS] Librem 15v3 hangs at Booting from Hard Disk...
by Youness Alaoui
On Wed, May 9, 2018 at 9:14 PM, Philip C. <pchampon(a)gmail.com> wrote:
> Hello everyone!
>
> I've been having some issues with a laptop recently. My Librem 15v3 was
> bouncing along, until one day I ran into an apt-get upgrade issue. I
> attempted to fix the affected script by pointing it to the base directory
> busybox lived. The upgrade completed without any apparent issue.
This is clearly totally unrelated to SeaBIOS, and it looks like an
linux/grub installation problem.
>
> But, now no matter what I do, unattended boots hang on
>
> SeaBIOS (version rel-1.11.0-0-g63451fc)
> Booting from Hard Disk...
> _
If you see nothing after that, then that probably means that SeaBIOS
executed whatever was on the drive's boot sector and that failed to do
anything, so grub crashed or there was no grub in the first place, or
it was misconfigured and it stopped instead of showing some error
message, etc.. whatever the issue is, it looks like it's not related
to SeaBIOS.
>
> I have tried reinstalling the OS, using their live boot ISO. Each time, no
> matter which disk I configure (/dev/sda or /dev/nvme0n1), the install fails
> with the message
>
> Installation failed Failed to run update-initramfs on the target The exit
> code was 2
What OS is that ? What's the error of update-initramfs ? Did you try
to run update-initramfs manually to see what error it gives you ? I
remember seeing a similar error related to a busybox depedency (this
error https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864143) and I
can't remember the exact fix, but it was something like : edit
/etc/initramfs-tools/initramfs.conf and change the "BUSYBOX=auto" to
either "y" or "n", one of them fixes it. Or maybe it was the file
/usr/share/initramfs-tools/conf-hooks.d/cryptsetup, or maybe you have
to add a line "BUSYBOXDIR=/bin" to the config..
Either way, you should fix whatever is causing that first.
>
> I have upgraded coreboot, no joy. I have also tried manually running grub,
> from the installer, ie
>
> mkdir /mnt/root
> cryptsetup luksOpen /dev/sda3 root
> mount /dev/mapper/root /mnt/root
> mount /dev/sda1 /mnt/root/boot
> grub-install --boot-directory=/mnt/root/boot /dev/sda
> update-grub2
>
Yeah, upgrading coreboot won't change anything if your hard drive
doesn't have a working grub installed on it.
I think your issue here might be that "update-grub2" will update the
grub files in /boot (from the live USB), not in /mnt/root/boot. I
would suggest to simplify your life and just "mount /dev/sda1 /boot"
so the update would work (even if you manually use grub-mkconfig -o
/mnt/root/boot, it will still scan some things in /boot, and it might
mess things up, so just mount it on top of the existing /boot and call
update-grub)
> The folks at purism/librem seem to be as confused as I am. Does anyone here
> have any insight into how I can fix this problem?
I haven't heard of this issue, usually, if it's related to coreboot, I
get asked for my opinion, but I suppose I wasn't poked about it by
tech support because it's a linux/install problem, and indeed, it's
not related to coreboot.
As for all that stuff about getting seabios debug, I don't know how
much that will help you. I'm sure all you'll see is something like
"jumping into boot sector" then nothing, it's not like the cbmem
console log will have the grub debug output in it saying "I'm about to
crash because I can't find my config" for example. Unless SeaBIOS sets
up a segfault handler or something prior to jumping into boot drive
and writes to the log a crash report, I have no idea if it does that.
>
> Thanks!
>
I hope that helps, good luck. And if you need more help, I suggest not
to spam this mailing list with non-seabios-development related
questions, you can continue emailing me directly.
Youness.
8 months, 1 week
bug: boot menu items 10+ cannot be selected
by Ian Kelling
The boot menu says option 10, but when you type 10, it selects #1 as
soon as you press 1. I think an easy fix would be that when there are at
least 10 items in the boot menu to print 01, 02, etc. and read 2
characters. I don't care about this being fixed, just figured I'd
report it.
--
Ian Kelling
https://iankelling.org
8 months, 1 week
Re: [SeaBIOS] Librem 15v3 hangs at Booting from Hard Disk...
by Paul Menzel
Dear Philip,
First of all, please respect the netiquette and do not top post. It
makes replying much harder. Please use the interleaved style in the future.
On 05/15/18 04:09, Philip C. wrote:
[…]
> On Wed, May 9, 2018 at 9:14 PM Philip C. <pchampon(a)gmail.com> wrote:
> But, now no matter what I do, unattended boots hang on
>
> SeaBIOS (version rel-1.11.0-0-g63451fc)
> Booting from Hard Disk...
Second, I really think this not a SeaBIOS issue, but a hard drive issue.
But it seems functional, as SeaBIOS is listing it in the boot menu, and
you can access it from the live installation.
> I managed to get some feedback from Kevin, on IRC, which was set debug to
> 8...
> I began the adventure, by taking advantage of a pureos script
> https://code.puri.sm/kakaroto/coreboot-files/raw/master/build_coreboot.sh
>
> I had to make a few modifications
> megadl '
> https://mega.nz/#!fA03xADA!5uqZiKwNZIP1J27xHzIKVQPQaNfqxdtzKjPRxxwZMc8'
> mv Intel\ CSME\ 11.0\ Firmware\ Repository\ Pack\ r50.rar
> coreboot/me_11_repository.rar
> comment out lines 226 and 227
> cd coreboot/flashrom && CFLAGS="-Wno-error=deprecated-declarations"
> make; cd -
> update the librem15v3 coreboot config file, setting seabios debug from
> -1 to 8
> comment out the attempt to check the sha256 of the coreboot (since
> debug changes sha)
> the script created a coreboot rom file and claimed that it flashed the
> rom
>
> However, when I rebooted, I didn't see any extra output on the screen and
> it is still hung on the Booting from Hard disk... message
>
> Any thoughts on how I can get the debug output?
1. You need to capture the coreboot and SeaBIOS messages. Does the
device have ports which can be used for debugging? As it’s a laptop,
that is probably not the case.
You could see if the messages are preserved during reboot. So, plug in
the device with the live distribution, try to boot from the drive, get
the error, and (warm) reboot, and select the distribution. Build
`cbmem`, by getting the coreboot source code [1], and then do `make -C
util/cbmem`. Or start a Linux kernel with
`CONFIG_GOOGLE_MEMCONSOLE_COREBOOT` and look into `/sys/firmware/log`.
2. See if the option *SPI Flash console output*
(`CONFIG_CONSOLE_SPI_FLASH`) is supported on your board. The Puri.sm
folks should know and help you with that.
> Send coreboot debug output to the SPI Flash in the FMAP CONSOLE area
>
> This option can cause premature wear on the SPI flash and should not
> be used as a normal means of debugging. It is only to be enabled and
> used when porting a new motherboard which has no other console
> available (no UART, no POST, no cbmem access(non bootable)). Since
> a non bootable machine will require the use of an external SPI Flash
> programmer, the developer can grab the console log at the same time.
>
> The flash console will not be erased on reboot, so once it is full,
> the flashconsole driver will stop writing to it. This is to avoid
> wear on the flash, and to avoid erasing sectors (which may freeze
> the SPI controller on skylake).
>
> The 'CONSOLE' area can be extracted from the FMAP with :
> cbfstool rom.bin read -r CONSOLE -f console.log
Kind regards,
Paul
8 months, 1 week
