On Saturday, October 28, 2017 at 1:25:33 PM UTC-4, Filip Magic wrote:
> On 10/28/17 11:29, Foppe de Haan wrote:
> > On Saturday, October 28, 2017 at 11:27:36 AM UTC+2, Foppe de Haan wrote:
> >> On Saturday, October 28, 2017 at 9:49:19 AM UTC+2, Roy Bernat wrote:
> >>> On Friday, 27 October 2017 11:26:01 UTC-4, Outback Dingo  wrote:
> >>>> So we need updated docs or somethings broken...
> >>>>
> >>>> i copied the iso to /home/user from the AppVM tried to create an hvm
> >>>> appvm got a unrecognized argument... ok
> >>>> then tried without --hvm... seems ok.... however..... qvm-start
> >>>> results in a traceback....
> >>>>
> >>>> [dingo@dom0 ~]$ qvm-create BSD --hvm --label blue
> >>>> usage: qvm-create [-h] [--verbose] [--quiet] [--class CLS]
> >>>>                   [--property NAME=VALUE] [--pool VOLUME_NAME=POOL_NAME]
> >>>>                   [-P POOL_NAME] [--template VALUE] [--label VALUE]
> >>>>                   [--help-classes]
> >>>>                   [--root-copy-from FILENAME | --root-move-from FILENAME]
> >>>>                   [VMNAME]
> >>>> qvm-create: error: unrecognized arguments: --hvm
> >>>> [dingo@dom0 ~]$ qvm-create BSD  --label blue
> >>>> sudo qvm-start BSD 
> >>>> --cdrom=/home/dingo/FreeBSD-11.1-RELEASE-amd64-disc1.iso
> >>>> Traceback (most recent call last):
> >>>>   File "/bin/qvm-start", line 9, in <module>
> >>>>     load_entry_point('qubesadmin==4.0.9', 'console_scripts', 
> >>>> 'qvm-start')()
> >>>>   File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
> >>>> line 160, in main
> >>>>     drive_assignment = get_drive_assignment(args.app, args.drive)
> >>>>   File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
> >>>> line 98, in get_drive_assignment
> >>>>     backend_domain_name, ident = drive_str.split(':', 1)
> >>>> ValueError: not enough values to unpack (expected 2, got 1)
> >>>> [dingo@dom0 ~]$ qvm-start BSD
> >>>> --cdrom=/home/dingo/FreeBSD-11.1-RELEASE-amd64-disc1.iso
> >>>> Traceback (most recent call last):
> >>>>   File "/usr/bin/qvm-start", line 9, in <module>
> >>>>     load_entry_point('qubesadmin==4.0.9', 'console_scripts', 
> >>>> 'qvm-start')()
> >>>>   File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
> >>>> line 160, in main
> >>>>     drive_assignment = get_drive_assignment(args.app, args.drive)
> >>>>   File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
> >>>> line 98, in get_drive_assignment
> >>>>     backend_domain_name, ident = drive_str.split(':', 1)
> >>>> ValueError: not enough values to unpack (expected 2, got 1)
> >>>> [dingo@dom0 ~]$ qvm-start BSD
> >>>> --cdrom=/home/dingo/FreeBSD-11.1-RELEASE-amd64-disc1.iso
> >>>> Traceback (most recent call last):
> >>>>   File "/usr/bin/qvm-start", line 9, in <module>
> >>>>     load_entry_point('qubesadmin==4.0.9', 'console_scripts', 
> >>>> 'qvm-start')()
> >>>>   File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
> >>>> line 160, in main
> >>>>     drive_assignment = get_drive_assignment(args.app, args.drive)
> >>>>   File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
> >>>> line 98, in get_drive_assignment
> >>>>     backend_domain_name, ident = drive_str.split(':', 1)
> >>>> ValueError: not enough values to unpack (expected 2, got 1)
> >>>>
> >>>> [user@personal dom0]$
> >>> You dont need to use --hvm . it is the default in version 4. 
> >>> Regarding the cdrom i have also the same issue it seems that this switch 
> >>> has beed deprecated .....
> >>>
> >>>
> >>> Roy
> >> try qubes-vm-boot-from-device or qvm-start VMNAME --cdrom=VMNAME:/path ; 
> >> or use the interface from the second page of the VM settings GUI.
> > (Btw, if you type qvm-<tab><tab>, or qubes-<tab><tab>, bash spits out a 
> > list of commands starting with those characters; you can usually find the 
> > command you are looking for that way; beyond that, --help or 'man 
> > qvm-command' will also provide hints as to available switches, except in 
> > the case of qvm-pci currently.)
> >
> Is qubes-vm-boot-from-device working for you guys ? I'm not able to
> install any OS from ISO in StandaloneVM.

nope having the same issue here, it starts the VM then exits. Going to try a 
block device to see if that works.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/44a31819-112b-43ca-bf08-9466a2b7dbc7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to