[Bug 1369224] [NEW] rsync preserve permission does not work
Public bug reported: Hi, I am a regular user of rsync on various systems, giving parameters '-prH' or '-prHl' to shift data over to other locations while retaining correct permissions. Today (Ubuntu 14.04.1 64 bits, rsync 3.1.0) I descovered the '-p' parameter is not working. As root I'm copying the contents of the home directory to a new location, but the owner/group is set as root.root, not the intended user. This is incorrect operation, and can be problematic for people who automatically schedule rsync operations. I can work around this (using tar 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 Architecture: amd64 Date: Sun Sep 14 09:30:16 2014 InstallationDate: Installed on 2014-04-21 (146 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.rsync: 2014-04-21T09:49:59 ** Affects: rsync (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1369224 Title: rsync preserve permission does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1369224/+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 1071011] Re: specific device not available in client (passthrough) with high cpu load on host, none in client
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 --enable-kvm -nam...) still a coredump message is shown, apport.log ends in wrote report /var/crash/_usr_bin_qemu-system-x86_64.0.crash -- 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 cpu load on host, none in client To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1071011/+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 1071011] Re: specific device not available in client (passthrough) with high cpu load on host, none in client
Hi Serge, I cannot see any pattern on boot or reboot of the host. One cold boot (the first after not using the pci device for a long time) of the host resulted into the device working properly on the client, but then shutting down the client again reverted to problem described. I should have tried a restart of the client first to keep the same kvm process. After that I've performed several poweroff's, including disconnecting from the mains for over a minute, but never seen the device working properly. An upstream install of qemu is okay if you have the proper apt commands (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 cpu load on host, none in client To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1071011/+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 1071011] [NEW] specific device not available in client (passthrough) with high cpu load on host, none in client
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 a reboot of the KVM host in at least one time. Reboots of the client showed the device continue to work correctly multiple times before I rebooted the host. 06:00.1 Audio device [0403]: Advanced Micro Devices [AMD] nee ATI Cedar HDMI Audio [Radeon HD 5400/6300 Series] [1002:aa68] If the device works correctly, a device is shown by the device manager within windows 7. If not no device is shown, while the host KVM process consumes all cpu cycles assigned to it (2 cpu's in this case) and the client shows not cpu power used. My guess this is specific to this device (a sound device on the graphics card, HD5440). The graphics device and an USB device in passthough both work without problems. When removing the sound device no high cpu usage is shown on the host. Adding the sound device again, high cpu usage is shown on the host. The host is a Quantal server installation. # lsb_release -rd Description:Ubuntu 12.10 Release:12.10 # 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 amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: qemu-kvm 1.2.0+noroms-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Wed Oct 24 21:59:10 2012 InstallationMedia: Ubuntu-Server 12.10 Quantal Quetzal - Release amd64 (20121017.2) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=58e57f77-7117-4eff-8162-47b465a72050 ro SourcePackage: qemu-kvm UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1102:bd03/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. ** Affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal -- 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 cpu load on host, none in client To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1071011/+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 1069302] Re: kvm client does not start with pci passthrough (amd hd5450)
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 qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1069302 Title: kvm client does not start with pci passthrough (amd hd5450) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1069302/+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 1069302] Re: kvm client does not start with pci passthrough (amd hd5450)
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_Tested_Adapters). -- 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/1069302 Title: kvm client does not start with pci passthrough (amd hd5450) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1069302/+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 1069302] [NEW] kvm client does not start with pci passthrough (amd hd5450)
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 operation.
- It could be due to an xorg update within Quantal that I'm having problems
now, but I've unassigned the device
- It could be due to a kernel update within Quantal, I'm seeing a kernel BUG
line within dmesg
Under 12.04 this client machine just can be started.
The message shown by virt-manager, on starting the machine:
Error starting domain: Timed out during operation: cannot acquire state change
lock
Traceback (most recent call last):
File /usr/share/virt-manager/virtManager/asyncjob.py, line 96, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File /usr/share/virt-manager/virtManager/asyncjob.py, line 117, in tmpcb
callback(*args, **kwargs)
File /usr/share/virt-manager/virtManager/domain.py, line 1090, in startup
self._backend.create()
File /usr/lib/python2.7/dist-packages/libvirt.py, line 620, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: Timed out during operation: cannot acquire state change lock
An extract from dmesg (grep -i msi) the device I'm trying to assign is
:06:00.0
(device :03:00.0 is the usb device for the other machine that does work)
[2.267420] xhci_hcd :04:00.0: irq 85 for MSI/MSI-X
[2.267426] xhci_hcd :04:00.0: irq 86 for MSI/MSI-X
[2.919867] r8169 :09:00.0: irq 87 for MSI/MSI-X
[ 11.237982] snd_hda_intel :05:00.1: irq 88 for MSI/MSI-X
[ 11.256406] snd_hda_intel :06:00.1: irq 89 for MSI/MSI-X
[ 40.246889] fglrx_pci :05:00.0: irq 90 for MSI/MSI-X
[ 40.486203] fglrx_pci :06:00.0: irq 91 for MSI/MSI-X
[ 2223.578420] pci-stub :03:00.0: irq 73 for MSI/MSI-X
[ 2223.587210] pci-stub :03:00.0: irq 73 for MSI/MSI-X
[ 2223.587228] pci-stub :03:00.0: irq 74 for MSI/MSI-X
[ 2466.712694] kernel BUG at /build/buildd/linux-3.5.0/drivers/pci/msi.c:341!
[ 2466.712743] RIP: 0010:[8136ba84] [8136ba84]
free_msi_irqs+0x144/0x150
[ 2466.712778] [8136c905] pci_disable_msi+0x45/0x70
[ 2466.712854] RIP [8136ba84] free_msi_irqs+0x144/0x150
the libvirt/qemu log for the device:
2012-10-21 07:14:04.523+: starting up
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin
QEMU_AUDIO_DRV=none /usr/bin/kvm -name opencl-d3 -S -M pc-1.2 -enable-kvm -m
1024 -smp 5,sockets=5,cores=1,threads=1 -uuid
50508978-b639-f497-0016-6c9d543f0d03 -no-user-config -nodefaults -chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/opencl-d3.monitor,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown
-device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive
file=/mnt/data/kvm/opencl-d3/vda.img,if=none,id=drive-virtio-disk0,format=raw
-device
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
-netdev tap,fd=36,id=hostnet0,vhost=on,vhostfd=37 -device
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:d4:a7:25,bus=pci.0,addr=0x3
-chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0
-vnc 127.0.0.1:13 -vga cirrus -device intel-hda,id=sound0,bus=pci.0,addr=0x4
-device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device
pci-assign,host=06:00.0,id=hostdev0,configfd=38,bus=pci.0,addr=0x7 -device
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6
char device redirected to /dev/pts/17
Host-side INTx sharing not supported, using MSI instead.
Some devices do not to work properly in this mode.
compared with 12.04, two lines are added to the log: Host-side... and
Some...
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: qemu-kvm 1.2.0+noroms-0ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
Uname: Linux 3.5.0-17-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.6.1-0ubuntu3
Architecture: amd64
Date: Sun Oct 21 09:18:25 2012
InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121015.2)
MachineType: To be filled by O.E.M. To be filled by O.E.M.
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic
root=UUID=a7db4ac4-4331-403e-a928-7e9ab41e1231 ro quiet splash vt.handoff=7
SourcePackage: qemu-kvm
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/12/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1102
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: SABERTOOTH 990FX
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
[Bug 1069302] Re: kvm client does not start with pci passthrough (amd hd5450)
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 amd64 Packages 100 /var/lib/dpkg/status apt-cache policy xorg xorg: Installed: 1:7.7+1ubuntu4 Candidate: 1:7.7+1ubuntu4 Version table: *** 1:7.7+1ubuntu4 0 500 http://nl.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages 100 /var/lib/dpkg/status apt-cache policy linux-generic linux-generic: Installed: 3.5.0.17.19 Candidate: 3.5.0.17.19 Version table: *** 3.5.0.17.19 0 500 http://nl.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages 100 /var/lib/dpkg/status -- 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/1069302 Title: kvm client does not start with pci passthrough (amd hd5450) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1069302/+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 1069302] Re: kvm client does not start with pci passthrough (amd hd5450)
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-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1069302 Title: kvm client does not start with pci passthrough (amd hd5450) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1069302/+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 1065628] Re: pci device not reset (passthrough)
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 pci device (amd hd5440), but this issue for me can be closed. Details for package used: 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 amd64 Packages 100 /var/lib/dpkg/status -- 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/1065628 Title: pci device not reset (passthrough) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1065628/+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 1065628] [NEW] pci device not reset (passthrough)
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 is re-started (without re-starting the kvm host) the pci device is not working properly. Seen on device: USB device with linux client (USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller) The device is implemented with MSI-X, as a test a keyboard is connected. First boot client (on fresh start of KVM host): The client is presented the pci USB device (usb 2.0 and usb 3.0) and the keyboard is presented as well. The keyboard properly works. Reboot: The client is presented the pci USB device (usb 2.0 and usb 3.0), but no keyboard is presented (it is plugged in). Disconnecting and re-connecting the usb keyboard is not helping. Unregistering and re-registering with it's driver (xhci_hcd) did not help. Trying to reset through echo 1 reset within /sys/devices/ did not help. Trying to use pci-config -s 03:00.0 -S and pci-config -s 03:00.0 -W did not help. I've been looking for a solution to get this working properly, but failed so far to find a solution. package used to start the client: libvirt (virsh and virt-manager) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: kvm 1:84+dfsg-0ubuntu16+1.0+noroms+0ubuntu14.2 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 Date: Thu Oct 11 20:03:16 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-31-generic root=UUID=2583ca5d-0a8a-46bc-b0c3-d8468dc2a421 ro quiet splash iommu=pt vt.handoff=7 SourcePackage: qemu-kvm UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1102:bd03/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. ** Affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- 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/1065628 Title: pci device not reset (passthrough) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1065628/+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 1065628] Re: pci device not reset (passthrough)
$ 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/main amd64 Packages *** 1.0+noroms-0ubuntu14.2 0 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status 1.0+noroms-0ubuntu13 0 500 http://nl.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages $ apt-cache policy libvirt-bin libvirt-bin: Installed: 0.9.8-2ubuntu17.4 Candidate: 0.9.8-2ubuntu17.4 Version table: *** 0.9.8-2ubuntu17.4 0 500 http://nl.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.9.8-2ubuntu17 0 500 http://nl.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages -- 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/1065628 Title: pci device not reset (passthrough) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1065628/+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 1065628] Re: pci device not reset (passthrough)
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 host the KVM process is nice flat, e.g. 1% cpu) Power off and again starting using virsh 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 (On the KVM host the KVM process uses 67% cpu continuously, but no cpu used shown in the kvm client, nothing started there either.) KVM Host top: PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 4679 libvirt- 20 0 4002m 1.0g 7284 S 54 6.6 2:58.40 kvm 4713 root -51 0 000 S 19 0.0 0:49.76 irq/73-kvm: 1401 root 20 0 835m 7500 4356 S 19 0.0 0:51.85 libvirtd 4689 root 20 0 721m 92m 17m S 19 0.6 0:53.77 python -- 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/1065628 Title: pci device not reset (passthrough) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1065628/+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 631064] Re: connection forbidden on localhost after wireless connected
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 following differences for LISTEN port 80: BEFORE tcp6 0 0 :::80 :::*LISTEN AFTER tcp0 0 0.0.0.0:80 0.0.0.0:* LISTEN ip -a shows only a difference for the configured network interface (3:): BEFORE 1: lo: LOOPBACK,UP,LOWER_UP mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: NO-CARRIER,BROADCAST,MULTICAST,UP mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 00:14:c2:e2:8a:36 brd ff:ff:ff:ff:ff:ff 3: eth1: NO-CARRIER,BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state DORMANT qlen 1000 link/ether 00:15:00:4a:49:ff brd ff:ff:ff:ff:ff:ff inet6 fe80::215:ff:fe4a:49ff/64 scope link valid_lft forever preferred_lft forever 4: pan0: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN link/ether 1e:9c:97:7c:cd:17 brd ff:ff:ff:ff:ff:ff AFTER 1: lo: LOOPBACK,UP,LOWER_UP mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: NO-CARRIER,BROADCAST,MULTICAST,UP mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 00:14:c2:e2:8a:36 brd ff:ff:ff:ff:ff:ff 3: eth1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 00:15:00:4a:49:ff brd ff:ff:ff:ff:ff:ff inet 10.0.0.168/24 brd 10.0.0.255 scope global eth1 inet6 fe80::215:ff:fe4a:49ff/64 scope link valid_lft forever preferred_lft forever 4: pan0: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN link/ether 1e:9c:97:7c:cd:17 brd ff:ff:ff:ff:ff:ff -- connection forbidden on localhost after wireless connected https://bugs.launchpad.net/bugs/631064 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in ubuntu. -- 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 631064] Re: connection forbidden on localhost after wireless connected
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 localhost ip6-localhost ip6-loopback AFTER: 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 localhost ip6-localhost ip6-loopback I've also altered on the hostnames used in the URL, and localhost ip6-localhost ip6-loopback all act the same as in pages fetches before wireless network got configured and access denied after. I've tried a /etc/init.d/apache restart, and this still fails for ip6-localhost ip6-loopback, both translate only into ::1 which is not connected anymore (connection refused), whereas is would at leas provide a '403 forbidden' right after the wireless network got configured. localhost succeeds, but has an extra translation first into ::1 and then 127.0.0.1 See selections for wget for localhost and ip6-localhost, (before wireless configured, after wireless configured, after apache restart): BEFORE wget http://localhost/server-info --2010-09-09 07:43:24-- http://localhost/server-info Resolving localhost... ::1, 127.0.0.1 Connecting to localhost|::1|:80... connected. HTTP request sent, awaiting response... 200 OK wget http://ip6-localhost/server-info --2010-09-09 07:43:24-- http://ip6-localhost/server-info Resolving ip6-localhost... ::1 Connecting to ip6-localhost|::1|:80... connected. HTTP request sent, awaiting response... 200 OK AFTER (wireless configured) wget http://localhost/server-info --2010-09-09 07:44:14-- http://localhost/server-info Resolving localhost... ::1, 127.0.0.1 Connecting to localhost|::1|:80... connected. HTTP request sent, awaiting response... 403 Forbidden 2010-09-09 07:44:14 ERROR 403: Forbidden. wget http://ip6-localhost/server-info --2010-09-09 07:44:14-- http://ip6-localhost/server-info Resolving ip6-localhost... ::1 Connecting to ip6-localhost|::1|:80... connected. HTTP request sent, awaiting response... 403 Forbidden 2010-09-09 07:44:14 ERROR 403: Forbidden. APACHE RESTART wget http://localhost/server-info --2010-09-09 07:52:22-- http://localhost/server-info Resolving localhost... ::1, 127.0.0.1 Connecting to localhost|::1|:80... failed: Connection refused. Connecting to localhost|127.0.0.1|:80... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/html] wget http://ip6-localhost/server-info --2010-09-09 07:54:56-- http://ip6-localhost/server-info Resolving ip6-localhost... ::1 Connecting to ip6-localhost|::1|:80... failed: Connection refused. -- connection forbidden on localhost after wireless connected https://bugs.launchpad.net/bugs/631064 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in ubuntu. -- 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 631064] Re: connection forbidden on localhost after wireless connected
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 - - [08/Sep/2010:05:00:49 +0200] GET /server-info HTTP/1.0 200 75989 - Wget/1.12 (linux-gnu) localhost - - [08/Sep/2010:05:00:57 +0200] GET /server-info HTTP/1.0 403 529 - Wget/1.12 (linux-gnu) localhost - - [08/Sep/2010:05:01:17 +0200] GET /server-info HTTP/1.1 403 500 - Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.8) Gecko/20100723 Ubuntu/10.04 (lucid) Firefox/3.6.8 localhost - - [08/Sep/2010:05:01:20 +0200] GET /favicon.ico HTTP/1.1 404 500 - Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.8) Gecko/20100723 Ubuntu/10.04 (lucid) Firefox/3.6.8 error.log: [Wed Sep 08 05:00:57 2010] [error] [client ::1] client denied by server configuration: /var/www/server-info [Wed Sep 08 05:01:17 2010] [error] [client ::1] client denied by server configuration: /var/www/server-info [Wed Sep 08 05:01:20 2010] [error] [client ::1] File does not exist: /var/www/favicon.ico -- connection forbidden on localhost after wireless connected https://bugs.launchpad.net/bugs/631064 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in ubuntu. -- 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 631064] [NEW] connection forbidden on localhost after wireless connected
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'). After booting my laptop, this site is available through http://localhost/server-status; and the page as generated by this module is presented. After my laptop connects to my wireless network, communication trhough http://localhost/server-status; is blocked, with apache2 serving the page Forbidden.. You don't have permission to access /server-status on this server. Replacing localhost with the ip number 127.0.0.1 allows correct and normal access. I've also had this problem withour being in the neighborhood of my wireless network. After re-starting apache2 all access is as expected, using localhost to the restricted site is possible again. To me it looks like (but I'm not internally known to apache) the localhost interface got re-initiated, generating a new authorisation key while apache2 only holds an old key for the localhost before it got re-instantiated. This bug might be related to https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/37054 but I got lost in that. This is reproducable by re-starting the laptop. This problem might not be that urgent because server machines only have wired and fixed ethernet cards that are already connected at boot time. IfModule mod_status.c # # Allow server status reports generated by mod_status, # with the URL of http://servername/server-status # Uncomment and change the .example.com to allow # access from other hosts. # ExtendedStatus On SeeRequestTail On Location /server-status SetHandler server-status Order deny,allow Deny from all #Allow from hp8220 Allow from localhost ip6-localhost #Allow from .example.com /Location /IfModule ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: apache2.2-bin 2.2.14-5ubuntu8 ProcVersionSignature: Ubuntu 2.6.32-24.42-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic i686 Architecture: i386 Date: Sun Sep 5 20:53:58 2010 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: apache2 ** Affects: apache2 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- connection forbidden on localhost after wireless connected https://bugs.launchpad.net/bugs/631064 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in ubuntu. -- 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 631064] Re: connection forbidden on localhost after wireless connected
** 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 Ubuntu Server Team, which is subscribed to apache2 in ubuntu. -- 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 559896] [NEW] qemu-kvm daemon fails: exit 1
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: uncomment line #SLEEP_MILLISECS=2000 in file /etc/default/qemu-kvm I don't know what this sleep is for, it looks to me a process is too speedy for another process to complete. When still commented, the following logs were written in /var/log/*: (kernel modules kvm* would not have been loaded) == daemon.log == Apr 10 11:22:56 kvm-02 init: qemu-kvm pre-start process (5904) terminated with status 1 == kern.log == Apr 10 11:22:56 kvm-02 kernel: [ 4375.839967] kvm: Nested Virtualization enabled Apr 10 11:22:56 kvm-02 kernel: [ 4375.839975] kvm: Nested Paging enabled == messages == Apr 10 11:22:56 kvm-02 kernel: [ 4375.839967] kvm: Nested Virtualization enabled Apr 10 11:22:56 kvm-02 kernel: [ 4375.839975] kvm: Nested Paging enabled == syslog == Apr 10 11:22:56 kvm-02 kernel: [ 4375.839967] kvm: Nested Virtualization enabled Apr 10 11:22:56 kvm-02 kernel: [ 4375.839975] kvm: Nested Paging enabled Apr 10 11:22:56 kvm-02 init: qemu-kvm pre-start process (5904) terminated with status 1 ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: qemu-kvm 0.12.3+noroms-0ubuntu5 ProcVersionSignature: Ubuntu 2.6.32-16.25-generic Uname: Linux 2.6.32-16-generic x86_64 Architecture: amd64 Date: Sat Apr 10 11:13:21 2010 InstallationMedia: Ubuntu-Server 10.04 Lucid Lynx - Beta amd64 (20100317) KvmCmdLine: UIDPID PPID CSZ RSS PSR STIME TTY TIME CMD root 4707 1 55 201859 538228 0 11:09 ?00:02:13 /usr/bin/kvm -S -M pc-0.12 -enable-kvm -m 512 -smp 1 -name test-1004 -uuid ff2e7e05-2697-3db6-5f3d-44c8dee08315 -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/test-1004.monitor,server,nowait -monitor chardev:monitor -no-reboot -boot d -drive file=/mnt/data/kvm/test-1004/sda.img,if=virtio,index=0 -drive file=/mnt/data/iso/ubuntu-10.04-beta2-server-i386.iso,if=ide,media=cdrom,index=2 -net nic,macaddr=52:54:00:3c:c5:fb,vlan=0,model=virtio,name=virtio.0 -net tap,fd=44,vlan=0,name=tap.0 -chardev pty,id=serial0 -serial chardev:serial0 -parallel none -usb -vnc 127.0.0.1:0 -vga cirrus -soundhw es1370 Lsusb: Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 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 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-16-generic root=UUID=9e6c4a89-df23-4cda-be81-fc678c696646 ro quiet splash ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: qemu-kvm dmi.bios.date: 10/09/2009 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS M3N78 PRO ACPI BIOS Revision 1301 dmi.board.name: M3N78 PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM3N78PROACPIBIOSRevision1301:bd10/09/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N78PRO:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- qemu-kvm daemon fails: exit 1 https://bugs.launchpad.net/bugs/559896 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- 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
