[Bug 282858] Re: Ubuntu-xen-desktop does not install a dom0 kernel

2010-01-03 Thread Todd Deshane
Official support for Xen on Ubuntu/Fedora isn't likely to be offered until Xen dom0 support gets into mainline linux. For updates on that effort and other alternatives for dom0 kernels to try see: http://wiki.xensource.com/xenwiki/XenDom0Kernels http://wiki.xensource.com/xenwiki/XenParavirtOps S

[Bug 370957] Re: xm xen tool crash on startup

2009-12-02 Thread Todd Deshane
I would suggest trying the latest PV-ops based kernel. There are also some other modern kernels supported by the Xen team. See: http://wiki.xensource.com/xenwiki/XenParavirtOps http://wiki.xensource.com/xenwiki/XenDom0Kernels -- xm xen tool crash on startup https://bugs.launchpad.net/bugs/3709

[Bug 370957] Re: xm xen tool crash on startup

2009-05-02 Thread Todd Deshane
Oh, OK. Kernel 2.6.28-11 is not a dom0 kernel. You will either need to build your own our grab the dom0 kernel from hardy. Ubuntu (and Fedora) are not releasing a new kernel until the dom0 kernel gets into mailine. See: http://wiki.xensource.com/xenwiki/XenParavirtOps ** Changed in: xen-tools (

[Bug 370957] Re: xm xen tool crash on startup

2009-05-02 Thread Todd Deshane
This is usually a sign of a python library/PATH problem. What versions of Xen/Xen tools etc. and how installed? Did you have any Xen from source installed on this system that could be conflicting with the python librarires? -- xm xen tool crash on startup https://bugs.launchpad.net/bugs/370957

[Bug 370957] Re: xm xen tool crash on startup

2009-05-02 Thread Todd Deshane
Did you try running the command with sudo (or as root)? -- xm xen tool crash on startup https://bugs.launchpad.net/bugs/370957 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-b...@lists.ubuntu.com http

[Bug 366268] Re: fails if no ssh keys exist

2009-04-24 Thread Todd Deshane
*** This bug is a duplicate of bug 352114 *** https://bugs.launchpad.net/bugs/352114 See also bug#354288 and https://code.launchpad.net/~deshantm/vmbuilder/vmbuilder-deshantm -- fails if no ssh keys exist https://bugs.launchpad.net/bugs/366268 You received this bug notification because you

[Bug 366268] Re: fails if no ssh keys exist

2009-04-24 Thread Todd Deshane
*** This bug is a duplicate of bug 352114 *** https://bugs.launchpad.net/bugs/352114 ** This bug has been marked a duplicate of bug 352114 vmbuilder: attempt to copy ssh key before user is created [Jaunty] [PATCH] -- fails if no ssh keys exist https://bugs.launchpad.net/bugs/366268 You re

[Bug 352114] Re: vmbuilder: attempt to copy ssh key before user is created [Jaunty] [PATCH]

2009-04-08 Thread Todd Deshane
** Attachment removed: "diff-u-dapper.py" http://launchpadlibrarian.net/25090831/diff-u-dapper.py -- vmbuilder: attempt to copy ssh key before user is created [Jaunty] [PATCH] https://bugs.launchpad.net/bugs/352114 You received this bug notification because you are a member of Ubuntu Bugs, whi

[Bug 352114] Re: vmbuilder: attempt to copy ssh key before user is created [Jaunty] [PATCH]

2009-04-05 Thread Todd Deshane
added a branch link ** Branch linked: lp:~deshantm/vmbuilder/vmbuilder-deshantm -- vmbuilder: attempt to copy ssh key before user is created [Jaunty] [PATCH] https://bugs.launchpad.net/bugs/352114 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 354288] Re: ssh keys for user are not owned by the user [Jaunty] [PATCH]

2009-04-05 Thread Todd Deshane
added a branch link ** Branch linked: lp:~deshantm/vmbuilder/vmbuilder-deshantm -- ssh keys for user are not owned by the user [Jaunty] [PATCH] https://bugs.launchpad.net/bugs/354288 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. --

[Bug 356043] Re: ubuntu-vm-builder fails to build kvm hardy

2009-04-05 Thread Todd Deshane
This looks like it might be a duplicate of bug #342359 Can you see if the changes in the following fix your problem too: https://code.launchpad.net/~jdstrand/vmbuilder/vmbuilder-jdstrand -- ubuntu-vm-builder fails to build kvm hardy https://bugs.launchpad.net/bugs/356043 You received this bug n

[Bug 354288] Re: ssh keys for user are not owned by the user [Jaunty] [PATCH]

2009-04-03 Thread Todd Deshane
At first I tried to go the os.chown way, but there were a few complications that made the code less elegant. First, the chown command takes, as the 2nd and 3rd arguments, the uid and gid of the user. The user that needs to own the .ssh directory and its contents is a user that is created within th

[Bug 335472] Re: device-mapper: remove ioctl failed: Device or resource busy

2009-04-03 Thread Todd Deshane
Looks like this is not a bug. Needed to add a --rootsize= to the command line. It completes now without error, must be the ubuntu-desktop was bigger than the default 4G disk -- device-mapper: remove ioctl failed: Device or resource busy https://bugs.launchpad.net/bugs/335472 You received this b

[Bug 335472] Re: device-mapper: remove ioctl failed: Device or resource busy

2009-04-02 Thread Todd Deshane
On a crash, the loopback device also stays mounted and it can't be umounted (not any way that I can find at least) For example: sudo losetup -a /dev/loop0: [0807]:2613376 (/tmp/vmbuilder_NclQw/disk0.img) -- device-mapper: remove ioctl failed: Device or resource bu

[Bug 354288] Re: ssh keys for user are not owned by the user [Jaunty] [PATCH]

2009-04-02 Thread Todd Deshane
** Attachment added: "chown-ssh-keys-dapper.py.diff" http://launchpadlibrarian.net/24735899/chown-ssh-keys-dapper.py.diff -- ssh keys for user are not owned by the user [Jaunty] [PATCH] https://bugs.launchpad.net/bugs/354288 You received this bug notification because you are a member of Ubun

[Bug 354288] [NEW] ssh keys for user are not owned by the user [Jaunty] [PATCH]

2009-04-02 Thread Todd Deshane
Public bug reported: with the options: --user username --ssh-user-key= the key is copied in, but the ownership is for root, not for the user. attached is a patch from the output of: diff -u /usr/share/pyshared/VMBuilder/plugins/ubuntu/dapper.py.orig /usr/share/pyshared/VMBuilder/plugins/ubuntu

[Bug 335472] Re: device-mapper: remove ioctl failed: Device or resource busy

2009-04-02 Thread Todd Deshane
More testing another tweak to the patch provided in bug #352114 This line doesn't work (gives the errors from above) vmbuilder kvm ubuntu --libvirt=qemu:///system --addpkg ubuntu-desktop --addpkg openssh-server --hostname ubuntu-desktop --user username --ssh-user-key=ssh_key But this line (witho

[Bug 352114] Re: vmbuilder: attempt to copy ssh key before user is created [Jaunty] [PATCH]

2009-04-02 Thread Todd Deshane
updated diff -u attached. This should maintain the proper ordering needed. ** Attachment added: "updated-diff-u-dappper.py.diff" http://launchpadlibrarian.net/24712008/updated-diff-u-dappper.py.diff -- vmbuilder: attempt to copy ssh key before user is created [Jaunty] [PATCH] https://bugs.lau

[Bug 352114] Re: vmbuilder: attempt to copy ssh key before user is created [Jaunty] [PATCH]

2009-04-02 Thread Todd Deshane
This patch might have a bug. The ordering might still have a problem related to #335472 -- vmbuilder: attempt to copy ssh key before user is created [Jaunty] [PATCH] https://bugs.launchpad.net/bugs/352114 You received this bug notification because you are a member of Ubuntu Bugs, which is subsc

[Bug 335472] Re: device-mapper: remove ioctl failed: Device or resource busy

2009-04-02 Thread Todd Deshane
tail of debug verbose output attached ** Attachment added: "output-debug-verbose" http://launchpadlibrarian.net/24710676/output-debug-verbose -- device-mapper: remove ioctl failed: Device or resource busy https://bugs.launchpad.net/bugs/335472 You received this bug notification because you ar

[Bug 335472] Re: device-mapper: remove ioctl failed: Device or resource busy

2009-04-01 Thread Todd Deshane
"ubuntu-vm-builder kvm jaunty" does not re-produce this. I am getting it with a more complicated command however: vmbuilder kvm ubuntu --libvirt=qemu:///system --addpkg ubuntu-desktop --addpkg openssh-server --hostname ubuntu-desktop --user username --ssh-user-key=ssh_key I'll try to reproduce

[Bug 335472] Re: device-mapper: remove ioctl failed: Device or resource busy

2009-04-01 Thread Todd Deshane
I am seeing this too. I'll post the debug/verbose tail of the log as soon as it comes out. ** Changed in: vm-builder (Ubuntu) Status: New => Confirmed -- device-mapper: remove ioctl failed: Device or resource busy https://bugs.launchpad.net/bugs/335472 You received this bug notification

[Bug 352114] Re: vmbuilder: attempt to copy ssh key before user is created [Jaunty] [PATCH]

2009-04-01 Thread Todd Deshane
diff -u attached ** Attachment added: "diff-u-dapper.py" http://launchpadlibrarian.net/24652770/diff-u-dapper.py -- vmbuilder: attempt to copy ssh key before user is created [Jaunty] [PATCH] https://bugs.launchpad.net/bugs/352114 You received this bug notification because you are a member of

[Bug 351943] Re: ubuntu-xen-server installs, but complains that it needs Python 2.5 in Jaunty

2009-03-30 Thread Todd Deshane
There hasn't been a linux-xen kernel since 8.04, hardy. The hardy kernel should work fine for your Xen kernel though. The intrepid xen hypervisor was backpored to hardy see: http://bderzhavets.wordpress.com/2008/11/13/backport-intrepid-xen-33-hypervisor-at-ubuntu-hardy-dom0-2624-21-xen/ Maybe som

[Bug 352114] [NEW] vmbuilder: attempt to copy ssh key before user is created [Jaunty] [PATCH]

2009-03-30 Thread Todd Deshane
Public bug reported: The SSH key needs to be copied after the user is created. The following patch fixes the problem diff /usr/share/pyshared/VMBuilder/plugins/ubuntu/dapper.py /usr/share/pyshared/VMBuilder/plugins/ubuntu/dapper.py.orig 81,83d80 < logging.debug("Creating initial user")

[Bug 132256] Re: [Feature request] symlinks for hvmloader and qemu-dm

2008-12-19 Thread Todd Deshane
It probably is still a problem, since Ubuntu's upstream (Debian) doesn't (I don't think) fix it either for some reason. Manually making the symlinks or having the tools just be smart enough to handle it is acceptable for most people anyway. That is why it was considered a feature request and not