Hi all, I''ve posted an updated version of VM-Tools. This version doesn''t have many user-visible changes but is almost a complete rewrite. VM-Tools is slowly become what it is intended to be, a small library that provides high level APIs for managing Xen with some example command line tools. This version includes a first pass at a library abstraction, a simple (and incomplete) Python binding using Pyrex, buffered console support, a virtual device abstraction (that''s designed to eventually support DSOs), and lots of bug fixes. This version still has some issues and I wouldn''t recommend using it for production use but it''s been used by a few people without any sort of data corruption. One of the things I''d really like to see is a standard higher-level library and virtual device layer that was used by all tools (vm-tools, Xend, etc.). What does everyone else think? Is the VM-Tools library too high level for use in something like Xend? As usually, I''d greatly appreciate any feedback on the tools/library. http://www.cs.utexas.edu/users/aliguori/vm-tools-0.0.2.tar.gz Regards, Anthony Liguori ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Anthony Liguori wrote:> Hi all, > > This version includes a first pass at a library abstraction, a simple > (and incomplete) Python binding using Pyrex, buffered console support, a > virtual device abstraction (that''s designed to eventually support DSOs), > and lots of bug fixes.Hopefully this will be a configure option, I would like to have tools that I can install and run without needing a python installation on the machine, and that I can run out of my ~bin or similar.> This version still has some issues and I wouldn''t recommend using it for > production use but it''s been used by a few people without any sort of > data corruption.I seem to have the following problems: 1) I can only mount disks read-only. 2) vm destroy leaves domains hanging in ''d-b---'' zombie-like state forever. Keep up the good work. Jacob ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Jacob Gorm Hansen wrote:> Hopefully this will be a configure option, I would like to have tools > that I can install and run without needing a python installation on the > machine, and that I can run out of my ~bin or similar.Yes, that''s the plan.> I seem to have the following problems: > > 1) I can only mount disks read-only.It currently defaults to read-only know. The previous default was read/write. I''m not sure why I changed that. At any rate, you have to add a '',w'' to the end of the block device option when calling vm-create. That''s not exposed in vm right now. It''s a pretty easy change to the vm script.> 2) vm destroy leaves domains hanging in ''d-b---'' zombie-like state > forever.Yes, this broke during the rewrite. It''s a little difficult to handling closing an xcs connection in an elegant way. If xcs doesn''t have it''s connection closed properly it never cleans up the domain. The domain doesn''t occupy any resources, it''s just annoying. I''m trying to operate on a weekly release schedule. I thought it was better to get another version out even though this problem still existed. I''m going to start a daily snapshot. The URL will be: http://www.cs.utexas.edu/users/aliguori/vm-tools-latest.tar.gz Expect a fix for #2 within the next day or two.> Keep up the good work.Thanks! Regards, Anthony Liguori> > Jacob > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xen-devel >-- Anthony Liguori anthony@codemonkey.ws ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On Sat, 19 Feb 2005, Anthony Liguori wrote:> Jacob Gorm Hansen wrote: > >> Hopefully this will be a configure option, I would like to have tools >> that I can install and run without needing a python installation on the >> machine, and that I can run out of my ~bin or similar. > > Yes, that''s the plan.no phython? sweet. I''ll try to give it a try tomorrow> http://www.cs.utexas.edu/users/aliguori/vm-tools-latest.tar.gz------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On Sat, 19 Feb 2005, Jacob Gorm Hansen wrote:> Hopefully this will be a configure option, I would like to have tools > that I can install and run without needing a python installation on the > machine, and that I can run out of my ~bin or similar.same here. We MUST have this for our Xen-bproc clusters. We''ll be testing these tools soon. ron ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On Sat, 19 Feb 2005, Anthony Liguori wrote:> http://www.cs.utexas.edu/users/aliguori/vm-tools-latest.tar.gzFWIW, I grabbed vm-tools-20050220, then I tried to run it with console output # vm-create -c /boot/vmlinuz-2.6.9-xenU -m 96 -C "/dev/hda1 ro" --attach-vif=aa:00:00:02:00:00 -B 0707:0301 vm-create: invalid option -- c Try `vm-create --help'' for more information. so I removed "-c" and tried again # losetup /dev/loop7 -o 131604480 /usr/src/cm/root/./suse-uml.img # ls -l /dev/loop7 /dev/hda1 brw-rw---- 1 root disk 3, 1 Dec 3 11:50 /dev/hda1 brw-rw---- 1 root disk 7, 7 Dec 3 11:50 /dev/loop7 # vm-create /boot/vmlinuz-2.6.9-xenU -m 96 -C "/dev/hda1 ro" --attach-vif=aa:00:00:02:00:00 -B 0707:0301 Configuring device VIRTUAL MEMORY ARRANGEMENT: Loaded kernel: c0100000->c03784e0 Init. ramdisk: c0379000->c0379000 Phys-Mach map: c0379000->c0391000 Page tables: c0391000->c0394000 Start info: c0394000->c0395000 Boot stack: c0395000->c0396000 TOTAL: c0000000->c0800000 ENTRY ADDRESS: c0100000 VCPUS: 1 # but I get no output # vm-list Name Status Memory Domain-0 -----r 256MB Domain-1 -s---- 96MB Domain-2 -s---- 96MB Domain-3 -s---- 96MB # vm-console 3 Opening console for Domain-3. Use Ctrl-] to exit. # ideas? ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Adam Sulmicki wrote:> FWIW, I grabbed vm-tools-20050220, then I tried to run it with console > outputGreat :-)> # vm-create -c /boot/vmlinuz-2.6.9-xenU -m 96 -C "/dev/hda1 ro" > --attach-vif=aa:00:00:02:00:00 -B 0707:0301 > vm-create: invalid option -- c > Try `vm-create --help'' for more information. > > so I removed "-c" and tried againYes. I removed support for ''-c'' in vm-create in favor of doing it at the vm script level. It just doesn''t make sense for vm-create to be exec() another process.> # losetup /dev/loop7 -o 131604480 /usr/src/cm/root/./suse-uml.img > # ls -l /dev/loop7 /dev/hda1 > brw-rw---- 1 root disk 3, 1 Dec 3 11:50 /dev/hda1 > brw-rw---- 1 root disk 7, 7 Dec 3 11:50 /dev/loop7 > > # vm-create /boot/vmlinuz-2.6.9-xenU -m 96 -C "/dev/hda1 ro" > --attach-vif=aa:00:00:02:00:00 -B 0707:0301You''re missing the "root=" part of the command line. It should be: # vm-create /boot/vmlinuz-2.6.9-xenU -m 96 -C "root=/dev/hda1 ro" --attach-vif=aa:00:00:02:00:00 -B 0707:0301> Configuring device > VIRTUAL MEMORY ARRANGEMENT: > Loaded kernel: c0100000->c03784e0 > Init. ramdisk: c0379000->c0379000 > Phys-Mach map: c0379000->c0391000 > Page tables: c0391000->c0394000 > Start info: c0394000->c0395000 > Boot stack: c0395000->c0396000 > TOTAL: c0000000->c0800000 > ENTRY ADDRESS: c0100000 > VCPUS: 1This means your system started up properly. While I do not like the fact that libxc dumps out to stdout a lot I have to admit it''s very useful :-)> # vm-list > Name Status Memory > Domain-0 -----r 256MB > Domain-1 -s---- 96MB > Domain-2 -s---- 96MB > Domain-3 -s---- 96MB > # vm-console 3 > Opening console for Domain-3. Use Ctrl-] to exit.I very recently fixed the buffering problems in vm-console. They probably didn''t make the last release. I''m planning on updating latest this evening. vm-console was accidently flushing the tty when it opened it up. The output you should be seeing is a VFS error from the kernel. Regards, -- Anthony Liguori anthony@codemonkey.ws ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
there was another problem that I realized once I went to home last night. I was using kernel from xen-2.x. once I changed the 2.6.9 to 2.6.10 it appers to boot # vm-create /boot/vmlinuz-2.6.10-xenU -m 96 -C "root=/dev/hda1 ro" --attach-vif=aa:00:00:02:00:00 -B 0707:0301 Configuring device VIRTUAL MEMORY ARRANGEMENT: Loaded kernel: c0100000->c03596c4 Init. ramdisk: c035a000->c035a000 Phys-Mach map: c035a000->c0372000 Page tables: c0372000->c0374000 Start info: c0374000->c0375000 Boot stack: c0375000->c0376000 TOTAL: c0000000->c0400000 ENTRY ADDRESS: c0100000 VCPUS: 1 # vm-console 5 Opening console for Domain-5. Use Ctrl-] to exit. Linux version 2.6.10-xenU (adam@redbull-ten) (gcc version 3.3.4 (pre 3.3.5 20040809)) #1 Fri Feb 18 15:37:30 MST 2005 [blah blah bah, fsck failed] Give root password for login: On Tue, 22 Feb 2005, Anthony Liguori wrote:> Adam Sulmicki wrote: > >> FWIW, I grabbed vm-tools-20050220, then I tried to run it with console >> output > > Great :-) > >> # vm-create -c /boot/vmlinuz-2.6.9-xenU -m 96 -C "/dev/hda1 ro" >> --attach-vif=aa:00:00:02:00:00 -B 0707:0301 >> vm-create: invalid option -- c >> Try `vm-create --help'' for more information. >> >> so I removed "-c" and tried again > > Yes. I removed support for ''-c'' in vm-create in favor of doing it at the vm > script level. It just doesn''t make sense for vm-create to be exec() another > process. > >> # losetup /dev/loop7 -o 131604480 /usr/src/cm/root/./suse-uml.img >> # ls -l /dev/loop7 /dev/hda1 >> brw-rw---- 1 root disk 3, 1 Dec 3 11:50 /dev/hda1 >> brw-rw---- 1 root disk 7, 7 Dec 3 11:50 /dev/loop7 >> >> # vm-create /boot/vmlinuz-2.6.9-xenU -m 96 -C "/dev/hda1 ro" >> --attach-vif=aa:00:00:02:00:00 -B 0707:0301 > > You''re missing the "root=" part of the command line. It should be: > > # vm-create /boot/vmlinuz-2.6.9-xenU -m 96 -C "root=/dev/hda1 ro" > --attach-vif=aa:00:00:02:00:00 -B 0707:0301 > >> Configuring device >> VIRTUAL MEMORY ARRANGEMENT: >> Loaded kernel: c0100000->c03784e0 >> Init. ramdisk: c0379000->c0379000 >> Phys-Mach map: c0379000->c0391000 >> Page tables: c0391000->c0394000 >> Start info: c0394000->c0395000 >> Boot stack: c0395000->c0396000 >> TOTAL: c0000000->c0800000 >> ENTRY ADDRESS: c0100000 >> VCPUS: 1 > > This means your system started up properly. While I do not like the fact > that libxc dumps out to stdout a lot I have to admit it''s very useful :-) > >> # vm-list >> Name Status Memory >> Domain-0 -----r 256MB >> Domain-1 -s---- 96MB >> Domain-2 -s---- 96MB >> Domain-3 -s---- 96MB >> # vm-console 3 >> Opening console for Domain-3. Use Ctrl-] to exit. > > I very recently fixed the buffering problems in vm-console. They probably > didn''t make the last release. I''m planning on updating latest this evening. > vm-console was accidently flushing the tty when it opened it up. The output > you should be seeing is a VFS error from the kernel. > > Regards, > >------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On Wednesday 23 February 2005 09:16, Adam Sulmicki wrote:> there was another problem that I realized once I went to home last night. > I was using kernel from xen-2.x. once I changed the 2.6.9 to 2.6.10 it > appers to boot > > # vm-create /boot/vmlinuz-2.6.10-xenU -m 96 -C "root=/dev/hda1 ro" > --attach-vif=aa:00:00:02:00:00 -B 0707:0301Try adding "w" to your block device, so: -B 0707:0301,w See if that helps. Thanks, Dan> Configuring device > VIRTUAL MEMORY ARRANGEMENT: > Loaded kernel: c0100000->c03596c4 > Init. ramdisk: c035a000->c035a000 > Phys-Mach map: c035a000->c0372000 > Page tables: c0372000->c0374000 > Start info: c0374000->c0375000 > Boot stack: c0375000->c0376000 > TOTAL: c0000000->c0400000 > ENTRY ADDRESS: c0100000 > VCPUS: 1 > # vm-console 5 > Opening console for Domain-5. Use Ctrl-] to exit. > Linux version 2.6.10-xenU (adam@redbull-ten) (gcc version 3.3.4 (pre 3.3.5 > 20040809)) #1 Fri Feb 18 15:37:30 MST 2005 > [blah blah bah, fsck failed] > Give root password for login: > > On Tue, 22 Feb 2005, Anthony Liguori wrote: > > Adam Sulmicki wrote: > >> FWIW, I grabbed vm-tools-20050220, then I tried to run it with console > >> output > > > > Great :-) > > > >> # vm-create -c /boot/vmlinuz-2.6.9-xenU -m 96 -C "/dev/hda1 ro" > >> --attach-vif=aa:00:00:02:00:00 -B 0707:0301 > >> vm-create: invalid option -- c > >> Try `vm-create --help'' for more information. > >> > >> so I removed "-c" and tried again > > > > Yes. I removed support for ''-c'' in vm-create in favor of doing it at the > > vm script level. It just doesn''t make sense for vm-create to be exec() > > another process. > > > >> # losetup /dev/loop7 -o 131604480 /usr/src/cm/root/./suse-uml.img > >> # ls -l /dev/loop7 /dev/hda1 > >> brw-rw---- 1 root disk 3, 1 Dec 3 11:50 /dev/hda1 > >> brw-rw---- 1 root disk 7, 7 Dec 3 11:50 /dev/loop7 > >> > >> # vm-create /boot/vmlinuz-2.6.9-xenU -m 96 -C "/dev/hda1 ro" > >> --attach-vif=aa:00:00:02:00:00 -B 0707:0301 > > > > You''re missing the "root=" part of the command line. It should be: > > > > # vm-create /boot/vmlinuz-2.6.9-xenU -m 96 -C "root=/dev/hda1 ro" > > --attach-vif=aa:00:00:02:00:00 -B 0707:0301 > > > >> Configuring device > >> VIRTUAL MEMORY ARRANGEMENT: > >> Loaded kernel: c0100000->c03784e0 > >> Init. ramdisk: c0379000->c0379000 > >> Phys-Mach map: c0379000->c0391000 > >> Page tables: c0391000->c0394000 > >> Start info: c0394000->c0395000 > >> Boot stack: c0395000->c0396000 > >> TOTAL: c0000000->c0800000 > >> ENTRY ADDRESS: c0100000 > >> VCPUS: 1 > > > > This means your system started up properly. While I do not like the fact > > that libxc dumps out to stdout a lot I have to admit it''s very useful :-) > > > >> # vm-list > >> Name Status Memory > >> Domain-0 -----r 256MB > >> Domain-1 -s---- 96MB > >> Domain-2 -s---- 96MB > >> Domain-3 -s---- 96MB > >> # vm-console 3 > >> Opening console for Domain-3. Use Ctrl-] to exit. > > > > I very recently fixed the buffering problems in vm-console. They > > probably didn''t make the last release. I''m planning on updating latest > > this evening. vm-console was accidently flushing the tty when it opened > > it up. The output you should be seeing is a VFS error from the kernel. > > > > Regards, > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xen-devel------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On Wed, 23 Feb 2005, Daniel Stekloff wrote:> On Wednesday 23 February 2005 09:16, Adam Sulmicki wrote: >> there was another problem that I realized once I went to home last night. >> I was using kernel from xen-2.x. once I changed the 2.6.9 to 2.6.10 it >> appers to boot >> >> # vm-create /boot/vmlinuz-2.6.10-xenU -m 96 -C "root=/dev/hda1 ro" >> --attach-vif=aa:00:00:02:00:00 -B 0707:0301> Try adding "w" to your block device, so: -B 0707:0301,w > See if that helps.yup, perfect! Thanks a lot! # vm-create /boot/vmlinuz-2.6.10-xenU -m 96 -C "root=/dev/hda1 ro" --attach-vif=aa:00:00:02:00:00 -B 0707:0301,w # vm-console 6 Opening console for Domain-6. Use Ctrl-] to exit. Linux version 2.6.10-xenU (adam@redbull-ten) [blah,blah] Welcome to SuSE Linux 9.2 (i586) - Kernel 2.6.10-xenU (tty1). linux login: ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel