Public bug reported:
$ euca-delete-volume -h
Creates a volume in a specified availability zone.
euca-delete-volume [-a, --access-key access_key ][-s, --secret-key
...
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: euca2ools 2.1.3-1ubuntu1
Uname: Linux 3.13.0-ar-d8ec26d x86_64
No update in nearly three years. This bug is still present in the
current LTS builds.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to likewise-open in Ubuntu.
https://bugs.launchpad.net/bugs/663633
Title:
package likewise-open (not
*** This bug is a duplicate of bug 663633 ***
https://bugs.launchpad.net/bugs/663633
** This bug has been marked a duplicate of bug 663633
package likewise-open (not installed) failed to install/upgrade: trying to
overwrite '/usr/bin/uuid', which is also in package uuid 0:1.6.2-1ubuntu1
Window manager varies. In the original report it was openbox (as I
believe I stated, in comment #7). Current window manager is xfwm4. For
the screenshot provided, I intentionally moved the window with
Alt+left_click as I knew this would trigger the issue (also indicated in
comment #7).
As requested here's a screenshot of the scaled window. The expected
behavior is that the window be resized to the dimensions of the guest.
Pressing Ctrl+Alt+u within this window corrects the issue and the window
is in fact resized to the guest dimensions.
** Attachment added: Screenshot -
Followed the steps provided and the current upstream source does not
suffer from this issue. Last commit in current upstream source: commit
6801038bc52d61f81ac8a25fbe392f1bad982887.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
You don't need a license to reproduce this. You only need to attempt to
boot from installation media.
I'll happily try upstream qemu, can't say that I've done it before. Any
pointers?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
I did some further digging on this and it appears that it only happens
when the virtual machine definition includes a floppy device, either via
-drive or -fda. Removal of the floppy device results in being able to
successfully boot and install Windows XP. However, this does seem to
prevent one
Public bug reported:
Attempting to build a Windows XP virt using KVM results in a black
screen after the familiar Setup is inspecting your computer's hardware
configuration. No matter how long I wait there is no apparent progress
of any kind and the VM CPU is pegged.
Very similar to:
I have no idea why you claim the 3 listed items are not provided, they
in fact have been.
1. install ofcs2-tools (apt-get install ofcs2-tools)
2. it should work, including after reboots
3. reread first post, it doesn't work after reboots due to startup order
--
You received this bug
** Changed in: ocfs2-tools (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ocfs2-tools in ubuntu.
https://bugs.launchpad.net/bugs/246613
Title:
ocfs2 startup link prior to open-iscsi
That's not really a viable solution as it introduces other issues. Once
libpam-cracklib is installed and activated, creation of accounts that
should not require a password prompt (disable login for example) all of
a sudden does prompt for a password.
--
Cannot change password on ldap client
The automated run of libvirt-migrate-qemu-disks is great if your virtual
machines are permanently defined within libvirt. However, if you simply
inject and run a VM as needed, with something like the following:
virsh create vm.xml
Which is what I've been doing. The VM definitions will not
You are indeed correct that specifying the format of the disk image file
corrected the issue. However, this is also a fairly large regression
over previous functionality. Configurations that worked flawlessly
under lucid will now break under maverick. Additionally, the reason for
the breakage
Jamie, I understand that the vm.xml does not contain enough information
for the version of libvirt in maverick. I understand that with
maverick's version one now has to supply a disk format. However, this
was not the case with libvirt under lucid. Furthermore, not providing
the disk format does
Sure applications change with versions. However, they normally also
provide useful error messages when something that was previously valid
no longer is. This is *not* the case here. There is *no* error
message.
I'm not saying that users shouldn't provide valid XML when defining a
VM. However,
Public bug reported:
Since upgrading to 10.10, attempting to start any VM (new or pre-
existing) that utilizes an SDL display fails. Initially, I thought it
might be something with qemu/kvm. However, starting a VM with an SDL
display manually with a command like the following, works fine:
kvm
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/656531/+attachment/1677836/+files/Dependencies.txt
--
libvirt unable to start VM with SDL display
https://bugs.launchpad.net/bugs/656531
You received this bug notification because you are a member of Ubuntu
Server Team,
I reported #656531, which was marked as a duplicate of this. Indeed it
is covered by this. However, I believe this is a much larger issue than
this report makes it out to be. Importance on all components except
qemu-kvm is still listed as undecided, and the problem isn't even with
qemu-kvm.
This is still an issue in Maverick.
--
AppArmor security driver does not support backingstore
https://bugs.launchpad.net/bugs/470636
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
Ubuntu-server-bugs mailing list
What's more, with libpam-cracklib installed, creation of accounts that
should have no password (password disabled accounts) still prompt for a
password. The prompting for a password on password disabled account
creation should probably be filed as a separate bug report, but I wanted
to note it
Restarting the libvirt daemon in addition to the above seems to have
cleared things up. I can now clone LVM backed VMs.
--
does not support cloning vm storage on lvm backend
https://bugs.launchpad.net/bugs/613549
You received this bug notification because you are a member of Ubuntu
Server Team,
Rebooted the server and now I'm no longer getting the Could not
determine original disk information: Disk '/dev/group/volume' does not
exist. error. However it fails to actually perform the cloning with the
following:
Traceback (most recent call last):
File
Made the requested apparmor change, checked the dmesg output before
attempting to clone the VM, found the following new entry:
[90351.748748] type=1505 audit(1281033561.731:23):
operation=profile_replace pid=7783 name=/usr/sbin/libvirtd
Looks good so far.
First attempt to clone the VM and set
No, nothing.
Here is the full kern.log since the reload:
Aug 5 12:39:21 kvm-host kernel: [90351.748748] type=1505
audit(1281033561.731:23): operation=profile_replace pid=7783
name=/usr/sbin/libvirtd
Aug 5 12:46:07 kvm-host kernel: [90757.988390] lo: Disabled Privacy Extensions
Aug 5
Public bug reported:
It would appear that libvirt does not support cloning a VM that is using
an LVM backend.
Selecting Clone presents the user with a dialog prompting for a new
name and options for networking and the storage details. However, below
the LVM based storage entry is a statement:
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/53054416/Dependencies.txt
--
does not support cloning vm storage on lvm backend
https://bugs.launchpad.net/bugs/613549
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Public bug reported:
Binary package hint: migrationtools
The package's README file indicates that one should edit
migrate_common.ph and change at least two lines:
$DEFAULT_MAIL_DOMAIN
$DEFAULT_BASE
However, migrate_common.ph is installed at
/usr/share/perl5/migrate_common.ph and is not
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/52533789/Dependencies.txt
--
package suggests editing an installed non-conffile for normal operation
https://bugs.launchpad.net/bugs/610103
You received this bug notification because you are a member of Ubuntu
Server Team,
Some further investigation shows that there is a symlink created in the
/etc/migrationtools directory:
$ ls -l /etc/migrationtools/migrate_common.ph
lrwxrwxrwx 1 root root 43 2010-07-26 06:53
/etc/migrationtools/migrate_common.ph -
/usr/share/migrationtools/migrate_common.ph
However, the
This bug is indeed still present in Lucid. With an account only present
in LDAP and the default common-password configuration, I get the
following when trying to change the password for the user stored in
LDAP:
$ sudo passwd testing
passwd: Authentication information cannot be recovered
passwd:
I too would like to see this fixed for Lucid. It's rather tedious to
create a domain then have to hand edit the configuration.
--
libvirt-bin hypervisor does not support virConnectNumOfInterfaces / unable to
create domain with virt-manager using network bridge
If it created the interface on it's startup, it should remove the
interface on it's shutdown. Simple as that.
--
libvirt does not remove interfaces on stop
https://bugs.launchpad.net/bugs/345485
You received this bug notification because you are a member of Ubuntu
Server Team, which is
True, I'd forgotten that libvirt could be stopped and the VMs remain
running.
--
libvirt does not remove interfaces on stop
https://bugs.launchpad.net/bugs/345485
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
I don't want them undefined or removed, only not set to auto start.
--
default network autostart symlink recreated
https://bugs.launchpad.net/bugs/372001
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
Still present in up to date Lucid beta
$ ifconfig -a | grep vir
virbr0Link encap:Ethernet HWaddr 5a:85:91:8b:65:30
$ sudo service libvirt-bin stop
libvirt-bin stop/waiting
$ ifconfig -a | grep vir
virbr0Link encap:Ethernet HWaddr 5a:85:91:8b:65:30
** Changed in: libvirt (Ubuntu)
Just had it happen again. Simply started the VM, didn't touch the SDL
window for it at all, guest wound up scaled. Here's the xwininfo output
for the SDL window:
xwininfo: Window id: 0x6e3 QEMU (winxp-work)
Absolute upper-left X: 640
Absolute upper-left Y: 367
Relative upper-left
@Dustin,
I've experienced the problem with a rebuild of the lucid package for karmic.
The package is in my PPA, https://launchpad.net/~jcollins/+archive/jaminppa.
@Anthony,
I can assure you that I've seen the scaling without resizing the client window
in any way. Simply starting the VM and
I frequently relocate my VM displays. My host system's window manager
is openbox. Normally, for moving any window about my screen, I utilize
the ALT+left-click feature to drag the window about. This has the added
benefit of ensuring I don't accidentally resize the window.
Most of my guests are
Public bug reported:
The release version of libvirt-0.7.5 suffers from a bug that causes it
to segfault on the first connection attempt from each virt-manager
launch. The upstream bug report for this is:
https://bugzilla.redhat.com/show_bug.cgi?id=556815
There is a patch referenced in the
** Patch added: patch to avoid freeing uninitialized pointer
http://launchpadlibrarian.net/38472167/9018-dont-free-an-uninitalized-pointer.patch
--
libvirt 0.7.5 crashed on first virt-manager connection
https://bugs.launchpad.net/bugs/513544
You received this bug notification because you
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/37560230/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/37560231/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/37560232/Dependencies.txt
**
Public bug reported:
Binary package hint: qemu-kvm
Normally, the SDL output window for a VM resizes to match the VM's
resolution. However, intermittently the output is instead scaled within
the window. I can't seem to find any pattern to when the output is
scaled versus when the window is
Steps to reproduce:
Create additional network definitions. I have the following (all set to start
on boot):
- public_1, 192.168.51.0/24, 192.168.51.128, 192.168.51.254, w/NAT
- private_1, 192.168.61.0/24, 192.168.61.128, 192.168.61.254, isolated
- private_2, 192.168.62.0/24, 192.168.62.128,
** Attachment added: device file used to eject the drive
http://launchpadlibrarian.net/31546265/no-cdrom.xml
--
virsh attach-disk doesn't work
https://bugs.launchpad.net/bugs/203020
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
I found using a device xml file works in Jaunty with
0.7.0-0ubuntu0~ppa2, haven't tried older version, but it may work with
them as well. I could not get the attach or detach -disk options to
work. However using the device xml seems to work. I've attached the
xml file I use to attach my
I can confirm that this is still a problem with jaunty.
--
samba can't be launched by a normal user (qemu related)
https://bugs.launchpad.net/bugs/50385
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
*** This bug is a duplicate of bug 50385 ***
https://bugs.launchpad.net/bugs/50385
** This bug has been marked a duplicate of bug 50385
samba can't be launched by a normal user (qemu related)
--
smb option doesn't appear to work
https://bugs.launchpad.net/bugs/371687
You received this
48 matches
Mail list logo
