ssh -c 3des-cbc host also works for me as well. And adding this to my
ssh config makes it automatic
Host *
Ciphers 3des-cbc
btw, this is only a problem through my cisco openconnect VPN. Different
VPNs don't have this issue.
--
You received this bug notification because you are a member of
Public bug reported:
1)
root@oil-maas-node-2:~# lsb_release -rd
Description:Ubuntu 12.04.4 LTS
Release:12.04
2)
root@oil-maas-node-2:~# apt-cache policy gdisk
gdisk:
Installed: 0.8.1-1build1
Candidate: 0.8.1-1build1
Version table:
*** 0.8.1-1build1 0
500
Public bug reported:
1) % lsb_release -rd
Description:Ubuntu Utopic Unicorn (development branch)
Release:14.10
2) % apt-cache policy uvtool-libvirt
uvtool-libvirt:
Installed: 0~bzr92-0ubuntu1
Candidate: 0~bzr92-0ubuntu1
Version table:
*** 0~bzr92-0ubuntu1 0
500
It takes 164 seconds in cloud init to bring up the first machine.
What's the outer VM config (resources), likewise, what's the host
machine resource level?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
Summary
---
Add-machine: Wed May 28 14:31:56 UTC 2014 (0)
KVM Ssh'able:Wed May 28 14:33:15 UTC 2014 (+79)
Cloud-init done: Wed May 28 14:35:14 UTC 2014 (+119)
Juju status started: Wed May 28 14:35:38 UTC 2014 (+24)
Total time: 222 seconds: 3 min, 40 seconds.
One modification to the outer KVM that may help here:
adding --unsafe-cache to your first level KVM will use host ram to cache
guest writes to the qcow2 image -- this means what it means, if kill
your VMs or host machine has power failure, you'll lose data.With
that in place the same test
For the reproducers, something worth trying is to use to try is external
snapshots (instead of internal which the snapshot-create-as does without
flags).
instead run: snapshot-create-as --disk-only
which will basically do qemu-img create -b your_original_qcow2 -f qcow2
pristine
And store the
I've been running the scripts from comment #10. I have two VMs each
running simultaneously; I've completed 24 hours of this sequence, about
50 total cycles with zero errors in the qcow2 images.
We're missing something; possibly hardware specific?
Host machine is an Intel NUC on Trusty.
Linux
I'm also starting work on updating uvt to use external snapshots
instead; this would be an alternative to use while chasing down the bug
in internal snapshots.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
Public bug reported:
I have a host with kvm loaded and after creating a container and
installing the qemu package, /dev/kvm doesn't exist. If I create it
manually qemu runs fine.
The upstart job should detect that it's in a container and create
/dev/kvm for use.
** Affects: qemu (Ubuntu)
** Changed in: qemu (Ubuntu)
Importance: Undecided = High
** Changed in: qemu (Ubuntu)
Status: New = In Progress
** Changed in: qemu (Ubuntu)
Assignee: (unassigned) = Ryan Harper (raharper)
--
You received this bug notification because you are a member of Ubuntu
Server Team
Public bug reported:
1.
$ lsb_release -rd
Description:Ubuntu 14.04 LTS
Release:14.04
2.
$ apt-cache policy python-novaclient
python-novaclient:
Installed: 1:2.17.0-0ubuntu1
Candidate: 1:2.17.0-0ubuntu1
Version table:
*** 1:2.17.0-0ubuntu1 0
500
can we confirm what filesystems and options are enabled when reproducing
(ie, ext4 +extent mapping)[1] ? Bug 1368815 sounds very much like this.
If the reproducing systems have ext4 extents mapping enabled, one could
create an ext4 fs without extent mapping[2] and see if this still
reproduces.
With the updated 2.0.0+dfsg-2ubuntu1.8 package in trusty/proposed, the
test-case still fails as written.
After upgrading qemu-kvm, qemu-system-common qemu-system-x86 from
trusty/proposed, no /dev/kvm exists even though /etc/init/qemu-kvm.conf
includes the updated script to write it out. This is
I don't think the fix is adequate since it requires an extra manual
step, rather, I think the packaging should (if possible) trigger the
upstart job to stop and then start again... Otherwise, anyone upgrading
this (or installing it on top of a system with qemu-kvm already
installed in a
I have a t61p with 64-bit hardy. I can confirm that setting the above
quirks to false fixes my suspend to ram (blank screen on resume).
--
wrong quirks set for Thinkpad T61 with nvidia video
https://bugs.launchpad.net/bugs/225230
You received this bug notification because you are a member of
On Jaunty amd64, still broken for me (gnome-terminal 2.26.0, libvde9
/libvde-common 0.20.0). Following the gnome bug entry[1], it looks like
it's a vde[2] bug instead. This fix isn't yet in Jaunty, but was just
recently updated to Karmic[3]. I installed the karmic versions of
libvte9,
Need the presence patch for jaunty amd64.
--
pidgin crashes in libmeanwhile just after connecting
https://bugs.launchpad.net/bugs/261695
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Tested the jaunty amd64 PPA package , fixed my presence issues.
--
pidgin crashes in libmeanwhile just after connecting
https://bugs.launchpad.net/bugs/261695
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I can confirm the above fix.
--
simple-scan fails to scan: invalid argument
https://bugs.launchpad.net/bugs/632026
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Tested with Epson Perfection 640U on Ubuntu 10.10 x86_64 desktop.
--
simple-scan fails to scan: invalid argument
https://bugs.launchpad.net/bugs/632026
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Maverick 10.10 64bit still doesn't have presence fix. I applied
presence_v2 patch from
http://www.lilotux.net/~mikael/pub/meanwhile/
and that resolves the issue.
--
pidgin crashes in libmeanwhile just after connecting
https://bugs.launchpad.net/bugs/261695
You received this bug notification
I've got a ZelHer P20 headset and a W520 Lenovo laptop, the same problem
occurs.
What I observed is that during the first 60 seconds of activating the
P20 headset, running bt-adapter -d will display the Name: (null) and in
the bluetooth-wizard, it only shows the bt address (mac-like format).
If you create and install an xmonad.hs file in ~/.xmonad/xmonad.hs the
Gnome + Xmonad session works as expected.
It would seem that the xmonad install could/should create a default
xmonad.hs file in the user home dir?
--
You received this bug notification because you are a member of Ubuntu
I experienced this on a clean install of 12.10 Desktop 64-bit edition.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1059358
Title:
xmonad file not found: ~/.xmonad/xmonad-x86_64-linux
To manage
ssh -c 3des-cbc host also works for me as well. And adding this to my
ssh config makes it automatic
Host *
Ciphers 3des-cbc
btw, this is only a problem through my cisco openconnect VPN. Different
VPNs don't have this issue.
--
You received this bug notification because you are a member of
Public bug reported:
Attempting to run libvirtd directly and enable the remote network
driver, I run libvirtd with:
% sudo service libvirt-bin stop
% sudo /usr/sbin/libvirtd -v --listen
2012-04-11 18:27:53.674+: 6018: info : libvirt version: 0.9.8
2012-04-11 18:27:53.674+: 6018: error
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/979212
Title:
libvirtd --listen fails with: Cannot read CA certificate
'/etc/pki/CA/cacert.pem': No such file or directory
To manage notifications
Using a slightly modified script (injecting sudo before each qemu-img
command) here's my process for testing:
1. uvt-simplestreams-libvirt --verbose sync --source
http://cloud-images.ubuntu.com/daily release=trusty arch=amd64
2. uvt-kvm create --memory 1024 --cpu 1 --disk 10 trusty-test1
Public bug reported:
1)
root@oil-maas-node-2:~# lsb_release -rd
Description:Ubuntu 12.04.4 LTS
Release:12.04
2)
root@oil-maas-node-2:~# apt-cache policy gdisk
gdisk:
Installed: 0.8.1-1build1
Candidate: 0.8.1-1build1
Version table:
*** 0.8.1-1build1 0
500
Public bug reported:
1) % lsb_release -rd
Description:Ubuntu Utopic Unicorn (development branch)
Release:14.10
2) % apt-cache policy uvtool-libvirt
uvtool-libvirt:
Installed: 0~bzr92-0ubuntu1
Candidate: 0~bzr92-0ubuntu1
Version table:
*** 0~bzr92-0ubuntu1 0
500
Looks like this was a result of permission issues.
% gpg --batch --verify
--keyring=/usr/share/keyrings/ubuntu-cloudimage-keyring.gpg
gpg: failed to create temporary file
`/home/rharper/.gnupg/.#lk0x1535050.lambic.26329': Permission denied
gpg: keyblock resource
No, it was from running:
sudo sbuild-update -k
but before I'd generating my own key first.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1321778
Title:
uvt-simplestreams-libvirt sync gpg keyring
Public bug reported:
please include virtio-scsi in linux-virtual. It's currently packaged in
linux-image-extras. Including it in the base kernel package would allow
the cloud image to make use of the virtio-scsi device which includes
TRIM/DISCARD support for minimizing ever growing virtual disk
Public bug reported:
I have a host with kvm loaded and after creating a container and
installing the qemu package, /dev/kvm doesn't exist. If I create it
manually qemu runs fine.
The upstart job should detect that it's in a container and create
/dev/kvm for use.
** Affects: qemu (Ubuntu)
** Changed in: qemu (Ubuntu)
Importance: Undecided = High
** Changed in: qemu (Ubuntu)
Status: New = In Progress
** Changed in: qemu (Ubuntu)
Assignee: (unassigned) = Ryan Harper (raharper)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
1.
$ lsb_release -rd
Description:Ubuntu 14.04 LTS
Release:14.04
2.
$ apt-cache policy python-novaclient
python-novaclient:
Installed: 1:2.17.0-0ubuntu1
Candidate: 1:2.17.0-0ubuntu1
Version table:
*** 1:2.17.0-0ubuntu1 0
500
I gave this a test. Here's the process. Everything appears to be good
according to the test case.
1. proposed added but disabled: grep proposed /etc/apt/sources.list
# proposed
#deb http://archive.ubuntu.com/ubuntu/ trusty-proposed restricted main
multiverse universe
2. pull-lp-source
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1338769
Title:
SRU = 0.0~git20140516~ to trusty
To manage notifications about
Testing the proposed packages on trusty. Some casual use:
1. download images
2. run some commands in the container
3. view the containers created
4. upgrade from 0.91 to 1.0.1 from proposed.
5. confirm containers and images still present
6. commit a container to a base image.
All appears
Public bug reported:
What should happen:
Upon login, an external monitor connected via displayport to the laptop
should be detected correctly and the screen size should be set to the
correct resolution. Further, if the display sleeps, it should restore
back to the previous state before powering
On Thu, Nov 13, 2014 at 4:08 PM, Joseph Salisbury
joseph.salisb...@canonical.com wrote:
Did this issue start happening after an update/upgrade? Was there a
I'm not 100% sure. It's possible that 13.10 (original install on this x1
carbon gen1) didn't
have this behavior.
kernel version where
upstream kernel didn't help:
[ 33.822175] [drm] vendor descriptor length:1b data:1b 5f 01 00 19 05 00 01
03 00 04
[ 33.988042] udl 1-2.3.1:1.0: fb1: udldrmfb frame buffer device
[ 33.988045] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 33.988046] [drm] No driver support
** Attachment added: 3.18.0-994-generic-dmesg-drm.out
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1392501/+attachment/4260689/+files/3.18.0-994-generic-dmesg-drm.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: 3.13.0-031300-generic-dmesg-drm.out
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1392501/+attachment/4260690/+files/3.13.0-031300-generic-dmesg-drm.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: 3.11.0-031100-generic-dmesg-drm.out
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1392501/+attachment/4260691/+files/3.11.0-031100-generic-dmesg-drm.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here's what I did:
After installing all of the kernels, I rebooted and tried each one.
Upon booting into desktop, login, document state after login, dumped
dmesg | grep drm into versioned file, unplugged laptop power, ctrl-alt-l
to lock display, wait 5 seconds for all displays to sleep, press key
Is there any reason to believe that this is related to bios version?
Any changelog from Lenovo that indicates they've fixed anything related
to display port?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've examined all of the changelogs for the x1 Carbon gen1
http://support.lenovo.com/us/en/downloads/ds030684
and there is nothing in there to indicate there is any fix for anything
graphic related. I don't feel that the bios out-dated tag is relevant
at this point.
--
You received this bug
can we confirm what filesystems and options are enabled when reproducing
(ie, ext4 +extent mapping)[1] ? Bug 1368815 sounds very much like this.
If the reproducing systems have ext4 extents mapping enabled, one could
create an ext4 fs without extent mapping[2] and see if this still
reproduces.
With the updated 2.0.0+dfsg-2ubuntu1.8 package in trusty/proposed, the
test-case still fails as written.
After upgrading qemu-kvm, qemu-system-common qemu-system-x86 from
trusty/proposed, no /dev/kvm exists even though /etc/init/qemu-kvm.conf
includes the updated script to write it out. This is
I don't think the fix is adequate since it requires an extra manual
step, rather, I think the packaging should (if possible) trigger the
upstart job to stop and then start again... Otherwise, anyone upgrading
this (or installing it on top of a system with qemu-kvm already
installed in a
It takes 164 seconds in cloud init to bring up the first machine.
What's the outer VM config (resources), likewise, what's the host
machine resource level?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Summary
---
Add-machine: Wed May 28 14:31:56 UTC 2014 (0)
KVM Ssh'able:Wed May 28 14:33:15 UTC 2014 (+79)
Cloud-init done: Wed May 28 14:35:14 UTC 2014 (+119)
Juju status started: Wed May 28 14:35:38 UTC 2014 (+24)
Total time: 222 seconds: 3 min, 40 seconds.
One modification to the outer KVM that may help here:
adding --unsafe-cache to your first level KVM will use host ram to cache
guest writes to the qcow2 image -- this means what it means, if kill
your VMs or host machine has power failure, you'll lose data.With
that in place the same test
Public bug reported:
1) # lsb_release -rd
Description:Ubuntu 12.04.4 LTS
Release:12.04
2) # apt-cache policy util-linux
util-linux:
Installed: 2.20.1-1ubuntu3
Candidate: 2.20.1-1ubuntu3
Version table:
*** 2.20.1-1ubuntu3 0
500 http://archive.ubuntu.com//ubuntu/
For the reproducers, something worth trying is to use to try is external
snapshots (instead of internal which the snapshot-create-as does without
flags).
instead run: snapshot-create-as --disk-only
which will basically do qemu-img create -b your_original_qcow2 -f qcow2
pristine
And store the
I've been running the scripts from comment #10. I have two VMs each
running simultaneously; I've completed 24 hours of this sequence, about
50 total cycles with zero errors in the qcow2 images.
We're missing something; possibly hardware specific?
Host machine is an Intel NUC on Trusty.
Linux
I'm also starting work on updating uvt to use external snapshots
instead; this would be an alternative to use while chasing down the bug
in internal snapshots.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Fri, Jan 23, 2015 at 10:16 PM, Chris J Arges 1414...@bugs.launchpad.net
wrote:
#!/bin/bash
# 2015 Chris J Arges chris.j.ar...@canonical.com
# Detect if we are running inside KVM
NESTED_VM=0
VM_STRINGS=KVM QEMU VMware VirtualBox Xen
VM_DETECT=$(dmesg | egrep -e '(Hypervisor
On Fri, Jan 23, 2015 at 10:16 PM, Chris J Arges 1414...@bugs.launchpad.net
wrote:
#!/bin/bash
# 2015 Chris J Arges chris.j.ar...@canonical.com
# Detect if we are running inside KVM
NESTED_VM=0
VM_STRINGS=KVM QEMU VMware VirtualBox Xen
VM_DETECT=$(dmesg | egrep -e '(Hypervisor
There's nothing preventing nested guests architectually IIUC. I don't know
that anyone has implemented it yet but seems reasonable to thing ahead and
avoid x86isms where possible.
On Sat, Jan 24, 2015 at 3:27 PM, Chris J Arges 1414...@bugs.launchpad.net
wrote:
Ryan,
I don't think Power8/kvm
There's nothing preventing nested guests architectually IIUC. I don't know
that anyone has implemented it yet but seems reasonable to thing ahead and
avoid x86isms where possible.
On Sat, Jan 24, 2015 at 3:27 PM, Chris J Arges 1414...@bugs.launchpad.net
wrote:
Ryan,
I don't think Power8/kvm
This issue should be fixed in the qemu-kvm version included in precise.
** Changed in: qemu-kvm (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
Hi,
Are you running ntp in the host or timekeeping in the guest? If so, is
the guest clock close to what current time should be?
Also, can you try adding this option:
-global mc146818rtc.lost_tick_policy=slew
--
You received this bug notification because you are a member of Ubuntu
Server
This issue should be fixed in the qemu-kvm version included in precise.
** Changed in: qemu-kvm (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/551545
Hi,
Are you running ntp in the host or timekeeping in the guest? If so, is
the guest clock close to what current time should be?
Also, can you try adding this option:
-global mc146818rtc.lost_tick_policy=slew
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I think you'll find that nested kvm and ksm will be a worst-case
scenario w.r.t memory swap-out. KSM actively scans the hosts memory for
pages it can unmap , which means when a guest (level 1) or nested guest
(level 2) needs to write to that memory, then you incur a page table
walk (Guest virtual
I think you'll find that nested kvm and ksm will be a worst-case
scenario w.r.t memory swap-out. KSM actively scans the hosts memory for
pages it can unmap , which means when a guest (level 1) or nested guest
(level 2) needs to write to that memory, then you incur a page table
walk (Guest virtual
Any information about the physical host running the L1 guest?
--
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/1413540
Title:
issues with KSM enabled for nested KVM VMs
To manage
Any information about the physical host running the L1 guest?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1413540
Title:
issues with KSM enabled for nested KVM VMs
To manage notifications about
Shame that virt.c isn't a standalone tool that could be reused.
On Thu, Jan 29, 2015 at 9:54 AM, Chris J Arges 1414...@bugs.launchpad.net
wrote:
FWIW, here is the systemd-virt-detect code used to detect if we are
running on a virt platform.
Shame that virt.c isn't a standalone tool that could be reused.
On Thu, Jan 29, 2015 at 9:54 AM, Chris J Arges 1414...@bugs.launchpad.net
wrote:
FWIW, here is the systemd-virt-detect code used to detect if we are
running on a virt platform.
One method that's pretty solid for QEMU (save folks who pass in custom DMI
table values to qemu) is the BIOS data available via dmidecode (or
/sysfs/dmi); would need to look at Power and arm for equivalent (likely
some device tree bits in /sysfs). Openstack exports a BIOS manufacture of
One method that's pretty solid for QEMU (save folks who pass in custom DMI
table values to qemu) is the BIOS data available via dmidecode (or
/sysfs/dmi); would need to look at Power and arm for equivalent (likely
some device tree bits in /sysfs). Openstack exports a BIOS manufacture of
On Wed, Mar 18, 2015 at 12:59 PM, Roderick Smith rod.sm...@canonical.com
wrote:
This is not a bug in sgdisk; it's either a bug in the charm or an
incorrect use of same. Specifically, the sgdisk command shown is:
sgdisk --zap-all --clear --mbrtogpt /dev/vdb
This command does four things, in
On Wed, Mar 18, 2015 at 12:59 PM, Roderick Smith rod.sm...@canonical.com
wrote:
This is not a bug in sgdisk; it's either a bug in the charm or an
incorrect use of same. Specifically, the sgdisk command shown is:
sgdisk --zap-all --clear --mbrtogpt /dev/vdb
This command does four things, in
On Fri, Mar 20, 2015 at 1:02 PM, Roderick Smith rod.sm...@canonical.com
wrote:
Examining the code, there are several sgdisk calls, but two are relevant
for this discussion. The first is the one reproduced in this initial bug
report:
sgdisk --zap-all --clear --mbrtogpt
This call does not
On Fri, Mar 20, 2015 at 1:02 PM, Roderick Smith rod.sm...@canonical.com
wrote:
Examining the code, there are several sgdisk calls, but two are relevant
for this discussion. The first is the one reproduced in this initial bug
report:
sgdisk --zap-all --clear --mbrtogpt
This call does not
On trusty with qemu-2.0 I can't get the blind input to work at all, it
appears that enter in -curses mode (among other keyboard inputs seems
broken.
To isolate the issue, I tried a trusty-server iso, same issue. Then I
tried this ttylinux image:
On trusty with qemu-2.0 I can't get the blind input to work at all, it
appears that enter in -curses mode (among other keyboard inputs seems
broken.
To isolate the issue, I tried a trusty-server iso, same issue. Then I
tried this ttylinux image:
Something's up with the installer itself. I can reproduce the issue on
Lucid which is older than ttylinux kernel. To confirm the -curses and
keyboard input works correctly, I appended BOOT_DEBUG=3 (during the
blind typing steps) after console=ttyS0
Then on the serial console page, I get a
And appending DEBIAN_FRONTEND=text works perfectly fine over serial
console.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1427829
Title:
enter doesn't work on iso install over serial
To manage
Something's up with the installer itself. I can reproduce the issue on
Lucid which is older than ttylinux kernel. To confirm the -curses and
keyboard input works correctly, I appended BOOT_DEBUG=3 (during the
blind typing steps) after console=ttyS0
Then on the serial console page, I get a
And appending DEBIAN_FRONTEND=text works perfectly fine over serial
console.
--
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/1427829
Title:
enter doesn't work on iso install over
** Changed in: qemu (Ubuntu)
Importance: Undecided = Medium
** Changed in: qemu (Ubuntu)
Status: New = Confirmed
--
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/1427829
Title:
** Changed in: qemu (Ubuntu)
Importance: Undecided = Medium
** Changed in: qemu (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1427829
Title:
enter
Public bug reported:
1)
$ lsb_release -rd
Description:Ubuntu 14.04.2 LTS
Release:14.04
2)
$ apt-cache policy maas
maas:
Installed: 1.8.0~beta3+bzr3825-0ubuntu1~trusty1
Candidate: 1.8.0~beta3+bzr3825-0ubuntu1~trusty1
Version table:
*** 1.8.0~beta3+bzr3825-0ubuntu1~trusty1 0
Public bug reported:
1)
$ lsb_release -rd
Description:Ubuntu 14.04.2 LTS
Release:14.04
2)
$ apt-cache policy maas
maas:
Installed: 1.8.0~beta3+bzr3825-0ubuntu1~trusty1
Candidate: 1.8.0~beta3+bzr3825-0ubuntu1~trusty1
Version table:
*** 1.8.0~beta3+bzr3825-0ubuntu1~trusty1 0
Jason Hobbs shared a workaround.
1) mark node as broken
2) power off node outside of maas (ipmi commands)
3) edit node and use 'Check Now' to sync power state
4) mark node as fixed
Node is now ready.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Jason Hobbs shared a workaround.
1) mark node as broken
2) power off node outside of maas (ipmi commands)
3) edit node and use 'Check Now' to sync power state
4) mark node as fixed
Node is now ready.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Public bug reported:
libvirtd crashed while creating VMs; this left storage volumes
associated with the instance present. uvt-kvm destroy foo should clean
up all related volumes, but because the VM is not currently defined,
uvtool does not remove the volumes. However, if one attempts to create
Public bug reported:
libvirtd crashed while creating VMs; this left storage volumes
associated with the instance present. uvt-kvm destroy foo should clean
up all related volumes, but because the VM is not currently defined,
uvtool does not remove the volumes. However, if one attempts to create
domain type='kvm'
os
type arch=ppc64le machine=pserieshvm/type
boot dev='hd' /
/os
features
acpi/
apic/
pae/
/features
devices
interface type='network'
source network='default'/
model type='virtio'/
/interface
serial type='pty'
source
Public bug reported:
uvt-kvm currently has only one template for creating KVM guests. The
template hardcodes x86-specific values which are not available on
non-x86 (arm and ppc64el). Ideally, uvtool could do something like
/usr/share/uvtool/$arch-template.xml though we'll need something to
Public bug reported:
uvt-kvm currently has only one template for creating KVM guests. The
template hardcodes x86-specific values which are not available on
non-x86 (arm and ppc64el). Ideally, uvtool could do something like
/usr/share/uvtool/$arch-template.xml though we'll need something to
cloud-init[1226]: /var/lib/cloud/instance/scripts/user_data.sh: 18:
/var/lib/cloud/instance/scripts/user_data.sh: initctl: not found
ubuntu@phony-trick:/var/log$ cat /proc/partitions
major minor #blocks name
1101048575 sr0
80 488386584 sda
81 488385560
cloud-init[1226]: /var/lib/cloud/instance/scripts/user_data.sh: 18:
/var/lib/cloud/instance/scripts/user_data.sh: initctl: not found
ubuntu@phony-trick:/var/log$ cat /proc/partitions
major minor #blocks name
1101048575 sr0
80 488386584 sda
81 488385560
Public bug reported:
1) vivid
2) 0~bzr99-0ubuntu1
3) uvt-kvm wait --insecure vm1 waits till the VM is up
4) times out but VM is up due to creating with a separate bridge:
I've created new bridges via virsh net-define scaling-1.xml, virsh net-
start scaling-1 which creates a new bridge device
Public bug reported:
1) vivid
2) 0~bzr99-0ubuntu1
3) uvt-kvm wait --insecure vm1 waits till the VM is up
4) times out but VM is up due to creating with a separate bridge:
I've created new bridges via virsh net-define scaling-1.xml, virsh net-
start scaling-1 which creates a new bridge device
1 - 100 of 1546 matches
Mail list logo
