Hi,
does qemu support the PXE boot menu? I have such a server here in my
network but qemu keeps loading some default system (the first one?)
instead of presenting me with the pxe menu.
Em Sex, 2007-09-21 às 19:40 -0500, Anthony Liguori escreveu:
> Andreas Hasenack wrote:
> > Hi,
> >
> > does qemu support the PXE boot menu? I have such a server here in my
> > network but qemu keeps loading some default system (the first one?)
> > instead o
Em Seg, 2007-09-24 às 13:05 -0300, Andreas Hasenack escreveu:
> Em Sex, 2007-09-21 às 19:40 -0500, Anthony Liguori escreveu:
> > Andreas Hasenack wrote:
> > > Hi,
> > >
> > > does qemu support the PXE boot menu? I have such a server here in my
> > >
lsmod run on a non-maximized window. All looks good.
** Attachment added: "good-lsmod.png"
https://bugs.launchpad.net/qemu/+bug/1819908/+attachment/5245830/+files/good-lsmod.png
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
htt
continuing from the previous screenshot, all I did here was to click the
maximize button. We can already see some bad rendering on the top right
corner.
** Attachment added: "lsmod-maximized.png"
https://bugs.launchpad.net/qemu/+bug/1819908/+attachment/5245831/+files/lsmod-maximized.png
--
Y
Public bug reported:
Host: Ubuntu disco
qemu-kvm: 1:3.1+dfsg-2ubuntu2
libvirt: 5.0.0-1ubuntu2
Guest: ubuntu bionic
guest is using cirrus video, with the extra modules kernel package installed
and the cirrus kernel module loaded. I also tried QXL, but got the same problem.
A non-maximized termin
Here, with the maximized window, I typed several commands again: lsmod,
clear, clear. If you look carefully, you can see the clear at the
bottom, then at the top again, and nothing changes. All I can see are
the characters I type, but not the command's output or effect. The
screen doesn't clear, an
** Description changed:
Host: Ubuntu disco
qemu-kvm: 1:3.1+dfsg-2ubuntu2
libvirt: 5.0.0-1ubuntu2
-
Guest: ubuntu bionic
- guest is using cirrus video, with the extra modules kernel package installed
and the cirrus kernel module loaded
+ guest is using cirrus video, with the extra modu
Any reason we are keeping this bug and #1674481 separate? We are not
sure?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1701449
Title:
high memory usage when using rbd with client caching
Status
** Description changed:
[Impact]
- * backport upstream fix to avoid double unmounts (e.g. bind mounts)
-hanging the freeze action.
+ * backport upstream fix to avoid double unmounts (e.g. bind mounts)
+ hanging the freeze action.
[Test Case]
* Prepare a guest
$ uvt-s
Also marking the ubuntu task as incomplete. It looks like it's sorted,
but let's give it some time for people to comment if they still have an
issue.
** Changed in: qemu (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-
Doing the same for the debian task, which doesn't have an upstream bug
anyway.
** Changed in: qemu (Debian)
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/685096
Titl
** Description changed:
[Impact]
- * An explanation of the effects of the bug on users and
+ * An explanation of the effects of the bug on users and
- * justification for backporting the fix to the stable release.
+ * justification for backporting the fix to the stable release.
- *
apt-get will be enough once it's published, and looks like it just was
published.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1866870
Title:
KVM Guest pauses after upgrade to Ubuntu 20.04
Status
I also have these two apparmor denied messages in dmesg:
[ 1380.529549] audit: type=1400 audit(1584023445.093:139): apparmor="DENIED"
operation="open" profile="libvirt-aa346a1d-8caa-4c55-bef9-c3acbe17bdac"
name="/" pid=19712 comm="qemu-system-x86" requested_mask="r" denied_mask="r"
fsuid=64055 o
/proc/cpuinfo
** Attachment added: "cpuinfo.txt"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1866870/+attachment/5336147/+files/cpuinfo.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/
virsh capabilities
** Attachment added: "virsh-capabilities.xml"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1866870/+attachment/5336148/+files/virsh-capabilities.xml
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https:
I tried launching a focal vm on a focal host, and the vm launched but is
in a paused state.
Attached is its log.
This is on an old E660 intel core system.
** Attachment added: "f1.log"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1866870/+attachment/5336146/+files/f1.log
--
You rece
virsh domcapabilities
** Attachment added: "virsh-domcapabilities.xml"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1866870/+attachment/5336149/+files/virsh-domcapabilities.xml
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEM
After changing cpu to :
I got this log (still in a paused state):
char device redirected to /dev/pts/3 (label charserial0)
2020-03-12T15:06:22.560159Z qemu-system-x86_64: warning: host doesn't support
requested feature: MSR(48EH).vmx-vnmi-pending [bit 22]
2020-03-12T15:06:22.560708Z qemu-system-
The package from the PPA failed the same way for me:
ubuntu@f1:~$ qemu-system-x86_64 --enable-kvm -cpu Penryn,vmx=on -m 512
--nodefaults --nographic
qemu-system-x86_64: warning: host doesn't support requested feature:
CPUID.01H:ECX.sse4.1 [bit 19]
KVM internal error. Suberror: 1
emulation failur
Also crashed with the packages from the other ppa:
ubuntu@f1:~$ qemu-system-x86_64 --help 2>&1|head -n 1
QEMU emulator version 4.2.0 (Debian 1:4.2-3ubuntu3~exp1)
ubuntu@f1:~$ qemu-system-x86_64 --enable-kvm -cpu Penryn,vmx=on -m 512
--nodefaults --nographic
qemu-system-x86_64: warning: host does
Ok, upstream tag v4.2.0 and these configure options reproduced the
crash:
export LDFLAGS="-Wl,--warn-common -Wl,-z,relro -Wl,-z,now -pie -m64 -g
-Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed"
export CFLAGS="-O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -g"
Full configure output: https://pas
Hello Dimitry, or anyone else affected,
Accepted qemu into oracular-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/qemu/1:9.0.2+ds-4ubuntu5.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https
Hello Dimitry, or anyone else affected,
Accepted qemu into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/qemu/1:8.2.2+ds-0ubuntu1.7 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
Given this possible regression:
* This changes the alignment of sections in the ELF binary via QEMUs
elfloader, if something goes wrong
with this change, it could lead to all kind of crashes (segfault) of any
emulated binaries.
Is there something we could do to mitigate it? Perhaps a q
26 matches
Mail list logo
