[Bug 1549788] Re: bind9 9.10.3.dfsg.P2-5 crash on exit
Yes, same for me. Setting back to confirmed. bind9-host 1:9.10.3.dfsg.P2-5, not sure why out package numbers differ. ** Changed in: bind9 (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1549788 Title: bind9 9.10.3.dfsg.P2-5 crash on exit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1549788/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1551351] Re: dhclient does not renew leases
Correction 1: Stefan not Stephan, sorry. Correction 2: Things broke down about another 1/2 day after the lease times changes to 1 hour. The client didn't seem to release this and resorted to broadcast type discover stuff. Then it was getting leases for 5 minutes, and the cycle continued until I re-booted. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1551351 Title: dhclient does not renew leases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1551351/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1551351] Re: dhclient does not renew leases
>From Stephan comment 14: "Hm, of course, if one starts dhclient in debug mode (foreground) by adding a "-d", everything does work." Yes, that does seem to work, but only for about another day, at least in my case. Thereafter, my ISP stopped returning my domain name, host name and some other stuff, and would only renew the lease for 1 hour instead of the normal 1 day. I suppose it doesn't matter because, I use supersede directives for that stuff anyhow. From my tcpdump captures, I have not been able to determine what, if anything, is different in the request, including the option parameter list request. In my opinion, this bug report should have an importance level of critical. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1551351 Title: dhclient does not renew leases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1551351/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1549788] Re: bind9 9.10.3.dfsg.P2-4 crash on exit
1:9.10.3.dfsg.P2-5 has the same issue, but the apparmor issue is fixed. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1549788 Title: bind9 9.10.3.dfsg.P2-4 crash on exit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1549788/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1549788] Re: bind9 9.10.3.dfsg.P2-4 crash on exit
Same for me: Feb 29 14:45:51 DOUG-64 named[1202]: connection refused resolving '19.82.133.155.in-addr.arpa/PTR/IN': 37.59.161.64#53 Feb 29 15:35:01 DOUG-64 systemd[1]: Stopping BIND Domain Name Server... Feb 29 15:35:01 DOUG-64 named[1202]: received control channel command 'stop' Feb 29 15:35:01 DOUG-64 named[1202]: shutting down: flushing changes Feb 29 15:35:01 DOUG-64 named[1202]: stopping command channel on 127.0.0.1#953 Feb 29 15:35:01 DOUG-64 named[1202]: no longer listening on 127.0.0.1#53 Feb 29 15:35:01 DOUG-64 named[1202]: no longer listening on 173.180.XXX.YYY#53 Feb 29 15:35:01 DOUG-64 named[1202]: no longer listening on 192.168.111.1#53 Feb 29 15:35:01 DOUG-64 named[1202]: exiting Feb 29 15:35:01 DOUG-64 named[1202]: ../../../lib/isc/mem.c:1229: REQUIRE(ctx->references == 1) failed Feb 29 15:35:02 DOUG-64 systemd[1]: bind9.service: Main process exited, code=dumped, status=6/ABRT Feb 29 15:35:02 DOUG-64 systemd[1]: Stopped BIND Domain Name Server. Feb 29 15:35:02 DOUG-64 systemd[1]: bind9.service: Unit entered failed state. Feb 29 15:35:02 DOUG-64 systemd[1]: bind9.service: Failed with result 'core-dump'. As of the last few days, I also have an apparmor issue: Feb 29 15:35:33 DOUG-64 kernel: [25130.612529] audit: type=1400 audit(1456788933.480:15): apparmor="DENIED" operation="open" profile="/usr/sbin/named" name="/proc/sys/net/ipv4/ip_local_port_range" pid=4932 comm="named" requested_mask="r" denied_mask="r" fsuid=109 ouid=0 but if I set that apparmor profile to "complain" mode, then my kernel will crash during the shutdown phase of a re-boot. Otherwise, and as far as I know the DNS is actually working properly. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1549788 Title: bind9 9.10.3.dfsg.P2-4 crash on exit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1549788/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1543794] Re: isc-dhcp-server fails to start on second & further attempts with 'Can't open /var/lib/dhcp/dhcpd.leases for append'
Yes, isc-dhcp - 4.3.3-5ubuntu8 fixes the issue with the dhclient stuff that caused this: Feb 26 14:05:21 DOUG-64 kernel: [ 17.518717] audit: type=1400 audit(1456524321.220:10): apparmor="DENIED" operation="open" profile="/sbin/dhclient" name="/etc/ssl/openssl.cnf" pid=483 comm="dhclient" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 However, that is not what this bug report is about. This bug report is about these ones: Feb 27 07:53:07 DOUG-64 kernel: [ 21.350331] audit: type=1400 audit(1456588387.171:12): apparmor="ALLOWED" operation="capable" profile="/usr/sbin/dhcpd" pid=1248 comm="dhcpd" capability=1 capname="dac_override" Feb 27 07:53:07 DOUG-64 kernel: [ 21.466959] audit: type=1400 audit(1456588387.287:13): apparmor="ALLOWED" operation="capable" profile="/usr/sbin/dhcpd" pid=1248 comm="dhcpd" capability=3 capname="fowner" Note: the above are "ALLOWED" because I have it set to complain mode. which were fixed, but have now returned. setting back to confirmed. ** Changed in: isc-dhcp (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1543794 Title: isc-dhcp-server fails to start on second & further attempts with 'Can't open /var/lib/dhcp/dhcpd.leases for append' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1543794/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1493156] Re: pm-suspend aborts if highest numbered CPU offline, as of kernel 4.2
** Changed in: pm-utils (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1493156 Title: pm-suspend aborts if highest numbered CPU offline, as of kernel 4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1493156/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1515207] Re: /bin/login aborted due to pointer double free in libpam.so
I think, but am not sure, this bug report is the root issue for failure of the daily server 64 iso installation when "samba server" is selected. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1515207 Title: /bin/login aborted due to pointer double free in libpam.so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1515207/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1493156] Re: pm-suspend aborts if highest numbered CPU offline, as of kernel 4.2
As of kernel 4.4-rc1 this bug becomes invalid, as the kernel was patched such that this issue no longer occurs. I'll wait until kernel 4.4 is finished, check again, then set the status of this bug report to invalid. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1493156 Title: pm-suspend aborts if highest numbered CPU offline, as of kernel 4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1493156/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1493156] [NEW] pm-suspend aborts if highest numbered CPU offline, as of kernel 4.2
Public bug reported:
Kernel 4.2 includes a significant commit
(87549141d516aee71d511138e27117c41e8aef68), after the patch the files
and directory are present even if the CPU is offline. If the CPU is
offline, writing to those files isn't allowed and so the echo in
94cpufreq fails.
If the failed echo is not the last pass through the loop, then
the bad exit code gets overwritten with a good one before
the loop exits. If the failed echo is the last pass through the loop, due to
the highest numbered CPU being offline, then then 94cpufreq returns an error
code and pm-suspend aborts.
So what is needed is something like (and this doesn't actually work
yet):
hibernate_cpufreq()
{
( cd /sys/devices/system/cpu/
for x in cpu[0-9]*; do
# if cpufreq is a symlink, it is handled by another cpu. Skip.
[ -L "$x/cpufreq" ] && continue
gov="$x/cpufreq/scaling_governor"
# if we do not have a scaling_governor file, skip.
[ -f "$gov" ] || continue
+ # if the CPU is offline, skip, unless no file, i.e. CPU0.
+ [ $(cat "$x/online") = "1" -o ! -f "$x/online" ] || continue
Or
+ if [ $(cat "$x/online") = "1" ] || [ ! -f "$x/online" ]; then
+ continue;
+fi
Or something similar that actually works.
# if our temporary governor is not available, skip.
grep -q "$TEMPORARY_CPUFREQ_GOVERNOR" \
"$x/cpufreq/scaling_available_governors" || continue
savestate "${x}_governor" < "$gov"
echo "$TEMPORARY_CPUFREQ_GOVERNOR" > "$gov"
done )
}
Or just force a good return code at the end (which is what I'm doing
now, so that I can move on).
Note: I also filed this same bug report upstream.
https://bugs.freedesktop.org/show_bug.cgi?id=91914
** Affects: pm-utils (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1493156
Title:
pm-suspend aborts if highest numbered CPU offline, as of kernel 4.2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1493156/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1484587] Re: CPU frequency management fails to re-engage on resume from suspend
When a user is using the intel_pstate driver in performance mode, then yes, prior to Kernel 4.2RC1 the CPU frequency will be typically be stuck after resume from suspend. This is not a pm-ultils issue (which is how I stumbled across this bug report). To test that the issue is fixed on kernel 4.2, just use primitive commands and not these higher level utilities (that I neither use or know anything about). For example use: grep MHz /proc/cpuinfo to observe CPU frequencies. The commit that, I think, fixes this issue is: commit 6c1e45917dec5e7c99ba8125fd8cc50f6e482a21 Author: Doug Smythies <doug.smyth...@gmail.com> Date: Mon Jun 1 21:12:34 2015 -0700 intel_pstate: Force setting target pstate when required -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1484587 Title: CPU frequency management fails to re-engage on resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1484587/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1257186] Re: memory leakage messages (no talloc stackframe)
Chad wrote: Xavier wrote that this needs to be moved somewhere else. Does anyone know how to do that? If someone can explain to me what needs to happen, I changed the trusty target from 14.04.2 (which is in the past) to 14.04.3 (which is in the future, albeit, not far off) ** Changed in: samba (Ubuntu Trusty) Milestone: ubuntu-14.04.2 = ubuntu-14.04.3 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1257186 Title: memory leakage messages (no talloc stackframe) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1257186/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1257186] Re: memory leakage messages (no talloc stackframe)
@Coeur: I entered this bug report over 11 months ago, and have simply ignored the error ever since. I haven't had any problems. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1257186 Title: memory leakage messages (no talloc stackframe) To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1257186/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1016148] Re: vsftpd *is* configured to allow anon by default
It is the configuration file that is incorrect, not the serverguide, so I am setting this one to invalid for the serverguide. However, I also checked the trusty and utoptic master files, and they are O.K. References: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/vsftpd/trusty/view/head:/vsftpd.conf http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/vsftpd/precise/view/head:/vsftpd.conf http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/utopic/vsftpd/utopic/view/head:/vsftpd.conf ** Changed in: serverguide Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/1016148 Title: vsftpd *is* configured to allow anon by default To manage notifications about this bug go to: https://bugs.launchpad.net/serverguide/+bug/1016148/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1308756] Re: VNC graphics issues on guest VMs after server host upgrade from 12.04 to 14.04
are you connecting to a vncserver service running within the guest VM? Or are you connecting to the qemu VNC head on the server which hosts the virtual machines? I connect to the host server IP address port 5900. Also, on which host and environment are you seeing the 'low graphics mode' dialog box? I see the 'low graphics mode' box on the guest VM running on the 14.04 server host after the upgrade from 12.04 server and before changing the machine type in the .xml file. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1308756 Title: VNC graphics issues on guest VMs after server host upgrade from 12.04 to 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1308756/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1308756] Re: VNC graphics issues on guest VMs after server host upgrade from 12.04 to 14.04
By the way, if I do the opposite: On an new Ubuntu 14.04 server installation with a newly installed guest Ubuntu dekstop; Use virsh edit and change the machine type to pc-1.0, then the quest VM has the same issues upon login. The information requested above: doug@s15:~$ dpkg -l | egrep 'qemu|kvm|libvirt' ii ipxe-qemu1.0.0+git-2013.c3d1e78-2ubuntu1 all PXE boot firmware - ROM images for qemu ii kvm-ipxe 1.0.0+git-2013.c3d1e78-2ubuntu1 all transitional dummy package ii libsys-virt-perl 1.2.1-1 amd64Perl module providing an extension for the libvirt library ii libvirt-bin 1.2.2-0ubuntu13 amd64programs for the libvirt library ii libvirt0 1.2.2-0ubuntu13 amd64library for interfacing with different virtualization systems ii python-libvirt 1.2.2-0ubuntu1 amd64libvirt Python bindings ii qemu-common 2.0.0~rc1+dfsg-0ubuntu3 all dummy transitional package from qemu-common to qemu-keymaps ii qemu-keymaps 2.0.0~rc1+dfsg-0ubuntu3 all QEMU keyboard maps ii qemu-kvm 2.0.0~rc1+dfsg-0ubuntu3 amd64QEMU Full virtualization on x86 hardware (transitional package) ii qemu-system-common 2.0.0~rc1+dfsg-0ubuntu3 amd64QEMU full system emulation binaries (common files) ii qemu-system-x86 2.0.0~rc1+dfsg-0ubuntu3 amd64QEMU full system emulation binaries (x86) ii qemu-utils 2.0.0~rc1+dfsg-0ubuntu3 amd64QEMU utilities doug@s15:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.04 LTS Release:14.04 Codename: trusty doug@s15:~$ virsh capabilities capabilities host uuidc09f3a27-cb5b-d911-9bbf-f46d04652d8e/uuid cpu archx86_64/arch modelWestmere/model vendorIntel/vendor topology sockets='1' cores='4' threads='2'/ feature name='rdtscp'/ feature name='avx'/ feature name='osxsave'/ feature name='xsave'/ feature name='tsc-deadline'/ feature name='pcid'/ feature name='pdcm'/ feature name='xtpr'/ feature name='tm2'/ feature name='est'/ feature name='vmx'/ feature name='ds_cpl'/ feature name='monitor'/ feature name='dtes64'/ feature name='pclmuldq'/ feature name='pbe'/ feature name='tm'/ feature name='ht'/ feature name='ss'/ feature name='acpi'/ feature name='ds'/ feature name='vme'/ /cpu power_management suspend_mem/ suspend_disk/ suspend_hybrid/ /power_management migration_features live/ uri_transports uri_transporttcp/uri_transport /uri_transports /migration_features topology cells num='1' cell id='0' memory unit='KiB'16002556/memory cpus num='8' cpu id='0' socket_id='0' core_id='0' siblings='0,4'/ cpu id='1' socket_id='0' core_id='1' siblings='1,5'/ cpu id='2' socket_id='0' core_id='2' siblings='2,6'/ cpu id='3' socket_id='0' core_id='3' siblings='3,7'/ cpu id='4' socket_id='0' core_id='0' siblings='0,4'/ cpu id='5' socket_id='0' core_id='1' siblings='1,5'/ cpu id='6' socket_id='0' core_id='2' siblings='2,6'/ cpu id='7' socket_id='0' core_id='3' siblings='3,7'/ /cpus /cell /cells /topology secmodel modelapparmor/model doi0/doi /secmodel secmodel modeldac/model doi0/doi baselabel type='kvm'+109:+106/baselabel baselabel type='qemu'+109:+106/baselabel /secmodel /host guest os_typehvm/os_type arch name='i686' wordsize32/wordsize emulator/usr/bin/qemu-system-i386/emulator machine canonical='pc-i440fx-trusty' maxCpus='255'pc/machine machine maxCpus='255'pc-0.12/machine machine maxCpus='255'pc-1.3/machine machine maxCpus='255'pc-q35-1.6/machine machine maxCpus='255'pc-q35-1.5/machine machine maxCpus='1'xenpv/machine machine maxCpus='255'pc-i440fx-1.6/machine machine maxCpus='255'pc-i440fx-1.7/machine machine maxCpus='255'pc-0.11/machine machine maxCpus='255'pc-0.10/machine machine maxCpus='255'pc-1.2/machine machine maxCpus='1'isapc/machine machine maxCpus='255'pc-q35-1.4/machine machine maxCpus='128'xenfv/machine machine maxCpus='255'pc-0.15/machine machine maxCpus='255'pc-0.14/machine machine maxCpus='255'pc-i440fx-1.5/machine
[Bug 1308756] Re: pc 1.0 machine type regressed with -vga vmware
I agree with the summary change to pc 1.0 machine type regressed with
-vga vmware:
And confirm via two new VM desktop guest installations. One was on a
14.04 server host upgraded from from a 12.04 server. The other was on a
new 14.04 server. In both cases the machine type was forced on the
command line:
sudo virt-install -n desk_tt3 -r 8192 --disk
path=/media/newhd/desk_tt3.img,bus=virtio,size=50 -c trusty-desktop-
amd64-20140417.iso --machine pc-1.0 --network bridge=br0,model=virtio
--video=vmvga --graphics vnc,listen=0.0.0.0 --noautoconsole -v --vcpus=4
They both had the low graphics issue upon re-boot after the installation
completed.
I agree with the recommendation to just change the machine type and this
bug being set to won't fix.
About the cirrus driver:
I was using virsh edit bla to change the driver, something I do often.
I made a new VM desktop guest from scratch with this command (which will
use the cirrus driver, by default):
sudo virt-install -n desk_tt4 -r 8192 --disk
path=/home/doug/img/desk_tt4.img,bus=virtio,size=50 -c trusty-desktop-
amd64-20140417.iso --machine pc-1.0 --network bridge=br0,model=virtio
--graphics vnc,listen=0.0.0.0 --noautoconsole -v --vcpus=4
And it worked fine. (Except that the cirrus driver has never worked
quite right for me, and the display size options are not as extensive as
the vmvga driver.) I'll come back to this if needed.
I disagree about bumping the memory size as a fix:
For many months (13.10 days) I have always been bumping the memory for
the video, as I calculated that it should be more. Typically, I have
this in the .xml file:
model type='vmvga' vram='16384' heads='1'/
And I even ran this just now:
model type='vmvga' vram='32768' heads='1'/
Question:
what file or location that contains this stuff mentioned above? (so that I can
look at the bigger context):
},{\
.driver = VGA,\
.property = vgamem_mb,\
.value = stringify(8),\
},{\
.driver = vmware-svga,\
.property = vgamem_mb,\
.value = stringify(8)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1308756
Title:
pc 1.0 machine type regressed with -vga vmware
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1308756/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1308756] Re: pc 1.0 machine type regressed with -vga vmware
Serge, Thanks for the information and the link to even more useful information. So, specifying vram size doesn't work, that is both good to know and explains some things. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1308756 Title: pc 1.0 machine type regressed with -vga vmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1308756/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty
My comment may not apply to this, but I'll make it anyhow: I upgraded my host server from ubuntu 12.04 to 14.04. Afterwards, none of my desktop VM's worked (I haven't even tried the server VM's yet). I made a new guest VM using the exact same virst-install command I had used for the original VM creation on the 12.04 host server, and compared the resulting .xml file. There were 3 or 4 differences, but this one: type arch='x86_64' machine='pc-1.0'hvm/type in 14.04 became this: type arch='x86_64' machine='pc-i440fx-1.7'hvm/type I used virsh edit and changed that line and the guest VM originally created under a 12.04 server host then worked under the 14.04 server host. Note: So far, this change has been made to 6 VM's (5 are either 14.04 originally or as upgraded from 13.10, and one was a 12.04 Desktop guest VM) and 5 of them are now working. The one is only not working for one log in type out of 5 possible (GNOME; GNOME Classic; GNOME Flashback (Compiz); GNOME Flashback (Metacity); Ubuntu (Default)). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1291321 Title: migration fails between 12.04 Precise and 14.04 Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1291321/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1308756] [NEW] VNC graphics issues on guest VMs after server host upgrade from 12.04 to 14.04
Public bug reported: I upgraded my host server from ubuntu 12.04 to 14.04. Afterwards, none of my desktop VM's worked (I haven't even tried the server VM's yet). During login the VM's complained about being unable to detect the graphics card (screenshot will be posted). Proceeding results in a screen of jibberish (screenshot will be posted). The VM guest is actually working fine, and I can SSH into it. I made a new guest VM using the exact same virst-install command I had used for the original VM creation on the 12.04 host server, and compared the resulting .xml file. There were 3 or 4 differences, but this one: type arch='x86_64' machine='pc-1.0'hvm/type in 14.04 became this: type arch='x86_64' machine='pc-i440fx-1.7'hvm/type I used virsh edit and changed that line and the guest VM originally created under a 12.04 server host then worked under the 14.04 server host. Note: So far, this change has been made to 6 VM's (5 are either 14.04 originally or as upgraded from 13.10, and one was a 12.04 Desktop guest VM) and 5 of them are now working. The one is only not working for one log in type out of 5 possible (GNOME; GNOME Classic; GNOME Flashback (Compiz); GNOME Flashback (Metacity); Ubuntu (Default)). I use both TightVNC viewer and UltraVNC viewer from a windows computer for this work, and have both viewers for this particular issue. I use both vmvga or default (cirrus) video, and have tested both for this issue. Typical VM creation command: sudo virt-install -n desk_tt -r 8192 --disk path=/media/newhd/desk_tt.img,bus=virtio,size=50 -c trusty-desktop- amd64-20140224.iso --network bridge=br0,model=virtio --video=vmvga --graphics vnc,listen=0.0.0.0 --noautoconsole -v --vcpus=4 ** Affects: qemu (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1308756 Title: VNC graphics issues on guest VMs after server host upgrade from 12.04 to 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1308756/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1308756] Re: VNC graphics issues on guest VMs after server host upgrade from 12.04 to 14.04
** Attachment added: screen shot of low graphics message box https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1308756/+attachment/4085756/+files/1404-vm-low-graphics.png -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1308756 Title: VNC graphics issues on guest VMs after server host upgrade from 12.04 to 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1308756/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1308756] Re: VNC graphics issues on guest VMs after server host upgrade from 12.04 to 14.04
** Attachment added: screen shot of resulting jibberish screen https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1308756/+attachment/4085757/+files/1404-vm-jibberish.png -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1308756 Title: VNC graphics issues on guest VMs after server host upgrade from 12.04 to 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1308756/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1308756] Re: VNC graphics issues on guest VMs after server host upgrade from 12.04 to 14.04
** Attachment added: a typical .xml file https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1308756/+attachment/4085765/+files/desk_tt.xml.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1308756 Title: VNC graphics issues on guest VMs after server host upgrade from 12.04 to 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1308756/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1308756] Re: VNC graphics issues on guest VMs after server host upgrade from 12.04 to 14.04
** Attachment added: a typical xml file, installed under a 12.04 host. https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1308756/+attachment/4085766/+files/desk_ss.xml.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1308756 Title: VNC graphics issues on guest VMs after server host upgrade from 12.04 to 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1308756/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1308756] Re: VNC graphics issues on guest VMs after server host upgrade from 12.04 to 14.04
All the differences in xml files, one from installing a new guest VM on a 12.04 server as the host and one installing the same guest again from the same server upgraded / updated to a 14.04 server host. ** Attachment added: All differences between 12.04 and 14.04 host xml file https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1308756/+attachment/4085792/+files/diff-1204-1404.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1308756 Title: VNC graphics issues on guest VMs after server host upgrade from 12.04 to 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1308756/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1284793] Re: [FFE] Merge qemu 2.0
The update of yesterday fixes issues I was having with vmvga. qemu-keymaps 2.0~git-20140317.2bda660-0ubuntu1 all QEMU keyboard maps qemu-kvm 2.0~git-20140317.2bda660-0ubuntu1 amd64 QEMU Full virtualization on x86 hardware qemu-system-common 2.0~git-20140317.2bda660-0ubuntu1 amd64QEMU full system emulation binaries ... qemu-system-x86 2.0~git-20140317.2bda660-0ubuntu1 amd64QEMU full system emulation binaries ... qemu-utils 2.0~git-20140317.2bda660-0ubuntu1 amd64 QEMU utilities -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1284793 Title: [FFE] Merge qemu 2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1284793/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1257186] [NEW] memory leakage messages
Public bug reported: This message appears a lot as of a recent update to samba (Trusty development branch): no talloc stackframe at ../source3/param/loadparm.c:4831, leaking memory From this upstream bug report, I am lead to believe the issue is in libpam-smbpass, but I don't really know for sure. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728666 I am filing this bug report mainly so that I can refer to it on the testing tracker as an issue, while still setting the test case to pass. Note that other than the error message itself, I am not aware of any bad side effect. doug@v32-serv04:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Trusty Tahr (development branch) Release:14.04 Codename: trusty ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1257186 Title: memory leakage messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1257186/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
