bugs.launchpad.net/qemu/+bug/1490611
Preview meta tags from the bugs.launchpad.net website.
Linked Hostnames
18- 64 links tobugs.launchpad.net
- 23 links tolaunchpad.net
- 3 links tolists.nongnu.org
- 2 links tocanonical.com
- 2 links towiki.ubuntu.com
- 1 link toanswers.launchpad.net
- 1 link toazure.microsoft.com
- 1 link toblog.launchpad.net
Thumbnail

Search Engine Appearance
Bug #1490611 “Using qemu >=2.2.1 to convert raw->VHD (fixed) add...” : Bugs : QEMU
[Impact] * Starting with a raw disk image, using "qemu-img convert" to convert from raw to VHD results in the output VHD file's virtual size being aligned to the nearest 516096 bytes (16 heads x 63 sectors per head x 512 bytes per sector), instead of preserving the input file's size as the output VHD's virtual disk size. * Microsoft Azure requires that disk images (VHDs) submitted for upload have virtual sizes aligned to a megabyte boundary. (Ex. 4096MB, 4097MB, 4098MB, etc. are OK, 4096....
Bing
Bug #1490611 “Using qemu >=2.2.1 to convert raw->VHD (fixed) add...” : Bugs : QEMU
[Impact] * Starting with a raw disk image, using "qemu-img convert" to convert from raw to VHD results in the output VHD file's virtual size being aligned to the nearest 516096 bytes (16 heads x 63 sectors per head x 512 bytes per sector), instead of preserving the input file's size as the output VHD's virtual disk size. * Microsoft Azure requires that disk images (VHDs) submitted for upload have virtual sizes aligned to a megabyte boundary. (Ex. 4096MB, 4097MB, 4098MB, etc. are OK, 4096....
DuckDuckGo
Bug #1490611 “Using qemu >=2.2.1 to convert raw->VHD (fixed) add...” : Bugs : QEMU
[Impact] * Starting with a raw disk image, using "qemu-img convert" to convert from raw to VHD results in the output VHD file's virtual size being aligned to the nearest 516096 bytes (16 heads x 63 sectors per head x 512 bytes per sector), instead of preserving the input file's size as the output VHD's virtual disk size. * Microsoft Azure requires that disk images (VHDs) submitted for upload have virtual sizes aligned to a megabyte boundary. (Ex. 4096MB, 4097MB, 4098MB, etc. are OK, 4096....
General Meta Tags
6- titleBug #1490611 “Using qemu >=2.2.1 to convert raw->VHD (fixed) add...” : Bugs : QEMU
- charsetUTF-8
- msapplication-TileColor#da532c
- msapplication-config/@@/browserconfig.xml?v=2022
- theme-color#ffffff
Open Graph Meta Tags
6- og:description[Impact] * Starting with a raw disk image, using "qemu-img convert" to convert from raw to VHD results in the output VHD file's virtual size being aligned to the nearest 516096 bytes (16 heads x 63 sectors per head x 512 bytes per sector), instead of preserving the input file's size as the output VHD's virtual disk size. * Microsoft Azure requires that disk images (VHDs) submitted for upload have virtual sizes aligned to a megabyte boundary. (Ex. 4096MB, 4097MB, 4098MB, etc. are OK, 4096....
- og:titleBug #1490611 “Using qemu >=2.2.1 to convert raw->VHD (fixed) add...” : Bugs : QEMU
- og:typewebsite
- og:image/@@/launchpad-og-image.png
- og:urlhttps://bugs.launchpad.net/bugs/1490611
Link Tags
9- alternatehttp://feeds.launchpad.net/bugs/1490611/bug.atom
- apple-touch-icon/@@/apple-touch-icon.png?v=2022
- canonicalhttps://bugs.launchpad.net/bugs/1490611
- icon/@@/favicon-32x32.png?v=2022
- icon/@@/favicon-16x16.png?v=2022
Links
107- http://blog.launchpad.net
- http://canonical.com
- http://git.qemu.org/?p=qemu.git;a=commitdiff;h=fb9245c2610932d33ce14
- http://lists.nongnu.org/archive/html/qemu-devel/2016-02/msg05511.html
- http://lists.nongnu.org/archive/html/qemu-devel/2016-02/msg06037.html