[Touch-packages] [Bug 1594902] Re: Failed to upgrade to libvirt-bin 1.3.1-1ubuntu10.1 on Ubuntu 16.04 64-bit
*** This bug is a duplicate of bug 1707400 *** https://bugs.launchpad.net/bugs/1707400 I just got into this same issue. My system is; NAME="Ubuntu" VERSION="16.04.1 LTS (Xenial Xerus)" So, before i install the libvirt-bin, I remember I just messed up my locale settings. I didn't notice that and then I tried to setup virtualization. But it kept failed and finally fond this bug tread. Even any of the work around didn't solve the issue. So accidentally I checked my locate settings by $ localectl. It was like this. System Locale: TIME=en_US VC Keymap: n/a X11 Layout: us X11 Model: pc105 I then changed it to as below. System Locale: LANG=en_US.UTF-8 VC Keymap: n/a X11 Layout: us X11 Model: pc105 great, problem solved. Hope this may help. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1594902 Title: Failed to upgrade to libvirt-bin 1.3.1-1ubuntu10.1 on Ubuntu 16.04 64-bit Status in apparmor package in Ubuntu: Confirmed Status in libvirt package in Ubuntu: Confirmed Bug description: Output from 'apt-get upgrade': Setting up libvirt-bin (1.3.1-1ubuntu10.1) ... initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'screen-cleanup' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `screen-cleanup' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `screen-cleanup' initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'binfmt-support' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `binfmt-support' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `binfmt-support' initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'screen-cleanup' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `screen-cleanup' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `screen-cleanup' initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'binfmt-support' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `binfmt-support' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `binfmt-support' initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'screen-cleanup' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `screen-cleanup' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `screen-cleanup' initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'binfmt-support' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `binfmt-support' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `binfmt-support' Job for libvirt-bin.service failed because the control process exited with error code. See "systemctl status libvirt-bin.service" and "journalctl -xe" for details. invoke-rc.d: initscript libvirt-bin, action "restart" failed. dpkg: error processing package libvirt-bin (--configure): subprocess installed post-installation script returned error exit status 1 E: Sub-process /usr/bin/dpkg returned an error code (1) Output from 'systemctl status libvirt-bin.service': ● libvirt-bin.service - Virtualization daemon Loaded: loaded (/lib/systemd/system/libvirt-bin.service; enabled; vendor preset: enabled) Active: inactive (dead) (Result: exit-code) since Tue 2016-06-21 17:55:16 BST; 4min 52s ago Docs: man:libvirtd(8) http://libvirt.org Process: 2984 ExecStart=/usr/sbin/libvirtd $libvirtd_opts (code=exited, status=6) Main PID: 2984 (code=exited, status=6) Jun 21 17:55:15 lydia systemd[1]: Failed to start Virtualization daemon. Jun 21 17:55:15 lydia systemd[1]: libvirt-bin.service: Unit entered failed state. Jun 21 17:55:15 lydia systemd[1]: libvirt-bin.service: Failed with result 'exit-code'. Jun 21 17:55:16 lydia systemd[1]: libvirt-bin.service: Service hold-off time over, scheduling restart. Jun 21 17:55:16 lydia systemd[1]: Stopped Virtualization daemon. Jun 21 17:55:16 lydia systemd[1]: libvirt-bin.service: Start request repeated too quickly. Jun 21
[Touch-packages] [Bug 1437740] Re: Ubuntu Vivid Vervet beta2 guest does not boot to Unity from QEMU-KVM host
I was having the same exact issue with 'qxl' & 'cirrus' driver on kvm guest. However, get resolved by changing the video to 'vga' on virt- manager. Still looking for a fix for 'qxl' driver.? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1437740 Title: Ubuntu Vivid Vervet beta2 guest does not boot to Unity from QEMU-KVM host Status in X.Org X server: New Status in xorg package in Ubuntu: Confirmed Bug description: I was testing Vivid Vervet beta2 (Ubuntu 15.04 _Vivid Vervet_ - Beta i386 (20150326), MD5SUM e838edda85712d283bd94b34dbb5d6ec) in QEMU KVM from Ubuntu 12.04.5 amd64 host ( "sudo kvm -m 1536 -hda /dev/sdd -net nic -net user,hostfwd=tcp::10022-:22"), but it does not start in graphic ("Try Ubuntu without installing" Unity) LiveCD mode. I got logs while logging to the qemu-kvm guest via ssh. The LiveCD works as expected only when selecting "Install Ubuntu" option. Please fix this bug before final release. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic i686 ApportVersion: 2.16.2-0ubuntu4 Architecture: i386 BootLog: CasperVersion: 1.356 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Mar 28 22:14:14 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Cirrus Logic GD 5446 [1013:00b8] (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc QEMU Virtual Machine [1af4:1100] LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Beta i386 (20150326) Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Bochs Bochs ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- Renderer: Software SourcePackage: xorg Symptom: display Title: Xorg crash UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2007 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr: dmi.product.name: Bochs dmi.sys.vendor: Bochs version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1 version.libdrm2: libdrm2 2.4.59-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Sat Mar 28 22:12:42 2015 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output VGA-0 xserver.version: 2:1.17.1-0ubuntu3 xserver.video_driver: modeset --- ApportVersion: 2.16.2-0ubuntu4 Architecture: i386 CasperVersion: 1.356 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' DistUpgraded: Fresh install DistroCodename: vivid DistroRelease: Ubuntu 15.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Cirrus Logic GD 5446 [1013:00b8] (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc QEMU Virtual Machine [1af4:1100] LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Beta i386 (20150326) Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Bochs Bochs Package: xorg 1:7.7+7ubuntu4 PackageArchitecture: i386 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Renderer: Software Tags: vivid ubuntu UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-10-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/01/2007 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:sv
[Touch-packages] [Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial
Cannot start virtual machines via kvm once install 'systemd-container' package. I am on Ubuntu16.04-xenial. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1529079 Title: Can't start virtual machines with installed systemd-container package on Xenial Status in libvirt package in Ubuntu: Triaged Status in systemd package in Ubuntu: Invalid Bug description: Can't start virtual machines after upgrade to Xenial. On Ubuntu Server 16.04: # virsh start testserver Cannot set property Before, or unknown property. On Kubuntu 16.04: Cannot set property Before, or unknown property. Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/create.py", line 1873, in do_install guest.start_install(meter=meter) File "/usr/share/virt-manager/virtinst/guest.py", line 414, in start_install noboot) File "/usr/share/virt-manager/virtinst/guest.py", line 478, in _create_guest dom = self.conn.createLinux(start_xml or final_xml, 0) File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3585, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: Cannot set property Before, or unknown property. At this moment there is no libvirt or systemd-related error messages in syslog when this error appear on the screen (or virsh output). Both systems was upgraded from 15.10. --- ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 16.04 Package: libvirt (not installed) ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.3.3-040303-generic root=UUID=a100d974-72cf-44ad-acf8-6ec060b773dd ro rootflags=subvol=@Xenial quiet nomdmonddf nomdmonisw ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=C SHELL=/bin/bash Tags: xenial Uname: Linux 4.3.3-040303-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified] mtime.conffile..etc.libvirt.qemu.networks.default.xml: 2015-02-27T11:49:59.773560 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp