17.07.2015 21:44, Vladimir Stavrinov wrote: > On Fri, Jul 17, 2015 at 08:53:01PM +0300, Michael Tokarev wrote: > >> some systemd debugging. I'm afraid there's nothing we can do here, > > I've tried switch back to sysvinit, but it doesn't help. > >> especially since it works here. I also highly doubt it is really >> kernel-related, there are *many* virtual systems with 3.16 kernel > > It is fresh installed stable system with 3.16 kernel. Then single > package with 3.2 kernel was installed. So we can choose different > kernels from menu with different result. > >> running around, including debian ones, and with more recent kernels > > The same fail with 4.0 kernel. > >> too. Also I highly doubt it is ovmf-related either. > > The same identical system is working without ovmf and with standard (non-efi) > grub. > > That is all facts instead of too many "highly doubt".
These can be facts for you. As long as I can't reproduce this behavour I still can't do anything. All my systems (there are many) work fine with debian 3.16 kernel and ovmf firmware. Besides, if you see the prob happens when switching to a different _kernel_, why are you filing the bugreport against ovmf? > Here is command line, starting this virtual machine: > > qemu-system-x86_64 -enable-kvm -hda /srv/vmx/linux-0.img -bios > /srv/vmx/OVMF.fd Did you try increasing memory available to the guest already? Thanks, /mjt -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
