and untar), but that is not as
cool/simple/efficient as using rsync.
Greetings,
Gerben
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: rsync 3.1.0-2ubuntu0.1
ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
Uname: Linux 3.13.0-35-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.4
A
Probably apparmor is blocking the executable.
in /var/log/apport.log I can see the line:
ERROR: apport (pid 4224) Fri Oct 26 22:29:35 2012: executable does not belong
to a package, ignoring
When copying qemu-system-x86_64 into /usr/bin
and executing within that directory ( ./qemu-system-x86_64
I'm getting a failure message when starting using virsh start (/usr/bin/kvm is
altered to point to upstream as described)
# virsh start Win7one
error: Failed to start domain Win7one
error: internal error Child process (LC_ALL=C
PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin /u
mands
(and sources.list alterations if needed) available.
Gerben
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1071011
Title:
specific device not available in client (passthrough) with high
Public bug reported:
I've got a specific device which is not always handed down to the kvm
client showing a high cpu load on the kvm host. No cpu load shown in the
client (win7).
A few (two) times I saw this device working properly with no high cpu
usage on the kvm host, but this was broken after
Please make this invalid. I've got the thing running properly under
quantal server including hdmi sound (assign two pci devices). I probably
did something stupid the first time.
Tip: catalyst driver, use custom installation and de-select ccc (from
http://wiki.xen.org/wiki/Xen_VGA_Passthrough_Teste
It could be the xorg software has a part in this situation. Please do
not follow up this bug anymore, I've reverted to a server installation
and can start clients using the graphics card.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
I do see I was able to run the client machine after the last apt update.
It could be some lock persists on the filesystem for that device to be
assigned (persisting over a reboot).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-k
lsb_release -rd
Description:Ubuntu 12.10
Release:12.10
root@kvm-03f:~#
apt-cache policy qemu-kvm
qemu-kvm:
Installed: 1.2.0+noroms-0ubuntu2
Candidate: 1.2.0+noroms-0ubuntu2
Version table:
*** 1.2.0+noroms-0ubuntu2 0
500 http://nl.archive.ubuntu.com/ubuntu/ quantal/main
Public bug reported:
Within Quantal I cannot start a kvm client using graphical card (amd hd
5450) (anymore). I can start a different client using a differrent
device (usb device)
I've had this machine running under Quantal with the pci device assigned and
was still trying to verify it's proper
Hi,
I've tested this in quantal, and everything works OK.
The pci device is present with every restart of the client, including
the connected usb device. All devices are working properly, including
removing and adding the usb divice.
Thanks for pointing me to quantal, I will test some different
Fresh start:
@pci-02:~$ lsusb
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 045e:0750 Microsoft Corp. Wired Keyboard 600
(On the KVM
$ lsb_release -rd
Description:Ubuntu 12.04.1 LTS
Release:12.04
$ apt-cache policy qemu-kvm
qemu-kvm:
Installed: 1.0+noroms-0ubuntu14.2
Candidate: 1.0+noroms-0ubuntu14.3
Version table:
1.0+noroms-0ubuntu14.3 0
500 http://nl.archive.ubuntu.com/ubuntu/ precise-updates/m
Public bug reported:
A restarted kvm client with a passthough pci device does not work
anymore (properly) with that device. The device does not seem to be re-
set properly.
If the KVM host is re-started the client one time starts properly with a
correctly functioning pci device, when the client i
Hi,
This is a default Ubuntu desktop installation, and I've registered my network
via the connections icon ->
"Connect to Hidden Wireless Network..." Every time the system starts it now
gets auto-connected showing an animated circular icon with two dots going round.
netstat -na shows the fol
Hi,
In both situations the same list is produced:
BEFORE:
getent hosts ::1
::1 localhost ip6-localhost ip6-loopback
getent hosts 127.0.0.1
127.0.0.1 localhost
getent hosts localhost
::1 localhost ip6-localhost ip6-loopback
getent hosts ip6-localhost
::1 lo
Hi,
Here are the parts for error.log and access.log
Used wget to avoid firefox'es 'offline browsing'
To be seen:
one time successful using wget (before wireless network configured)
one time unsuccessful using wget (after '')
one time unsuccessful using firefox (after '')
access.log:
localhost - -
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/631064/+attachment/1547321/+files/Dependencies.txt
--
connection "forbidden" on localhost after wireless connected
https://bugs.launchpad.net/bugs/631064
You received this bug notification because you are a member of Ubu
Public bug reported:
Binary package hint: apache2
1) ubuntu locid (32 bit??)
2) 2.2.14-5ubuntu8
3) expected a valid response, not the "forbidden" page
4) got presented the "forbidden" page
Details:
I've restricted a location to be accessed from only the localhost (e.g. 'apache
status').
Aft
Since testing 10.04 beta1 / beta2 I've seen this happening quite some
times on my existing guests (8.04/8.10). I cannot recall this happening
on my 8.04 host.
Is this pure based on the client kernel, or can this also depend on the
server?
--
qemu-kvm and guest kernel < 2.6.24 sporadic boot fail:
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/43655993/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/43655994/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/43655995/Dependencies.txt
** A
Public bug reported:
Binary package hint: qemu-kvm
10.04 server beta2 amd-64
ii qemu-kvm 0.12.3+noroms-0ubuntu5
kvm hypervisor to be running (so virt-manager can use kvm in stead of
qemu)
kvm hypervisor did not start
# start qemu-kvm
start: Job failed to start
RESOLUTION
22 matches
Mail list logo
