[Bug 550409] [NEW] Slow disk IO for all guests with all disc modes and types.
Public bug reported: Very slow disk throughput for all guest OS's. Windows seems to be the slowest at ~3MBps. Linux guests usually get ~18MBps. All tests performed on two physical hosts. Host1: Intel Core2 - 2.8GHz, 4GB RAM, 2 SATA2 7500RPM discs in an mdraid0. Host2: Intel Core2 Quad - 2.4GHz, 5GB RAM, 6 SATA2 7500RPM discs. Mix of hw raid0/5, mdraid0/5, LVM, and LVM on mdraid5. Tested on both Ubuntu 9.10 and Ubuntu Lucid Beta1. Tested disc IO by copying a large file (>100MB). Tested against the following guests with the following average results: -Windows XP x86 - <4MBps - Installation takes >8 hours. -Ubuntu 9.10 server - <=20MBps -Ubuntu 9.10 server built for virtualization (vmbuilder virt optimization) - <=20MBps Tested on multiple hosts with multiple configurations. Same results on all physical hosts. Guest disk types: raw/qcow2, preallocated/thin provisioning, IDE/SCSI/VirtIO emulation. (Virtio emul only on Linux guests) Host disk types: ext3/4 on disc, ext3/4 on LVM on disc, ext3/4 on LVM on mdraid5 (3 7500RPM SATA2). Average host disk throughput: ext3/4 on disc - 80MBps, ext3/4 on LVM on disc - 80MBps, ext3/4 on LVM on mdraid5 - 75MBps Average guest disk throughput (WindowsXP): 3MBps on all hosts. Average guest disk throughput (Linux): 18MBps on all hosts. I also did a few non standard tests to rule some things out. 1. Hosted WindowsXP guest image on /dev/shm. This yielded much better, but still very poor results of ~20MBps. 2. Tested all guests on all hosts using both KVM and QEMU with the same results. 3. Tested all possible guest disc emulation modes on all guests, with no variation in results. 3. Tested WindowsXP guest image on an mdraid0 of 2 7500RPM Sata2 discs (160MBps on host). Same result. <4MBps. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: libvirt-bin 0.7.5-5ubuntu15 ProcVersionSignature: Ubuntu 2.6.32-16.25-generic Uname: Linux 2.6.32-16-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sun Mar 28 12:13:13 2010 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100317.1) ProcEnviron: LANGUAGE= PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: libvirt ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- Slow disk IO for all guests with all disc modes and types. https://bugs.launchpad.net/bugs/550409 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550409] Re: Slow disk IO for all guests with all disc modes and types.
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/42298604/Dependencies.txt -- Slow disk IO for all guests with all disc modes and types. https://bugs.launchpad.net/bugs/550409 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550409] Re: Slow disk IO for all guests with all disc modes and types.
** Description changed: - Very slow disk throughput for all guest OS's. Windows seems to be the slowest at ~3MBps. Linux guests usually get ~18MBps. All tests performed on two physical hosts. + Very slow disk throughput for all guest OS's. Windows seems to be the slowest at ~3MBps. Linux guests usually get ~18MBps. All tests performed on two physical hosts. Host1: Intel Core2 - 2.8GHz, 4GB RAM, 2 SATA2 7500RPM discs in an mdraid0. Host2: Intel Core2 Quad - 2.4GHz, 5GB RAM, 6 SATA2 7500RPM discs. Mix of hw raid0/5, mdraid0/5, LVM, and LVM on mdraid5. Tested on both Ubuntu 9.10 and Ubuntu Lucid Beta1. Tested disc IO by copying a large file (>100MB). Tested against the following guests with the following average results: -Windows XP x86 - <4MBps - Installation takes >8 hours. -Ubuntu 9.10 server - <=20MBps -Ubuntu 9.10 server built for virtualization (vmbuilder virt optimization) - <=20MBps Tested on multiple hosts with multiple configurations. Same results on all physical hosts. Guest disk types: raw/qcow2, preallocated/thin provisioning, IDE/SCSI/VirtIO emulation. (Virtio emul only on Linux guests) Host disk types: ext3/4 on disc, ext3/4 on LVM on disc, ext3/4 on LVM on mdraid5 (3 7500RPM SATA2). Average host disk throughput: ext3/4 on disc - 80MBps, ext3/4 on LVM on disc - 80MBps, ext3/4 on LVM on mdraid5 - 75MBps Average guest disk throughput (WindowsXP): 3MBps on all hosts. Average guest disk throughput (Linux): 18MBps on all hosts. I also did a few non standard tests to rule some things out. 1. Hosted WindowsXP guest image on /dev/shm. This yielded much better, but still very poor results of ~20MBps. 2. Tested all guests on all hosts using both KVM and QEMU with the same results. 3. Tested all possible guest disc emulation modes on all guests, with no variation in results. 3. Tested WindowsXP guest image on an mdraid0 of 2 7500RPM Sata2 discs (160MBps on host). Same result. <4MBps. + Possibly related: + -When creating guest images using virt-manager, on a FS under LVM, thin provisioning is ALWAYS the norm. Specifying a disc allocation the same size as the guest image, always results in a thin-provisioned guest image. Creating images on a FS without LVM works correctly. As stated though, I've seen the same performance regardless of thin-provisioning. + + I'm not sure what package is causing the problem. I tested against both + kvm and qemu with the same result, so I suspect libvirt, but I don't + know enough yet about how the 2/3 interact. I believe my testing has + ruled out the possibility of any problems with the host FS/discs. + ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: libvirt-bin 0.7.5-5ubuntu15 ProcVersionSignature: Ubuntu 2.6.32-16.25-generic Uname: Linux 2.6.32-16-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sun Mar 28 12:13:13 2010 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100317.1) ProcEnviron: - LANGUAGE= - PATH=(custom, no user) - LANG=en_US.utf8 - SHELL=/bin/bash + LANGUAGE= + PATH=(custom, no user) + LANG=en_US.utf8 + SHELL=/bin/bash SourcePackage: libvirt -- Slow disk IO for all guests with all disc modes and types. https://bugs.launchpad.net/bugs/550409 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 430093] Re: Eucalyptus "403 Forbidden" when trying to run instance
Same error. New install. Also new re-install after much frustration :) 20:31:49 WARN PipelineRegistry | => More than one candidate pipeline. Ignoring offer by: internal-query-pipeline-Eucalyptus of type InternalQueryPipeline com.eucalyptus.ws.AuthenticationException: User authentication failed. ... -- Eucalyptus "403 Forbidden" when trying to run instance https://bugs.launchpad.net/bugs/430093 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550409] Re: Slow disk IO for all guests with all disc modes and types.
1. create the guests The first set of guests I created (both Windows and Linux) were created with virt-manager. I used default settings for both Windows and Linux guests. Windows guests defaulted to IDE emulation, and Linux guests defaulted to Virtio emulation. I have since tried all possible emulation modes on both guest OS's. Without virt-manager, I have created Linux guests using vmbuilder. vmbuilder kvm ubuntu --suite lucid --flavour virtual --arch i386 --libvirt qemu:///system --user=foo --pass=bar 2. start the guests Guests are normally started with virt-manager, which results in the following command: /usr/bin/kvm -S -M pc-0.12 -cpu qemu32 -enable-kvm -m 512 -smp 1 -name winxp -uuid eb0416e2-54d2-d4cb-936d-331edbe443c0 -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/winxp.monitor,server,nowait -monitor chardev:monitor -localtime -boot c -drive file=/datahauz/storage/software/Windows/EN_WINDOWS_XP_PRO_WITH_SP2.ISO,if=ide,media=cdrom,index=2 -drive file=/datahauz/storage/kvm/tinyxp.img,if=ide,index=0,boot=on,format=raw -net nic,macaddr=52:54:00:0d:11:23,vlan=0,name=nic.0 -net tap,fd=37,vlan=0,name=tap.0 -chardev pty,id=serial0 -serial chardev:serial0 -parallel none -usb -usbdevice tablet -vnc 127.0.0.1:0 -k en-us -vga cirrus 3. run the benchmarks Several benchmarks were used. Under windows I used IOmeter, and also timed file copies while observing both host and guest disc access. I did the following file copy tests. 1. Scp a 2GB file from the hosts disc, to the guests disc. 2. Scp a 2GB file from the hosts memory to the guests disc. 3. Scp a 2GB file from the guests disc to the hosts disc. 4. Scp a 2GB file from the guests disc to the hosts memory. Then I put the guest disc image in /dev/shm and tried the same tests again. With the guest disc hosted on /dev/shm, I get slightly better disc speeds (15MBps windows, 30MBps Linux) Another point to note, is that when scping to the Linux guest disc, I get about 20MBps, but to the guest memory (/dev/shm) I get 38MBps. Either way, Linux guests do better on both disc and memory throughput, but are still much slower (1/4) The speed I would expect. My expectations are based on performance results under VMware, Virtualbox, and Xen, which are all quite similar (~40-70MBps disc throughput) -- Slow disk IO for all guests with all disc modes and types. https://bugs.launchpad.net/bugs/550409 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 550409] Re: Slow disk IO for all guests with all disc modes and types.
This is the command used to start one of the affect Linux guests: /usr/bin/kvm -S -M pc-0.12 -enable-kvm -m 512 -smp 1 -name ubuntu -uuid 9de5914b-f448-cb8d-066f-ec51286c80c0 -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/ubuntu.monitor,server,nowait -monitor chardev:monitor -boot c -drive file=/datahauz/kvm/ubuntu.qemu,if=virtio,index=0,boot=on,format=qcow2 -drive if=ide,media=cdrom,index=2 -net nic,macaddr=52:54:00:12:34:56,vlan=0,name=nic.0 -net tap,fd=39,vlan=0,name=tap.0 -chardev pty,id=serial0 -serial chardev:serial0 -parallel none -usb -vnc 127.0.0.1:0 -k en-us -vga cirrus The SCP file transfers (Linux guest) were tested against both the guest disk as well as guest /dev/shm. Pushing a file through the network stack to /dev/shm was faster than pushing a file from the guest disc to shm. This at least tells us that the guest machine is capable of dealing with greater throughput than the disc. I just wanted to make sure the bottleneck was confined to the disc. FYI, the disc throughput on the Linux guests is poor, but it is at least usable (though not in a production environment). The throughput on Windows guests is 1/10th the speed. For all tests, I verified results by at least two methods. Under Windows guests, I performed file copies to/from guest disc, ftp transfer of large files to the guest disc, and used IOmeter. All three tests provided nearly identical results. ~2MBps R and ~2MBps W +/-500KBps. Under Linux guests, I performed file copies to/from guest disc, scp transfer of large files to/from the guest disc, and ran Bonnie++ (results follow). I also created >2GB files using 'dd' from both /dev/zero and from /dev/mem. Bonnie++ Linux Guest: b...@webtest:~$ time dd if=/dev/zero of=1g bs=4096 count=25 25+0 records in 25+0 records out 102400 bytes (1.0 GB) copied, 67.6536 s, 15.1 MB/s real1m7.663s user0m0.080s sys 0m1.510s And again to a raw device without a file system: r...@webtest:~# time dd if=/dev/zero of=/dev/vdb bs=4096 count=40 40+0 records in 40+0 records out 163840 bytes (1.6 GB) copied, 66.2002 s, 24.7 MB/s real1m6.208s user0m0.070s sys 0m1.750s b...@webtest:~$ bonnie++ Writing with putc()...done Writing intelligently...done Rewriting...done Reading with getc()...done Reading intelligently...done start 'em...done...done...done... Create files in sequential order...done. Stat files in sequential order...done. Delete files in sequential order...done. Create files in random order...done. Stat files in random order...done. Delete files in random order...done. Version 1.03c --Sequential Output-- --Sequential Input- --Random- -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks-- MachineSize K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP webtest 1G 12754 17 11505 2 18583 3 65015 93 500392 53 + +++ --Sequential Create-- Random Create -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete-- files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP 16 + +++ + +++ + +++ + +++ + +++ + +++ webtest,1G,12754,17,11505,2,18583,3,65015,93,500392,53,+,+++,16,+,+++,+,+++,+,+++,+,+++,+,+++,+,+++ Linux Host: b...@octillion:~$ time dd if=/dev/zero of=1g bs=4096 count=25 25+0 records in 25+0 records out 102400 bytes (1.0 GB) copied, 5.2139 s, 196 MB/s real0m5.412s user0m0.080s sys 0m2.800s b...@octillion:~$ bonnie++ Writing a byte at a time...done Writing intelligently...done done Reading a byte at a time...done Reading intelligently...done start 'em...done...done...done...done...done... Create files in sequential order...done. Stat files in sequential order...done. Delete files in sequential order...done. Create files in random order...done. Stat files in random order...done. Delete files in random order...done. Version 1.96 --Sequential Output-- --Sequential Input- --Random- Concurrency 1 -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks-- MachineSize K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP octillion 10G 161 97 76547 18 42493 12 1976 96 114159 10 262.1 3 Latency 147ms4926ms 16159ms 21546us 176ms 198ms Version 1.96 --Sequential Create-- Random Create octillion -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete-- files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP 16 15145 28 + +++ 22692 29 18729 30 + +++ 25217 30 Latency 695us 749us 577us 728us 60us 131us 1.96,1.96,octillion,1,1269961838,10G,,161,97,76547,18,42493,12,1976,96,114159,10,262.1,3,16,15145,28,+,+++,22692,29,18729,30,+,+++,25217,30,147ms,4926ms,16159m
Re: [Bug 550409] Re: Slow disk IO for all guests with all disc modes and types.
I also just ran IOmeter on the Windows guest again, against both IDE and SCSI emulation, against guest discs hosted on the mdraid5 with lvm, as well as a single SATA2 7500RPM disc. Identical results against both targets. 4096B blocks = 0.75MBps. 16KB blocks = 1.0MBps, 32KB blocks = 4MBps, >=64KB blocks = 4MBps. All tests 50/50 read/write, and run again 50/50 sequential/random. -- Slow disk IO for all guests with all disc modes and types. https://bugs.launchpad.net/bugs/550409 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 540649] Re: mission-control-5 crashed with SIGSEGV in g_closure_invoke()
Same issue with a few notes. 1. This happened after running some updates this morning.. Unfortunately, I don't know which ones. 2. When this happened, I closed empathy and restarted. I got the same result as Ian Corne. 3. After rebooting, empathy was no longer installed, and I couldn't reinstall due to conflicts with nautilus-sendto-empathy. 4. I did an apt-get update && apt-get upgrade, and then apt-get install empathy. This solved the problem. -- mission-control-5 crashed with SIGSEGV in g_closure_invoke() https://bugs.launchpad.net/bugs/540649 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 483335] Re: Rhythmbox 0.12.5 cannot start playback of Last.fm after pausing
*** This bug is a duplicate of bug 441444 *** https://bugs.launchpad.net/bugs/441444 Confirmed in Ubuntu 10.04 Desktop (amd64). Steps to reproduce: 1. Start Rhythmbox 2. Click on Last.FM 3. Enter Last.FM account details and sign in. 4. Play any station. 5. Stop playback. 6. Start playback on the same channel (without switching channels). Attached output of command `rhythmbox -D lastfm &> rhythmbox-debug.txt` ** Attachment added: "rhythmbox-debug.txt" http://launchpadlibrarian.net/49099686/rhythmbox-debug.txt -- Rhythmbox 0.12.5 cannot start playback of Last.fm after pausing https://bugs.launchpad.net/bugs/483335 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 483335] Re: Rhythmbox 0.12.5 cannot start playback of Last.fm after pausing
*** This bug is a duplicate of bug 441444 *** https://bugs.launchpad.net/bugs/441444 I can also confirm this affects all new installations of Ubuntu Desktop 10.04 (amd64 and x86). I have tested on 7 physical machines, both after a vanilla install as well as after updating all packages. -- Rhythmbox 0.12.5 cannot start playback of Last.fm after pausing https://bugs.launchpad.net/bugs/483335 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 255307] Re: Can't connect to msn accounts
Empathy 2.28.1.1 doesn't seem to call telepathy-butterfly anymore. I have the same problem, but there is no telepathy process to kill, and msn NEVER works for any of my msn accounts on two of three of my Karmic machines. I have not found a work around that results in MSN connecting. -- Can't connect to msn accounts https://bugs.launchpad.net/bugs/255307 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641290] Re: [04f3:0903] Elan Microelectronics Corp fingerprint reader not recognised
Same issue here as Malammar. The first time I tried 'sudo ./enroll', it did read my print and I did get a pgm out of it. Subsequent tests however just time out, like so: bens@quadrillion /usr/local/src/libfprint/examples $ sudo ./enroll This program will enroll your right index finger, unconditionally overwriting any right-index print that was enrolled previously. If you want to continue, press enter, otherwise hit Ctrl+C fp:debug [fp_init] fp:debug [register_driver] registered driver upekts fp:debug [register_driver] registered driver aes3500 fp:debug [register_driver] registered driver aes4000 fp:debug [register_driver] registered driver aes2501 fp:debug [register_driver] registered driver aes2550 fp:debug [register_driver] registered driver uru4000 fp:debug [register_driver] registered driver vcom5s fp:debug [register_driver] registered driver upeksonly fp:debug [register_driver] registered driver aes1610 fp:debug [register_driver] registered driver aes1660 fp:debug [register_driver] registered driver aes2660 fp:debug [register_driver] registered driver vfs101 fp:debug [register_driver] registered driver vfs301 fp:debug [register_driver] registered driver vfs5011 fp:debug [register_driver] registered driver upektc fp:debug [register_driver] registered driver upektc_img fp:debug [register_driver] registered driver etes603 fp:debug [register_driver] registered driver vfs0050 fp:debug [register_driver] registered driver elan fp:debug [find_supporting_driver] driver elan supports USB device 04f3:0903 fp:debug [find_supporting_driver] selected driver elan supports USB device 04f3:0903 Found device claimed by ElanTech Fingerprint Sensor driver sync:debug [fp_dev_open] async:debug [fp_async_dev_open] elan:debug [dev_init] async:debug [fpi_drvcb_open_complete] status 0 sync:debug [sync_open_cb] status 0 Opened device. It's now time to enroll your finger. You will need to successfully scan your finger 5 times to complete the process. Scan your finger now. sync:debug [fp_enroll_finger_img] async:debug [fp_async_enroll_start] starting enrollment fp:debug [generic_acquire_start] action 1 elan:debug [dev_activate] elan:debug [elan_activate] elan:debug [elan_dev_reset] drv:debug [__ssm_call_handler] 0x1f9cce0 entering state 0 elan:debug [elan_run_cmd] 4019 sync:debug [fp_enroll_finger_img] elan will handle enroll stage 0/4 elan:debug [elan_cmd_cb] elan:debug [elan_cmd_cb] transfer timed out drv:debug [fpi_ssm_mark_aborted] error -110 from state 0 drv:debug [fpi_ssm_mark_completed] 0x1f9cce0 completed with status -110 elan:debug [activate_complete] fp:debug [fpi_imgdev_activate_complete] status -110 async:debug [fpi_drvcb_enroll_started] status -110 sync:debug [sync_enroll_cb] result -110 sync:error [fp_enroll_finger_img] unrecognised return code -110 sync:debug [fp_enroll_finger_img] ending enrollment async:debug [fp_async_enroll_stop] elan:debug [dev_deactivate] elan:debug [dev_change_state] 0 poll:debug [fpi_timeout_add] in 10ms poll:debug [get_next_timeout_expiry] next timeout in 0.009986s poll:debug [get_next_timeout_expiry] first timeout already expired poll:debug [handle_timeout] elan:debug [elan_change_state] 0 elan:debug [elan_deactivate] elan:debug [elan_dev_reset] drv:debug [__ssm_call_handler] 0x1f9cce0 entering state 0 elan:debug [deactivate_run_state] elan:debug [elan_run_cmd] 000b elan:debug [elan_cmd_cb] elan:debug [elan_cmd_cb] transfer timed out drv:debug [fpi_ssm_mark_aborted] error -110 from state 0 drv:debug [fpi_ssm_mark_completed] 0x1f9cce0 completed with status -110 elan:debug [deactivate_complete] fp:debug [fpi_imgdev_deactivate_complete] async:debug [fpi_drvcb_enroll_stopped] sync:debug [enroll_stop_cb] Enroll failed with error -22 sync:debug [fp_dev_close] elan:debug [dev_deinit] elan:debug [elan_dev_reset] async:debug [fpi_drvcb_close_complete] sync:debug [sync_close_cb] fp:debug [fp_exit] This is running the code from git from today. I also could not get fprint-demo to recognise the elan device. 0903 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641290 Title: [04f3:0903] Elan Microelectronics Corp fingerprint reader not recognised To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1641290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1160599] Re: AMD-Vi initialization fails
Not currently, as I'm no longer running Xen for the purpose originally required. The issue was eventually resolved by a patch that was floating around the Xen-dev mailing list, but I don't know if it ever made it into mainline 4.2 (I was told it would be included). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1160599 Title: AMD-Vi initialization fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1160599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1160599] [NEW] AMD-Vi initialization fails
Public bug reported: Build: Ubuntu 12.04 and Linux Mint 13 Maya Package: xen-hypervisor-4.1-amd64:amd64 (4.1.2-2ubuntu2.5, 4.1.2-2ubuntu2.6) Expected: AMD-Vi initialization successful and IOMMU enabled Actual: AMD-Vi initialization fails and IOMMU disabled Upgrade from: xen-hypervisor-4.1-amd64:amd64 (4.1.2-2ubuntu2.6, 4.1.2-2ubuntu2) Upgrade to: xen-hypervisor-4.1-amd64:amd64 (4.1.2-2ubuntu2.5, 4.1.2-2ubuntu2.6) After upgrade, AMD-Vi initialization fails and I/O virtualization disabled: (XEN) Initing memory sharing. (XEN) IVHD Error: Invalid IO-APIC 0xff (XEN) AMD-Vi: Error initialization (XEN) I/O virtualisation disabled Full xm-dmesg output: (XEN) Xen version 4.1.2 (Ubuntu 4.1.2-2ubuntu2.6) (stefan.ba...@canonical.com) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) Mon Feb 4 16:41:16 UTC 2013 (XEN) Bootloader: GRUB 1.99-21ubuntu3.9 (XEN) Command line: pci_msitranslate=0 xen-pciback=passthrough xen-pciback.hide=(06:00.0)(06.00.1) (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds (XEN) Disc information: (XEN) Found 7 MBR signatures (XEN) Found 6 EDD information structures (XEN) Xen-e820 RAM map: (XEN) - 0009e800 (usable) (XEN) 0009e800 - 000a (reserved) (XEN) 000e - 0010 (reserved) (XEN) 0010 - bab4f000 (usable) (XEN) bab4f000 - baf83000 (reserved) (XEN) baf83000 - baf93000 (ACPI data) (XEN) baf93000 - bbcfa000 (ACPI NVS) (XEN) bbcfa000 - bca4f000 (reserved) (XEN) bca4f000 - bca5 (usable) (XEN) bca5 - bcc56000 (ACPI NVS) (XEN) bcc56000 - bd083000 (usable) (XEN) bd083000 - bd7f4000 (reserved) (XEN) bd7f4000 - bd80 (usable) (XEN) f800 - fc00 (reserved) (XEN) fec0 - fec01000 (reserved) (XEN) fec1 - fec11000 (reserved) (XEN) fec2 - fec21000 (reserved) (XEN) fed0 - fed01000 (reserved) (XEN) fed61000 - fed71000 (reserved) (XEN) fed8 - fed9 (reserved) (XEN) fef0 - 0001 (reserved) (XEN) 00011000 - 00043f00 (usable) (XEN) ACPI: RSDP 000F0490, 0024 (r2 ALASKA) (XEN) ACPI: XSDT BAF89070, 005C (r1 ALASKA A M I 1072009 AMI 10013) (XEN) ACPI: FACP BAF90BF8, 010C (r5 ALASKA A M I 1072009 AMI 10013) (XEN) ACPI Warning (tbfadt-0232): FADT (revision 5) is longer than ACPI 2.0 version, truncating length 0x10C to 0xF4 [20070126] (XEN) ACPI Warning (tbfadt-0444): Optional field "Pm2ControlBlock" has zero address or length: /1 [20070126] (XEN) ACPI: DSDT BAF89168, 7A8A (r2 ALASKA A M I 0 INTL 20051117) (XEN) ACPI: FACS BBCF4F80, 0040 (XEN) ACPI: APIC BAF90D08, 009E (r3 ALASKA A M I 1072009 AMI 10013) (XEN) ACPI: FPDT BAF90DA8, 0044 (r1 ALASKA A M I 1072009 AMI 10013) (XEN) ACPI: MCFG BAF90DF0, 003C (r1 ALASKA A M I 1072009 MSFT 10013) (XEN) ACPI: HPET BAF90E30, 0038 (r1 ALASKA A M I 1072009 AMI 5) (XEN) ACPI: SSDT BAF90FC0, 1714 (r1 AMD POWERNOW 1 AMD 1) (XEN) ACPI: IVRS BAF90EC0, 0100 (r1 AMD RD890S 202031 AMD 0) (XEN) System RAM: 16287MB (16678040kB) (XEN) Domain heap initialised (XEN) ACPI: 32/64X FACS address mismatch in FADT - bbcf4f80/, using 32 (XEN) Processor #16 5:1 APIC version 16 (XEN) Processor #17 5:1 APIC version 16 (XEN) Processor #18 5:1 APIC version 16 (XEN) Processor #19 5:1 APIC version 16 (XEN) Processor #20 5:1 APIC version 16 (XEN) Processor #21 5:1 APIC version 16 (XEN) Processor #22 5:1 APIC version 16 (XEN) Processor #23 5:1 APIC version 16 (XEN) IOAPIC[0]: apic_id 9, version 33, address 0xfec0, GSI 0-23 (XEN) IOAPIC[1]: apic_id 10, version 33, address 0xfec2, GSI 24-55 (XEN) Enabling APIC mode: Flat. Using 2 I/O APICs (XEN) Table is not found! (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Detected 3913.328 MHz processor. (XEN) Initing memory sharing. (XEN) IVHD Error: Invalid IO-APIC 0xff (XEN) AMD-Vi: Error initialization (XEN) I/O virtualisation disabled (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) Platform timer is 14.318MHz HPET (XEN) Allocated console ring of 16 KiB. (XEN) HVM: ASIDs enabled. (XEN) SVM: Supported advanced features: (XEN) - Nested Page Tables (NPT) (XEN) - Last Branch Record (LBR) Virtualisation (XEN) - Next-RIP Saved on #VMEXIT (XEN) - VMCB Clean Bits (XEN) - Pause-Intercept Filter (XEN) HVM: SVM enabled (XEN) HVM: Hardware Assisted Paging detected. (XEN) Brought up 8 CPUs (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x100 -> 0x234d000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 00042000->00042800 (4047290 pages to be allocated) (XEN) Init. ramdisk: 00043c817000->00043efff800 (XEN) VI
[Bug 1160599] Re: AMD-Vi initialization fails
** Attachment added: "lshw output" https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1160599/+attachment/3599568/+files/hw.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1160599 Title: AMD-Vi initialization fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1160599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 580319] Re: dhcp3-server launches before upstart brings all interface, thus failing to start
Confirmed here as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/580319 Title: dhcp3-server launches before upstart brings all interface, thus failing to start -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 393012] Re: smb: Error while copying file, "Invalid argument"
I have the same problem, but with perhaps a bit more information. I am able to copy files using nautilus to a samba share hosted on XPsp3 or earlier. The bug is only present (for me) when copying to a share hosted on Windows 7 or Server 2008r2. Something to do with the new authentication requirements? I am able to copy files to the share using smbclient, or even the cp command to ~/.gvfs/sharename. The bug only exists when using the Nautilus interface. The mount point created by Nautilus/gvfs also works fine. * When copying to a Win7/Server2008r2 share via Nautilus: -files <48KB transfer correctly. -files >48KB transfer only the first 48KB. * Copying via 'cp' to ~/.gvfs/sharename completes successfully. * Copying via 'smbclient' completes successfully. ie: smbclient server\\share > cp foo.txt foo.txt * Copying via 'mc' completes successfully. Steps to reproduce: 1. Create a share on a Win7 or Server 2008r2 server. 2. Use Nautilus to browse to the share. 3. Copy file >48KB. Result "Invalid Argument" OR: 1. Create a share on a Win7 or Server 2008r2 server. 2. gvfs-copy foo.txt smb://server/share/ Result "Invalid Argument" In my case, I can not reproduce against WinXP or earlier. This is clearly a problem with gvfs-copy. -- smb: Error while copying file, "Invalid argument" https://bugs.launchpad.net/bugs/393012 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 393012] Re: smb: Error while copying file, "Invalid argument"
Should also mention that I have no problem reading data from the share. -- smb: Error while copying file, "Invalid argument" https://bugs.launchpad.net/bugs/393012 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 393012] Re: smb: Error while copying file, "Invalid argument"
Filed with bugzilla.gnome.org https://bugzilla.gnome.org/show_bug.cgi?id=633937 ** Bug watch added: GNOME Bug Tracker #633937 https://bugzilla.gnome.org/show_bug.cgi?id=633937 -- smb: Error while copying file, "Invalid argument" https://bugs.launchpad.net/bugs/393012 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
